subject:"RE\: \[VOTE\] Release Maven 2.0.7"



On 15 Jun 07, at 4:58 AM 15 Jun 07, Andrew Williams wrote:

Am I the only one getting a test failure on IT0002 with the 2.0.7  
bundle?


junit.framework.AssertionFailedError: Expected file was not found: / 
Users/aje/.m2/repository/org/apache/maven/its/maven-core-it-support/ 
1.0/maven-core-it-support-1.0.jar


(yes, I did install the maven-core-it-support - but seems that / 
Users/aje/.m2/repository/org/apache/maven/its/maven-core-it- 
support/ does not exist)




You have to install all the support plugins and artifacts, and  
someone seems to have broke the invoker which installs the support  
artifacts. But once it's installed the ITs are fine.


I added the tiny script I used here:

http://svn.apache.org/repos/asf/maven/core-integration-testing/trunk/ 
core-integration-testing-support/


John, might you take a look? Maybe fix the invoker and release it?


Andy

On 13 Jun 2007, at 06:12, Jason van Zyl wrote:


Hi,

The release notes are here:

http://jira.codehaus.org/secure/ReleaseNote.jspa? 
projectId=10500styleName=Htmlversion=13138


The tag is here:

http://svn.apache.org/repos/asf/maven/components/tags/maven-2.0.7/

Staging repository:

http://people.apache.org/~jvanzyl/maven-2.0.7-staging-repository/

And the distros you are interested in are here:

http://people.apache.org/~jvanzyl/maven-2.0.7/

Thanks,

Jason.



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



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




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




Thanks,

Jason

--
Jason van Zyl
Founder and PMC Chair, Apache Maven
jason at sonatype dot com
--




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

Re: [VOTE] Release Maven 2.0.7



On 15 Jun 07, at 5:36 AM 15 Jun 07, Brian E. Fox wrote:


Where are we on the 2.0.7 vote? It seems like there are some issues
requiring a new RC such as licenses and notices, but I've lost track.
The original RC was technically ok on my builds.



I've updated them all, the licenses are fixed. This was with the  
source distribution so I just remade it, I didn't rebuild. I already  
fixed and closed the issues Brett was having and that I rebuilt and  
redeployed on Wednesday. Everything is still fine.



