[
http://jira.codehaus.org/browse/MRELEASE-261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=205043#action_205043
]
Eric Miles commented on MRELEASE-261:
-------------------------------------
Dennis,
The good news is that the prepare goal SOMEWHAT worked. While it was able to
change the POMs and check those in appropriately, however it failed on tagging
the release. Instead of having tag for each one of the modules (which is what
I would expect), only the parent pom project was tagged and was tagged in an
odd way. I'm attaching a screenshot, but the tag contains a branches, tags,
and trunk folder underneath the tag. Take a look at the odd-tags.png file I
have attached.
Ignoring the tagging issue, I attempted to perform the release itself. At this
point I received the same issue I was receiving before, before I added the
-DcommitByProject JVM parameter you identifiedL
{noformat}
emiles-macbook:release-parent emiles$ mvn release:perform -DcommitByProject=true
[INFO] Scanning for projects...
[INFO] Reactor build order:
[INFO] Unnamed - com.captechventures:release-parent:pom:0.0.3-SNAPSHOT
[INFO] Unnamed - com.captechventures:release-module1:jar:0.0.3-SNAPSHOT
[INFO] Unnamed - com.captechventures:release-module2:jar:0.0.3-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO] Building Unnamed - com.captechventures:release-parent:pom:0.0.3-SNAPSHOT
[INFO] task-segment: [release:perform] (aggregator-style)
[INFO] ------------------------------------------------------------------------
[INFO] [release:perform {execution: default-cli}]
[INFO] Checking out the project to perform the release ...
[INFO] Executing: /bin/sh -c cd
/Users/emiles/Projects/release-workspace/release-parent/target && svn
--non-interactive checkout
http://localhost/dev/release-parent/tags/release-parent-0.0.2
/Users/emiles/Projects/release-workspace/release-parent/target/checkout
[INFO] Working directory:
/Users/emiles/Projects/release-workspace/release-parent/target
[INFO] Executing goals 'deploy'...
[WARNING] Base directory is a file. Using base directory as POM location.
[WARNING] Maven will be executed in interactive mode, but no input stream has
been configured for this MavenInvoker instance.
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Error executing Maven.
Working directory
"/Users/emiles/Projects/release-workspace/release-parent/target/checkout/Users/emiles/Projects/release-workspace/release-parent"
does not exist!
[INFO] ------------------------------------------------------------------------
[INFO] For more information, run Maven with the -e switch
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 5 seconds
[INFO] Finished at: Mon Jan 04 12:22:31 EST 2010
[INFO] Final Memory: 11M/20M
[INFO] ------------------------------------------------------------------------
{noformat}
I had a configuration that I followed from one of the test cases checked in,
where the workingDirectory was specified in the configuration of the plugin.
seen as follows:
{noformat}
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-release-plugin</artifactId>
<version>2.0-beta-10-20091102.165928-8</version>
<configuration>
<workingDirectory>${basedir}/target/checkout</workingDirectory>
<useReleaseProfile>true</useReleaseProfile>
<allowTimestampedSnapshots>true</allowTimestampedSnapshots>
</configuration>
</plugin>
{noformat}
I thought maybe this was the reason for the error, so I removed the
workingDirectory configuration, performed all my checkins, did a prepare and
attempted to release again and I received the same error as what is identified
as above (I'm assuming this directory is the default config).
> release:prepare should support flat directory multi-module projects
> -------------------------------------------------------------------
>
> Key: MRELEASE-261
> URL: http://jira.codehaus.org/browse/MRELEASE-261
> Project: Maven 2.x Release Plugin
> Issue Type: Improvement
> Components: prepare
> Environment: linux / maven2 / svn
> Reporter: paul.whe...@gmail.com
> Assignee: Maria Odea Ching
> Fix For: 2.0
>
> Attachments: flatProject.main.patch, flatProject.test.patch,
> maven-release-issue.tar.gz, maven-release-issue.zip,
> MRELEASE-261-sample-project.zip, MRELEASE-261-with-its-v3.patch,
> MRELEASE-261-with-its.patch, MRELEASE-261.patch, odd-tags.png,
> PrepareReleaseMojo.patch
>
>
> What I mean by flat file structure firstly.
> parent/pom.xml
> module1/pom.xml
> module2/pom.xml
> .
> .
> .
> module15/pom.xml
> the parent references the modules like so
> <modules>
> <module>../module1</module>
> <module>../module2</module>
> .
> .
> .
> <module>../module15</module>
> </modules>
> When i release:prepare only the parent project is tagged the modules
> projects versions are incremented etc but the modules are not tagged in svn.
> I use this structure as i use eclipse as my IDE.
> I would love to see a fix for the issue marked as closed here
> http://jira.codehaus.org/browse/MRELEASE-138. I am currenrly tagging by hand
> each submodule of the projects but it would be so nice to have the release
> plugin do this for me.
> forgive my english.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
