You are viewing a plain text version of this content. The canonical link for it is here.
Posted to scout-dev@ws.apache.org by David Jencks <da...@yahoo.com> on 2009/07/27 22:19:19 UTC

Steps towards 1.1 release, including use of apache nexus

I've been working via jira and private emails with Kurt to get scout  
ready for 1.1 release.

Here are a few more things that need to happen before the release:

1. (most important) The pom has been changed to use the apache 6 pom  
as parent.  This deploys to the apache nexus instance.  In order for  
this to work the project NEEDS to get permissions set up there.
First, add a task to https://issues.apache.org/jira/browse/INFRA-1896  
asking for scout access. The project needs some record on the dev list  
indicating that it wants to use nexus.  A couple +1s to this part of  
this email should suffice.  Brian is pretty quick about this but I'd  
allow at least a day.

2. The pom isn't using the scout copy of the jaxr api any more, its  
using the geronimo copy, which is what the tck is run against.  I  
recommend removing the scout jaxr api copy and the current root/parent  
pom and moving the scout project down a level to trunk (well, branches/ 
v1.1).  Right now I'm looking at site generation, hopefully moving the  
site into the scout project will work fine.

3. There need to be LICENSE and NOTICE files in the svn checkout  
directory.  If all the code is developed at apache and there aren't  
any other special circumstances then the ones generated and added to  
the binary jar files will be fine.  You can copy them out of target/ 
maven-shared-archive-resources/META-INF/ after a build.  If the  
project needs different/additional info in these files then please let  
me know what it is, as it needs to be appended to the legal files in  
the binary jar.

4. You should use the maven-release-plugin for the release.  I'll  
provide more hints later on how.  However, the version should  
currently be 1.1-SNAPSHOT until the release candidate is actually  
made.  I'll be providing a pom patch soon that will include this change.

5. I'll be running the tck very shortly on the code currently in svn  
together with the geronimo jaxb 2.1 spec release candidate.   We had  
to re-roll the spec release due to some minor problems with the legal  
files.  The current staging directory is

https://repository.apache.org/content/repositories/geronimo-staging-029/

thanks
david jencks

---------------------------------------------------------------------
To unsubscribe, e-mail: scout-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: scout-dev-help@ws.apache.org


Re: Steps towards 1.1 release, including use of apache nexus

Posted by Kurt T Stam <ku...@gmail.com>.
David Jencks wrote:
> I've been working via jira and private emails with Kurt to get scout 
> ready for 1.1 release.
>
> Here are a few more things that need to happen before the release:
>
> 1. (most important) The pom has been changed to use the apache 6 pom 
> as parent.  This deploys to the apache nexus instance.  In order for 
> this to work the project NEEDS to get permissions set up there.
> First, add a task to https://issues.apache.org/jira/browse/INFRA-1896 
> asking for scout access. The project needs some record on the dev list 
> indicating that it wants to use nexus.  A couple +1s to this part of 
> this email should suffice.  Brian is pretty quick about this but I'd 
> allow at least a day.
>
+1, I will add the subtask when we have sufficient "+1s" on this.
>
> 2. The pom isn't using the scout copy of the jaxr api any more, its 
> using the geronimo copy, which is what the tck is run against.  I 
> recommend removing the scout jaxr api copy and the current root/parent 
> pom and moving the scout project down a level to trunk (well, 
> branches/v1.1).  Right now I'm looking at site generation, hopefully 
> moving the site into the scout project will work fine.
+1. No need to maintain more then version of the spec api.
>
> 3. There need to be LICENSE and NOTICE files in the svn checkout 
> directory.  If all the code is developed at apache and there aren't 
> any other special circumstances then the ones generated and added to 
> the binary jar files will be fine.  You can copy them out of 
> target/maven-shared-archive-resources/META-INF/ after a build.  If the 
> project needs different/additional info in these files then please let 
> me know what it is, as it needs to be appended to the legal files in 
> the binary jar.
The defaults are prob just fine for us.
>
> 4. You should use the maven-release-plugin for the release.  I'll 
> provide more hints later on how.  However, the version should 
> currently be 1.1-SNAPSHOT until the release candidate is actually 
> made.  I'll be providing a pom patch soon that will include this change.
I'd love to learn how to use it. I had a helluva time with it before.
>
> 5. I'll be running the tck very shortly on the code currently in svn 
> together with the geronimo jaxb 2.1 spec release candidate.   We had 
> to re-roll the spec release due to some minor problems with the legal 
> files.  The current staging directory is
>
> https://repository.apache.org/content/repositories/geronimo-staging-029/
Thx David!
>
> thanks
> david jencks
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: scout-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: scout-dev-help@ws.apache.org
>
>


