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: [email protected]
For additional commands, e-mail: [email protected]




---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to