As far as I know, when you do a mvn install the new code from Module1
would be compiled and installed in the local repo as snapshot. After
that Module3 would use that snapshot to build. The package lifecycle is
just one step too early to fix the dependencies. Ofcourse, you have to
do the mvn install at the parent directory, otherwise the new snapshot
version wouldn't be build.
Hth,
Nick Stolwijk
mark_in_gr wrote:
I have a multi-module project which is basically structured like this:
parent(pom only)
---module1
---module2
---module3
Module3 has Module1 and Module2 as dependencies. My question is: if I make a
source code change in a class in Module1, I would like to simply to a
Build(package or install) at the Module3 Level without having to do a clean
first. Is this possible?
It looks like it is not. Unlike ant based projects I have worked with, it
appears that with Maven2, whether you use package(which would resolve the
Module1 dependency from the target directory) or install(which would take
Module1 from the local repo), the existing artifact for Module1, either the
target or local repo, is being used as a dependency when building(mvn
compile) Module3. The only way I can get maven to recognize source code
updates in Module1 is to first do a mvn clean . . . followed by package.
Bottom line . . . is there anyway to JUST build a modules dependency
artifact when compiling the parent module, without doing a clean first?
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
