+1 from me. -Marshall
On 7/15/2010 10:33 PM, Marshall Schor wrote: > The remaining build artifacts have been released in a series of 4 staged > releases, all to be voted on. > > This is the first release of these artifacts (version 1 was canceled). > > Jira's fixed: > > > Sub-task > > * [UIMA-1757 <https://issues.apache.org/jira/browse/UIMA-1757>] - > use docbkx to create docbooks in place of current docbook tools > project > * [UIMA-1758 <https://issues.apache.org/jira/browse/UIMA-1758>] - > remove dependency on checked-out other projects > * [UIMA-1759 <https://issues.apache.org/jira/browse/UIMA-1759>] - > make project versioning more conventional > * [UIMA-1763 <https://issues.apache.org/jira/browse/UIMA-1763>] - > Switch to using Nexus for releasing > > > Bug > > * [UIMA-1051 <https://issues.apache.org/jira/browse/UIMA-1051>] - > doc build not working on Linux > * [UIMA-1805 <https://issues.apache.org/jira/browse/UIMA-1805>] - > change aggregate for build projects version to follow version > convention for those > * [UIMA-1806 <https://issues.apache.org/jira/browse/UIMA-1806>] - > fixes for releasing, in build poms > * [UIMA-1813 <https://issues.apache.org/jira/browse/UIMA-1813>] - > aggregate parent pom build fails rat test > > > Improvement > > * [UIMA-1814 <https://issues.apache.org/jira/browse/UIMA-1814>] - > Try making release:prepare work with all build projects by adding > in relative-path > > > Task > > * [UIMA-1755 <https://issues.apache.org/jira/browse/UIMA-1755>] - > Improve Maven build > * [UIMA-1816 <https://issues.apache.org/jira/browse/UIMA-1816>] - > update parent-pom-top references to version 2 > > > > The release is staged in 4 staging repositories: > > https://repository.apache.org/content/repositories/orgapacheuima-051 > > https://repository.apache.org/content/repositories/orgapacheuima-008/ > > https://repository.apache.org/content/repositories/orgapacheuima-010/ > > Suggested way to test: add this to your maven "settings" in the > <profiles> section: > > <profile> > <id>staged-release</id> > <repositories> > <repository> > <id>staged-release</id> > > <url>https://repository.apache.org/content/repositories/orgapacheuima-051/</url> > </repository> > <repository> > <id>staged-release2</id> > > <url>https://repository.apache.org/content/repositories/orgapacheuima-008/</url> > </repository> > <repository> > <id>staged-release3</id> > > <url>https://repository.apache.org/content/repositories/orgapacheuima-010/</url> > </repository> > <repository> > <id>staged-release4</id> > > <url>https://repository.apache.org/content/repositories/orgapacheuima-011/</url> > </repository> > </repositories> > <pluginRepositories> > <pluginRepository> > <id>staged-release-plugin</id> > > <url>https://repository.apache.org/content/repositories/orgapacheuima-051/</url> > </pluginRepository> > </pluginRepositories> > </profile> > > Note that all 4 staging repos are listed, and one is listed as a > pluginRepository, too, because its contents are referenced by some build > tooling. > > The trunk has already been updated to change references to these POMs to use > the > to-be-released version, ready for testing with these staging repositories, > when > you use the maven parameter -Pstaged-release to activate this profile. For > example: > > mvn install -Pstaged-release > > More background on this approach is here: > http://maven.apache.org/guides/development/guide-testing-releases.html > > Also, please inspect the release artifacts to insure they have the > proper license /notice files. > > Vote open for 72 hours. > > It would be very good to approve this quickly, because until the release > happens, other people may have errors when building (because they will refer > to > the to-be-released versions), unless they use the same "settings.xml" setup > described above. > > [ ] +1 > [ ] +0 > [ ] -1 > > Thanks for your help in checking/verifying, in advance! > > -Marshall Schor > > > >
