Once JSilver will be deployed in the Maven Central repository
(http://code.google.com/p/jsilver/issues/detail?id=1) the Doclava build/deploy
can benefit as well of such improvement, so jsilver jar doesn't need anymore to
be imported and installed locally.
The attached patch contains the improvement for the pom and has to be applied
only after jsilver will be available.
Moreover minor metadata issues have been fixed:
* the scm urls were referring to the tag instead of the trunk
* the bootclasspath is available under sun.boot.class.path property that makes
the build portable
* the tools.jar dependency is already available in the Maven classpath, not
needed to be imported
Feel free to ping me whenever something goes wrong.
Original issue reported on code.google.com by simone.t...@gmail.com on 13 Nov 2010 at 11:33
Original issue reported on code.google.com by
simone.t...@gmail.com
on 13 Nov 2010 at 11:33Attachments: