+1 (even I have no voice for voiting)
We have couple of changes, related to allow maven-scm better work with
remote repositories (as example of using such extensions - source browser in
http://www.emforge.org)
We are not able to incorporate our changes now - since project near to
release and it is
+1, new settings work for me!
Olivier Lamy wrote:
Hi,
The last release of maven-scm is now 14 months old.
I'd like to release maven-scm 1.1 which include two new providers git
and accurev and fix some issues.
We solved 41 issues :
http://jira.codehaus.org/secure/ReleaseNote.jspa?version=13984&
Hi,
The vote has passed with the following result :
+1 (binding) : evenisse, vsiveton, dfabulich, olamy
+1 (non binding) : nicolas, handyande
I will move artifacts to the central repo.
Thanks !
--
Olivier
+1
BTW 1.1.1 is planned in september and 1.2 later (no date schedule)
Cheers,
Vincent
2008/8/23 Olivier Lamy <[EMAIL PROTECTED]>:
> Hi,
> The last release of maven-scm is now 14 months old.
> I'd like to release maven-scm 1.1 which include two new providers git
> and accurev and fix some issues
struberg wrote:
>
>> And why you don't want to use this structure ?.
>
> I guess the main argument is that eclipse cannot nest projects, so there's
> no way to edit your parent pom (+ parent site, etc) with eclipse (instead
> you have to vi + svn commit on the command line).
>
> BUT: My gut f
struberg wrote:
>
> I assume this is also a problem within maven-scm-1.0, isn't?
> So releasing maven-scm-1.1 doesn't make it worse, and we should address
> this issue in 1.1.1
>
> Only my private opinion, but as someone already mentioned, if we wait for
> all errors to be fixed, then we'll ne
TECTED]> schrieb am Mo, 25.8.2008:
> Von: Olivier Lamy <[EMAIL PROTECTED]>
> Betreff: Why using flattened structure [was Re: [VOTE] Release Maven Scm 1.1
> (take 3)]
> An: scm-dev@maven.apache.org
> Datum: Montag, 25. August 2008, 10:29
> I change the subject because
ything released.
LieGrü,
strub
--- ChrisGWarp <[EMAIL PROTECTED]> schrieb am Mo, 25.8.2008:
> Von: ChrisGWarp <[EMAIL PROTECTED]>
> Betreff: Re: [VOTE] Release Maven Scm 1.1 (take 3)
> An: scm-dev@maven.apache.org
> Datum: Montag, 25. August 2008, 1:23
> -1
>
> Not
I change the subject because I don't see any link with the vote on the
scm release.
And why you don't want to use this structure ?.
--
Olivier
2008/8/25 ChrisGWarp <[EMAIL PROTECTED]>:
>
>
>
> Olivier Lamy wrote:
>>
>> Try :
>> svn co
>> http://svn.warpspeed.com.au/test-repos/FireDragon/branche
Olivier Lamy wrote:
>
> Try :
> svn co
> http://svn.warpspeed.com.au/test-repos/FireDragon/branches/olamy-test/
> FireDragon-olamy-test && cd FireDragon-olamy-test && mvn
> release:prepare release:perform -B
>
> I have build two releases with success here :
> http://svn.warpspeed.com.au/test-
Try :
svn co http://svn.warpspeed.com.au/test-repos/FireDragon/branches/olamy-test/
FireDragon-olamy-test && cd FireDragon-olamy-test && mvn
release:prepare release:perform -B
I have build two releases with success here :
http://svn.warpspeed.com.au/test-repos/FireDragon/tags/
HTH,
--
Olivier
2
Olivier Lamy wrote:
>
> I will play with your repo in a dedicated branch :
> http://svn.warpspeed.com.au/test-repos/FireDragon/branches/olamy-test/
>
Go for it! That is what it is there for.
-Chris
--
View this message in context:
http://www.nabble.com/-VOTE--Release-Maven-Scm-1.1-%28take
I will play with your repo in a dedicated branch :
http://svn.warpspeed.com.au/test-repos/FireDragon/branches/olamy-test/
--
Olivier
2008/8/25 ChrisGWarp <[EMAIL PROTECTED]>:
>
>
>
> Olivier Lamy wrote:
>>
>> Hi,
>> For me it's not a SCM issue !.
>> Don't use flat structure and it will works lik
Olivier Lamy wrote:
>
> Hi,
> For me it's not a SCM issue !.
> Don't use flat structure and it will works like a charm !
>
> Move all files which are in
> http://svn.warpspeed.com.au/test-repos/FireDragon/trunk/FireDragon/ to
> http://svn.warpspeed.com.au/test-repos/FireDragon/trunk/ (and chan
Hi,
For me it's not a SCM issue !.
Don't use flat structure and it will works like a charm !
Move all files which are in
http://svn.warpspeed.com.au/test-repos/FireDragon/trunk/FireDragon/ to
http://svn.warpspeed.com.au/test-repos/FireDragon/trunk/ (and change
all modules paths like FireDragonReso
+0
I want it to be released because of the Git integration but the SVN
issue (SCM-392) seems important as well.
- Imran
On Mon, Aug 25, 2008 at 5:23 AM, ChrisGWarp <[EMAIL PROTECTED]> wrote:
>
> -1
>
> Not until SCM-392 has been fixed. This is a critical issue for us.
>
> And I don't imagine tha
-1
Not until SCM-392 has been fixed. This is a critical issue for us.
And I don't imagine that it is that an uncommon a problem either.
http://jira.codehaus.org/browse/SCM-392
-Chris
--
View this message in context:
http://www.nabble.com/-VOTE--Release-Maven-Scm-1.1-%28take-3%29-tp19123852p
+1
Emmanuel
On Sat, Aug 23, 2008 at 8:23 PM, Olivier Lamy <[EMAIL PROTECTED]> wrote:
> Hi,
> The last release of maven-scm is now 14 months old.
> I'd like to release maven-scm 1.1 which include two new providers git
> and accurev and fix some issues.
>
> We solved 41 issues :
>
> http://jira.co
+1
Andy
On 23 Aug 2008, at 19:23, Olivier Lamy wrote:
Hi,
The last release of maven-scm is now 14 months old.
I'd like to release maven-scm 1.1 which include two new providers git
and accurev and fix some issues.
We solved 41 issues :
http://jira.codehaus.org/secure/ReleaseNote.jspa?version=1
+1
LieGrü,
strub
--- Olivier Lamy <[EMAIL PROTECTED]> schrieb am Sa, 23.8.2008:
> Von: Olivier Lamy <[EMAIL PROTECTED]>
> Betreff: [VOTE] Release Maven Scm 1.1 (take 3)
> An: "Maven Developers List" <[EMAIL PROTECTED]>, scm-dev@maven.apache.org
> Dat
Hi,
The last release of maven-scm is now 14 months old.
I'd like to release maven-scm 1.1 which include two new providers git
and accurev and fix some issues.
We solved 41 issues :
http://jira.codehaus.org/secure/ReleaseNote.jspa?version=13984&styleName=Html&projectId=10527&Create=Create
Staging
21 matches
Mail list logo
