Re: [VOTE] Release Maven Scm 1.1 (take 3)

2008-08-27 Thread Dan Fabulich

+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=13984styleName=HtmlprojectId=10527Create=Create

Staging repo: http://people.apache.org/~olamy/staging-repo/ .

Staging site: http://maven.apache.org/scm-1.1/ .

One more issue has been fixed since take 2 ([SCM-402] - scm:checkin
doesn't work on OS X 10.5 Leopard)

Vote open for 72 hours.

[ ] +1
[ ] +0
[ ] -1

Here my +1.

Thanks
--
Olivier

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]






Re: [VOTE] Release Maven Scm 1.1 (take 3)

2008-08-27 Thread Alexey Kakunin
+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 not make sense to include big changes. Releasing of 1.1
will allow us to start move our changes into 1.2 trunk



2008/8/27 Dan Fabulich [EMAIL PROTECTED]

 +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=13984styleName=HtmlprojectId=10527Create=Create

 Staging repo: 
 http://people.apache.org/~olamy/staging-repo/http://people.apache.org/%7Eolamy/staging-repo/.

 Staging site: http://maven.apache.org/scm-1.1/ .

 One more issue has been fixed since take 2 ([SCM-402] - scm:checkin
 doesn't work on OS X 10.5 Leopard)

 Vote open for 72 hours.

 [ ] +1
 [ ] +0
 [ ] -1

 Here my +1.

 Thanks
 --
 Olivier

 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]






-- 
With best regards,
Alexey Kakunin


Re: AW: Why using flattened structure [was Re: [VOTE] Release Maven Scm 1.1 (take 3)]

2008-08-26 Thread ChrisGWarp



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 feeling tells me that this is no maven-scm problem but a
 problem within the maven-release-plugin. Can anyone shed a light on this?
 
 So I agree with Chris that we should address this issue, but also with
 Olivier that this should not hinder us from releasing maven-scm.
 
 LieGrue,
 strub
 

Yes it is an eclipse related issue.

Yes this is occuring during a release:prepare, however, surely it must be
the SCM that is doing the commit? It is just being called internally by the
release plugin. Hence, an SCM issue.

-Chris

-- 
View this message in context: 
http://www.nabble.com/Why-using-flattened-structure--was-Re%3A--VOTE--Release-Maven-Scm-1.1-%28take-3%29--tp19139828p19158235.html
Sent from the Maven - SCM mailing list archive at Nabble.com.



Re: [VOTE] Release Maven Scm 1.1 (take 3)

2008-08-25 Thread Olivier Lamy
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 moduleFireDragonResources/module )


Cheers,
--
Olivier

2008/8/25 ChrisGWarp [EMAIL PROTECTED]:

 -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-tp19123852p19135931.html
 Sent from the Maven - SCM mailing list archive at Nabble.com.




Re: [VOTE] Release Maven Scm 1.1 (take 3)

2008-08-25 Thread ChrisGWarp



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 change
 all modules paths like moduleFireDragonResources/module )
 

Ie, make it a nested, non flat structure.

I find statements such as these both niave and arrogant and all together
unhelpful. 

For it presumes a few things.

1. That the existing structure can indeed be changed. In some cases it may
be able to be changed, in others it certainly will not.
2. Subclipse will not cope with this structure (having projects overlap)
3. It does not fix the issue (which is a real one), it simply ignores it.

Looking at the dates from the Subversion issue (2007) it has been around for
a while.Their point of view is that it is a maven bug in that it is maven
that fails to deal with a known issue. I can see their point.

The fact of the matter is that Maven supports non nested directory
structures, and so should the plugins.

The SCM/subversion modules must be able to cater for this situation, it is
not an uncommon one.Whilst it may be a hack to commit each project
separately, it (to me at least, and from what I can read others as well) an
acceptable workaround.

Perhaps there should be an option to use SVNKit, as that does handle this
situation.

-Chris

-- 
View this message in context: 
http://www.nabble.com/-VOTE--Release-Maven-Scm-1.1-%28take-3%29-tp19123852p19138633.html
Sent from the Maven - SCM mailing list archive at Nabble.com.



Re: [VOTE] Release Maven Scm 1.1 (take 3)

2008-08-25 Thread ChrisGWarp



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-3%29-tp19123852p19138719.html
Sent from the Maven - SCM mailing list archive at Nabble.com.



Re: [VOTE] Release Maven Scm 1.1 (take 3)

2008-08-25 Thread Olivier Lamy
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

2008/8/25 ChrisGWarp [EMAIL PROTECTED]:



 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-3%29-tp19123852p19138719.html
 Sent from the Maven - SCM mailing list archive at Nabble.com.




Re: [VOTE] Release Maven Scm 1.1 (take 3)

2008-08-25 Thread Mark Struberg
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 never get anything 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 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-tp19123852p19135931.html
 Sent from the Maven - SCM mailing list archive at
 Nabble.com.

__
Do You Yahoo!?
Sie sind Spam leid? Yahoo! Mail verfügt über einen herausragenden Schutz gegen 
Massenmails. 
http://mail.yahoo.com


Re: [VOTE] Release Maven Scm 1.1 (take 3)

2008-08-24 Thread Andrew Williams

+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=13984styleName=HtmlprojectId=10527Create=Create

Staging repo: http://people.apache.org/~olamy/staging-repo/ .

Staging site: http://maven.apache.org/scm-1.1/ .

One more issue has been fixed since take 2 ([SCM-402] - scm:checkin
doesn't work on OS X 10.5 Leopard)

Vote open for 72 hours.

[ ] +1
[ ] +0
[ ] -1

Here my +1.

Thanks
--
Olivier





Re: [VOTE] Release Maven Scm 1.1 (take 3)

2008-08-24 Thread ChrisGWarp

-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-tp19123852p19135931.html
Sent from the Maven - SCM mailing list archive at Nabble.com.



Re: [VOTE] Release Maven Scm 1.1 (take 3)

2008-08-24 Thread Imran M Yousuf
+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 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-tp19123852p19135931.html
 Sent from the Maven - SCM mailing list archive at Nabble.com.





-- 
Imran M Yousuf
Entrepreneur  Software Engineer
Smart IT Engineering
Dhaka, Bangladesh
Email: [EMAIL PROTECTED]
Blog: http://imyousuf-tech.blogs.smartitengineering.com/
Mobile: +880-1711402557