ws-scout-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From David Jencks <>
Subject Re: Steps towards 1.1 release, including use of apache nexus
Date Tue, 28 Jul 2009 00:52:47 GMT
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 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

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 
> 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
> thanks
> david jencks
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message