You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by Marshall Schor <ms...@schor.com> on 2010/10/01 00:05:39 UTC
[VOTE] Release build poms: parent-pom-top and parent-pom-docbook
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
[VOTE][RESULT] Release build poms: parent-pom-top and parent-pom-docbook
Posted by Marshall Schor <ms...@schor.com>.
The vote passes:
+1 Jörn Kottmann
+1 Tommasso Teofili
+1 Marshall Schor
No other votes were received.
-Marshall Schor
On 9/30/2010 6:05 PM, 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
>
>
Re: [VOTE] Release build poms: parent-pom-top and parent-pom-docbook
Posted by Jörn Kottmann <ko...@gmail.com>.
+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
Re: [VOTE] Release build poms: parent-pom-top and parent-pom-docbook
Posted by Marshall Schor <ms...@schor.com>.
Being that these were such small changes, and concerns just build tooling, and
with very little likelyhood of causing release issues, I plan to close the vote
on these a bit early - this evening.
-Marshall
On 9/30/2010 6:05 PM, 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
>
>
Re: [VOTE] Release build poms: parent-pom-top and parent-pom-docbook
Posted by Tommaso Teofili <to...@gmail.com>.
+1
Tommaso
2010/10/1 Marshall Schor <ms...@schor.com>
> 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
>
Re: [VOTE] Release build poms: parent-pom-top and parent-pom-docbook
Posted by Marshall Schor <ms...@schor.com>.
I spot checked parent-pom-docbook for the proper source-zip - looks fine, has
the licenses / notice files, builds from source fine with maven-3.0-rc3.
I built the docbooks ok, and uimaj-distr ran without the extra @pre warnings.
+1 to release.
-Marshall
On 9/30/2010 6:05 PM, 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
>
>