-Original Message-
From: Mark Hobson [mailto:[EMAIL PROTECTED]
Sent: Friday, June 15, 2007 8:01 AM
To: Maven Developers List
Subject: Re: [VOTE] Release Maven 2.0.7

On 15/06/07, Andrew Williams [EMAIL PROTECTED] wrote:

Am I the only one getting a test failure on IT0002 with the 2.0.7
bundle?

junit.framework.AssertionFailedError: Expected file was not found: /
Users/aje/.m2/repository/org/apache/maven/its/maven-core-it-support/
1.0/maven-core-it-support-1.0.jar

(yes, I did install the maven-core-it-support - but seems that / 
Users/

aje/.m2/repository/org/apache/maven/its/maven-core-it-support/ does
not exist)


Nope, I get it too - see my mail to dev regarding r546719.

Mark

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


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




Thanks,

Jason

--
Jason van Zyl
Founder and PMC Chair, Apache Maven
jason at sonatype dot com
--




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

RE: [VOTE] Release Maven 2.0.7

2007-06-15 Thread Brian E. Fox

Where are we on the 2.0.7 vote? It seems like there are some issues
requiring a new RC such as licenses and notices, but I've lost track.
The original RC was technically ok on my builds.

-Original Message-
From: Mark Hobson [mailto:[EMAIL PROTECTED] 
Sent: Friday, June 15, 2007 8:01 AM
To: Maven Developers List
Subject: Re: [VOTE] Release Maven 2.0.7

On 15/06/07, Andrew Williams [EMAIL PROTECTED] wrote:
 Am I the only one getting a test failure on IT0002 with the 2.0.7
 bundle?

 junit.framework.AssertionFailedError: Expected file was not found: /
 Users/aje/.m2/repository/org/apache/maven/its/maven-core-it-support/
 1.0/maven-core-it-support-1.0.jar

 (yes, I did install the maven-core-it-support - but seems that /Users/
 aje/.m2/repository/org/apache/maven/its/maven-core-it-support/ does
 not exist)

Nope, I get it too - see my mail to dev regarding r546719.

Mark

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

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

Re: [VOTE] Release Maven 2.0.7

2007-06-15 Thread Andrew Williams

Am I the only one getting a test failure on IT0002 with the 2.0.7  
bundle?


junit.framework.AssertionFailedError: Expected file was not found: / 
Users/aje/.m2/repository/org/apache/maven/its/maven-core-it-support/ 
1.0/maven-core-it-support-1.0.jar


(yes, I did install the maven-core-it-support - but seems that /Users/ 
aje/.m2/repository/org/apache/maven/its/maven-core-it-support/ does  
not exist)


Andy

On 13 Jun 2007, at 06:12, Jason van Zyl wrote:


Hi,

The release notes are here:

http://jira.codehaus.org/secure/ReleaseNote.jspa? 
projectId=10500styleName=Htmlversion=13138


The tag is here:

http://svn.apache.org/repos/asf/maven/components/tags/maven-2.0.7/

Staging repository:

http://people.apache.org/~jvanzyl/maven-2.0.7-staging-repository/

And the distros you are interested in are here:

http://people.apache.org/~jvanzyl/maven-2.0.7/

Thanks,

Jason.



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



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




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

Re: [VOTE] Release Maven 2.0.7

Can we restart the vote once this is sorted out? I have no idea which  
svn rev we are voting on any more, or who checked and voted for which.


- Brett

On 15/06/2007, at 10:56 PM, Brian E. Fox wrote:


Ok, the last one I tested was Wed night. In that case +1.


-Original Message-
From: Jason van Zyl [mailto:[EMAIL PROTECTED]
Sent: Friday, June 15, 2007 8:53 AM
To: Maven Developers List
Subject: Re: [VOTE] Release Maven 2.0.7


On 15 Jun 07, at 5:36 AM 15 Jun 07, Brian E. Fox wrote:


Where are we on the 2.0.7 vote? It seems like there are some issues
requiring a new RC such as licenses and notices, but I've lost track.
The original RC was technically ok on my builds.



I've updated them all, the licenses are fixed. This was with the
source distribution so I just remade it, I didn't rebuild. I already
fixed and closed the issues Brett was having and that I rebuilt and
redeployed on Wednesday. Everything is still fine.


-Original Message-
From: Mark Hobson [mailto:[EMAIL PROTECTED]
Sent: Friday, June 15, 2007 8:01 AM
To: Maven Developers List
Subject: Re: [VOTE] Release Maven 2.0.7

On 15/06/07, Andrew Williams [EMAIL PROTECTED] wrote:

Am I the only one getting a test failure on IT0002 with the 2.0.7
bundle?

junit.framework.AssertionFailedError: Expected file was not found: /
Users/aje/.m2/repository/org/apache/maven/its/maven-core-it-support/
1.0/maven-core-it-support-1.0.jar

(yes, I did install the maven-core-it-support - but seems that /
Users/
aje/.m2/repository/org/apache/maven/its/maven-core-it-support/ does
not exist)


Nope, I get it too - see my mail to dev regarding r546719.

Mark

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


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




Thanks,

Jason

--
Jason van Zyl
Founder and PMC Chair, Apache Maven
jason at sonatype dot com
--




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


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


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

Re: [VOTE] Release Maven 2.0.7



On 15 Jun 07, at 6:09 AM 15 Jun 07, Brett Porter wrote:

Can we restart the vote once this is sorted out? I have no idea  
which svn rev we are voting on any more, or who checked and voted  
for which.




It is sorted out, I was planning on releasing it today. What's the  
problem?



- Brett

On 15/06/2007, at 10:56 PM, Brian E. Fox wrote:


Ok, the last one I tested was Wed night. In that case +1.


-Original Message-
From: Jason van Zyl [mailto:[EMAIL PROTECTED]
Sent: Friday, June 15, 2007 8:53 AM
To: Maven Developers List
Subject: Re: [VOTE] Release Maven 2.0.7


On 15 Jun 07, at 5:36 AM 15 Jun 07, Brian E. Fox wrote:


Where are we on the 2.0.7 vote? It seems like there are some issues
requiring a new RC such as licenses and notices, but I've lost  
track.

The original RC was technically ok on my builds.



I've updated them all, the licenses are fixed. This was with the
source distribution so I just remade it, I didn't rebuild. I already
fixed and closed the issues Brett was having and that I rebuilt and
redeployed on Wednesday. Everything is still fine.


-Original Message-
From: Mark Hobson [mailto:[EMAIL PROTECTED]
Sent: Friday, June 15, 2007 8:01 AM
To: Maven Developers List
Subject: Re: [VOTE] Release Maven 2.0.7

On 15/06/07, Andrew Williams [EMAIL PROTECTED] wrote:

Am I the only one getting a test failure on IT0002 with the 2.0.7
bundle?

junit.framework.AssertionFailedError: Expected file was not  
found: /
Users/aje/.m2/repository/org/apache/maven/its/maven-core-it- 
support/

1.0/maven-core-it-support-1.0.jar

(yes, I did install the maven-core-it-support - but seems that /
Users/
aje/.m2/repository/org/apache/maven/its/maven-core-it-support/ does
not exist)


Nope, I get it too - see my mail to dev regarding r546719.

Mark

 
-

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


 
-

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




Thanks,

Jason

--
Jason van Zyl
Founder and PMC Chair, Apache Maven
jason at sonatype dot com
--




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


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


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




Thanks,

Jason

--
Jason van Zyl
Founder and PMC Chair, Apache Maven
jason at sonatype dot com
--




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

Re: [VOTE] Release Maven 2.0.7

2007-06-15 Thread Andrew Williams


Thanks, that script does sort it for me :)
Andy

On 15 Jun 2007, at 13:55, Jason van Zyl wrote:



On 15 Jun 07, at 4:58 AM 15 Jun 07, Andrew Williams wrote:

Am I the only one getting a test failure on IT0002 with the 2.0.7  
bundle?


junit.framework.AssertionFailedError: Expected file was not  
found: /Users/aje/.m2/repository/org/apache/maven/its/maven-core- 
it-support/1.0/maven-core-it-support-1.0.jar


(yes, I did install the maven-core-it-support - but seems that / 
Users/aje/.m2/repository/org/apache/maven/its/maven-core-it- 
support/ does not exist)




You have to install all the support plugins and artifacts, and  
someone seems to have broke the invoker which installs the support  
artifacts. But once it's installed the ITs are fine.


I added the tiny script I used here:

http://svn.apache.org/repos/asf/maven/core-integration-testing/ 
trunk/core-integration-testing-support/


John, might you take a look? Maybe fix the invoker and release it?


Andy

On 13 Jun 2007, at 06:12, Jason van Zyl wrote:


Hi,

The release notes are here:

http://jira.codehaus.org/secure/ReleaseNote.jspa? 
projectId=10500styleName=Htmlversion=13138


The tag is here:

http://svn.apache.org/repos/asf/maven/components/tags/maven-2.0.7/

Staging repository:

http://people.apache.org/~jvanzyl/maven-2.0.7-staging-repository/

And the distros you are interested in are here:

http://people.apache.org/~jvanzyl/maven-2.0.7/

Thanks,

Jason.



 
-

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



 
-

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




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




Thanks,

Jason

--
Jason van Zyl
Founder and PMC Chair, Apache Maven
jason at sonatype dot com
--




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




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

Re: [VOTE] Release Maven 2.0.7



On 15/06/2007, at 11:27 PM, Jason van Zyl wrote:



On 15 Jun 07, at 6:09 AM 15 Jun 07, Brett Porter wrote:

Can we restart the vote once this is sorted out? I have no idea  
which svn rev we are voting on any more,


We're voting on the tag used to build the releases.


Which has been changed since most people voted.




or who checked and voted for which.


I haven't changed the location of what people have tried. We will  
start the vote again over the weekend and no one will look at it.  
So if we're going to do that then we should start again on Monday.


Not really following your logic here... I think it's fine to restart  
it now if the bundle is done, get the 3 votes you need and wait  
another 72 hours.


However, as far as I can tell it's not yet ready for that - the  
staging repository does not match the release artifacts as Max reported.


I'm positive we all agreed in the past that if a vote got stalled due  
to a problem that is corrected that the vote would be restarted, the  
tag (and staging binaries) deleted, and the release re-done to  
minimise the risk of any errors slipping through.


Thanks,
Brett

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

Re: [VOTE] Release Maven 2.0.7



On 15 Jun 07, at 6:09 AM 15 Jun 07, Brett Porter wrote:

Can we restart the vote once this is sorted out? I have no idea  
which svn rev we are voting on any more,


We're voting on the tag used to build the releases.


or who checked and voted for which.


I haven't changed the location of what people have tried. We will  
start the vote again over the weekend and no one will look at it. So  
if we're going to do that then we should start again on Monday.




- Brett

On 15/06/2007, at 10:56 PM, Brian E. Fox wrote:


Ok, the last one I tested was Wed night. In that case +1.


-Original Message-
From: Jason van Zyl [mailto:[EMAIL PROTECTED]
Sent: Friday, June 15, 2007 8:53 AM
To: Maven Developers List
Subject: Re: [VOTE] Release Maven 2.0.7


On 15 Jun 07, at 5:36 AM 15 Jun 07, Brian E. Fox wrote:


Where are we on the 2.0.7 vote? It seems like there are some issues
requiring a new RC such as licenses and notices, but I've lost  
track.

The original RC was technically ok on my builds.



I've updated them all, the licenses are fixed. This was with the
source distribution so I just remade it, I didn't rebuild. I already
fixed and closed the issues Brett was having and that I rebuilt and
redeployed on Wednesday. Everything is still fine.


-Original Message-
From: Mark Hobson [mailto:[EMAIL PROTECTED]
Sent: Friday, June 15, 2007 8:01 AM
To: Maven Developers List
Subject: Re: [VOTE] Release Maven 2.0.7

On 15/06/07, Andrew Williams [EMAIL PROTECTED] wrote:

Am I the only one getting a test failure on IT0002 with the 2.0.7
bundle?

junit.framework.AssertionFailedError: Expected file was not  
found: /
Users/aje/.m2/repository/org/apache/maven/its/maven-core-it- 
support/

1.0/maven-core-it-support-1.0.jar

(yes, I did install the maven-core-it-support - but seems that /
Users/
aje/.m2/repository/org/apache/maven/its/maven-core-it-support/ does
not exist)


Nope, I get it too - see my mail to dev regarding r546719.

Mark

 
-

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


 
-

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




Thanks,

Jason

--
Jason van Zyl
Founder and PMC Chair, Apache Maven
jason at sonatype dot com
--




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


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


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




Thanks,

Jason

--
Jason van Zyl
Founder and PMC Chair, Apache Maven
jason at sonatype dot com
--




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

Re: [VOTE] Release Maven 2.0.7



On 15 Jun 07, at 6:52 AM 15 Jun 07, Brett Porter wrote:



On 15/06/2007, at 11:27 PM, Jason van Zyl wrote:



On 15 Jun 07, at 6:09 AM 15 Jun 07, Brett Porter wrote:

Can we restart the vote once this is sorted out? I have no idea  
which svn rev we are voting on any more,


We're voting on the tag used to build the releases.


Which has been changed since most people voted.




or who checked and voted for which.


I haven't changed the location of what people have tried. We will  
start the vote again over the weekend and no one will look at it.  
So if we're going to do that then we should start again on Monday.


Not really following your logic here... I think it's fine to  
restart it now if the bundle is done, get the 3 votes you need and  
wait another 72 hours.


It's not fine, no one will look at it. If it's going up for a vote it  
means that people need to look at it again and run it with their  
builds. What's the point in just gather 3 votes to satisfy policy? If  
we put it up for a vote again then we start the whole process again.




However, as far as I can tell it's not yet ready for that - the  
staging repository does not match the release artifacts as Max  
reported.


I'm positive we all agreed in the past that if a vote got stalled  
due to a problem that is corrected that the vote would be  
restarted, the tag (and staging binaries) deleted, and the release  
re-done to minimise the risk of any errors slipping through.


Then I will do the process again on Sunday and put it up for a vote  
on Monday so that people present during the week can check the  
binaries again. And we'll shoot for next Wednesday as the release.




Thanks,
Brett

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




Thanks,

Jason

--
Jason van Zyl
Founder and PMC Chair, Apache Maven
jason at sonatype dot com
--




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

Re: [VOTE] Release Maven 2.0.7

This vote is cancelled and will be re-instated on Monday. I will re- 
stage as fast as I can so that anyone who wants to check can. But  
doing a vote over the weekend has traditionally not yielded a decent  
enough set of people trying things so we'll shoot for next Wednesday.  
Schedule updated in the wiki.


On 12 Jun 07, at 10:12 PM 12 Jun 07, Jason van Zyl wrote:


Hi,

The release notes are here:

http://jira.codehaus.org/secure/ReleaseNote.jspa? 
projectId=10500styleName=Htmlversion=13138


The tag is here:

http://svn.apache.org/repos/asf/maven/components/tags/maven-2.0.7/

Staging repository:

http://people.apache.org/~jvanzyl/maven-2.0.7-staging-repository/

And the distros you are interested in are here:

http://people.apache.org/~jvanzyl/maven-2.0.7/

Thanks,

Jason.



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



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




Thanks,

Jason

--
Jason van Zyl
Founder and PMC Chair, Apache Maven
jason at sonatype dot com
--




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

RE: [VOTE] Release Maven 2.0.7

2007-06-15 Thread Jörg Schaible

Folks,

I have a weird problem with this release. In a multi-project setup is one of my 
submodules failing, because the surefire plugin is missing classes in the class 
path when install is invoked from above. install works fine from the sub 
project level though. Now the really weirtd part: I can run test from the top 
level and then the test in the submodule succeeds, the classpath is right! It 
seems only bogus during install ?!? I already tried to strip down an example, 
but I was not able to reproduce this in a simpler setup so far. :-/

I fear this may also impact the release process :(

- surefire-plugin is fixed to version 2.3
- works for M2.0.5
- cannot verify with M2.0.6, build fails because of MNG-2919 earlier (at least 
this is fixed now)

- Jörg



Jason van Zyl wrote on Wednesday, June 13, 2007 7:13 AM:

 Hi,
 
 The release notes are here:
 
 http://jira.codehaus.org/secure/ReleaseNote.jspa?
 projectId=10500styleName=Htmlversion=13138
 
 The tag is here:
 
 http://svn.apache.org/repos/asf/maven/components/tags/maven-2.0.7/
 
 Staging repository:
 
 http://people.apache.org/~jvanzyl/maven-2.0.7-staging-repository/
 
 And the distros you are interested in are here:
 
 http://people.apache.org/~jvanzyl/maven-2.0.7/
 
 Thanks,
 
 Jason.
 
 
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 
 
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]

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

Re: [VOTE] Release Maven 2.0.7

Yup, I'm certainly not going to complain about a 5 day vote to cover  
the weekend.


Cheers,
Brett

On 16/06/2007, at 12:05 AM, Jason van Zyl wrote:



On 15 Jun 07, at 6:52 AM 15 Jun 07, Brett Porter wrote:



On 15/06/2007, at 11:27 PM, Jason van Zyl wrote:



On 15 Jun 07, at 6:09 AM 15 Jun 07, Brett Porter wrote:

Can we restart the vote once this is sorted out? I have no idea  
which svn rev we are voting on any more,


We're voting on the tag used to build the releases.


Which has been changed since most people voted.




or who checked and voted for which.


I haven't changed the location of what people have tried. We will  
start the vote again over the weekend and no one will look at it.  
So if we're going to do that then we should start again on Monday.


Not really following your logic here... I think it's fine to  
restart it now if the bundle is done, get the 3 votes you need and  
wait another 72 hours.


It's not fine, no one will look at it. If it's going up for a vote  
it means that people need to look at it again and run it with their  
builds. What's the point in just gather 3 votes to satisfy policy?  
If we put it up for a vote again then we start the whole process  
again.




However, as far as I can tell it's not yet ready for that - the  
staging repository does not match the release artifacts as Max  
reported.


I'm positive we all agreed in the past that if a vote got stalled  
due to a problem that is corrected that the vote would be  
restarted, the tag (and staging binaries) deleted, and the release  
re-done to minimise the risk of any errors slipping through.


Then I will do the process again on Sunday and put it up for a vote  
on Monday so that people present during the week can check the  
binaries again. And we'll shoot for next Wednesday as the release.




Thanks,
Brett

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




Thanks,

Jason

--
Jason van Zyl
Founder and PMC Chair, Apache Maven
jason at sonatype dot com
--




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


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

Re: [VOTE] Release Maven 2.0.7



On 15 Jun 07, at 7:22 AM 15 Jun 07, Jörg Schaible wrote:


Folks,

I have a weird problem with this release. In a multi-project setup  
is one of my submodules failing, because the surefire plugin is  
missing classes in the class path when install is invoked from  
above. install works fine from the sub project level though. Now  
the really weirtd part: I can run test from the top level and  
then the test in the submodule succeeds, the classpath is right! It  
seems only bogus during install ?!? I already tried to strip down  
an example, but I was not able to reproduce this in a simpler setup  
so far. :-/


I fear this may also impact the release process :(

- surefire-plugin is fixed to version 2.3
- works for M2.0.5
- cannot verify with M2.0.6, build fails because of MNG-2919  
earlier (at least this is fixed now)




The process is already stopped. You have to give me a sample project  
if you want me to look at anything. It will go up for a vote on Monday.



- Jörg



Jason van Zyl wrote on Wednesday, June 13, 2007 7:13 AM:


Hi,

The release notes are here:

http://jira.codehaus.org/secure/ReleaseNote.jspa?
projectId=10500styleName=Htmlversion=13138

The tag is here:

http://svn.apache.org/repos/asf/maven/components/tags/maven-2.0.7/

Staging repository:

http://people.apache.org/~jvanzyl/maven-2.0.7-staging-repository/

And the distros you are interested in are here:

http://people.apache.org/~jvanzyl/maven-2.0.7/

Thanks,

Jason.



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



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


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




Thanks,

Jason

--
Jason van Zyl
Founder and PMC Chair, Apache Maven
jason at sonatype dot com
--




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

Re: [VOTE] Release Maven 2.0.7

2007-06-15 Thread Andrew Williams

I just noticed that the dav deploy is still broken (as in 2.0.6 I  
think) not a new problem, just checking folk were aware.


Andy

On 15 Jun 2007, at 14:17, Jason van Zyl wrote:



On 15 Jun 07, at 6:09 AM 15 Jun 07, Brett Porter wrote:

Can we restart the vote once this is sorted out? I have no idea  
which svn rev we are voting on any more, or who checked and voted  
for which.




It is sorted out, I was planning on releasing it today. What's the  
problem?



- Brett

On 15/06/2007, at 10:56 PM, Brian E. Fox wrote:


Ok, the last one I tested was Wed night. In that case +1.


-Original Message-
From: Jason van Zyl [mailto:[EMAIL PROTECTED]
Sent: Friday, June 15, 2007 8:53 AM
To: Maven Developers List
Subject: Re: [VOTE] Release Maven 2.0.7


On 15 Jun 07, at 5:36 AM 15 Jun 07, Brian E. Fox wrote:


Where are we on the 2.0.7 vote? It seems like there are some issues
requiring a new RC such as licenses and notices, but I've lost  
track.

The original RC was technically ok on my builds.



I've updated them all, the licenses are fixed. This was with the
source distribution so I just remade it, I didn't rebuild. I already
fixed and closed the issues Brett was having and that I rebuilt and
redeployed on Wednesday. Everything is still fine.


-Original Message-
From: Mark Hobson [mailto:[EMAIL PROTECTED]
Sent: Friday, June 15, 2007 8:01 AM
To: Maven Developers List
Subject: Re: [VOTE] Release Maven 2.0.7

On 15/06/07, Andrew Williams [EMAIL PROTECTED] wrote:

Am I the only one getting a test failure on IT0002 with the 2.0.7
bundle?

junit.framework.AssertionFailedError: Expected file was not  
found: /
Users/aje/.m2/repository/org/apache/maven/its/maven-core-it- 
support/

1.0/maven-core-it-support-1.0.jar

(yes, I did install the maven-core-it-support - but seems that /
Users/
aje/.m2/repository/org/apache/maven/its/maven-core-it-support/  
does

not exist)


Nope, I get it too - see my mail to dev regarding r546719.

Mark

--- 
--

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


--- 
--

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




Thanks,

Jason

--
Jason van Zyl
Founder and PMC Chair, Apache Maven
jason at sonatype dot com
--




 
-

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


 
-

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


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




Thanks,

Jason

--
Jason van Zyl
Founder and PMC Chair, Apache Maven
jason at sonatype dot com
--




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




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

Re: [VOTE] Release Maven 2.0.7



On 15/06/2007, at 11:27 PM, Jason van Zyl wrote:



On 15 Jun 07, at 6:09 AM 15 Jun 07, Brett Porter wrote:

Can we restart the vote once this is sorted out? I have no idea  
which svn rev we are voting on any more,


We're voting on the tag used to build the releases.


Which has been changed since most people voted.




or who checked and voted for which.


I haven't changed the location of what people have tried. We will  
start the vote again over the weekend and no one will look at it.  
So if we're going to do that then we should start again on Monday.


Not really following your logic here... I think it's fine to restart  
it now if the bundle is done, get the 3 votes you need and wait  
another 72 hours.


However, as far as I can tell it's not yet ready for that - the  
staging repository does not match the release artifacts as Max reported.


I'm positive we all agreed in the past that if a vote got stalled due  
to a problem that is corrected that the vote would be restarted, the  
tag (and staging binaries) deleted, and the release re-done to  
minimise the risk of any errors slipping through.


Thanks,
Brett

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



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

RE: [VOTE] Release Maven 2.0.7

2007-06-15 Thread Jörg Schaible

Jason van Zyl wrote on Friday, June 15, 2007 4:28 PM:

 On 15 Jun 07, at 7:22 AM 15 Jun 07, Jörg Schaible wrote:
 
 Folks,
 
 I have a weird problem with this release. In a multi-project setup
 is one of my submodules failing, because the surefire plugin is
 missing classes in the class path when install is invoked from
 above. install works fine from the sub project level though. Now
 the really weirtd part: I can run test from the top level and
 then the test in the submodule succeeds, the classpath is right! It
 seems only bogus during install ?!? I already tried to strip down
 an example, but I was not able to reproduce this in a simpler setup
 so far. :-/ 
 
 I fear this may also impact the release process :(
 
 - surefire-plugin is fixed to version 2.3
 - works for M2.0.5
 - cannot verify with M2.0.6, build fails because of MNG-2919
 earlier (at least this is fixed now)
 
 
 The process is already stopped. You have to give me a sample project
 if you want me to look at anything.

Since I am leaving office quite soon, this is unfortunately more or less a 
simple heads-up just in case someone else runs into the same problem. I don't 
know what triggers the behaviour. Any kind of simplified setup worked for me. 
I'd loved to find an example setup ...

- Jörg

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

Re: [VOTE] Release Maven 2.0.7


regrettably -1:

- http://people.apache.org/~jvanzyl/maven-2.0.7-staging-repository/ 
maven-2.0.7/org/apache/maven/maven/2.0.7/maven-2.0.7.pom contains  
2.0.7-SNAPSHOT as the maven version and that will result in  
dependencies from the repository will cause failures.


- I get loader constraints trying to build anything with the site  
descriptor attached (eg surefire root, or the plugins root), which  
does not occur on 2.0.6 or earlier) - filing in JIRA now.


- we still have that test failure, though it only occurs on the  
solaris server (even in a clean env) - we should probably check other  
operating systems to see if this is a map ordering problem


Cheers,
Brett

On 13/06/2007, at 3:12 PM, Jason van Zyl wrote:


Hi,

The release notes are here:

http://jira.codehaus.org/secure/ReleaseNote.jspa? 
projectId=10500styleName=Htmlversion=13138


The tag is here:

http://svn.apache.org/repos/asf/maven/components/tags/maven-2.0.7/

Staging repository:

http://people.apache.org/~jvanzyl/maven-2.0.7-staging-repository/

And the distros you are interested in are here:

http://people.apache.org/~jvanzyl/maven-2.0.7/

Thanks,

Jason.



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



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


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

Re: [VOTE] Release Maven 2.0.7



On 13 Jun 07, at 11:20 PM 13 Jun 07, Brett Porter wrote:


regrettably -1:

- http://people.apache.org/~jvanzyl/maven-2.0.7-staging-repository/ 
maven-2.0.7/org/apache/maven/maven/2.0.7/maven-2.0.7.pom contains  
2.0.7-SNAPSHOT as the maven version and that will result in  
dependencies from the repository will cause failures.




Yah, Kenney already noticed this. It can be fixed in the stage and  
won't hurt anything.


- I get loader constraints trying to build anything with the site  
descriptor attached (eg surefire root, or the plugins root), which  
does not occur on 2.0.6 or earlier) - filing in JIRA now.




I'll verify and report, assign to 2.0.7 so I see it.

- we still have that test failure, though it only occurs on the  
solaris server (even in a clean env) - we should probably check  
other operating systems to see if this is a map ordering problem




I've run on OS X, Windows and Fedora without problem. You sure it's  
not just Continuum or did you bootstrap from a normal user account  
and run them?



Cheers,
Brett

On 13/06/2007, at 3:12 PM, Jason van Zyl wrote:


Hi,

The release notes are here:

http://jira.codehaus.org/secure/ReleaseNote.jspa? 
projectId=10500styleName=Htmlversion=13138


The tag is here:

http://svn.apache.org/repos/asf/maven/components/tags/maven-2.0.7/

Staging repository:

http://people.apache.org/~jvanzyl/maven-2.0.7-staging-repository/

And the distros you are interested in are here:

http://people.apache.org/~jvanzyl/maven-2.0.7/

Thanks,

Jason.



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



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


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




Thanks,

Jason

--
Jason van Zyl
Founder and PMC Chair, Apache Maven
jason at sonatype dot com
--




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

Re: [VOTE] Release Maven 2.0.7



On 13 Jun 07, at 11:20 PM 13 Jun 07, Brett Porter wrote:


regrettably -1:

- http://people.apache.org/~jvanzyl/maven-2.0.7-staging-repository/ 
maven-2.0.7/org/apache/maven/maven/2.0.7/maven-2.0.7.pom contains  
2.0.7-SNAPSHOT as the maven version and that will result in  
dependencies from the repository will cause failures.


- I get loader constraints trying to build anything with the site  
descriptor attached (eg surefire root, or the plugins root), which  
does not occur on 2.0.6 or earlier) - filing in JIRA now.




I just ran site and site:attach-descriptor in surefire root and I  
can't reproduce. Can someone else try deploying some sites using site  
descriptor attach? Update surefire and try to deploy the site.


- we still have that test failure, though it only occurs on the  
solaris server (even in a clean env) - we should probably check  
other operating systems to see if this is a map ordering problem


Cheers,
Brett

On 13/06/2007, at 3:12 PM, Jason van Zyl wrote:


Hi,

The release notes are here:

http://jira.codehaus.org/secure/ReleaseNote.jspa? 
projectId=10500styleName=Htmlversion=13138


The tag is here:

http://svn.apache.org/repos/asf/maven/components/tags/maven-2.0.7/

Staging repository:

http://people.apache.org/~jvanzyl/maven-2.0.7-staging-repository/

And the distros you are interested in are here:

http://people.apache.org/~jvanzyl/maven-2.0.7/

Thanks,

Jason.



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



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


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




Thanks,

Jason

--
Jason van Zyl
Founder and PMC Chair, Apache Maven
jason at sonatype dot com
--




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

Re: [VOTE] Release Maven 2.0.7

2007-06-14 Thread Julien HENRY

IMHO it should be fixed before 2.0.7. If not, the
release process will be broken (the scm tag will be
done even if something goes wrong during the build).

--- Brett Porter [EMAIL PROTECTED] a écrit :

 It's possibly a problem in the windows batch file in
 2.0.7 - I think  
 it was changed and it may no longer be correctly
 propogating the  
 error code.
 
 - Brett
 
 On 14/06/2007, at 1:07 AM, Jason van Zyl wrote:
 
  Is this not a release plugin problem?
 
  If this error halted your build, was this with an
 older version of  
  the release plugin?
 
  On 13 Jun 07, at 8:01 AM 13 Jun 07, Julien HENRY
 wrote:
 
  (non-binding) -1
 
  I just tried to prepare a release in a
 multi-module
  project. Usually, the release:prepare failed
 (because
  Maven does not find released dependent artifact).
 An
  easy fix was to run
  mvn install
  and then
  mvn release:prepare
  again.
 
  The problem I have with maven-2.0.7 is release
  preparation was not stopped (build is
 successful). The
  exception was ignored, and the release is not
 safe
  (what happend when it is a serious error?)
 
  Here is the log :
 
  [INFO] [release:prepare]
  [INFO] Verifying that there are no local
  modifications...
  [INFO] Executing: svn --non-interactive status
  [INFO] Working directory: 
  [INFO] Checking dependencies and plugins for
 snapshots
  ...
  What is the release version for XXX?
 (X)
  3.0.11: :
  What is the release version for ?
  () 3.0.11: :
  ...
  What is SCM release tag or label for X?
  (X) xx-3.0.11: :
  What is the new development version for
 XXX?
  (X) 3.0.12-SNAPSHOT: :
  What is the new development version for
  ? (YY)
 3.0.12-SNAPSHOT:
  :
  ...
  [INFO] Transforming 'XXX'...
  [INFO] Transforming 'YYY'...
  ...
  [INFO] Executing preparation goals 'clean
  integration-test'...
  [INFO] Executing: mvn clean integration-test
  --no-plugin-updates
  [INFO] Scanning for projects...
  [INFO] Reactor build order:
  [INFO]   X
  [INFO]   Y
  [INFO]   ...
  [INFO]
 

-
 
  ---
  [INFO] Building 
  [INFO]task-segment: [clean,
 integration-test]
  [INFO]
 

-
 
  ---
  [INFO] [clean:clean]
  
  [INFO]
 

-
 
  ---
  [INFO] Building YYY
  [INFO]task-segment: [clean,
 integration-test]
  [INFO]
 

-
 
  ---
  [INFO] [clean:clean]
  ...
  [INFO] [resources:resources]
  [INFO] Using default encoding to copy
 filtered
  resources.
  [INFO] [compiler:compile]
  [INFO] No sources to compile
  [INFO] [resources:testResources]
  [INFO] Using default encoding to copy
 filtered
  resources.
  [INFO] [compiler:testCompile]
  [INFO] No sources to compile
  [INFO] [surefire:test]
  [INFO] No tests to run.
  [INFO] [war:war]
  [INFO] Exploding webapp...
  [INFO] Assembling webapp YYY in
 

D:\Projets\xxx\target\YY-3.0.11
  [INFO] Copy webapp webResources to
  D:\Projets\xx\target 
  \YY-3.0.11
  [INFO]
 

-
 
  ---
  [ERROR] FATAL ERROR
  [INFO]
 

-
 
  ---
  [INFO] basedir C:\Documents and
 
 Settings\jhenry\.m2\repository\xxx 
  \YY\3.0.11
  does not exist
  [INFO]
 

-
 
  ---
  [INFO] Trace
  java.lang.IllegalStateException: basedir
  C:\Documents and
 

Settings\jhenry\.m2\repository\x\Y
 
  \3.0.11
  does not
  exist
  at
  org.codehaus.plexus.util.DirectoryScanner.scan 
  (DirectoryScanner.java:542)
  at
 

org.apache.maven.plugin.war.AbstractWarMojo.getWarFiles
 
  (AbstractWarMojo.java:824)
  at
 

org.apache.maven.plugin.war.AbstractWarMojo.copyResources
 
  (AbstractWarMojo.java:408)
  at
 

org.apache.maven.plugin.war.AbstractWarMojo.buildWebapp
 
  (AbstractWarMojo.java:518)
  at
 

org.apache.maven.plugin.war.AbstractWarMojo.buildExplodedWebapp
 
  (AbstractWarMojo.java:347)
  at
 

org.apache.maven.plugin.war.WarMojo.performPackaging(WarMojo.java:
 
  164)
  at
 

org.apache.maven.plugin.war.WarMojo.execute(WarMojo.java:130)
  at
 

org.apache.maven.plugin.DefaultPluginManager.executeMojo
 
  (DefaultPluginManager.java:443)
  at

Re: [VOTE] Release Maven 2.0.7

All fixed. Running a battery of checks now but the change is very  
small and I know it has been working in the form it is now because I  
only changed it about 8 days ago when trying to get rid of a class of  
problems as the one found in the jbi-components build. I don't think  
this needs revote.


All the new stuff is here:

http://people.apache.org/~jvanzyl/

On 13 Jun 07, at 11:20 PM 13 Jun 07, Brett Porter wrote:


regrettably -1:

- http://people.apache.org/~jvanzyl/maven-2.0.7-staging-repository/ 
maven-2.0.7/org/apache/maven/maven/2.0.7/maven-2.0.7.pom contains  
2.0.7-SNAPSHOT as the maven version and that will result in  
dependencies from the repository will cause failures.


- I get loader constraints trying to build anything with the site  
descriptor attached (eg surefire root, or the plugins root), which  
does not occur on 2.0.6 or earlier) - filing in JIRA now.


- we still have that test failure, though it only occurs on the  
solaris server (even in a clean env) - we should probably check  
other operating systems to see if this is a map ordering problem


Cheers,
Brett

On 13/06/2007, at 3:12 PM, Jason van Zyl wrote:


Hi,

The release notes are here:

http://jira.codehaus.org/secure/ReleaseNote.jspa? 
projectId=10500styleName=Htmlversion=13138


The tag is here:

http://svn.apache.org/repos/asf/maven/components/tags/maven-2.0.7/

Staging repository:

http://people.apache.org/~jvanzyl/maven-2.0.7-staging-repository/

And the distros you are interested in are here:

http://people.apache.org/~jvanzyl/maven-2.0.7/

Thanks,

Jason.



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



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


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




Thanks,

Jason

--
Jason van Zyl
Founder and PMC Chair, Apache Maven
jason at sonatype dot com
--




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

Re: [VOTE] Release Maven 2.0.7



On 14 Jun 07, at 12:48 AM 14 Jun 07, Julien HENRY wrote:


IMHO it should be fixed before 2.0.7. If not, the
release process will be broken (the scm tag will be
done even if something goes wrong during the build).



You tried with these:

http://people.apache.org/~jvanzyl/maven-2.0.7/

And you've tried the 2.0-beta-4 version of the release plugin?



--- Brett Porter [EMAIL PROTECTED] a écrit :


It's possibly a problem in the windows batch file in
2.0.7 - I think
it was changed and it may no longer be correctly
propogating the
error code.

- Brett

On 14/06/2007, at 1:07 AM, Jason van Zyl wrote:


Is this not a release plugin problem?

If this error halted your build, was this with an

older version of

the release plugin?

On 13 Jun 07, at 8:01 AM 13 Jun 07, Julien HENRY

wrote:



(non-binding) -1

I just tried to prepare a release in a

multi-module

project. Usually, the release:prepare failed

(because

Maven does not find released dependent artifact).

An

easy fix was to run

mvn install

and then

mvn release:prepare

again.

The problem I have with maven-2.0.7 is release
preparation was not stopped (build is

successful). The

exception was ignored, and the release is not

safe

(what happend when it is a serious error?)

Here is the log :

[INFO] [release:prepare]
[INFO] Verifying that there are no local
modifications...
[INFO] Executing: svn --non-interactive status
[INFO] Working directory: 
[INFO] Checking dependencies and plugins for

snapshots

...
What is the release version for XXX?

(X)

3.0.11: :
What is the release version for ?
() 3.0.11: :
...
What is SCM release tag or label for X?
(X) xx-3.0.11: :
What is the new development version for

XXX?

(X) 3.0.12-SNAPSHOT: :
What is the new development version for
? (YY)

3.0.12-SNAPSHOT:

:
...
[INFO] Transforming 'XXX'...
[INFO] Transforming 'YYY'...
...
[INFO] Executing preparation goals 'clean
integration-test'...
[INFO] Executing: mvn clean integration-test
--no-plugin-updates
[INFO] Scanning for projects...
[INFO] Reactor build order:
[INFO]   X
[INFO]   Y
[INFO]   ...
[INFO]




-



---
[INFO] Building 
[INFO]task-segment: [clean,

integration-test]

[INFO]




-



---
[INFO] [clean:clean]

[INFO]




-



---
[INFO] Building YYY
[INFO]task-segment: [clean,

integration-test]

[INFO]




-



---
[INFO] [clean:clean]
...
[INFO] [resources:resources]
[INFO] Using default encoding to copy

filtered

resources.
[INFO] [compiler:compile]
[INFO] No sources to compile
[INFO] [resources:testResources]
[INFO] Using default encoding to copy

filtered

resources.
[INFO] [compiler:testCompile]
[INFO] No sources to compile
[INFO] [surefire:test]
[INFO] No tests to run.
[INFO] [war:war]
[INFO] Exploding webapp...
[INFO] Assembling webapp YYY in




D:\Projets\xxx\target\YY-3.0.11

[INFO] Copy webapp webResources to
D:\Projets\xx\target
\YY-3.0.11
[INFO]




-



---
[ERROR] FATAL ERROR
[INFO]




-



---
[INFO] basedir C:\Documents and


Settings\jhenry\.m2\repository\xxx

\YY\3.0.11
does not exist
[INFO]




-



---
[INFO] Trace
java.lang.IllegalStateException: basedir
C:\Documents and




Settings\jhenry\.m2\repository\x\Y



\3.0.11
does not
exist
at
org.codehaus.plexus.util.DirectoryScanner.scan
(DirectoryScanner.java:542)
at




org.apache.maven.plugin.war.AbstractWarMojo.getWarFiles



(AbstractWarMojo.java:824)
at




org.apache.maven.plugin.war.AbstractWarMojo.copyResources



(AbstractWarMojo.java:408)
at




org.apache.maven.plugin.war.AbstractWarMojo.buildWebapp



(AbstractWarMojo.java:518)
at




org.apache.maven.plugin.war.AbstractWarMojo.buildExplodedWebapp



(AbstractWarMojo.java:347)
at




org.apache.maven.plugin.war.WarMojo.performPackaging(WarMojo.java:



164)
at




org.apache.maven.plugin.war.WarMojo.execute(WarMojo.java:130)

at




org.apache.maven.plugin.DefaultPluginManager.executeMojo



(DefaultPluginManager.java:443)
at

Re: [VOTE] Release Maven 2.0.7


Do we need to reopen an issue that this originally fixed?

I'll close 3055 after testing.

- Brett

On 14/06/2007, at 5:54 PM, Jason van Zyl wrote:

All fixed. Running a battery of checks now but the change is very  
small and I know it has been working in the form it is now because  
I only changed it about 8 days ago when trying to get rid of a  
class of problems as the one found in the jbi-components build. I  
don't think this needs revote.


All the new stuff is here:

http://people.apache.org/~jvanzyl/

On 13 Jun 07, at 11:20 PM 13 Jun 07, Brett Porter wrote:


regrettably -1:

- http://people.apache.org/~jvanzyl/maven-2.0.7-staging-repository/ 
maven-2.0.7/org/apache/maven/maven/2.0.7/maven-2.0.7.pom contains  
2.0.7-SNAPSHOT as the maven version and that will result in  
dependencies from the repository will cause failures.


- I get loader constraints trying to build anything with the site  
descriptor attached (eg surefire root, or the plugins root), which  
does not occur on 2.0.6 or earlier) - filing in JIRA now.


- we still have that test failure, though it only occurs on the  
solaris server (even in a clean env) - we should probably check  
other operating systems to see if this is a map ordering problem


Cheers,
Brett

On 13/06/2007, at 3:12 PM, Jason van Zyl wrote:


Hi,

The release notes are here:

http://jira.codehaus.org/secure/ReleaseNote.jspa? 
projectId=10500styleName=Htmlversion=13138


The tag is here:

http://svn.apache.org/repos/asf/maven/components/tags/maven-2.0.7/

Staging repository:

http://people.apache.org/~jvanzyl/maven-2.0.7-staging-repository/

And the distros you are interested in are here:

http://people.apache.org/~jvanzyl/maven-2.0.7/

Thanks,

Jason.



 
-

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



 
-

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


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




Thanks,

Jason

--
Jason van Zyl
Founder and PMC Chair, Apache Maven
jason at sonatype dot com
--




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


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

Re: [VOTE] Release Maven 2.0.7

2007-06-14 Thread Dimitris Kapanidis


+1, tested on a project with 15 modules.

Arnaud HERITIER wrote:

+1, tested on my m2 projects

Arnaud

On 13/06/07, Jason van Zyl [EMAIL PROTECTED] wrote:


Hi,

The release notes are here:

http://jira.codehaus.org/secure/ReleaseNote.jspa?
projectId=10500styleName=Htmlversion=13138

The tag is here:

http://svn.apache.org/repos/asf/maven/components/tags/maven-2.0.7/

Staging repository:

http://people.apache.org/~jvanzyl/maven-2.0.7-staging-repository/

And the distros you are interested in are here:

http://people.apache.org/~jvanzyl/maven-2.0.7/

Thanks,

Jason.



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



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








--

Dimitris Kapanidis
Software Q.A. Manager
Scytl Secure Electronic Voting
Tuset 20 · 08006 Barcelona
Phone:  + 34 934 230 324
Fax + 34 933 251 028
http://www.scytl.com

NOTICE: The information in this e-mail and in any of its attachments is confidential and intended solely for the attention and use of the named addressee(s). If you are not the intended recipient, any disclosure, copying, distribution or retaining of this message or any part of it, without the prior written consent of Scytl Secure Electronic Voting, SA is prohibited and may be unlawful. If you have received this in error, please contact the sender and delete the material from any computer. 





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

Re: [VOTE] Release Maven 2.0.7

2007-06-14 Thread Joakim Erdfelt


-1 (conditional)

evoking the spirit of dkulp ...

1) The embedded maven-core-2.0.7-uber.jar has bad LICENSE.txt and 
NOTICE.txt files.
1a) The LICENSE.txt at the root of the maven-core-2.0.7-uber.jar is for 
JSch's LGPL license. not ASL.

1b) There is no NOTICE.txt file at the root.
1c) There is a META-INF/NOTICE.txt file, but it only mentioned 
wagon-file provider.

1d) The META-INF/MANIFEST.MF was built by me!? huh?

Aside: With this new uber-jar setup, can we include wagon-webdav now?

- Joakim

Jason van Zyl wrote:

Hi,

The release notes are here:

http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500styleName=Htmlversion=13138 



The tag is here:

http://svn.apache.org/repos/asf/maven/components/tags/maven-2.0.7/

Staging repository:

http://people.apache.org/~jvanzyl/maven-2.0.7-staging-repository/

And the distros you are interested in are here:

http://people.apache.org/~jvanzyl/maven-2.0.7/

Thanks,

Jason.



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



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




--
- Joakim Erdfelt
 [EMAIL PROTECTED]
 Open Source Software (OSS) Developer


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

Re: [VOTE] Release Maven 2.0.7

2007-06-14 Thread Max Bowsher

Joakim Erdfelt wrote:
 -1 (conditional)
 
 evoking the spirit of dkulp ...
 
 1) The embedded maven-core-2.0.7-uber.jar has bad LICENSE.txt and
 NOTICE.txt files.
 1a) The LICENSE.txt at the root of the maven-core-2.0.7-uber.jar is for
 JSch's LGPL license. not ASL.
 1b) There is no NOTICE.txt file at the root.
 1c) There is a META-INF/NOTICE.txt file, but it only mentioned
 wagon-file provider.
 1d) The META-INF/MANIFEST.MF was built by me!? huh?
 
 Aside: With this new uber-jar setup, can we include wagon-webdav now?
 
 - Joakim

