New ebuild for xdoclet 1.2.1. This is my first ebuild, so comments are welcome. Reproducible: Always Steps to Reproduce:
Created attachment 32197 [details] xdoclet-1.2.1.ebuild
Created attachment 32198 [details] xdoclet-1.2.1.ebuild Sorry, that was an old version. This is the right one.
This ebuild builds without error on amd64, provided ANT_OPT=-Xmx128m was added to the emerge command. It also fixed a bug from the 1.2.0-beta1 version that prevented xdoclet from building the jboss examples. (ClassNotFoundException for xdoclet.ejb.EjbDocletTask). Please get this into portage as soon as possible. Thanks for making the ebuild available so soon.
I missed this bug when adding my own update for xdoclet-1.2.1. I go over it again shortly
BTW, I found that allowing maven to execute caused several files to be downloaded from the internet automatically. This was easy to miss unless you go over the emerge output afterwards. I couldn't figure out how to prevent maven from doing this, so I disabled maven-related parts of the ebuild I included.
I did this two months ago, so I don't know what maven does :o) I will take a look at it, but it seems to me that maven was related to the documentation part of the ebuild. Anyway, there are more and more java projects adopting maven, and maven works that way, downloading missing dependencies to build the project. How is this going to be addressed by Gentoo? Maybe we could experiment with this ebuild?
Added ANT_OPT=-Xmx128m (thanks to Michael Labhard <m.labhard@comcast.net>, Bug #52249). You're right. Maven seems to be used to build the documentation. A maven plugin for XDoclet is also built. In the xdoclet-1.2.1.ebuild, I have disabled anything Maven related. As for how to deal with Maven; This question was discussed on the gentoo-java mailing lists. I dont think any concensus was reached. Everyone may be adopting Maven, but it is an atrocity when used within a ports system like ours. For now I'm dealing with it as I would any other security problem: disabling it. I may build the documentation locally and upload a .tar.bz2 to the master mirror at some point however.
