Jose Gonzalez Gomez wrote:
I understand that you're deploying your snapshot versions for your
projects in your internal repository, but I don't fully understand
your environment (or maybe Maven's way of working)... let me explain:
I understand that you can publish snapshot versions of artifacts under
development that are used across projects using a checked out source
tree of those artifacts. The problem comes when you have several
developers working on a project and using artifacts that are private
to that project, and where several developers may be changing the same
artifact (think of two different developers working on two different
EJBs in the same artifact, or two different parts of a web interface).
In this case you cannot publish that artifact until changes are
comitted, and every developer must use her own snapshot copy of the
artifact with her local changes that must be taken from her local
repository. It's in this case that I don't want those artifacts to be
taken from any other repository. How do you handle this, or how do you
configure Maven to tell that those artifacts should only be taken from
the developer local repository?
Jose, I think that one way to solve the problem that you have posed would be to expand the namespace used by individuals/teams for the development artifacts. If you and I are each making mutually exclusive changes to an artifact that we each call artifact-dev-SNAPSHOT.jar, then there is a serious problem, which you identified. If on the other hand, you call your artifact artifact-j-dev-SNAPSHOT.jar and I call my artifact artifact-a-dev-SNAPSHOT.jar, then each SNAPSHOT is qualified by owner. As long as each owner uses a unique name then there can be no problems. This naming convention allows the various teams to roll their changes stepwise into an artifact-dev-SNAPSHOT.jar at integration time, if that is desirable.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