Another problem - the assembly in
http://people.apache.org/~jvanzyl/maven-2.0.7/
is different to the assembly in
http://people.apache.org/~jvanzyl/maven-2.0.7-staging-repository/

The one in the staging repo:
 - has unix EOLs for m2.bat, mvn.bat and m2.conf
 - has in the uberjar manifest:
 Built-By: jvanzyl
 Build-Jdk: 1.5.0_07
   unlike the other, which has:
 Built-By: joakim
 Build-Jdk: 1.4.2_12
 - has a META-INF/NOTICE.txt from maven-plugin-api instead of from
   wagon-file.
 - is missing the wagon providers!


Also, the one in http://people.apache.org/~jvanzyl/maven-2.0.7/ contains
some org.xml.sax and org.w3c.dom classes ... should it? The 2.0.6
release uberjar contains them too.


Max.





signature.asc
Description: OpenPGP digital signature

RE: [VOTE] Release Maven 2.0.7

2007-06-14 Thread Brian E. Fox

For what it's worth, the original staged version seems ok on all my
builds. 

-Original Message-
From: Max Bowsher [mailto:[EMAIL PROTECTED] 
Sent: Thursday, June 14, 2007 9:22 AM
To: Maven Developers List
Subject: Re: [VOTE] Release Maven 2.0.7

Joakim Erdfelt wrote:
 -1 (conditional)

 evoking the spirit of dkulp ...

 1) The embedded maven-core-2.0.7-uber.jar has bad LICENSE.txt and 
 NOTICE.txt files.
 1a) The LICENSE.txt at the root of the maven-core-2.0.7-uber.jar is 
 for JSch's LGPL license. not ASL.
 1b) There is no NOTICE.txt file at the root.
 1c) There is a META-INF/NOTICE.txt file, but it only mentioned 
 wagon-file provider.
 1d) The META-INF/MANIFEST.MF was built by me!? huh?

 Aside: With this new uber-jar setup, can we include wagon-webdav now?

 - Joakim

