uima-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jörn Kottmann <kottm...@gmail.com>
Subject Re: [VOTE] Release build poms: parent-pom-top and parent-pom-docbook
Date Fri, 01 Oct 2010 07:27:03 GMT
  +1

Jörn

On 10/1/10 12:05 AM, Marshall Schor wrote:
>   There are two Jiras solved in this release.
>
> parent-pom-top: https://issues.apache.org/jira/browse/UIMA-1884 (add @pre to
> javadoc known tags)
> parent-pom-docbook: https://issues.apache.org/jira/browse/UIMA-1888  (docbook
> builds missing a file)
>
> These poms have been released to the staging repository, along with 6 other
> build poms that recursively depend on these poms.
>
> The staging repository is here:
>
> https://repository.apache.org/content/repositories/orgapacheuima-001/
>
> To enable you to test this, please add this stanza to your settings.xml in the
> .m2 spot:
>
>      <profile>
>        <id>staged-release</id>
>        <repositories>
>          <repository>
>            <id>staged-release</id>
>            <url>https://repository.apache.org/content/repositories/orgapacheuima-001/</url>
>          </repository>
>        </repositories>
>      </profile>
>
> and then run your maven builds with the extra parameter -Pstaged-release
>
> I've updated a couple of the actual 2.3.1 artifacts to depend on these new build
> tooling versions, in SVN:
> uima-docbook-overview-and-setup and
> uimaj-distr.
>
> (I have the others ready to update, as soon as the vote passes).
>
> To test, besides the normal inspections, you can try:
>
> a1) delete from your local .m2 repo ... org/apache/uima/uima-docbook-olink  (to
> force redownloading it)
> a2) mvn package  -Pstaged-release
> on the uimaj-docbook-overview-and-setup
>
> and
> b1) try running mvn package -Pstaged-release,apache-release
> on the uimaj-distr project - it should build javadocs without complaining about
> an unknown @pre tag among its voluminous output.  The apache-release profile is
> needed to get this to invoke the javadoc step that the apache release does.  It
> won't actually do any releases...  You'll see lots of javadoc errors - I'm not
> planning on holding up a release just for these - we can fix these over time...
> These are in javadocs for "internal" code; our public api javadocs have been
> cleaned up.
>
> Of course, you can manually change any other docbook projects to test them -
> just update their parent to the next version :-).
>
> Thanks for your votes.  I think we're getting closer to a real 2.3.1 release.
>
> -Marshall Schor


Mime
View raw message