---------------------------------------------------------------------
To unsubscribe, e-mail: scout-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: scout-dev-help@ws.apache.org


Re: Steps towards 1.1 release, including use of apache nexus

Posted by David Jencks <da...@yahoo.com>.
On Jul 27, 2009, at 1:41 PM, Tom Cunningham wrote:

> David Jencks wrote:
>> I've been working via jira and private emails with Kurt to get  
>> scout ready for 1.1 release.
>>
>> Here are a few more things that need to happen before the release:
>>
>> 1. (most important) The pom has been changed to use the apache 6  
>> pom as parent.  This deploys to the apache nexus instance.  In  
>> order for this to work the project NEEDS to get permissions set up  
>> there.
>> First, add a task to https://issues.apache.org/jira/browse/ 
>> INFRA-1896 asking for scout access. The project needs some record  
>> on the dev list indicating that it wants to use nexus.  A couple  
>> +1s to this part of this email should suffice.  Brian is pretty  
>> quick about this but I'd allow at least a day.
> +1
>
> Can the project get some handholding on this part?

sure.  For starters.... after nexus is set up with the right  
permissions...

mvn release:prepare -Papache-release
# this checks a lot of stuff and creates the svn tag and may update  
the original tag to the next dev version (e.g. 1.2-SNAPSHOT)
mvn release:perform -Papache-release

this svn exports the new tag, builds it, and deploys it into the nexus  
repo.

Now you log into apache's nexus and close the staging repo created by  
the deploy.  This prevents more stuff being added. (up till now, you  
can keep running the release plugin on different projects and  
accumulate lots of stuff in one staging repo, for instance you might  
want to vote on several projects as one vote)

Now you call the vote on the dev list and wait as the +1s pour in.

After 72 hours and the vote passes you go back into nexus and promote  
the release.  It then gets into the releases area of nexus and gets  
synched to maven central pretty quickly.

I'm less familiar with site generation.  I tend to stage sites into my  
people.apache.org area using some stuff in my ~/.m2/settings.xml and  
mvn site:deploy.

>    Are there any docs on how to use the Apache instance (what's the  
> URL, etc)?

https://repository.apache.org/
http://www.sonatype.com/books/nexus-book/reference/

The maven component guide to releasing bits of maven is also useful:

http://maven.apache.org/developers/release/releasing.html

thanks
david jencks


>     I read the Nexus Maven chapter and it looks interesting.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: scout-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: scout-dev-help@ws.apache.org
>

---------------------------------------------------------------------
To unsubscribe, e-mail: scout-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: scout-dev-help@ws.apache.org


Re: Steps towards 1.1 release, including use of apache nexus

Posted by Tom Cunningham <tc...@redhat.com>.
David Jencks wrote:
> I've been working via jira and private emails with Kurt to get scout 
> ready for 1.1 release.
>
> Here are a few more things that need to happen before the release:
>
> 1. (most important) The pom has been changed to use the apache 6 pom 
> as parent.  This deploys to the apache nexus instance.  In order for 
> this to work the project NEEDS to get permissions set up there.
> First, add a task to https://issues.apache.org/jira/browse/INFRA-1896 
> asking for scout access. The project needs some record on the dev list 
> indicating that it wants to use nexus.  A couple +1s to this part of 
> this email should suffice.  Brian is pretty quick about this but I'd 
> allow at least a day. 
+1