Another problem - the assembly in
http://people.apache.org/~jvanzyl/maven-2.0.7/
is different to the assembly in
http://people.apache.org/~jvanzyl/maven-2.0.7-staging-repository/

The one in the staging repo:
 - has unix EOLs for m2.bat, mvn.bat and m2.conf
 - has in the uberjar manifest:
 Built-By: jvanzyl
 Build-Jdk: 1.5.0_07
   unlike the other, which has:
 Built-By: joakim
 Build-Jdk: 1.4.2_12
 - has a META-INF/NOTICE.txt from maven-plugin-api instead of from
   wagon-file.
 - is missing the wagon providers!

Also, the one in http://people.apache.org/~jvanzyl/maven-2.0.7/ contains
some org.xml.sax and org.w3c.dom classes ... should it? The 2.0.6
release uberjar contains them too.

Max.

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

Re: [VOTE] Release Maven 2.0.7



On 14 Jun 07, at 5:58 AM 14 Jun 07, Joakim Erdfelt wrote:


-1 (conditional)

evoking the spirit of dkulp ...

1) The embedded maven-core-2.0.7-uber.jar has bad LICENSE.txt and  
NOTICE.txt files.
1a) The LICENSE.txt at the root of the maven-core-2.0.7-uber.jar is  
for JSch's LGPL license. not ASL.

