On Fri, Oct 16, 2009 at 1:23 AM, Antonio Petrelli <[email protected]> wrote: > 2009/10/15 Nathan Bubna <[email protected]>: >> Separate from the example apps? Or just from the main artifact(s). > > From the main artifact, because it involves a specific web application > to be deployed. It could be included into another example app without > problem. > >> This is one of the "maven mysteries" to me: what would be the "Maven >> way" to organize our three overlapping jars and 3 example apps and >> conjoined documentation? > > 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". > About the example apps, there are two ways to make it work: > 1. separate them from the main distribution, under a pom-typed Maven > project with one module for each app. > 2. create a pom project that contains the main distribution and the > apps (eventually under another pom project) as modules. > > Tiles uses the second approach, though there is the "showcase" app > (not updated) separated from the rest. > > And what do you mean with conjoined documentation? 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. > Antonio > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
