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 incorporating change to docbkx 2.0.11 version
Date Mon, 06 Sep 2010 07:09:43 GMT
  On 9/5/10 11:13 PM, Marshall Schor wrote:
>   This version upgrade removes the need for special one-time setups to get docbkx
> to work :-)
> Updated: parent-pom-docbook - to version 3.  Jira fixed:
> https://issues.apache.org/jira/browse/UIMA-1862
> Also updated and being released: parent poms that refer to this as a parent, to
> refer to the new version.
> The release artifacts are staged in the Apache Nexus repository.  Unfortunately,
> I "closed" the initial staging repository leaving out one of the parent-poms so
> I had to open another staging repository just for it.  Please consider this
> release to consist of both staging repositories:
> https://repository.apache.org/content/repositories/orgapacheuima-033/
> https://repository.apache.org/content/repositories/orgapacheuima-034/
> To enable you to test this, please follow the same procedures as before for
> testing build poms:
> 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-033/</url>
>          </repository>
>          <repository>
>            <id>staged-release2</id>
>            <url>https://repository.apache.org/content/repositories/orgapacheuima-034/</url>
>          </repository>
>        </repositories>
>      </profile>
> For testing, I've gone ahead and updated the trunk projects in uimaj that build
> docbooks (our 4 "books" plus the PearPackagingMavenPlugin) to refer to this new
> version.  So a good test is to
> cd ..../aggregate-uimaj-docbooks
> mvn clean install -Pstaged-release
> and
> cd ..../PearPackagingMavenPlugin
> mvn clean install -Pstaged-release
> Of course, any other project (e.g., sandbox projects) that have docbooks, can
> (and probably should) be used to test this - but for those, please update the
> version of the parent poms to specify the poms being released (version 2 needs
> to be changed to version 3), and include the -Pstaged-release parameter to let
> maven use the artifacts from the staging repositories.
> Also, please inspect the release artifacts to insure they have the proper
> license /notice files, and can be built from the source-release zips.

Where must the license and notice files be placed ? After building the
Pear Packaging Maven Plugin jar file it contained the two files
in the META-INF folder.

How can the source release zip be created ? Do I have to build the uima 
source distribution or is there a way to build it for an individual 
project ?


View raw message