maven-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Kalle Korhonen <kalle.o.korho...@gmail.com>
Subject Re: Local Clone Helpfullness as a possible Maven Plugin
Date Wed, 02 Feb 2011 22:25:58 GMT
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 <bimargulies@gmail.com> 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: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org


Mime
View raw message