Re: [VOTE] [CANCELED] Release of build parent poms and tools, version 1

[Marshall Schor <ms...@schor.com>]

I'm canceling this vote, because of Jiras
https://issues.apache.org/jira/browse/UIMA-1822 and
https://issues.apache.org/jira/browse/UIMA-1823
The artifacts won't be released; I'll increment the release number,
though, rather than reuse it, per Apache / Maven suggested best practice.

-Marshall

On 6/23/2010 4:31 PM, Marshall Schor wrote:
> The way we use Maven has been realigned to conform with more
> conventional ways of using Maven and best practices.  This includes
> using the common Apache Release parent POM, the maven release plugin, a
> maven plugin for running the docbook processing, and many other
> improvements.
>
> The top parent pom for uima projects is already released (at version
> 2).  This release is for the remaining build tools and parent poms, and
> is at version 1.
>
> 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 here:
> 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-010/</url>
>         </repository>
>       </repositories>
>     </profile>
>
> Please verify this by changing references to 1-SNAPSHOT versions of the
> build artifacts (except the parent-pom-top which is at version 2, and 
> uima-docbook-olink project, which is not being released) to version 1
> (without the SNAPSHOT), and see if things build, using the command
>
>   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.
>
> [ ] +1
> [ ] +0
> [ ] -1
>
> Thanks for your help in checking/verifying, in advance!
>
> -Marshall
>
>
>
> -Marshall
>
>
>
>
>