forgot to insert the link to referenced note, see below On 10/21/2010 10:15 AM, Marshall Schor wrote: > I'm canceling this vote (to save other's time in doing reviews at this point). > > I plan to follow the release process 3b referenced in this note, and > essentially
http://markmail.org/thread/ryh6voctne6vqb7d > keep the trunk projects referring to SNAPSHOT releases of the build tooling. > We'll see if that works when I try doing release:prepare/perform :-) > > So - no review of the build tooling updates until we are asked to review for > release, a UIMA release. > > -Marshall > > On 10/14/2010 9:19 AM, Marshall Schor wrote: >> We solved >> >> * [UIMA-1900 <https://issues.apache.org/jira/browse/UIMA-1900>] - make >> parent-poms build their dependents for easier releasing >> * [UIMA-1901 <https://issues.apache.org/jira/browse/UIMA-1901>] - >> upgrade to >> current maven plugin versions >> >> This was built using the Maven 3 release (non beta, non RC). >> >> The Parent Poms have been released to the staging repository, here: >> https://repository.apache.org/content/repositories/orgapacheuima-007/ >> >> 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-007/</url> >> </repository> >> </repositories> >> </profile> >> >> and then run your maven builds with the extra parameter -Pstaged-release >> >> To update the 2.3.1 artifacts to depend on these new build tooling versions, >> you can use >> Eclipse's search - file, specify pom.xml as the file, and use a regular >> expression to find >> the previous value, e.g., one or more of the following: >> >> (?s)(parent-pom-top</artifactId>\s*<version>)5< >> (?s)(parent-pom-docbook</artifactId>\s*<version>)4< >> (?s)(parent-pom-ibm-notice</artifactId>\s*<version>)4< >> (?s)(parent-pom-eclipse-plugins-ibm-notice</artifactId>\s*<version>)4< >> (?s)(parent-pom-distr</artifactId>\s*<version>)3< >> >> then click on Replace... and use the replace argument $16 (means $1 >> followed by >> a 6 (for top), or $15, or $14, or $13, then press "Preview" and check the >> results before proceeding :-) . >> >> I've done this in my local workspace, and have successfully built uimaj, >> uima-as, add-ons, and the uimaj-distr using these new build versions. >> >> Thanks for your votes. >> >> -Marshall >> >> P.S., the new approach of having parent-poms have their direct children as >> <modules> worked like a charm - it was very easy to release all the dependent >> parts - Maven updated all the parts' versions correctly, and the release was >> just mvn release:prepare, followed by mvn release:perform. >> >> -Marshall >> >> >> >> >> >
