2010/12/8 fhomasp <[email protected]>: > I've been looking at the example of building a distribution with a > multimodule project > http://maven.apache.org/plugins/maven-assembly-plugin/examples/multimodule/module-binary-inclusion-simple.html > > At this point I made a new module which will assemble the folders with their > data in the correct structure. Now I want to build the whole distribution, > which brought me to the above quoted page. > > The problem is, how do I get the newly created release modules' assembly in > the distribution alongside with the dependencies in this distribution > assembly? I already got the dependencies as explained in the link above, > referencing an original jar (not the new assembly module). Because the new > assembly modules are in packaging pom... I could switch to jar there too, > but I'd have a jar included that is a dummy of some sort. > > I am thinking about excluding the jar, and also the original jar as well. > This is because the former is a dummy and the latter is already included in > the new assembly module, which might clash if it's twice on the classpath, > right?
This one of the reasons I told you to use a separate module, because you can include all the dependencies you need, filter them in assembly descriptors, include all the files you want, even in other modules (in Tiles we include sources from the other modules by accessing to the parent directory). I'm sorry so say it, but that link you posted is, essentially, worthless (in fact I wonder why it has not been removed yet). Antonio --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
