It doesn't look to me like there is a project structure that validates
that in the release project so I can't tell you for sure whether it
works or not.
If you want to make a sample project for testing we would be happy to
try and get it to work.
On 13-Jul-08, at 3:06 AM, ChrisGWarp wrote:
Hi all.
From what I can gather, the release plugin has been fixed to work
with
the flattened eclipse based project structure.
But the results that I'm getting below tend to make me think that
it is
the SCM plugin causing me the grief, and I cann't image that I'm doing
anything that out of the ordinary, so perhaps someone can point out
what
I've done wrong.
I have 4 directories, all at the same level so that they work with
eclipse.
<workspace dir>\FireDragon (the J2EE Multi Module Build Project)
<workspace dir>\FireDragonResources (the resources project)
<workspace dir>\FireDragonWeb (the web/war project)
<workspace dir>\FireDragonEAR (the ear project).
The multi module build project has this in it:
<modules>
<module>../FireDragonResources</module>
<module>../FireDragonWeb</module>
<module>../FireDragonEAR</module>
</modules>
And each of the modules (Resources, WAR, EAR) have this as the
parent:
<parent>
<groupId>au.com.warpspeed.firedragon</groupId>
<artifactId>FireDragon</artifactId>
<version>1.0.5-SNAPSHOT</version>
<relativePath>../FireDragon/pom.xml</relativePath>
</parent>
The project builds fine, so all of that is ok.
However, when I do a release:prepare, I get this as the final bit
of the
output:
[INFO]
------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
------------------------------------------------------------------------
[INFO] FireDragon - J2EE Multi Module Project ................
SUCCESS [13.125s]
[INFO] FireDragon - Resources Project ........................
SUCCESS [3.875s]
[INFO] FireDragon - WAR Project ..............................
SUCCESS [3:36.109s]
[INFO] FireDragon - EAR Project ..............................
SUCCESS [1:10.562s]
[INFO]
------------------------------------------------------------------------
[INFO]
------------------------------------------------------------------------
[INFO] BUILD SUCCESSFUL
[INFO]
------------------------------------------------------------------------
[INFO] Total time: 5 minutes 7 seconds
[INFO] Finished at: Sat Jul 12 21:38:26 EST 2008
[INFO] Final Memory: 19M/41M
[INFO]
------------------------------------------------------------------------
[INFO] Checking in modified POMs...
[INFO] Executing: svn --username chris --password ***** --non-
interactive
commit --file C:\DOCUME~1\Chris\LOCALS~1\Temp\maven-
scm-108910589.commi
t --targets C:\DOCUME~1\Chris\LOCALS~1\Temp\maven-scm-3540-targets
[INFO] Working directory: C:\Documents and Settings\Chris\My
Documents\IBM\rationalsdp7.0\workspace\FireDragon
[INFO]
------------------------------------------------------------------------
[ERROR] BUILD FAILURE
[INFO]
------------------------------------------------------------------------
[INFO] Unable to commit files
Provider message:
The svn command failed.
Command output:
svn: 'C:\Documents and Settings\Chris\My
Documents\IBM\rationalsdp7.0\workspace' is not a working copy
svn: Can't open file 'C:\Documents and Settings\Chris\My
Documents\IBM\rationalsdp7.0\workspace\.svn\entries': The system
cannot find
the path specified.
[INFO]
------------------------------------------------------------------------
[INFO] For more information, run Maven with the -e switch
[INFO]
------------------------------------------------------------------------
[INFO] Total time: 5 minutes 24 seconds
[INFO] Finished at: Sat Jul 12 21:38:28 EST 2008
[INFO] Final Memory: 7M/13M
[INFO]
------------------------------------------------------------------------
Is the release plugin not really fixed (as claimed since beta-6
and I'm
using beta-8) or have I done something else that is wrong?
-Chris
--
View this message in context:
http://www.nabble.com/Release-SCM-broken-for-eclipse--tp18426787p18426787.html
Sent from the Maven - SCM mailing list archive at Nabble.com.
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder, Apache Maven
jason at sonatype dot com
----------------------------------------------------------
First, the taking in of scattered particulars under one Idea,
so that everyone understands what is being talked about ... Second,
the separation of the Idea into parts, by dividing it at the joints,
as nature directs, not breaking any limb in half as a bad carver might.
-- Plato, Phaedrus (Notes on the Synthesis of Form by C. Alexander)