1b) There is no NOTICE.txt file at the root.
1c) There is a META-INF/NOTICE.txt file, but it only mentioned  
wagon-file provider.

1d) The META-INF/MANIFEST.MF was built by me!? huh?



I'll fix these up, someone changed the shade plugin and I didn't  
notice (I believe xfire Dan when he modified it for CXF).



Aside: With this new uber-jar setup, can we include wagon-webdav now?



Not for this release.


- Joakim

Jason van Zyl wrote:

Hi,

The release notes are here:

http://jira.codehaus.org/secure/ReleaseNote.jspa? 
projectId=10500styleName=Htmlversion=13138


The tag is here:

http://svn.apache.org/repos/asf/maven/components/tags/maven-2.0.7/

Staging repository:

http://people.apache.org/~jvanzyl/maven-2.0.7-staging-repository/

And the distros you are interested in are here:

http://people.apache.org/~jvanzyl/maven-2.0.7/

Thanks,

Jason.



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



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




--
- Joakim Erdfelt
 [EMAIL PROTECTED]
 Open Source Software (OSS) Developer


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




Thanks,

Jason

--
Jason van Zyl
Founder and PMC Chair, Apache Maven
jason at sonatype dot com
--




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

Re: [VOTE] Release Maven 2.0.7

2007-06-14 Thread Wendy Smoak


On 6/14/07, Jason van Zyl [EMAIL PROTECTED] wrote:


All the new stuff is here:

http://people.apache.org/~jvanzyl/


Is there a buildable-from-source distribution?

I only see -bin here: http://people.apache.org/~jvanzyl/maven-2.0.7/

--
Wendy

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

Re: [VOTE] Release Maven 2.0.7



On 14 Jun 07, at 7:14 AM 14 Jun 07, Wendy Smoak wrote:


On 6/14/07, Jason van Zyl [EMAIL PROTECTED] wrote:


All the new stuff is here:

http://people.apache.org/~jvanzyl/


Is there a buildable-from-source distribution?

I only see -bin here: http://people.apache.org/~jvanzyl/maven-2.0.7/



We've never had one, but I can certainly make one by exporting the  
tag and zipping it up. All the source archives to date are simply the  
source as record, they don't include anything in there to build them.  
I don't think this is useful at all to anyone but if it's a legal  
requirement to have a buildable-from-source distribution it will take  
me a few minutes to make it. I'm not sure Maven SCM supports and  
export that would work and I'm certainly not going to mess around  
with that at this stage to put in the build. But if we want to give  
people what I actually used to build the release then the tag should  
be exported and zipped up.



--
Wendy

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




Thanks,

Jason

--
Jason van Zyl
Founder and PMC Chair, Apache Maven
jason at sonatype dot com
--




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

Re: [VOTE] Release Maven 2.0.7



On 14 Jun 07, at 5:58 AM 14 Jun 07, Joakim Erdfelt wrote:


-1 (conditional)

evoking the spirit of dkulp ...

1) The embedded maven-core-2.0.7-uber.jar has bad LICENSE.txt and  
NOTICE.txt files.
1a) The LICENSE.txt at the root of the maven-core-2.0.7-uber.jar is  
for JSch's LGPL license. not ASL.

1b) There is no NOTICE.txt file at the root.
1c) There is a META-INF/NOTICE.txt file, but it only mentioned  
wagon-file provider.

1d) The META-INF/MANIFEST.MF was built by me!? huh?



Actually, I didn't read this. In the Uber JAR I can live with that.  
The legal requirement for the distributable is satisfied. I'll fix  
this later:


http://jira.codehaus.org/browse/MSHADE-1


Aside: With this new uber-jar setup, can we include wagon-webdav now?

- Joakim

Jason van Zyl wrote:

Hi,

The release notes are here:

http://jira.codehaus.org/secure/ReleaseNote.jspa? 
projectId=10500styleName=Htmlversion=13138


The tag is here:

http://svn.apache.org/repos/asf/maven/components/tags/maven-2.0.7/

Staging repository:

http://people.apache.org/~jvanzyl/maven-2.0.7-staging-repository/

And the distros you are interested in are here:

http://people.apache.org/~jvanzyl/maven-2.0.7/

Thanks,

Jason.



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



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




--
- Joakim Erdfelt
 [EMAIL PROTECTED]
 Open Source Software (OSS) Developer


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




Thanks,

Jason

--
Jason van Zyl
Founder and PMC Chair, Apache Maven
jason at sonatype dot com
--




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

Re: [VOTE] Release Maven 2.0.7

2007-06-14 Thread Joakim Erdfelt


Jason van Zyl wrote:


On 14 Jun 07, at 7:14 AM 14 Jun 07, Wendy Smoak wrote:


On 6/14/07, Jason van Zyl [EMAIL PROTECTED] wrote:


All the new stuff is here:

http://people.apache.org/~jvanzyl/


Is there a buildable-from-source distribution?

I only see -bin here: http://people.apache.org/~jvanzyl/maven-2.0.7/



We've never had one, but I can certainly make one by exporting the tag 
and zipping it up. All the source archives to date are simply the 
source as record, they don't include anything in there to build them. 
I don't think this is useful at all to anyone but if it's a legal 
requirement to have a buildable-from-source distribution it will take 
me a few minutes to make it. I'm not sure Maven SCM supports and 
export that would work and I'm certainly not going to mess around with 
that at this stage to put in the build. But if we want to give people 
what I actually used to build the release then the tag should be 
exported and zipped up.



Last one I see is maven-2.0.5
http://www.apache.org/dist/maven/source/

--
- Joakim Erdfelt
 [EMAIL PROTECTED]
 Open Source Software (OSS) Developer


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

RE: [VOTE] Release Maven 2.0.7

2007-06-14 Thread Brian E. Fox

I'm no lawyer, but since the tag is publicly available from SVN, why
wouldn't that be sufficient? It would be convenient for some I suppose,
but I doubt it's a requirement.

