and keep pulling dependencies into user-local repo?

I am trying to get all of the artifacts the current project (and all its modules) produces in isolation to all of those it depends upon. Right now all I can do (AFAIK) is to configure a file://${dir} repo (externally setting the dir property so all children get the same thing) and then mvn deploy.

Maybe the install plugin could be updated to include an alternative location to install into? Probably installing to both (optionally the alt of course). Still need some way to root the dir though. Is there an easy way to find the root of a mulit-module project (as in the first one with out its parent actually living in ../pom.xml)?

The motivation is to use those exact artifacts on a dependent build, so there is continuity and direct cause/effect on chained builds. This is critical when the project builds are distributed and you want to correlate between them. With-out the correlation its not as easy to be precisely confident about effects one might have caused the other.

Would also be nice to give a list of other local repos to read from only which will take precedence to anything in the user-local cache and SNAPSHOTs... as in if there is a matching SNAPSHOT in one of those read-only repos it will always be used. And to top it all off... allowing this configuration to be put into a profiles.xml peer the the top-level pom and have it picked up by all children?

For now all I have figured to do was to have something external copy a set of dependency artifacts into the local cache. This works, but has some area of grey... for what the build will actually use. Can't really run it offline, as there could be an external dependency which was added, etc. So its a bit hackish :-(

Any ideas on how to streamline this in Maven? Updating the install plugin might work for half... but the local repo thingy sounds like it needs to live closer to the mvn core (prolly not something a plugin can do easily)?

--jason

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to