Anders Hammar wrote: > > I'd like to first stress the fact that an aggregating project and a parent > project is two different things... > Thanks a lot for clarification.
Anders Hammar wrote: > > After this lesson, back to your question. I would need to know what > resources you're trying to generate and what for, to say for sure if it's > the right way to do it. If you're creating some aggregating report then I > believe it's ok (have a look at the javadoc:aggregate). > Ok, so here a the dirty details. The main project is a Tibco project. Technology is not really relevant, but the point is that such a project can be used to develop/build several artifacts. Each artifact has its set of dependencies and they can be built independently. IDE used to create such a project is called a Tibco Designer and it manages global project dependencies (this set of dependencies is a union of its artifact dependencies or at least it can be so). We have developed a Maven plugin that can build each artifact based on its pom. Now we would like to be able to generate a dependency file for IDE based on the artifacts in a project. One thing that comes to mind is to make one artifact per project and this is actually a long term goal but "as is" situation is that we have several artifacts per project. Hope this clarifes. As to inheritance vs. aggregation we actually use both. Aggregation to build all artifacts in a project together (and actually we have further poms that aggregate projects together) and inheritance to share some configuration common for all artifacts in a project. One idea that I have now is to use iteration that Maven does over modules to make each artifact update the main project dependency file based on its own pom content. Greetings, Tomasz -- View this message in context: http://maven.40175.n5.nabble.com/How-to-collect-module-dependencies-in-a-Java-Mojo-in-a-parent-project-tp3381251p3381421.html Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