-Original Message-
From: Jason van Zyl [mailto:[EMAIL PROTECTED] 
Sent: Thursday, June 14, 2007 11:19 AM
To: Maven Developers List
Subject: Re: [VOTE] Release Maven 2.0.7

On 14 Jun 07, at 7:14 AM 14 Jun 07, Wendy Smoak wrote:

 On 6/14/07, Jason van Zyl [EMAIL PROTECTED] wrote:

 All the new stuff is here:

 http://people.apache.org/~jvanzyl/

 Is there a buildable-from-source distribution?

 I only see -bin here: http://people.apache.org/~jvanzyl/maven-2.0.7/

We've never had one, but I can certainly make one by exporting the tag
and zipping it up. All the source archives to date are simply the source
as record, they don't include anything in there to build them.  
I don't think this is useful at all to anyone but if it's a legal
requirement to have a buildable-from-source distribution it will take me
a few minutes to make it. I'm not sure Maven SCM supports and export
that would work and I'm certainly not going to mess around with that at
this stage to put in the build. But if we want to give people what I
actually used to build the release then the tag should be exported and
zipped up.

 --
 Wendy

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

Thanks,

Jason

--
Jason van Zyl
Founder and PMC Chair, Apache Maven
jason at sonatype dot com
--

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

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

Re: [VOTE] Release Maven 2.0.7

Brian E. Fox ha scritto:
 I'm no lawyer, but since the tag is publicly available from SVN, why
 wouldn't that be sufficient? It would be convenient for some I suppose,
 but I doubt it's a requirement.

AFAIK if you don't release the source code in a package with LICENSE and
NOTICE file then no one will be able to your your source code because it
is not clear otherwise what rights people have on files that are only
available via svn and have an header telling them See the NOTICE file
distributed with this work. So if you don't redistribute the work the
license is invalid.

Stefano

 -Original Message-
 From: Jason van Zyl [mailto:[EMAIL PROTECTED] 
 Sent: Thursday, June 14, 2007 11:19 AM
 To: Maven Developers List
 Subject: Re: [VOTE] Release Maven 2.0.7
 
 
 On 14 Jun 07, at 7:14 AM 14 Jun 07, Wendy Smoak wrote:
 
 On 6/14/07, Jason van Zyl [EMAIL PROTECTED] wrote:

 All the new stuff is here:

 http://people.apache.org/~jvanzyl/
 Is there a buildable-from-source distribution?

 I only see -bin here: http://people.apache.org/~jvanzyl/maven-2.0.7/

 
 We've never had one, but I can certainly make one by exporting the tag
 and zipping it up. All the source archives to date are simply the source
 as record, they don't include anything in there to build them.  
 I don't think this is useful at all to anyone but if it's a legal
 requirement to have a buildable-from-source distribution it will take me
 a few minutes to make it. I'm not sure Maven SCM supports and export
 that would work and I'm certainly not going to mess around with that at
 this stage to put in the build. But if we want to give people what I
 actually used to build the release then the tag should be exported and
 zipped up.
 
 --
 Wendy

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


 
 Thanks,
 
 Jason
 
 --
 Jason van Zyl
 Founder and PMC Chair, Apache Maven
 jason at sonatype dot com
 --
 
 
 
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED] For additional
 commands, e-mail: [EMAIL PROTECTED]
 
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 
 



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

Re: [VOTE] Release Maven 2.0.7



On 14 Jun 07, at 8:31 AM 14 Jun 07, Brian E. Fox wrote:


I'm no lawyer, but since the tag is publicly available from SVN, why
wouldn't that be sufficient? It would be convenient for some I  
suppose,

but I doubt it's a requirement.


Took me a few minutes so it doesn't hurt, I just exported the tag,  
zipped it up, signed, and checksummed it:


http://people.apache.org/~jvanzyl/maven-2.0.7/



-Original Message-
From: Jason van Zyl [mailto:[EMAIL PROTECTED]
Sent: Thursday, June 14, 2007 11:19 AM
To: Maven Developers List
Subject: Re: [VOTE] Release Maven 2.0.7


On 14 Jun 07, at 7:14 AM 14 Jun 07, Wendy Smoak wrote:


On 6/14/07, Jason van Zyl [EMAIL PROTECTED] wrote:


All the new stuff is here:

http://people.apache.org/~jvanzyl/


Is there a buildable-from-source distribution?

I only see -bin here: http://people.apache.org/~jvanzyl/maven-2.0.7/



We've never had one, but I can certainly make one by exporting the tag
and zipping it up. All the source archives to date are simply the  
source

as record, they don't include anything in there to build them.
I don't think this is useful at all to anyone but if it's a legal
requirement to have a buildable-from-source distribution it will  
take me

a few minutes to make it. I'm not sure Maven SCM supports and export
that would work and I'm certainly not going to mess around with  
that at

this stage to put in the build. But if we want to give people what I
actually used to build the release then the tag should be exported and
zipped up.


--
Wendy

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




Thanks,

Jason

--
Jason van Zyl
Founder and PMC Chair, Apache Maven
jason at sonatype dot com
--




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

commands, e-mail: [EMAIL PROTECTED]


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




Thanks,

Jason

--
Jason van Zyl
Founder and PMC Chair, Apache Maven
jason at sonatype dot com
--




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

Re: [VOTE] Release Maven 2.0.7

Jason van Zyl ha scritto:
 
 On 14 Jun 07, at 8:31 AM 14 Jun 07, Brian E. Fox wrote:
 
 I'm no lawyer, but since the tag is publicly available from SVN, why
 wouldn't that be sufficient? It would be convenient for some I suppose,
 but I doubt it's a requirement.
 
 Took me a few minutes so it doesn't hurt, I just exported the tag,
 zipped it up, signed, and checksummed it:
 
 http://people.apache.org/~jvanzyl/maven-2.0.7/

It is missing the NOTICE and LICENSE files that are the key for the
concern of the previous mail ;-)

Apart that I think it is ok.

Stefano



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

What is a release? (was: Re: [VOTE] Release Maven 2.0.7)

2007-06-14 Thread Wendy Smoak

On 6/14/07, Jason van Zyl [EMAIL PROTECTED] wrote:

We've never had one, but I can certainly make one by exporting the
tag and zipping it up. All the source archives to date are simply the
source as record, they don't include anything in there to build them.
I don't think this is useful at all to anyone but if it's a legal
requirement to have a buildable-from-source distribution it will take
me a few minutes to make it. I'm not sure Maven SCM supports and
export that would work and I'm certainly not going to mess around
with that at this stage to put in the build. But if we want to give
people what I actually used to build the release then the tag should
be exported and zipped up.

I did that (svn export and zip) for Archiva 0.9-alpha-2, but I had to
add LICENSE and NOTICE because they were not in svn. For Struts I use
the assembly plugin to piece together the same thing you get with svn
export.

Anyway, I don't think it's a legal requirement so much as it's what
we do. I mentioned it when I cleaned up the /dist/maven directory,
and Henri commented on it then but we never finished the discussion.

The release FAQ is as close to ASF policy as we've got:
http://www.apache.org/dev/release.html

The Apache Software Foundation produces open source software. All
releases are in the form of the source materials needed to make
changes to the software being released. In some cases, binary/bytecode
packages are also produced as a convenience to users that might not
have the appropriate tools to build a compiled version of the source.
...

There's a similar conversation happening on commons-dev:
http://www.nabble.com/-all--What-is-a-release--WAS%3A--vote--releasing-jci-RC3-as-1.0-...maybe-this-time--t3898124.html#a11050531

--
Wendy

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

Re: [VOTE] Release Maven 2.0.7

2007-06-14 Thread Wendy Smoak


On 6/14/07, Jason van Zyl [EMAIL PROTECTED] wrote:


Took me a few minutes so it doesn't hurt, I just exported the tag,
zipped it up, signed, and checksummed it:

http://people.apache.org/~jvanzyl/maven-2.0.7/


Thanks.  Almost there... it needs LICENSE and NOTICE added.  :)

I have a note to add those files at the 'top' of each subproject so
they're present when someone checks the source out from svn.  The
remote resources plugin can still do its thing for the jars.

--
Wendy

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

Re: What is a release? (was: Re: [VOTE] Release Maven 2.0.7)

2007-06-14 Thread Carlos Sanchez

that's what I understood too, source release is mandatory and binary optional

On 6/14/07, Wendy Smoak [EMAIL PROTECTED] wrote:

On 6/14/07, Jason van Zyl [EMAIL PROTECTED] wrote:

The release FAQ is as close to ASF policy as we've got:
http://www.apache.org/dev/release.html

There's a similar conversation happening on commons-dev:
http://www.nabble.com/-all--What-is-a-release--WAS%3A--vote--releasing-jci-RC3-as-1.0-...maybe-this-time--t3898124.html#a11050531

--
Wendy

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

--
I could give you my word as a Spaniard.
No good. I've known too many Spaniards.
-- The Princess Bride

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

Re: [VOTE] Release Maven 2.0.7

Wendy Smoak ha scritto:
 On 6/14/07, Jason van Zyl [EMAIL PROTECTED] wrote:
 
 Took me a few minutes so it doesn't hurt, I just exported the tag,
 zipped it up, signed, and checksummed it:

 http://people.apache.org/~jvanzyl/maven-2.0.7/
 
 Thanks.  Almost there... it needs LICENSE and NOTICE added.  :)
 
 I have a note to add those files at the 'top' of each subproject so
 they're present when someone checks the source out from svn.  The
 remote resources plugin can still do its thing for the jars.

For Apache mime4j we use the assembly plugin to generate a source
package including NOTICE/LICENSE generated by the remote resources plugin:
http://svn.apache.org/viewvc/james/mime4j/trunk/src/assemble/src.xml?revision=536368view=markup

Stefano


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

Re: [VOTE] Release Maven 2.0.7



On 14 Jun 07, at 9:37 AM 14 Jun 07, Stefano Bagnara wrote:


Wendy Smoak ha scritto:

On 6/14/07, Jason van Zyl [EMAIL PROTECTED] wrote:


Took me a few minutes so it doesn't hurt, I just exported the tag,
zipped it up, signed, and checksummed it:

http://people.apache.org/~jvanzyl/maven-2.0.7/


Thanks.  Almost there... it needs LICENSE and NOTICE added.  :)

I have a note to add those files at the 'top' of each subproject so
they're present when someone checks the source out from svn.  The
remote resources plugin can still do its thing for the jars.


For Apache mime4j we use the assembly plugin to generate a source
package including NOTICE/LICENSE generated by the remote resources  
plugin:
http://svn.apache.org/viewvc/james/mime4j/trunk/src/assemble/ 
src.xml?revision=536368view=markup




Yes, I'm aware of how the assembly plugin works.

Did you use the tag you used to create the release? Otherwise you're  
not using what what used to create the release. If you're running  
this from the release plugin then that's fine, otherwise it's not.



Stefano


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




Thanks,

Jason

--
Jason van Zyl
Founder and PMC Chair, Apache Maven
jason at sonatype dot com
--




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

Re: [VOTE] Release Maven 2.0.7



On 14 Jun 07, at 9:34 AM 14 Jun 07, Wendy Smoak wrote:


On 6/14/07, Jason van Zyl [EMAIL PROTECTED] wrote:


Took me a few minutes so it doesn't hurt, I just exported the tag,
zipped it up, signed, and checksummed it:

http://people.apache.org/~jvanzyl/maven-2.0.7/


Thanks.  Almost there... it needs LICENSE and NOTICE added.  :)

I have a note to add those files at the 'top' of each subproject so
they're present when someone checks the source out from svn.  The
remote resources plugin can still do its thing for the jars.



Don't do that? What's the point? This is not a requirement and as  
soon as something changes in the template you're going to have to go  
update them all.



--
Wendy

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




Thanks,

Jason

--
Jason van Zyl
Founder and PMC Chair, Apache Maven
jason at sonatype dot com
--




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

Re: What is a release? (was: Re: [VOTE] Release Maven 2.0.7)



On 14 Jun 07, at 9:39 AM 14 Jun 07, Carlos Sanchez wrote:

that's what I understood too, source release is mandatory and  
binary optional




This is a throwback to HTTPD where a source distribution made more  
sense because of platform issues. I'm willing to bet 99.% of  
users don't build from sources and take the binaries. Of course it's  
important to have the sources available but in all practical terms  
most users will never use them.



On 6/14/07, Wendy Smoak [EMAIL PROTECTED] wrote:

On 6/14/07, Jason van Zyl [EMAIL PROTECTED] wrote:

 We've never had one, but I can certainly make one by exporting the
 tag and zipping it up. All the source archives to date are  
simply the
 source as record, they don't include anything in there to build  
them.

 I don't think this is useful at all to anyone but if it's a legal
 requirement to have a buildable-from-source distribution it will  
take

 me a few minutes to make it. I'm not sure Maven SCM supports and
 export that would work and I'm certainly not going to mess around
 with that at this stage to put in the build. But if we want to give
 people what I actually used to build the release then the tag  
should

 be exported and zipped up.

I did that (svn export and zip) for Archiva 0.9-alpha-2, but I had to
add LICENSE and NOTICE because they were not in svn.  For Struts I  
use

the assembly plugin to piece together the same thing you get with svn
export.

Anyway, I don't think it's a legal requirement so much as it's what
we do.  I mentioned it when I cleaned up the /dist/maven directory,
and Henri commented on it then but we never finished the discussion.

The release FAQ is as close to ASF policy as we've got:
http://www.apache.org/dev/release.html

The Apache Software Foundation produces open source software. All
releases are in the form of the source materials needed to make
changes to the software being released. In some cases, binary/ 
bytecode

packages are also produced as a convenience to users that might not
have the appropriate tools to build a compiled version of the source.
...

There's a similar conversation happening on commons-dev:
http://www.nabble.com/-all--What-is-a-release--WAS%3A--vote-- 
releasing-jci-RC3-as-1.0-...maybe-this-time--t3898124.html#a11050531


--
Wendy

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





--
I could give you my word as a Spaniard.
No good. I've known too many Spaniards.
-- The Princess Bride

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




Thanks,

Jason

--
Jason van Zyl
Founder and PMC Chair, Apache Maven
jason at sonatype dot com
--




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

Re: What is a release? (was: Re: [VOTE] Release Maven 2.0.7)

2007-06-14 Thread robert burrell donkin


On 6/14/07, Jason van Zyl [EMAIL PROTECTED] wrote:



