Well, there're some times when you need to go backward. And it sometimes does
work, check this out:
in this exemple, the release plugin is asking again:
What is the new development version for "company-parent"?
(com.company:company-parent) 2-SNAPSHOT: : 1-SNAPSHOT
And it does work (see trace below.)
The difference with the previous example is that, here, it's not trying to
resolve project dependencies.
mvn release:prepare -DdryRun=true -Pjse
[INFO] Scanning for projects...
[INFO] Searching repository for plugin with prefix: 'release'.
[INFO] org.twdata.maven: checking for updates from central
[INFO] org.apache.maven.plugins: checking for updates from central
[INFO] org.codehaus.mojo: checking for updates from central
[INFO]
------------------------------------------------------------------------
[INFO] Building company-parent
[INFO] task-segment: [release:prepare] (aggregator-style)
[INFO]
------------------------------------------------------------------------
[INFO] [release:prepare]
[INFO] Verifying that there are no local modifications...
[INFO] Executing: svn --non-interactive status
[INFO] Working directory:
/Users/nodje/Documents/Project/company/company-parent-1
[INFO] Checking dependencies and plugins for snapshots ...
What is the release version for "company-parent"?
(com.company:company-parent) 1: : 1.0
What is SCM release tag or label for "company-parent"?
(com.company:company-parent) company-parent-1.0: :
What is the new development version for "company-parent"?
(com.company:company-parent) 2-SNAPSHOT: : 1-SNAPSHOT
[INFO] Transforming 'company-parent'...
[INFO] Not generating release POMs
[INFO] Executing preparation goals - since this is simulation mode it is
running against the original project, not the rewritten ones
[INFO] Executing goals 'clean verify'...
[INFO] Executing: mvn clean verify --no-plugin-updates -P jse
[INFO] Scanning for projects...
[INFO]
------------------------------------------------------------------------
[INFO] Building company-parent
[INFO] task-segment: [clean, verify]
[INFO]
------------------------------------------------------------------------
[INFO] artifact org.mortbay.jetty:maven-jetty-plugin: checking for
updates from central
[INFO] artifact org.apache.maven.plugins:maven-scm-plugin: checking
for updates from central
[INFO] [clean:clean]
[INFO] [site:attach-descriptor]
[INFO] Preparing source:jar
[WARNING] Removing: jar from forked lifecycle, to prevent recursive
invocation.
[INFO] No goals needed for project - skipping
[INFO] [source:jar {execution: default}]
[INFO] Preparing source:test-jar
[WARNING] Removing: jar from forked lifecycle, to prevent recursive
invocation.
[WARNING] Removing: test-jar from forked lifecycle, to prevent
recursive invocation.
[INFO] No goals needed for project - skipping
[INFO] [source:test-jar {execution: default}]
[INFO]
------------------------------------------------------------------------
[INFO] BUILD SUCCESSFUL
[INFO]
------------------------------------------------------------------------
[INFO] Total time: 8 seconds
[INFO] Finished at: Thu Sep 25 16:19:17 JST 2008
[INFO] Final Memory: 19M/47M
[INFO]
------------------------------------------------------------------------
[INFO] Full run would be checking in 1 files with message:
'[maven-release-plugin] prepare release company-parent-1.0'
[INFO] Full run would be tagging
/Users/nodje/Documents/Project/company/company-parent-1 with label:
'company-parent-1.0'
[INFO] Transforming 'company-parent'...
[INFO] Not removing release POMs
[INFO] Full run would be checking in 1 files with message:
'[maven-release-plugin] prepare for next development iteration'
[INFO] Release preparation simulation complete.
[INFO]
------------------------------------------------------------------------
[INFO] BUILD SUCCESSFUL
[INFO]
------------------------------------------------------------------------
[INFO] Total time: 2 minutes 8 seconds
[INFO] Finished at: Thu Sep 25 16:19:17 JST 2008
[INFO] Final Memory: 9M/30M
[INFO]
------------------------------------------------------------------------
Brett Porter wrote:
>
> perhaps it is not letting you go backwards... does 3-SNAPSHOT work?
>
> - Brett
>
> 2008/9/22 nodje <[EMAIL PROTECTED]>:
>>
>> hum, I need some help here please. The Maven Release plugin is somehow
>> not
>> working as expected.
>> To put the problem simply:
>>
>> mvn release:prepare -DdryRun=true
>> [INFO] Scanning for projects...
>> [INFO] Searching repository for plugin with prefix: 'release'.
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] Building commons-xml
>> [INFO] task-segment: [release:prepare] (aggregator-style)
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] [release:prepare]
>> [INFO] Verifying that there are no local modifications...
>> [INFO] Executing: svn --non-interactive status
>> [INFO] Working directory:
>> /Users/nodje/Documents/project/company/commons-xml-1.0-SNAPSHOT
>> [INFO] Checking dependencies and plugins for snapshots ...
>> There are still some remaining snapshot dependencies.: Do you want to
>> resolve them now? (yes/no) no: : yes
>> Dependency type to resolve,: specify the selection number ( 0:All
>> 1:Project
>> Dependencies 2:Plugins 3:Reports 4:Extensions ): (0/1/2/3) 1: :
>> Resolve Project Dependency Snapshots.: 'com.company:company-parent' set
>> to
>> release? (yes/no) yes: :
>> What is the next development version? (2-SNAPSHOT) 2-SNAPSHOT: : 1
>>
>> What is the next development version? (2-SNAPSHOT) 2-SNAPSHOT: : 1
>>
>> What is the next development version? (2-SNAPSHOT) 2-SNAPSHOT: : 1
>>
>> What is the next development version? (2-SNAPSHOT) 2-SNAPSHOT: : 1
>>
>> What is the next development version? (2-SNAPSHOT) 2-SNAPSHOT: : 1
>>
>> What is the next development version? (2-SNAPSHOT) 2-SNAPSHOT: : 1
>>
>> What is the next development version? (2-SNAPSHOT) 2-SNAPSHOT: : 1
>>
>> What is the next development version? (2-SNAPSHOT) 2-SNAPSHOT: : 1
>>
>> What is the next development version? (2-SNAPSHOT) 2-SNAPSHOT: : 1
>>
>> What is the next development version? (2-SNAPSHOT) 2-SNAPSHOT: : 1
>>
>> What is the next development version? (2-SNAPSHOT) 2-SNAPSHOT: : 1
>>
>> What is the next development version? (2-SNAPSHOT) 2-SNAPSHOT: : 1
>>
>> What is the next development version? (2-SNAPSHOT) 2-SNAPSHOT: : 1
>>
>> What is the next development version? (2-SNAPSHOT) 2-SNAPSHOT: : 1
>>
>> What is the next development version? (2-SNAPSHOT) 2-SNAPSHOT: :
>> 1.1-SNAPSHOT
>>
>> What is the next development version? (2-SNAPSHOT) 2-SNAPSHOT: :
>> 2-SNAPSHOT
>> What is the release version for "commons-xml"?
>> (com.company.commons:commons-xml) 1.0: :
>>
>> In short, it would in this case never accept any values different than
>> the
>> default one.
>>
>> cheers
>>
>>
>> nodje wrote:
>>>
>>> I'm a newbie with the release plugin and have a hard time already
>>> managing
>>> dependencies.
>>> After much thinking, I end up with this process:
>>> - branch first the current trunk version to a branch named 1.0-SNAPSHOT.
>>> The trunk version becomes 1.1-SNAPSHOT
>>> - release the branch version: the release is the 1.0 version, the branch
>>> becomes 1.0.1-SNAPSHOT
>>>
>>> I need the branch step first in order to be able to fix bug that could
>>> appear on the 1.0 version. A tag not being modifiable, I need to be able
>>> to rerelease from the 1.0-SNAPSHOT line. And so came the idea of the
>>> 1.0.1-SNAPSHOT version.
>>>
>>> If anyone has another solution for this problem, he is much welcome!
>>>
>>> Anyways, while trying this I'm confronted to a Maven release-plugin
>>> problem:
>>>
>>> I'm trying to release a component that depends only on the
>>> company-parent.pom (that follows the 1-SNAPSHOT -> 2-SNAPSHOT release
>>> numbering pattern)
>>>
>>> I want the development version to be updated to depend on the released
>>> version 1 or 1.1-SNAPSHOT of the company-parent pom.
>>>
>>> here's the trace of the command:
>>>
>>> mvn release:prepare -DdryRun=true
>>> [INFO] Scanning for projects...
>>> [INFO] Searching repository for plugin with prefix: 'release'.
>>> [INFO]
>>> ------------------------------------------------------------------------
>>> [INFO] Building commons-xml
>>> [INFO] task-segment: [release:prepare] (aggregator-style)
>>> [INFO]
>>> ------------------------------------------------------------------------
>>> [INFO] [release:prepare]
>>> [INFO] Verifying that there are no local modifications...
>>> [INFO] Executing: svn --non-interactive status
>>> [INFO] Working directory:
>>> /Users/nodje/Documents/project/company/commons-xml-1.0-SNAPSHOT
>>> [INFO] Checking dependencies and plugins for snapshots ...
>>> There are still some remaining snapshot dependencies.: Do you want to
>>> resolve them now? (yes/no) no: : yes
>>> Dependency type to resolve,: specify the selection number ( 0:All
>>> 1:Project Dependencies 2:Plugins 3:Reports 4:Extensions ): (0/1/2/3) 1:
>>> :
>>> Resolve Project Dependency Snapshots.: 'com.company:company-parent' set
>>> to
>>> release? (yes/no) yes: :
>>> What is the next development version? (2-SNAPSHOT) 2-SNAPSHOT: : 1
>>>
>>> What is the next development version? (2-SNAPSHOT) 2-SNAPSHOT: : 1
>>>
>>> What is the next development version? (2-SNAPSHOT) 2-SNAPSHOT: : 1
>>>
>>> What is the next development version? (2-SNAPSHOT) 2-SNAPSHOT: : 1
>>>
>>> What is the next development version? (2-SNAPSHOT) 2-SNAPSHOT: : 1
>>>
>>> What is the next development version? (2-SNAPSHOT) 2-SNAPSHOT: : 1
>>>
>>> What is the next development version? (2-SNAPSHOT) 2-SNAPSHOT: : 1
>>>
>>> What is the next development version? (2-SNAPSHOT) 2-SNAPSHOT: : 1
>>>
>>> What is the next development version? (2-SNAPSHOT) 2-SNAPSHOT: : 1
>>>
>>> What is the next development version? (2-SNAPSHOT) 2-SNAPSHOT: : 1
>>>
>>> What is the next development version? (2-SNAPSHOT) 2-SNAPSHOT: : 1
>>>
>>> What is the next development version? (2-SNAPSHOT) 2-SNAPSHOT: : 1
>>>
>>> What is the next development version? (2-SNAPSHOT) 2-SNAPSHOT: : 1
>>>
>>> What is the next development version? (2-SNAPSHOT) 2-SNAPSHOT: : 1
>>>
>>> What is the next development version? (2-SNAPSHOT) 2-SNAPSHOT: :
>>> 1.1-SNAPSHOT
>>>
>>> What is the next development version? (2-SNAPSHOT) 2-SNAPSHOT: :
>>> 2-SNAPSHOT
>>> What is the release version for "commons-xml"?
>>> (com.company.commons:commons-xml) 1.0: :
>>> What is SCM release tag or label for "commons-xml"?
>>> (com.company.commons:commons-xml) commons-xml-1.0: :
>>> What is the new development version for "commons-xml"?
>>> (com.company.commons:commons-xml) 1.1-SNAPSHOT: : 1.0.1-SNAPSHOT
>>> [INFO] Transforming 'commons-xml'...
>>> [INFO] Not generating release POMs
>>> [INFO] Executing preparation goals - since this is simulation mode it is
>>> running against the original project, not the rewritten ones
>>> [INFO] Executing goals 'clean verify'...
>>> [INFO] Executing: mvn clean verify --no-plugin-updates
>>> [INFO] Scanning for projects...
>>> [INFO]
>>> ------------------------------------------------------------------------
>>> [INFO] Building commons-xml
>>> [INFO] task-segment: [clean, verify]
>>> [INFO]
>>> ------------------------------------------------------------------------
>>> [INFO] [clean:clean]
>>> [INFO] Deleting directory
>>> /Users/nodje/Documents/project/company/commons-xml-1.0-SNAPSHOT/target
>>> [INFO] [resources:resources]
>>> [INFO] Using default encoding to copy filtered resources.
>>> [INFO] [compiler:compile]
>>> [INFO] Compiling 2 source files to
>>> /Users/nodje/Documents/project/company/commons-xml-1.0-SNAPSHOT/target/classes
>>> [INFO] [resources:testResources]
>>> [INFO] Using default encoding to copy filtered resources.
>>> [INFO] [compiler:testCompile]
>>> [INFO] Nothing to compile - all classes are up to date
>>> [INFO] [surefire:test]
>>> [INFO] No tests to run.
>>> [INFO] [jar:jar]
>>> [INFO] Building jar:
>>> /Users/nodje/Documents/project/company/commons-xml-1.0-SNAPSHOT/target/stageof.jar
>>> [INFO] Preparing source:jar
>>> [WARNING] Removing: jar from forked lifecycle, to prevent
>>> recursive invocation.
>>> [INFO] No goals needed for project - skipping
>>> [INFO] [source:jar {execution: default}]
>>> [INFO] Building jar:
>>> /Users/nodje/Documents/project/company/commons-xml-1.0-SNAPSHOT/target/stageof-sources.jar
>>> [INFO] Preparing source:test-jar
>>> [WARNING] Removing: jar from forked lifecycle, to prevent
>>> recursive invocation.
>>> [WARNING] Removing: test-jar from forked lifecycle, to prevent
>>> recursive invocation.
>>> [INFO] No goals needed for project - skipping
>>> [INFO] [source:test-jar {execution: default}]
>>> [INFO] Building jar:
>>> /Users/nodje/Documents/project/company/commons-xml-1.0-SNAPSHOT/target/stageof-test-sources.jar
>>> [INFO]
>>> ------------------------------------------------------------------------
>>> [INFO] BUILD SUCCESSFUL
>>> [INFO]
>>> ------------------------------------------------------------------------
>>> [INFO] Total time: 4 seconds
>>> [INFO] Finished at: Fri Sep 19 20:48:08 CST 2008
>>> [INFO] Final Memory: 27M/65M
>>> [INFO]
>>> ------------------------------------------------------------------------
>>> [INFO] Full run would be checking in 1 files with message:
>>> '[maven-release-plugin] prepare release commons-xml-1.0'
>>> [INFO] Full run would be tagging
>>> /Users/nodje/Documents/project/company/commons-xml-1.0-SNAPSHOT with
>>> label: 'commons-xml-1.0'
>>> [INFO] Transforming 'commons-xml'...
>>> [INFO] Not removing release POMs
>>> [INFO] Full run would be checking in 1 files with message:
>>> '[maven-release-plugin] prepare for next development iteration'
>>> [INFO] Release preparation simulation complete.
>>> [INFO]
>>> ------------------------------------------------------------------------
>>> [INFO] BUILD SUCCESSFUL
>>> [INFO]
>>> ------------------------------------------------------------------------
>>> [INFO] Total time: 1 minute 5 seconds
>>> [INFO] Finished at: Fri Sep 19 20:48:08 CST 2008
>>> [INFO] Final Memory: 9M/30M
>>> [INFO]
>>> ------------------------------------------------------------------------
>>>
>>> As you can see, the question 'What is the next development version?
>>> (2-SNAPSHOT) 2-SNAPSHOT: :'
>>> doesn't seem to accept anything else than the proposed default answer.
>>>
>>> Why is that so? Is it a bug or is there something I'm missing here?
>>> I'm using Maven-2.0.9
>>>
>>> cheers
>>>
>>
>> --
>> View this message in context:
>> http://www.nabble.com/problem-with-release%3Aprepare-in-resolving-dependency-tp19572360p19603976.html
>> Sent from the Maven - Users mailing list archive at Nabble.com.
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
>
>
>
> --
> Brett Porter
> Blog: http://blogs.exist.com/bporter/
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
--
View this message in context:
http://www.nabble.com/problem-with-release%3Aprepare-in-resolving-dependency-tp19572360p19664319.html
Sent from the Maven - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
