@Xqnstyl: We don’t use a repository manager. The original (local) repository came from one developer’s machine and as new artifacts are needed, we have a couple of simple scripts that will fetch the artifact, its POM, the source if available and then add it to Perforce.

One key note is that we do not use Maven for performing a release. VMware has its own build and release process (which just happens to call `mvn package` at a particular step). We also haven’t adopted the process of revving individual modules in the project and having people depend on them. The versions are currently all in lockstep and you always depend on the current version (sadly).

So typically when work is done (even in a branch), it’s the code and the contents of the POM that change, not the version associated with it.

As for the Maven SCM support for Perforce, we don’t use it. All devs have the p4 client as well as P4WSAD on their systems to edit and submit changesets. Because we don’t use Maven to do releases, we haven’t had a need to try the plugin. From my cursory reading of the page you linked to, I don’t see another case that would be relevant to us.

ks

When I used Maven with Perforce in the past, we had to take great care when merging pom.xml files between branches. How do you handle merging pom.xml files between branches where you want the version to stay different, especially after performing a Maven release?

I see Perforce has a KB article on Maven integration: http://kb.perforce.com/?article=1023. What’s your take on it?

Cheers!