I tried to do full mvn install of build, uimaj and sandbox with the branches/depend-on-parent-pom-top-4 versions and everything worked. +1 Tommaso
2010/7/7 Marshall Schor <m...@schor.com> > fixed under https://issues.apache.org/jira/browse/UIMA-1830 > > Thanks for pointing this out... > > -Marshall > > On 7/7/2010 9:29 AM, Marshall Schor wrote: > > > > On 7/7/2010 6:22 AM, Jörn Kottmann wrote: > >> Trying to follow your instructions, why is the parent pom version in > >> build/uima-docbook-olink/pom.xml > >> still 2, shouldn't that be 4-SNAPSHOT ? > > I think you are right. Because the olink project is never intended to be > > released, however, I don't think it matters. This project is just an > artifact > > we use to share docbook olink resources, and (with our current build > process) > > will remain forevermore at the 1-SNAPSHOT level. > > > > -Marshall > >> Jörn > >> > >> Marshall Schor wrote: > >>> Version 4 of the parent-pom-top is ready for release. > >>> > >>> The following Jira's are fixed: > >>> > >>> * [UIMA-1827 <https://issues.apache.org/jira/browse/UIMA-1827>] - > Build of > >>> docbooks failing - because plugin repositories don't include the > snapshots > >>> * [UIMA-1828 <https://issues.apache.org/jira/browse/UIMA-1828>] - > change > >>> maven prereq level to 3.0-beta-1 > >>> > >>> > >>> The release is staged here: > >>> https://repository.apache.org/content/repositories/orgapacheuima-040/ > >>> > >>> 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-040/ > </url> > >>> </repository> > >>> </repositories> > >>> </profile> > >>> > >>> Then change in your workspace the version of parent-pom-top to 4 (from > >>> 4-SNAPSHOT), and confirm that builds work, using > >>> > >>> mvn clean install -Pstaged-release > >>> > >>> More background on this approach is here: > >>> http://maven.apache.org/guides/development/guide-testing-releases.html > >>> > >>> (One "easy" way to change this using eclipse is to do the following in > a > >>> workspace containing multiple projects (tested with eclipse 3.5) > >>> 1) select menu: Search -> File and type in the regex pattern: > >>> (<artifactId>parent-pom-top</artifactId>\R\s*)<version>4-SNAPSHOT > >>> 1a) be sure to click the case-sensitive and regex boxes > >>> 1b) select to look in *.xml files > >>> 2) click on "Replace", let it find the target(s), and for the replace > string use > >>> regex pattern: $1<version>4 > >>> 2a) tick the box - use regular expression > >>> 2b) click on preview, and inspect some or all of the proposed changes > to see > >>> they are ok, then push OK. > >>> > >>> This will change all the files at once. > >>> > >>> > >>> Also, please inspect the release artifacts to insure they have the > proper > >>> license /notice files. > >>> > >>> Finally, someone should verify that the parent-pom-top can be built > from the > >>> source-release.zip. > >>> > >>> Vote open for 72 hours. > >>> > >>> [ ] +1 > >>> [ ] +0 > >>> [ ] -1 > >>> > >>> Thanks for your help in checking/verifying, in advance! > >>> -Marshall > >>> > >>> > >> > >> > > >