Can the project get some handholding on this part?    Are there any docs 
on how to use the Apache instance (what's the URL, etc)?     I read the 
Nexus Maven chapter and it looks interesting.

---------------------------------------------------------------------
To unsubscribe, e-mail: scout-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: scout-dev-help@ws.apache.org


Re: Steps towards 1.1 release, including use of apache nexus

Posted by Kurt T Stam <ku...@gmail.com>.
Thanks David,

Going over it now.

--Kurt

David Jencks wrote:
> I forgot to note that the site reports show a bunch of really easy to 
> fix errors.... there are a few javadoc problems you see on the console 
> and the pmd report has a few suggestions.  With commit access these 
> could be fixed in 10 minutes :-)
>
> thanks
> david jencks
>
> On Jul 27, 2009, at 5:52 PM, David Jencks wrote:
>
>> I've posted a comment some more patches to SCOUT-82 that
>> -- update the pom with some stuff I left out for releasing
>> -- update the reports the site will get
>> -- improve (IMO) the site, and include the generated reports
>> -- has a suggestion on reorganizing the svn tree to eliminate the 
>> specs and the scout-parent.
>>
>> I think that with this pom the release will work with just
>>
>> mvn clean release:prepare
>> mvn release:perform
>>
>> My first try to check the tck had some odd results so I'm trying 
>> again.  I don't think there are any problems, but won't know for sure 
>> for a few hours.
>>
>> Brian is working on the nexus permissions and needs to know the 
>> groupId.  Since it used to be org.apache.ws.scout I'm assuming it 
>> will continue to be (updated in patch 4a)  and I'm going to add a 
>> comment to that effect in the jira task on infra 1896
>>
>>
>> thanks
>> david jencks
>>
>>
>>
>> On Jul 27, 2009, at 1:19 PM, David Jencks wrote:
>>
>>> I've been working via jira and private emails with Kurt to get scout 
>>> ready for 1.1 release.
>>>
>>> Here are a few more things that need to happen before the release:
>>>
>>> 1. (most important) The pom has been changed to use the apache 6 pom 
>>> as parent.  This deploys to the apache nexus instance.  In order for 
>>> this to work the project NEEDS to get permissions set up there.
>>> First, add a task to 
>>> https://issues.apache.org/jira/browse/INFRA-1896 asking for scout 
>>> access. The project needs some record on the dev list indicating 
>>> that it wants to use nexus.  A couple +1s to this part of this email 
>>> should suffice.  Brian is pretty quick about this but I'd allow at 
>>> least a day.
>>>
>>> 2. The pom isn't using the scout copy of the jaxr api any more, its 
>>> using the geronimo copy, which is what the tck is run against.  I 
>>> recommend removing the scout jaxr api copy and the current 
>>> root/parent pom and moving the scout project down a level to trunk 
>>> (well, branches/v1.1).  Right now I'm looking at site generation, 
>>> hopefully moving the site into the scout project will work fine.
>>>
>>> 3. There need to be LICENSE and NOTICE files in the svn checkout 
>>> directory.  If all the code is developed at apache and there aren't 
>>> any other special circumstances then the ones generated and added to 
>>> the binary jar files will be fine.  You can copy them out of 
>>> target/maven-shared-archive-resources/META-INF/ after a build.  If 
>>> the project needs different/additional info in these files then 
>>> please let me know what it is, as it needs to be appended to the 
>>> legal files in the binary jar.
>>>
>>> 4. You should use the maven-release-plugin for the release.  I'll 
>>> provide more hints later on how.  However, the version should 
>>> currently be 1.1-SNAPSHOT until the release candidate is actually 
>>> made.  I'll be providing a pom patch soon that will include this 
>>> change.
>>>
>>> 5. I'll be running the tck very shortly on the code currently in svn 
>>> together with the geronimo jaxb 2.1 spec release candidate.   We had 
>>> to re-roll the spec release due to some minor problems with the 
>>> legal files.  The current staging directory is
>>>
>>> https://repository.apache.org/content/repositories/geronimo-staging-029/ 
>>>
>>>
>>> thanks
>>> david jencks
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: scout-dev-unsubscribe@ws.apache.org
>>> For additional commands, e-mail: scout-dev-help@ws.apache.org
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: scout-dev-unsubscribe@ws.apache.org
>> For additional commands, e-mail: scout-dev-help@ws.apache.org
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: scout-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: scout-dev-help@ws.apache.org
>
>


