Building a submodule and what it depends on -------------------------------------------- Key: JBBUILD-548 URL: https://jira.jboss.org/jira/browse/JBBUILD-548 Project: JBoss Build System Issue Type: Task Components: Sonatype Reporter: Paul Gier Assignee: Paul Gier The biggest issue is that we cannot seem to figure out how Maven is supposed to work when it comes to projects that consists of sub-modules. At least the workflow Maven 'defaults' to seem to make this construct very cumbersome to maintain. Example: -------------- In hibernate core we have a structure like this: trunk pom.xml parent pom.xml core pom.xml connection-c3p0 pom.xml <other modules> <pom.xml per module> Lets say we change something in the "core" module and I wan to go and check if connection-c3p0 has an issue with that. Our intuition says that one should be able to do: cd connection-c3p0 mvn compile But this will not cause core to be recompiled even though this module has a dependency on it and it should be possible for maven to deduce this needs to be compiled. Instead it goes to the local repo and check if something happend there - and no there didn't, we are just trying to do a compile check. On the blog someone mentioned reactor or the new -amd option, but doing the following: cd connection-c3p0 mvn -amd compile does not seem to change anything, even with a change in core nothing gets recompiled. What -amd does seem to do is the "opposite" direction. i.e. going to root and type mvn -am -pl core,connection-c3p0 compile does seem to do this - but why does the user have to tell Maven manually which dependencies it want built ? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira