For a simple 'just-a-jar' project, that's fine. If I need some stuff from someone's release profile .. The local change case is probably more compelling.
On Wed, Feb 2, 2011 at 5:25 PM, Kalle Korhonen <[email protected]> wrote: > Why do you need to re-release? I typically checkout/clone, build, edit > the pom directly and change the version to > <existingversion>-<mycompany>-1, then take both the pom and the > (snapshot) library and deploy them to Nexus. > > Kalle > > > On Wed, Feb 2, 2011 at 2:17 PM, Benson Margulies <[email protected]> > wrote: >> 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: [email protected] >> For additional commands, e-mail: [email protected] >> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
