Here's something that happens to me frequently. Goal: make a local release off the trunk of some FOSS thing that will be a while releasing a fix that I need.
Typical set of activities: 1: git svn clone 2: branch 3: edit poms, change version, scm paths, deploymentRepository 4: run release plugin #3 is rather a fiddly, error prone process. If, on top of this, I also want to make local changes and push them back, it's fiddly to sort out the purely local pom changes. All of this suggests two possible lines of country: 1) more fun in the version plugin to deal with scm and deployment. 2) some sort of a way to 'shadow' a POM with local changes instead of editing them in. Opinions? --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
