> Remember that maven always uses the version in the local repository. > So if module B depends on 1.0-SNAPSHOT of module A, and you change > something to module A, then you need to call jar:install on module A. > Otherwise module B will not see the changes.
Yeah, that's what multiproject does: call the artifact:install in order of dependencies. Here's the thing, if you're working online, it will always try to get the module A SNAPSHOT dependency that module B needs from the remote repository first, then fail over to the local repository because it's a SNAPSHOT. See what I mean? - Dave --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
