The reference to the master pom will be changed to 0.19 again when it's available in Maven Central (after a successful vote). Matt changed some configuration for the rat plugin which checks for missing license headers during the release and new committers were added. The changes don't affect daily development so it's okay to temporarily revert the master pom version in the project to 0.10 so Jenkins won't complain about the missing master pom.
Jasha On 9 January 2013 00:04, Chris Geer <[email protected]> wrote: > Does this affect 0.19 since it currently uses the 0.19 rave-master? Does > the tag need to be recut? > > On Tue, Jan 8, 2013 at 10:20 AM, <[email protected]> wrote: > > > Author: mfranklin > > Date: Tue Jan 8 17:20:35 2013 > > New Revision: 1430393 > > > > URL: http://svn.apache.org/viewvc?rev=1430393&view=rev > > Log: > > Returning trunk to prior release of Rave Master POM > > > > Modified: > > rave/trunk/pom.xml > > > > Modified: rave/trunk/pom.xml > > URL: > > > http://svn.apache.org/viewvc/rave/trunk/pom.xml?rev=1430393&r1=1430392&r2=1430393&view=diff > > > > > ============================================================================== > > --- rave/trunk/pom.xml (original) > > +++ rave/trunk/pom.xml Tue Jan 8 17:20:35 2013 > > @@ -24,7 +24,7 @@ > > <parent> > > <groupId>org.apache.rave</groupId> > > <artifactId>rave-master</artifactId> > > - <version>0.19</version> > > + <version>0.10</version> > > <relativePath>../rave-master-pom/pom.xml</relativePath> > > </parent> > > > > > > > > >
