On 11/1/2010 3:05 PM, Marshall Schor wrote: > Here's a bit more info that might help debug this, perhaps. > > The release:prepare step shows, for the first transformation (from -SNAPSHOT > to > release) a mixture of "Transforming" and "Updating" messages, here's a sample > > > [INFO] Transforming 'UIMA Base: uimaj-test-util: JUnit utilities'... > [INFO] Transforming 'UIMA Base: uimaj-core'... > [INFO] Updating uimaj-test-util to 2.3.1 > [INFO] Transforming 'UIMA Base: jVinci: Vinci Transport Library'... > [INFO] Transforming 'UIMA Base: uimaj-adapter-vinci: Vinci Adapter'... > [INFO] Updating uimaj-core to 2.3.1 > [INFO] Updating jVinci to 2.3.1 > [INFO] Ignoring artifact version update for expression: 2.3.1 because it is > already updated. > [INFO] Transforming 'UIMA Base: uimaj-cpe: Collection Processing Engine'... > [INFO] Updating uimaj-core to 2.3.1 > [INFO] Updating uimaj-adapter-vinci to 2.3.1 > [INFO] Ignoring artifact version update for expression: 2.3.1 because it is > already updated. > [INFO] Updating jVinci to 2.3.1 > [INFO] Ignoring artifact version update for expression: 2.3.1 because it is > already updated. > [INFO] Updating uimaj-test-util to 2.3.1 > [INFO] Ignoring artifact version update for expression: 2.3.1 because it is > already updated. > [INFO] Transforming 'UIMA Base: uimaj-document-annotation'... > [INFO] Updating uimaj-core to 2.3.1 > [INFO] Updating uimaj-test-util to 2.3.1 > > > The same messages, at the end of release:prepare, show only the Transforming > messages: > > [INFO] Transforming 'UIMA Base: uimaj-test-util: JUnit utilities'... > [INFO] Transforming 'UIMA Base: uimaj-core'... > [INFO] Transforming 'UIMA Base: jVinci: Vinci Transport Library'... > [INFO] Transforming 'UIMA Base: uimaj-adapter-vinci: Vinci Adapter'... > [INFO] Transforming 'UIMA Base: uimaj-cpe: Collection Processing Engine > [INFO] Transforming 'UIMA Base: uimaj-document-annotation'... > [INFO] Transforming 'UIMA Base: uimaj-tools: Tools'... > [INFO] Transforming 'UIMA Base: uimaj-examples: SDK Examples'... > [INFO] Transforming 'UIMA Base: uimaj-adapter-soap: SOAP Adapter'...
These messages, from the release:prepare -DdryRun invocation were: [INFO] Transforming 'UIMA Base: uimaj-test-util: JUnit utilities'... [INFO] Transforming 'UIMA Base: uimaj-core'... [INFO] Updating uimaj-test-util to 2.3.2-SNAPSHOT [INFO] Transforming 'UIMA Base: jVinci: Vinci Transport Library'... [INFO] Transforming 'UIMA Base: uimaj-adapter-vinci: Vinci Adapter'... [INFO] Updating uimaj-core to 2.3.2-SNAPSHOT [INFO] Updating jVinci to 2.3.2-SNAPSHOT [INFO] Ignoring artifact version update for expression: 2.3.2-SNAPSHOT because it is already updated. [INFO] Transforming 'UIMA Base: uimaj-cpe: Collection Processing Engine'... [INFO] Updating uimaj-core to 2.3.2-SNAPSHOT [INFO] Updating uimaj-adapter-vinci to 2.3.2-SNAPSHOT [INFO] Ignoring artifact version update for expression: 2.3.2-SNAPSHOT because it is already updated. [INFO] Updating jVinci to 2.3.2-SNAPSHOT [INFO] Ignoring artifact version update for expression: 2.3.2-SNAPSHOT because it is already updated. [INFO] Updating uimaj-test-util to 2.3.2-SNAPSHOT [INFO] Ignoring artifact version update for expression: 2.3.2-SNAPSHOT because it is already updated. [INFO] Transforming 'UIMA Base: uimaj-document-annotation'... [INFO] Updating uimaj-core to 2.3.2-SNAPSHOT [INFO] Updating uimaj-test-util to 2.3.2-SNAPSHOT > I think the Updating ... and Ignoring artifact version update... come from the > part of the code that updates the properties. And these messages are missing > in > the 2nd transformation, which probably is indicative of this part of the code > not running at this point, for some reason. > > -Marshall > > > > > On 11/1/2010 2:01 PM, Marshall Schor wrote: >> On 11/1/2010 1:51 PM, Brett Porter wrote: >>> This was a known bug, fixed in maven-release-plugin 2.1. Are you using that >>> release? >> Yes. 2.1 shows in the help:effective-pom, and in this info message at the >> top >> of the release:prepare: >> >> [INFO] --- maven-release-plugin:2.1:prepare (default-cli) >> >> -Marshall Schor >>> On 01/11/2010, at 12:26 PM, Marshall Schor wrote: >>> >>>> I have a pom which has a property which has as a value "2.3.1-SNAPSHOT". >>>> >>>> The property is used to factor into one spot the version level for >>>> dependencies, >>>> where the dependencies are for other modules in a multi-module build (most >>>> of >>>> which have the same >>>> version level). >>>> >>>> When I do mvn release:prepare -DdryRun on a POM which includes this as a >>>> module, >>>> the release:prepare successfully updates the property, first, to "2.3.1" >>>> for the >>>> "tag", and then, for the next development version, to "2.3.2-SNAPSHOT". I >>>> think >>>> it figures out that this property is being used as a dependency version >>>> value, >>>> and matches it to version levels of things in the "Reactor", to figure out >>>> it >>>> needs updating. >>>> >>>> So far everything seems to be correct. >>>> >>>> But, if I do exactly the same thing, but leave off the "-DdryRun", it >>>> updates >>>> the property, first (as before), to "2.3.1" for the tag, but then does >>>> *not* >>>> update it for the next development version. >>>> >>>> Any idea why? Is this a (known) bug? I can, of course, work around this >>>> by >>>> manually updating this property to the right level and committing that >>>> change to >>>> the trunk. >>>> >>>> -Marshall Schor >>>> >>>> >>>> >>>> --------------------------------------------------------------------- >>>> To unsubscribe, e-mail: [email protected] >>>> For additional commands, e-mail: [email protected] >>>> >>> -- >>> Brett Porter >>> [email protected] >>> http://brettporter.wordpress.com/ >>> >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: [email protected] >>> For additional commands, e-mail: [email protected] >>> >>> >>> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> >> > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
