[
https://jira.codehaus.org/browse/MRELEASE-138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=313314#comment-313314
]
Hannes Kogler edited comment on MRELEASE-138 at 11/10/12 4:48 AM:
------------------------------------------------------------------
thanx for attaching my patch, but how will the release-process will take place
now?
moreover there are several other issues who rely on the same problem:
http://jira.codehaus.org/browse/MRELEASE-633
http://jira.codehaus.org/browse/MRELEASE-516
http://jira.codehaus.org/browse/MRELEASE-261
.. now flat directory structure should also be supported in combination with
CVS! just using the commitByProject flag!
PLEASE just make a NEW RELEASE of THE PLUGIN with those changes to honor the
time (and money) spent into these issues!
Who has RELEASE rights for the Maven Release Plugin???
was (Author: ntshko):
thanx for attaching my patch, but how will the release-process will take
place now?
moreover there are several other issues who rely on the same problem:
http://jira.codehaus.org/browse/MRELEASE-633
http://jira.codehaus.org/browse/MRELEASE-516
http://jira.codehaus.org/browse/MRELEASE-261
.. now flat directory structure should also be supported in combination of CVS!
just using the commitByProject flag!
PLEASE just make a NEW RELEASE of THE PLUGIN with those changes to honor the
time (and money) spent into these issues!
Who has RELEASE rights for the Maven Release Plugin???
> release:prepare fails when checking in modified POMs of a multi-modules
> project
> -------------------------------------------------------------------------------
>
> Key: MRELEASE-138
> URL: https://jira.codehaus.org/browse/MRELEASE-138
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: scm
> Affects Versions: 2.0-beta-4
> Environment: WinXP + Eclipse
> Reporter: ol
> Assignee: Robert Scholte
> Priority: Critical
> Attachments: MRELEASE-138.patch
>
>
> Here is the project structure on the disk :
> {noformat}
> c:\javadev\prj\myproject\module1
> c:\javadev\prj\myproject\module2
> c:\javadev\prj\myproject\master
> {noformat}
> These 3 folders represent the 3 eclipse projects, each one containing a
> pom.xml.
> The master project's pom is the parent of the modules.
> When I execute the release:prepare goal, Everything works fine (it asks to me
> the tag name, the next dev version, ...) until I receive this error :
> {noformat}
> [INFO] Checking in modified POMs...
> [INFO]
> ------------------------------------------------------------------------
> [ERROR] BUILD ERROR
> [INFO]
> ------------------------------------------------------------------------
> [INFO] An error is occurred in the checkin process:
> C:\javadev\prj\myproject\module1\pom.xml was not contained in
> C:\javadev\prj\myproject\master
> [INFO]
> ------------------------------------------------------------------------
> [DEBUG] Trace
> org.apache.maven.lifecycle.LifecycleExecutionException: An error is occurred
> in the checkin process: C:\javadev\prj\myproject\module1\pom.xml was not
> contained in C:\javadev\prj\myproject\master
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:559)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:488)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:458)
> ....
> {noformat}
> The problem is that the project structure is the only one that can be used
> with eclipse.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