On 14 Jun 07, at 9:39 AM 14 Jun 07, Carlos Sanchez wrote:

 that's what I understood too, source release is mandatory and
 binary optional


This is a throwback to HTTPD where a source distribution made more
sense because of platform issues. I'm willing to bet 99.% of
users don't build from sources and take the binaries. Of course it's
important to have the sources available but in all practical terms
most users will never use them.



users don't use source distributions but downstream developers and packagers
do.

this is open source. cutting source releases means that the source for a
release will always be available.

- robert

Re: What is a release? (was: Re: [VOTE] Release Maven 2.0.7)

2007-06-14 Thread Carlos Sanchez


I'm not talking about what our users do, I'm talking about what the
ASF policy seems to be

On 6/14/07, Jason van Zyl [EMAIL PROTECTED] wrote:


On 14 Jun 07, at 9:39 AM 14 Jun 07, Carlos Sanchez wrote:

 that's what I understood too, source release is mandatory and
 binary optional


This is a throwback to HTTPD where a source distribution made more
sense because of platform issues. I'm willing to bet 99.% of
users don't build from sources and take the binaries. Of course it's
important to have the sources available but in all practical terms
most users will never use them.

 On 6/14/07, Wendy Smoak [EMAIL PROTECTED] wrote:
 On 6/14/07, Jason van Zyl [EMAIL PROTECTED] wrote:

  We've never had one, but I can certainly make one by exporting the
  tag and zipping it up. All the source archives to date are
 simply the
  source as record, they don't include anything in there to build
 them.
  I don't think this is useful at all to anyone but if it's a legal
  requirement to have a buildable-from-source distribution it will
 take
  me a few minutes to make it. I'm not sure Maven SCM supports and
  export that would work and I'm certainly not going to mess around
  with that at this stage to put in the build. But if we want to give
  people what I actually used to build the release then the tag
 should
  be exported and zipped up.

 I did that (svn export and zip) for Archiva 0.9-alpha-2, but I had to
 add LICENSE and NOTICE because they were not in svn.  For Struts I
 use
 the assembly plugin to piece together the same thing you get with svn
 export.

 Anyway, I don't think it's a legal requirement so much as it's what
 we do.  I mentioned it when I cleaned up the /dist/maven directory,
 and Henri commented on it then but we never finished the discussion.

 The release FAQ is as close to ASF policy as we've got:
 http://www.apache.org/dev/release.html

 The Apache Software Foundation produces open source software. All
 releases are in the form of the source materials needed to make
 changes to the software being released. In some cases, binary/
 bytecode
 packages are also produced as a convenience to users that might not
 have the appropriate tools to build a compiled version of the source.
 ...

 There's a similar conversation happening on commons-dev:
 http://www.nabble.com/-all--What-is-a-release--WAS%3A--vote--
 releasing-jci-RC3-as-1.0-...maybe-this-time--t3898124.html#a11050531

 --
 Wendy

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




 --
 I could give you my word as a Spaniard.
 No good. I've known too many Spaniards.
 -- The Princess Bride

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



Thanks,

Jason

--
Jason van Zyl
Founder and PMC Chair, Apache Maven
jason at sonatype dot com
--




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





--
I could give you my word as a Spaniard.
No good. I've known too many Spaniards.
-- The Princess Bride

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

Re: [VOTE] Release Maven 2.0.7

Jason van Zyl ha scritto:
 
 On 14 Jun 07, at 9:37 AM 14 Jun 07, Stefano Bagnara wrote:
 
 Wendy Smoak ha scritto:
 On 6/14/07, Jason van Zyl [EMAIL PROTECTED] wrote:

 Took me a few minutes so it doesn't hurt, I just exported the tag,
 zipped it up, signed, and checksummed it:

 http://people.apache.org/~jvanzyl/maven-2.0.7/

 Thanks.  Almost there... it needs LICENSE and NOTICE added.  :)

 I have a note to add those files at the 'top' of each subproject so
 they're present when someone checks the source out from svn.  The
 remote resources plugin can still do its thing for the jars.

 For Apache mime4j we use the assembly plugin to generate a source
 package including NOTICE/LICENSE generated by the remote resources
 plugin:
 http://svn.apache.org/viewvc/james/mime4j/trunk/src/assemble/src.xml?revision=536368view=markup


 
 Yes, I'm aware of how the assembly plugin works.
 
 Did you use the tag you used to create the release? Otherwise you're not
 using what what used to create the release. If you're running this from
 the release plugin then that's fine, otherwise it's not.

This question is interesting:

we run release:perform and we let maven do everything else: how do I
know if I run this from the release plugin or not ?

my assembly plugin is configured as follows:

  plugin
artifactIdmaven-assembly-plugin/artifactId
version2.2-beta-1/version
configuration

descriptorSourceDirectory${basedir}/src/assemble//descriptorSourceDirectory
/configuration
executions
  execution
idmake-assembly/id !-- this is used for inheritance
merges --
phasepackage/phase !-- append to the packaging phase. --
goals
  goalattached/goal !-- goals == mojos --
/goals
  /execution
/executions
  /plugin
--

Stefano


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

Re: [VOTE] Release Maven 2.0.7

Jason van Zyl ha scritto:
 
 On 14 Jun 07, at 9:34 AM 14 Jun 07, Wendy Smoak wrote:
 
 On 6/14/07, Jason van Zyl [EMAIL PROTECTED] wrote:

 Took me a few minutes so it doesn't hurt, I just exported the tag,
 zipped it up, signed, and checksummed it:

 http://people.apache.org/~jvanzyl/maven-2.0.7/

 Thanks.  Almost there... it needs LICENSE and NOTICE added.  :)

 I have a note to add those files at the 'top' of each subproject so
 they're present when someone checks the source out from svn.  The
 remote resources plugin can still do its thing for the jars.

 
 Don't do that? What's the point? This is not a requirement and as soon
 as something changes in the template you're going to have to go update
 them all.

I've had a discussion with Robert Burrell Donkin about this.

He suggested to place LICENSE/NOTICE files also in the svn but I
preferred to have a single source (the remote-resource plugin) for the
resulting NOTICE/LICENSE and so we don't place the files in svn. The
legal/license issues are only related to redistributed packages.

Stefano


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

Re: What is a release? (was: Re: [VOTE] Release Maven 2.0.7)



On 14 Jun 07, at 10:36 AM 14 Jun 07, Carlos Sanchez wrote:


I'm not talking about what our users do, I'm talking about what the
ASF policy seems to be



Ask five people and you'll get five different answers.

Bottom line is who cares, I'll keep adapting to what people think is  
necessary and we'll feed it back into the system.



On 6/14/07, Jason van Zyl [EMAIL PROTECTED] wrote:


On 14 Jun 07, at 9:39 AM 14 Jun 07, Carlos Sanchez wrote:

 that's what I understood too, source release is mandatory and
 binary optional


This is a throwback to HTTPD where a source distribution made more
sense because of platform issues. I'm willing to bet 99.% of
users don't build from sources and take the binaries. Of course it's
important to have the sources available but in all practical terms
most users will never use them.

 On 6/14/07, Wendy Smoak [EMAIL PROTECTED] wrote:
 On 6/14/07, Jason van Zyl [EMAIL PROTECTED] wrote:

  We've never had one, but I can certainly make one by  
exporting the

  tag and zipping it up. All the source archives to date are
 simply the
  source as record, they don't include anything in there to build
 them.
  I don't think this is useful at all to anyone but if it's a  
legal

  requirement to have a buildable-from-source distribution it will
 take
  me a few minutes to make it. I'm not sure Maven SCM supports and
  export that would work and I'm certainly not going to mess  
around
  with that at this stage to put in the build. But if we want  
to give

  people what I actually used to build the release then the tag
 should
  be exported and zipped up.

 I did that (svn export and zip) for Archiva 0.9-alpha-2, but I  
had to

 add LICENSE and NOTICE because they were not in svn.  For Struts I
 use
 the assembly plugin to piece together the same thing you get  
with svn

 export.

 Anyway, I don't think it's a legal requirement so much as it's  
what
 we do.  I mentioned it when I cleaned up the /dist/maven  
directory,
 and Henri commented on it then but we never finished the  
discussion.


 The release FAQ is as close to ASF policy as we've got:
 http://www.apache.org/dev/release.html

 The Apache Software Foundation produces open source software. All
 releases are in the form of the source materials needed to make
 changes to the software being released. In some cases, binary/
 bytecode
 packages are also produced as a convenience to users that might  
not
 have the appropriate tools to build a compiled version of the  
source.

 ...

 There's a similar conversation happening on commons-dev:
 http://www.nabble.com/-all--What-is-a-release--WAS%3A--vote--
 releasing-jci-RC3-as-1.0-...maybe-this-time-- 
t3898124.html#a11050531


 --
 Wendy

  
-

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




 --
 I could give you my word as a Spaniard.
 No good. I've known too many Spaniards.
 -- The Princess Bride

  
-

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



Thanks,

Jason

--
Jason van Zyl
Founder and PMC Chair, Apache Maven
jason at sonatype dot com
--




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





--
I could give you my word as a Spaniard.
No good. I've known too many Spaniards.
-- The Princess Bride

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




Thanks,

Jason

--
Jason van Zyl
Founder and PMC Chair, Apache Maven
jason at sonatype dot com
--




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

Re: What is a release? (was: Re: [VOTE] Release Maven 2.0.7)



On 14 Jun 07, at 10:34 AM 14 Jun 07, robert burrell donkin wrote:


On 6/14/07, Jason van Zyl [EMAIL PROTECTED] wrote:



On 14 Jun 07, at 9:39 AM 14 Jun 07, Carlos Sanchez wrote:

 that's what I understood too, source release is mandatory and
 binary optional


This is a throwback to HTTPD where a source distribution made more
sense because of platform issues. I'm willing to bet 99.% of
users don't build from sources and take the binaries. Of course it's
important to have the sources available but in all practical terms
most users will never use them.



users don't use source distributions but downstream developers and  
packagers

do.



No they don't. They check things out of SVN and create vendor  
branches. I don't know a single tools vendor who doesn't use SCM of  
the tool they are integrating.


this is open source. cutting source releases means that the source  
for a

release will always be available.



- robert


Thanks,

Jason

--
Jason van Zyl
Founder and PMC Chair, Apache Maven
jason at sonatype dot com
--




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

Re: What is a release? (was: Re: [VOTE] Release Maven 2.0.7)

Jason van Zyl ha scritto:

On 14 Jun 07, at 10:36 AM 14 Jun 07, Carlos Sanchez wrote:

I'm not talking about what our users do, I'm talking about what the
ASF policy seems to be

Ask five people and you'll get five different answers.

Bottom line is who cares, I'll keep adapting to what people think is
necessary and we'll feed it back into the system.

I have some statistic of downloads for Apache JAMES Server (email server).

We distribute both binary and source distributions:

2,584 binary.zip
589 binary.tar.gz
-
3,173

466 source.zip
118 source.tar.gz
343 sdksource.zip
164 source-withcontainer.zip
-
1,091

So it seems 25% of all downloads were source distribution.
It is not maven, but maybe this help your choices.

Furthermore I created a maven skin for apache james including code for
Google Analytics, and expecially including special code so that links to
package downloads to mirror sites are monitored on the onClick and added
to statistics.

if you are interested see the final part of this file:
http://svn.apache.org/viewvc/james/project/trunk/maven-skin/src/main/resources/META-INF/maven/site.vm?revision=532445view=markup

Stefano

On 6/14/07, Jason van Zyl [EMAIL PROTECTED] wrote:

On 14 Jun 07, at 9:39 AM 14 Jun 07, Carlos Sanchez wrote:

that's what I understood too, source release is mandatory and
binary optional

This is a throwback to HTTPD where a source distribution made more
sense because of platform issues. I'm willing to bet 99.% of
users don't build from sources and take the binaries. Of course it's
important to have the sources available but in all practical terms
most users will never use them.

On 6/14/07, Wendy Smoak [EMAIL PROTECTED] wrote:
On 6/14/07, Jason van Zyl [EMAIL PROTECTED] wrote:

