Greetings -- Is there a best practices document describing maven's role in a multiproject environment?
One of the problems I'm currently trying to tackle is this: - internal components have dependencies to SNAPSHOT versions of other internal components. - after each project is compiled, it's SNAPSHOT artifact is created and 'installed' to the local repository (for use by other projects) - when the next project is compiled, it's dependencies are downloaded from the repository (overwriting the SNAPSHOT artifact that was created in the previous line item) I want to avoid deploying these artifacts to the remote repository until after it's determined that the entire multiproject build was successful. If anyone has a similar configuration, I'd be curious to hear how you're working around this. Thanks, -adrian- --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
