yes, it has already been improved in svn, but I suppose there is still room
for improvement
regards,
Hervé
Le lundi 22 août 2011, Vincent Siveton a écrit :
> Very cool Hervé and thanks for your efforts.
> If you have time, review the documentation!
>
> Cheers,
>
> Vincent
>
> 2011/8/21 Hervé
Very cool Hervé and thanks for your efforts.
If you have time, review the documentation!
Cheers,
Vincent
2011/8/21 Hervé BOUTEMY :
> Hi,
>
> I want to to make a release in a few days with what is actually done: there
> are a lot of new things.
>
> If anybody has something to add before the relea
Cool let's go.
I like the filter stuff to prevent having a too huge number displayed.
2011/8/21 Hervé BOUTEMY :
> Hi,
>
> I want to to make a release in a few days with what is actually done: there
> are a lot of new things.
>
> If anybody has something to add before the release, please tell.
>
>
Hi,
I want to to make a release in a few days with what is actually done: there
are a lot of new things.
If anybody has something to add before the release, please tell.
Regards,
Hervé
-
To unsubscribe, e-mail: dev-unsubscr..
I didn't realize how horrible this was until i attempted to stage the
apache pom. I emailed the infra team and i suggest others follow that
thread as well. IMO the apache svn is now fundamentally broken.
Dennis Lundberg wrote:
Brett Porter wrote:
You might need to report it to the infrastr
On 16-Apr-09, at 4:02 PM, Brett Porter wrote:
On 17/04/2009, at 4:10 AM, Dennis Lundberg wrote:
Brett Porter wrote:
You might need to report it to the infrastructure team.
However, since release:prepare picks up where it leaves off, if you
don't start over (keep release.properties) and run
Brett Porter wrote:
>
> On 17/04/2009, at 4:10 AM, Dennis Lundberg wrote:
>
>> Brett Porter wrote:
>>> You might need to report it to the infrastructure team.
>>>
>>> However, since release:prepare picks up where it leaves off, if you
>>> don't start over (keep release.properties) and run release
On 17/04/2009, at 4:10 AM, Dennis Lundberg wrote:
Brett Porter wrote:
You might need to report it to the infrastructure team.
However, since release:prepare picks up where it leaves off, if you
don't start over (keep release.properties) and run release:prepare
again, you should find that the
Thanks retrying the same command did the trick.
I ll finish the release process and call for a vote later.
Thanks.
Raphaël
2009/4/16 Dennis Lundberg
> Brett Porter wrote:
> > You might need to report it to the infrastructure team.
> >
> > However, since release:prepare picks up where it leave
Brett Porter wrote:
> You might need to report it to the infrastructure team.
>
> However, since release:prepare picks up where it leaves off, if you
> don't start over (keep release.properties) and run release:prepare
> again, you should find that the tag is created successfully after a
> period
I think there is some sync between the eu and us mirrors now. The mirror
you use is geoip'd so I don't think you can control which one you get.
Brett Porter wrote:
You might need to report it to the infrastructure team.
However, since release:prepare picks up where it leaves off, if you
don't
You might need to report it to the infrastructure team.
However, since release:prepare picks up where it leaves off, if you
don't start over (keep release.properties) and run release:prepare
again, you should find that the tag is created successfully after a
period in between.
- Brett
On
Hi folks,
Has anyone any idea on how to solve this issue?
Regards,
Raphaël
Le 15 avril 2009 20:07, Raphaël Piéroni a écrit :
> Hi follks,
>
> I retried with SVN 1.6.0 But it still fails with a behaviour that seems to
> confirm that s...@apache is lagging
> I dunno what to do next.
>
> Raphaël
Hi follks,
I retried with SVN 1.6.0 But it still fails with a behaviour that seems to
confirm that s...@apache is lagging
I dunno what to do next.
Raphaël
[INFO] Checking in modified POMs...
[INFO] Executing: /bin/sh -c cd /Users/raphaelpieroni/Projects/archetype &&
svn --non-interactive commit
I got a strange behaviour :
rollback the release, then i do :
macbook-pro-de-raphael-pieroni:archetype raphaelpieroni$ svn st
macbook-pro-de-raphael-pieroni:archetype raphaelpieroni$ svn up
svn: No such revision 764991
macbook-pro-de-raphael-pieroni:archetype raphaelpieroni$ svn up
At revision 764
Still fails even with subversion 1.5.0
[INFO] Checking in modified POMs...
[INFO] Executing: /bin/sh -c cd /Users/raphaelpieroni/Projects/archetype &&
svn --non-interactive commit --file /tmp/maven-scm-966248461.commit
--targets /tmp/maven-scm-20952-targets
[INFO] Working directory: /Users/raphael
Setting the plugin version in pluginmanagement didn't work
I have a wrong version of svn it seems
svn --version
svn, version 1.5.6 (r36142)
I try downgrading to 1.5.0
2009/4/14 Olivier Lamy
> Or you update maven-release-plugin version to 2.0-beta-9 .
>
>
> 2009/4/14 Arnaud HERITIER :
> > Or y
Or you update maven-release-plugin version to 2.0-beta-9 .
2009/4/14 Arnaud HERITIER :
> Or you have to use SVN 1.5.0 or 1.6.0 bianires. No 1.5.x.
> Arnaud
>
> On Tue, Apr 14, 2009 at 11:33 PM, Brian Fox wrote:
>
>> Raphaël Piéroni wrote:
>>
>>> Hi folks,
>>>
>>> I try to prepare the release of
Or you have to use SVN 1.5.0 or 1.6.0 bianires. No 1.5.x.
Arnaud
On Tue, Apr 14, 2009 at 11:33 PM, Brian Fox wrote:
> Raphaël Piéroni wrote:
>
>> Hi folks,
>>
>> I try to prepare the release of the next version of the archetype plugin,
>> but i fail.
>> The release plugin tell me it can't create
Raphaël Piéroni wrote:
Hi folks,
I try to prepare the release of the next version of the archetype plugin,
but i fail.
The release plugin tell me it can't create the tag.
I run mvn release:prepare -DdryRun=true without any problem,
but when i remove the dryRun, i got this exception :
[INFO] Ch
Hi folks,
I try to prepare the release of the next version of the archetype plugin,
but i fail.
The release plugin tell me it can't create the tag.
I run mvn release:prepare -DdryRun=true without any problem,
but when i remove the dryRun, i got this exception :
[INFO] Checking in modified POMs..
21 matches
Mail list logo