Committing a tag doesn't make much sense, it can be pushed afterward. It's
just a flag on a commit ID.
Le 18 juil. 2013 00:27, sebb seb...@gmail.com a écrit :
On 17 July 2013 23:19, Julien Vermillard jvermill...@gmail.com wrote:
I think the main problem is maven release is pushing your
Thanks Jeff ! I think we should try it next time which should be soon in a
Milestone cycle.
Le 18 juil. 2013 00:31, Jeff MAURY jeffma...@jeffmaury.com a écrit :
The release plugin has a pushChanges flag for git which is true by default
for preserving compatibility but could be useful.
Jeff
On 17 July 2013 10:56, elecha...@apache.org wrote:
Updated Branches:
refs/heads/trunk 0d04eba45 - 84b2003fc
Revert [maven-release-plugin] prepare for next development iteration
This reverts commit 0d04eba4525ca85886c4a03acc20b444ff69a52d.
However trunk is now in an incorrect state, as
Le 7/17/13 2:21 PM, sebb a écrit :
On 17 July 2013 10:56, elecha...@apache.org wrote:
Updated Branches:
refs/heads/trunk 0d04eba45 - 84b2003fc
Revert [maven-release-plugin] prepare for next development iteration
This reverts commit 0d04eba4525ca85886c4a03acc20b444ff69a52d.
However
On 17 July 2013 13:26, Emmanuel Lécharny elecha...@gmail.com wrote:
Le 7/17/13 2:21 PM, sebb a écrit :
On 17 July 2013 10:56, elecha...@apache.org wrote:
Updated Branches:
refs/heads/trunk 0d04eba45 - 84b2003fc
Revert [maven-release-plugin] prepare for next development iteration
This
Le 7/17/13 3:00 PM, sebb a écrit :
On 17 July 2013 13:26, Emmanuel Lécharny elecha...@gmail.com wrote:
Le 7/17/13 2:21 PM, sebb a écrit :
On 17 July 2013 10:56, elecha...@apache.org wrote:
Updated Branches:
refs/heads/trunk 0d04eba45 - 84b2003fc
Revert [maven-release-plugin] prepare for
On 17 July 2013 15:19, Emmanuel Lécharny elecha...@gmail.com wrote:
Le 7/17/13 3:00 PM, sebb a écrit :
On 17 July 2013 13:26, Emmanuel Lécharny elecha...@gmail.com wrote:
Le 7/17/13 2:21 PM, sebb a écrit :
On 17 July 2013 10:56, elecha...@apache.org wrote:
Updated Branches:
Le 7/17/13 5:53 PM, sebb a écrit :
On 17 July 2013 15:19, Emmanuel Lécharny elecha...@gmail.com wrote:
Le 7/17/13 3:00 PM, sebb a écrit :
On 17 July 2013 13:26, Emmanuel Lécharny elecha...@gmail.com wrote:
Le 7/17/13 2:21 PM, sebb a écrit :
On 17 July 2013 10:56, elecha...@apache.org wrote:
On 17 July 2013 17:00, Emmanuel Lécharny elecha...@gmail.com wrote:
Le 7/17/13 5:53 PM, sebb a écrit :
On 17 July 2013 15:19, Emmanuel Lécharny elecha...@gmail.com wrote:
Le 7/17/13 3:00 PM, sebb a écrit :
On 17 July 2013 13:26, Emmanuel Lécharny elecha...@gmail.com wrote:
Le 7/17/13 2:21 PM,
Le 7/17/13 6:15 PM, sebb a écrit :
On 17 July 2013 17:00, Emmanuel Lécharny elecha...@gmail.com wrote:
Le 7/17/13 5:53 PM, sebb a écrit :
On 17 July 2013 15:19, Emmanuel Lécharny elecha...@gmail.com wrote:
With SVN the way I do it is:
We don't use SVN anymore.
I realise that.
Maybe Git
On 17 July 2013 23:19, Julien Vermillard jvermill...@gmail.com wrote:
I think the main problem is maven release is pushing your modification
when it could do all the work locally.
It's not possible to do it all locally. It must at least commit the
tag to be used for the release vote.
perhaps
The release plugin has a pushChanges flag for git which is true by default
for preserving compatibility but could be useful.
Jeff
On Thu, Jul 18, 2013 at 12:26 AM, sebb seb...@gmail.com wrote:
On 17 July 2013 23:19, Julien Vermillard jvermill...@gmail.com wrote:
I think the main problem is
12 matches
Mail list logo
