I would appreciate any suggestions on how to handle the local repository when there are multiple copies of the same project on the file system, ultimately wanting to install jars there.
To go into more detail: I have a 'superproject', consisting of around 10 subprojects. Ideally each of these is a maven project which produces some artifact (jar, war, ear, etc.). There are dependencies between them, so each does an install of the artifact to the local repo (and the whole thing is build with the reactor). Now once in a while, it is relatively common that I may have to pull out another copy of the whole superproject to somewhere else on the filesystem, to play around with something without affecting work in progress in the main location. Obviously experimental work can sometimes be handled with branches, but sometimes it is simply more convenient to have multiple versions on the filesystem that are each able to build. In this case, if I am producing the same version of the same artifacts (e.g. xxx-1.0-dev.whatever) they will interfere with each other when they are installed (uploaded) to the local repo. One way I can think of handling this is to have multiple local repos. A different repo would be used for each instance of the superproject. I would still want a backup local repo where other common jars are found, and I believe I can do this by stacking repos. Another way I can think of doing this is to not use the local repo to handle dependencies between the projects, but only as a source of external jars. The project dependencies would use an override to look for the jars in the target directory of the other projects. Can anybody comment on this or offer any suggestions? Regards, Colin -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
