2009/10/17 Nathan Bubna <[email protected]>: > On Fri, Oct 16, 2009 at 1:23 AM, Antonio Petrelli > <[email protected]> wrote: >> Sorry, overlapping jars? What are you referring to? > > We distribute three jars: velocity-tools-generic, > velocity-tools-view, and velocity-tools. the view jar contains the > generic classes and some additional ones, and the plain velocity-tools > jar includes the generic and view classes and some additional ones > (the struts integration). Three jars whose contents "overlap".
The the best choice is to modularize source code and then use the Maven Shade Plugin to create a "uber jar". However in this case I prefer the "modularize as much as possible" approach, i.e. creating very specific JARs with correct dependencies. In this case, the modules would be: tools-generic (depending on velocity) tools-view (depending on generic) tools-struts (depending on view and generic) Maven users will get the dependencies automatically resolved. Is it really necessary to create those "uber jars" after all? Is it so difficult to put three jars instead of one in the classpath? Note that it is possible with the Shade plugin, but it seems so useless to me. > Merely that the documentation for the three different parts (generic, > view, struts) is all interlinked; the struts docs link to view & > generic docs and view docs link to generic docs. There are two ways: * creating Javadocs for all the modules of a project (approach used by Tiles) * using the "detectOfflineLinks" parameter, that detects links between Javadocs sites: http://maven.apache.org/plugins/maven-javadoc-plugin/javadoc-mojo.html#detectOfflineLinks Note that you can even configure external links (e.g. if you want to link to Javadocs of Java itself, you can do it). Antonio --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
