Hi Harald, first of all thanks for your help...
Harald Entner-3 wrote: > > m4 does not have any dependencies to its submodules (it just aggregates > them). That seemed to be not the full truth...if i try to supplemental define a dependency in my m4 module to make the dependency to m4.1 explicit... <dependencies> <dependency> <groupId>${project.groupId}</groupId> <artifactId>m4.1</artifactId> <version>${project.version}</version> </dependency> <dependency> I will get the following message: [INFO] ------------------------------------------------------------------------ [ERROR] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] The projects in the reactor contain a cyclic reference: Edge between 'Vertex{label='com.xyz.test.build:m4.1'}' and 'Vertex{label='com.xyz.test.build:m4.1'}' introduces to cycle in the graph com.xyz.test.build:m4.1 --> com.xyz.test.build:m4.1 That's indicating that the dependency has been inserted already... Harald Entner-3 wrote: > > so in order to build 3.2, it is sufficient that m4 is built first > (e.g. maven includes modules and dependencies defined in m4). In my opinion the dependencies of m4 should be built first...(m4.1...m4.5)... Harald Entner-3 wrote: > Does it built correctly if you delete your repository (at least the m* > entries? If it does, i don't see a problem, as it is still working that > way. Doesn't change anything in the order of the build.... Kind regards Karl Heinz Marbaise -- View this message in context: http://old.nabble.com/Dependencies-and-Aggregation-tp28214892p28215393.html Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org