uima-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Tommaso Teofili <tommaso.teof...@gmail.com>
Subject Re: [VOTE] Release build poms incorporating change to docbkx 2.0.11 version
Date Wed, 08 Sep 2010 05:43:15 GMT
+1 to release.
Tommaso

2010/9/7 Marshall Schor <msa@schor.com>

>  +1 to release.
>
> I downloaded and built all of these artifacts on a separate computer (a
> Mac).  I
> did find one "cosmetic" error, which doesn't affect the function.  The
> component
> parent-pom-eclipse-plugins-ibm-notice is running part of its parent pom's
> build
> process intended only for actual eclipse plugins - this part renames the
> build
> artifact to follow OSGi naming rules.
>
> Because of this, the zip file that is made for source-release creates a top
> level folder with a name parent-pom-eclipse-plugins-ibm-notice_3.0.0.  This
> doesn't hurt anything (other than cause some confusion).  It's easily
> fixable by
> including a special 0-length file named
> "marker-file-identifying-parent-pom-eclipse-plugins" which, if present,
> prevents
> the build process from running those steps.  So I'll fix that and it will
> get
> picked up with the next release (at some time in the future)...
>
> I also confirmed that with the new build tooling, the docbooks in uimaj
> built.
>
> As a bonus, I did all this on a fresh install of Helios (Eclipse 3.6) where
> I
> installed a snapshot build of the m2eclipse; that worked fine.  For those
> interested, I got the snapshot from here:
>
> https://repository.sonatype.org/content/sites/forge-sites/m2e/0.11.1/N/0.11.1.201009041932
>
> -Marshall
>
> On 9/5/2010 5: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.
> >
> > Vote open for 72 hours.
> >
> > Thanks for your vote; with this change, we're removing one of the onerous
> > one-time-setup steps (I'll update the website as soon as this is
> approved).
> >
> > -Marshall
> >
> >
> >
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message