---------------------------------------------------------------------
To unsubscribe, e-mail: scout-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: scout-dev-help@ws.apache.org


Re: Steps towards 1.1 release, including use of apache nexus

Posted by David Jencks <da...@yahoo.com>.
I forgot to note that the site reports show a bunch of really easy to  
fix errors.... there are a few javadoc problems you see on the console  
and the pmd report has a few suggestions.  With commit access these  
could be fixed in 10 minutes :-)

thanks
david jencks

On Jul 27, 2009, at 5:52 PM, David Jencks wrote:

> I've posted a comment some more patches to SCOUT-82 that
> -- update the pom with some stuff I left out for releasing
> -- update the reports the site will get
> -- improve (IMO) the site, and include the generated reports
> -- has a suggestion on reorganizing the svn tree to eliminate the  
> specs and the scout-parent.
>
> I think that with this pom the release will work with just
>
> mvn clean release:prepare
> mvn release:perform
>
> My first try to check the tck had some odd results so I'm trying  
> again.  I don't think there are any problems, but won't know for  
> sure for a few hours.
>
> Brian is working on the nexus permissions and needs to know the  
> groupId.  Since it used to be org.apache.ws.scout I'm assuming it  
> will continue to be (updated in patch 4a)  and I'm going to add a  
> comment to that effect in the jira task on infra 1896
>
>
> thanks
> david jencks
>
>
>
> On Jul 27, 2009, at 1:19 PM, David Jencks wrote:
>
>> I've been working via jira and private emails with Kurt to get  
>> scout ready for 1.1 release.
>>
>> Here are a few more things that need to happen before the release:
>>
>> 1. (most important) The pom has been changed to use the apache 6  
>> pom as parent.  This deploys to the apache nexus instance.  In  
>> order for this to work the project NEEDS to get permissions set up  
>> there.
>> First, add a task to https://issues.apache.org/jira/browse/ 
>> INFRA-1896 asking for scout access. The project needs some record  
>> on the dev list indicating that it wants to use nexus.  A couple  
>> +1s to this part of this email should suffice.  Brian is pretty  
>> quick about this but I'd allow at least a day.
>>
>> 2. The pom isn't using the scout copy of the jaxr api any more, its  
>> using the geronimo copy, which is what the tck is run against.  I  
>> recommend removing the scout jaxr api copy and the current root/ 
>> parent pom and moving the scout project down a level to trunk  
>> (well, branches/v1.1).  Right now I'm looking at site generation,  
>> hopefully moving the site into the scout project will work fine.
>>
>> 3. There need to be LICENSE and NOTICE files in the svn checkout  
>> directory.  If all the code is developed at apache and there aren't  
>> any other special circumstances then the ones generated and added  
>> to the binary jar files will be fine.  You can copy them out of  
>> target/maven-shared-archive-resources/META-INF/ after a build.  If  
>> the project needs different/additional info in these files then  
>> please let me know what it is, as it needs to be appended to the  
>> legal files in the binary jar.
>>
>> 4. You should use the maven-release-plugin for the release.  I'll  
>> provide more hints later on how.  However, the version should  
>> currently be 1.1-SNAPSHOT until the release candidate is actually  
>> made.  I'll be providing a pom patch soon that will include this  
>> change.
>>
>> 5. I'll be running the tck very shortly on the code currently in  
>> svn together with the geronimo jaxb 2.1 spec release candidate.    
>> We had to re-roll the spec release due to some minor problems with  
>> the legal files.  The current staging directory is
>>
>> https://repository.apache.org/content/repositories/geronimo-staging-029/
>>
>> thanks
>> david jencks
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: scout-dev-unsubscribe@ws.apache.org
>> For additional commands, e-mail: scout-dev-help@ws.apache.org
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: scout-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: scout-dev-help@ws.apache.org
>