We've never had one, but I can certainly make one by exporting the
tag and zipping it up. All the source archives to date are
simply the
source as record, they don't include anything in there to build
them.
I don't think this is useful at all to anyone but if it's a legal
requirement to have a buildable-from-source distribution it will
take
me a few minutes to make it. I'm not sure Maven SCM supports and
export that would work and I'm certainly not going to mess around
with that at this stage to put in the build. But if we want to give
people what I actually used to build the release then the tag
should
be exported and zipped up.

I did that (svn export and zip) for Archiva 0.9-alpha-2, but I had to
add LICENSE and NOTICE because they were not in svn. For Struts I
use
the assembly plugin to piece together the same thing you get with svn
export.

The release FAQ is as close to ASF policy as we've got:
http://www.apache.org/dev/release.html

The Apache Software Foundation produces open source software. All
releases are in the form of the source materials needed to make
changes to the software being released. In some cases, binary/
bytecode
packages are also produced as a convenience to users that might not
have the appropriate tools to build a compiled version of the source.
...

There's a similar conversation happening on commons-dev:
http://www.nabble.com/-all--What-is-a-release--WAS%3A--vote--
releasing-jci-RC3-as-1.0-...maybe-this-time--t3898124.html#a11050531

--
Wendy

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

Re: What is a release? (was: Re: [VOTE] Release Maven 2.0.7)

Jason van Zyl ha scritto:

On 14 Jun 07, at 10:36 AM 14 Jun 07, Carlos Sanchez wrote:

I'm not talking about what our users do, I'm talking about what the
ASF policy seems to be

Ask five people and you'll get five different answers.

Bottom line is who cares, I'll keep adapting to what people think is
necessary and we'll feed it back into the system.

I have some statistic of downloads for Apache JAMES Server (email server).

We distribute both binary and source distributions:

2,584 binary.zip
589 binary.tar.gz
-
3,173

466 source.zip
118 source.tar.gz
343 sdksource.zip
164 source-withcontainer.zip
-
1,091

So it seems 25% of all downloads were source distribution.
It is not maven, but maybe this help your choices.

if you are interested see the final part of this file:
http://svn.apache.org/viewvc/james/project/trunk/maven-skin/src/main/resources/META-INF/maven/site.vm?revision=532445view=markup

Stefano

On 6/14/07, Jason van Zyl [EMAIL PROTECTED] wrote:

On 14 Jun 07, at 9:39 AM 14 Jun 07, Carlos Sanchez wrote:

that's what I understood too, source release is mandatory and
binary optional

On 6/14/07, Wendy Smoak [EMAIL PROTECTED] wrote:
On 6/14/07, Jason van Zyl [EMAIL PROTECTED] wrote:

We've never had one, but I can certainly make one by exporting the
tag and zipping it up. All the source archives to date are
simply the
source as record, they don't include anything in there to build
them.
I don't think this is useful at all to anyone but if it's a legal
requirement to have a buildable-from-source distribution it will
take
me a few minutes to make it. I'm not sure Maven SCM supports and
export that would work and I'm certainly not going to mess around
with that at this stage to put in the build. But if we want to give
people what I actually used to build the release then the tag
should
be exported and zipped up.

I did that (svn export and zip) for Archiva 0.9-alpha-2, but I had to
add LICENSE and NOTICE because they were not in svn. For Struts I
use
the assembly plugin to piece together the same thing you get with svn
export.

The release FAQ is as close to ASF policy as we've got:
http://www.apache.org/dev/release.html

The Apache Software Foundation produces open source software. All
releases are in the form of the source materials needed to make
changes to the software being released. In some cases, binary/
bytecode
packages are also produced as a convenience to users that might not
have the appropriate tools to build a compiled version of the source.
...

There's a similar conversation happening on commons-dev:
http://www.nabble.com/-all--What-is-a-release--WAS%3A--vote--
releasing-jci-RC3-as-1.0-...maybe-this-time--t3898124.html#a11050531

--
Wendy

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

Re: What is a release? (was: Re: [VOTE] Release Maven 2.0.7)

this is open source. cutting source releases means that the source  
for a

release will always be available.


I agree, we should definitely be producing a source tarball that is  
signed and voted on. I fully admit to being slack in the first few  
releases, but we had them for 2.0.3, 2.0.4 and 2.0.5 so should  
continue. Thanks for putting it together as well.


I'll try adding it to the POM under a release profile.

users don't use source distributions but downstream developers and  
packagers

do.



No they don't. They check things out of SVN and create vendor  
branches. I don't know a single tools vendor who doesn't use SCM of  
the tool they are integrating.


hat type=downstream-packager
We've recently decided to stop pulling from SVN and use release  
source tarballs instead for releases (we'll continue using SVN for  
development purposes, of course).

/hat

Cheers,
Brett

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

Re: What is a release? (was: Re: [VOTE] Release Maven 2.0.7)



On 14 Jun 07, at 2:32 PM 14 Jun 07, Stefano Bagnara wrote:


Jason van Zyl ha scritto:


On 14 Jun 07, at 10:36 AM 14 Jun 07, Carlos Sanchez wrote:


I'm not talking about what our users do, I'm talking about what the
ASF policy seems to be



Ask five people and you'll get five different answers.

Bottom line is who cares, I'll keep adapting to what people think is
necessary and we'll feed it back into the system.


I have some statistic of downloads for Apache JAMES Server (email  
server).


We distribute both binary and source distributions:

2,584 binary.zip
  589 binary.tar.gz
-
3,173



Do you actually deploy with Maven? I imagine you have the standard  
set of people debugging the sources. I would say that's the number  
one use of source downloads whereas with Maven coupled with doing  
proper releases, inside IDEs all current integration pull down the  
source and javadoc JARs. This is for Maven itself as well.



  466 source.zip
  118 source.tar.gz
  343 sdksource.zip
  164 source-withcontainer.zip
-
1,091

So it seems 25% of all downloads were source distribution.
It is not maven, but maybe this help your choices.


Takes me a couple minutes so it's not a big deal to make it.



Furthermore I created a maven skin for apache james including code for
Google Analytics, and expecially including special code so that  
links to
package downloads to mirror sites are monitored on the onClick and  
added

to statistics.

if you are interested see the final part of this file:
http://svn.apache.org/viewvc/james/project/trunk/maven-skin/src/ 
main/resources/META-INF/maven/site.vm?revision=532445view=markup


Stefano


On 6/14/07, Jason van Zyl [EMAIL PROTECTED] wrote:


On 14 Jun 07, at 9:39 AM 14 Jun 07, Carlos Sanchez wrote:


that's what I understood too, source release is mandatory and
binary optional



This is a throwback to HTTPD where a source distribution made more
sense because of platform issues. I'm willing to bet 99.% of
users don't build from sources and take the binaries. Of course  
it's

important to have the sources available but in all practical terms
most users will never use them.


On 6/14/07, Wendy Smoak [EMAIL PROTECTED] wrote:

On 6/14/07, Jason van Zyl [EMAIL PROTECTED] wrote:

We've never had one, but I can certainly make one by  
exporting the

tag and zipping it up. All the source archives to date are

simply the

source as record, they don't include anything in there to build

them.
I don't think this is useful at all to anyone but if it's a  
legal

requirement to have a buildable-from-source distribution it will

take

me a few minutes to make it. I'm not sure Maven SCM supports and
export that would work and I'm certainly not going to mess  
around
with that at this stage to put in the build. But if we want  
to give

people what I actually used to build the release then the tag

should

be exported and zipped up.


I did that (svn export and zip) for Archiva 0.9-alpha-2, but I  
had to
add LICENSE and NOTICE because they were not in svn.  For  
Struts I

use
the assembly plugin to piece together the same thing you get  
with svn

export.

Anyway, I don't think it's a legal requirement so much as it's  
what
we do.  I mentioned it when I cleaned up the /dist/maven  
directory,
and Henri commented on it then but we never finished the  
discussion.


The release FAQ is as close to ASF policy as we've got:
http://www.apache.org/dev/release.html

The Apache Software Foundation produces open source software.  
All

releases are in the form of the source materials needed to make
changes to the software being released. In some cases, binary/
bytecode
packages are also produced as a convenience to users that  
might not
have the appropriate tools to build a compiled version of the  
source.

...

There's a similar conversation happening on commons-dev:
http://www.nabble.com/-all--What-is-a-release--WAS%3A--vote--
releasing-jci-RC3-as-1.0-...maybe-this-time-- 
t3898124.html#a11050531


--
Wendy




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




Thanks,

Jason

--
Jason van Zyl
Founder and PMC Chair, Apache Maven
jason at sonatype dot com
--




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

Re: What is a release? (was: Re: [VOTE] Release Maven 2.0.7)



On 14 Jun 07, at 5:39 PM 14 Jun 07, Brett Porter wrote:

this is open source. cutting source releases means that the  
source for a

release will always be available.


I agree, we should definitely be producing a source tarball that is  
signed and voted on. I fully admit to being slack in the first few  
releases, but we had them for 2.0.3, 2.0.4 and 2.0.5 so should  
continue. Thanks for putting it together as well.




Go look at anything made in the past, none of them were buildable  
distributions except 2.0.3 (2.0, 2.0.1, and 2.0.2 don't seem to be  
archived so I don't know about those). So obviously no one is using  
them for packaging anything downstream. This will be the first  
release with a usable source distribution since 2.0.3. But like I  
said before I doubt anyone really cares as no one has ever complained  
about them. What's there could be used for debugging which is good  
but as something you could use for a release, never happened. 2.0.3  
is usable, 2.0.4 and 2.0.5 are not. Wasn't one with 2.0.6.



I'll try adding it to the POM under a release profile.



If you're going to add it to the POM make sure you:

- export the tag
- take the whole thing in it's entirety so someone could actually  
build the release

- use the same licenses
- integrate the profile for signing and checksumming


users don't use source distributions but downstream developers  
and packagers

do.



No they don't. They check things out of SVN and create vendor  
branches. I don't know a single tools vendor who doesn't use SCM  
of the tool they are integrating.


hat type=downstream-packager
We've recently decided to stop pulling from SVN and use release  
source tarballs instead for releases (we'll continue using SVN for  
development purposes, of course).

/hat



No you didn't because the last one that would have worked is 2.0.3.


Cheers,
Brett

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




Thanks,

Jason

--
Jason van Zyl
Founder and PMC Chair, Apache Maven
jason at sonatype dot com
--




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

Re: What is a release? (was: Re: [VOTE] Release Maven 2.0.7)



On 15/06/2007, at 11:45 AM, Jason van Zyl wrote:




I'll try adding it to the POM under a release profile.



If you're going to add it to the POM make sure you:

- export the tag
- take the whole thing in it's entirety so someone could actually  
build the release

- use the same licenses
- integrate the profile for signing and checksumming


Yes, will do.



hat type=downstream-packager
We've recently decided to stop pulling from SVN and use release  
source tarballs instead for releases (we'll continue using SVN for  
development purposes, of course).

/hat



No you didn't because the last one that would have worked is 2.0.3.



recently decided - the first one will be based off 2.0.7.

- Brett

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

Re: What is a release? (was: Re: [VOTE] Release Maven 2.0.7)


All done for 2.0.8-SNAPSHOT and 2.1-SNAPSHOT.

- Brett

On 15/06/2007, at 12:10 PM, Brett Porter wrote:



On 15/06/2007, at 11:45 AM, Jason van Zyl wrote:




I'll try adding it to the POM under a release profile.



If you're going to add it to the POM make sure you:

- export the tag
- take the whole thing in it's entirety so someone could actually  
build the release

- use the same licenses
- integrate the profile for signing and checksumming


Yes, will do.



hat type=downstream-packager
We've recently decided to stop pulling from SVN and use release  
source tarballs instead for releases (we'll continue using SVN  
for development purposes, of course).

/hat



No you didn't because the last one that would have worked is 2.0.3.



recently decided - the first one will be based off 2.0.7.

- Brett

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


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

Re: [VOTE] Release Maven 2.0.7