---------------------------------------------------------------------
To unsubscribe, e-mail: scout-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: scout-dev-help@ws.apache.org


Re: Steps towards 1.1 release, including use of apache nexus

Posted by David Jencks <da...@yahoo.com>.
I've posted a comment some more patches to SCOUT-82 that
-- update the pom with some stuff I left out for releasing
-- update the reports the site will get
-- improve (IMO) the site, and include the generated reports
-- has a suggestion on reorganizing the svn tree to eliminate the  
specs and the scout-parent.

I think that with this pom the release will work with just

mvn clean release:prepare
mvn release:perform

My first try to check the tck had some odd results so I'm trying  
again.  I don't think there are any problems, but won't know for sure  
for a few hours.

Brian is working on the nexus permissions and needs to know the  
groupId.  Since it used to be org.apache.ws.scout I'm assuming it will  
continue to be (updated in patch 4a)  and I'm going to add a comment  
to that effect in the jira task on infra 1896


thanks
david jencks



On Jul 27, 2009, at 1:19 PM, David Jencks wrote:

> I've been working via jira and private emails with Kurt to get scout  
> ready for 1.1 release.
>
> Here are a few more things that need to happen before the release:
>
> 1. (most important) The pom has been changed to use the apache 6 pom  
> as parent.  This deploys to the apache nexus instance.  In order for  
> this to work the project NEEDS to get permissions set up there.
> First, add a task to https://issues.apache.org/jira/browse/ 
> INFRA-1896 asking for scout access. The project needs some record on  
> the dev list indicating that it wants to use nexus.  A couple +1s to  
> this part of this email should suffice.  Brian is pretty quick about  
> this but I'd allow at least a day.
>
> 2. The pom isn't using the scout copy of the jaxr api any more, its  
> using the geronimo copy, which is what the tck is run against.  I  
> recommend removing the scout jaxr api copy and the current root/ 
> parent pom and moving the scout project down a level to trunk (well,  
> branches/v1.1).  Right now I'm looking at site generation, hopefully  
> moving the site into the scout project will work fine.
>
> 3. There need to be LICENSE and NOTICE files in the svn checkout  
> directory.  If all the code is developed at apache and there aren't  
> any other special circumstances then the ones generated and added to  
> the binary jar files will be fine.  You can copy them out of target/ 
> maven-shared-archive-resources/META-INF/ after a build.  If the  
> project needs different/additional info in these files then please  
> let me know what it is, as it needs to be appended to the legal  
> files in the binary jar.
>
> 4. You should use the maven-release-plugin for the release.  I'll  
> provide more hints later on how.  However, the version should  
> currently be 1.1-SNAPSHOT until the release candidate is actually  
> made.  I'll be providing a pom patch soon that will include this  
> change.
>
> 5. I'll be running the tck very shortly on the code currently in svn  
> together with the geronimo jaxb 2.1 spec release candidate.   We had  
> to re-roll the spec release due to some minor problems with the  
> legal files.  The current staging directory is
>
> https://repository.apache.org/content/repositories/geronimo-staging-029/
>
> thanks
> david jencks
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: scout-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: scout-dev-help@ws.apache.org
>

---------------------------------------------------------------------
To unsubscribe, e-mail: scout-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: scout-dev-help@ws.apache.org