The following work around may help: 1) In the folder containing all the modules add an aggegrator pom that has one module - the parent of the flat structure. 2) Add the information needed by the release (release plugin, scm info, etc.) to that pom. 3) Do your release from that pom.
It needs no other interaction with your project. It does not even need to be the parent of the projects parent pom. The entire project is still configured/managed from the parent pom in the flat structure and is unaware of this extra aggregator pom - i.e., no changes. Stan Devitt -----Original Message----- From: Arnaud HERITIER [mailto:[EMAIL PROTECTED] Sent: Sunday, December 07, 2008 8:48 AM To: Maven Users List Subject: Re: Release plugin woes there are several issues already opened for the support of flat projects in the release plugin. In a flat maven multiproject you have to define the scm part in each pom. you have also to do it for the site distribution The release plugin isn't able to compute the location of the module in the scm with a flat multiproject What is the constraint which doesn't allow you to have a hierarchical multiproject ? On Wed, Dec 3, 2008 at 1:41 PM, <[EMAIL PROTECTED]> wrote: > Hi! > > > I've in severe trouble with releasing a CVS based flat maven multiproject: > > > Structure: > > <modules> > <module>../JEEFrameworkRefAppJAVA</module> > <module>../JEEFrameworkRefAppEJB</module> > <module>../JEEFrameworkRefAppWAR</module> > <module>../JEEFrameworkRefAppEAR</module> > </modules> > > > Yes - having it this way is not convention over configuration and will > probably generate trouble for more plugins - but I can't convince the > users that it's the proper way of doing it. > > > directory containing: > > JEEFrameworkRefAppWAR > JEEFrameworkRefAppJAVA > JEEFrameworkRefAppEJB > JEEFrameworkRefAppEAR > JEEFrameworkRefApp <-- this is actually the top-pom with the modules > as specified above. > > > so I cd into JEEFrameworkRefApp and do a > > mvn release:prepare -Dusername=myId -Dpassword=myScmPw > > and tried both with and without: > -Dmaven.scm.provider.cvs.implementation=cvs_native > with this flag I get: > > [INFO] Executing: cvs -z3 -f -q commit -R -F > /tmp/scm-commit-message62844.txt pom.xml AVA/pom.xml JB/pom.xml > AR/pom.xml AR/pom.xml [INFO] Working directory: > /home/karltdav/work/JEEFramework/JEE/JEEFrameworkRefApp > [INFO] > ---------------------------------------------------------------------- > -- > [ERROR] BUILD FAILURE > [INFO] > ---------------------------------------------------------------------- > -- > [INFO] Unable to commit files > Provider message: > The cvs command failed. > Command output: > cvs [commit aborted]: no such directory `AVA' > > [INFO] > ---------------------------------------------------------------------- > -- > [DEBUG] Trace > org.apache.maven.BuildFailureException: Unable to commit files > Provider message: > The cvs command failed. > Command output: > cvs [commit aborted]: no such directory `AVA' > > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Default LifecycleExecutor.java:697) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoa l(DefaultLifecycleExecutor.java:551) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultL ifecycleExecutor.java:521) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandle Failures(DefaultLifecycleExecutor.java:369) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments( DefaultLifecycleExecutor.java:266) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifec ycleExecutor.java:181) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:302) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav a:39) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor Impl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at > org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) > at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) > at > org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) > at org.codehaus.classworlds.Launcher.main(Launcher.java:375) > Caused by: org.apache.maven.plugin.MojoFailureException: Unable to > commit files Provider message: > The cvs command failed. > Command output: > cvs [commit aborted]: no such directory `AVA' > > at > org.apache.maven.plugins.release.PrepareReleaseMojo.execute(PrepareRelea seMojo.java:144) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginMa nager.java:458) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Default LifecycleExecutor.java:676) > ... 16 more > [INFO] > ---------------------------------------------------------------------- > -- > > > (notice the strange filenames) > > > without native client flag I get: > > [DEBUG] Executing CVS command: commit -F > /tmp/scm-commit-message11403.txt pom.xml pom.xml pom.xml pom.xml > pom.xml [INFO] > ---------------------------------------------------------------------- > -- > [ERROR] BUILD FAILURE > [INFO] > ---------------------------------------------------------------------- > -- > [INFO] Unable to commit files > Provider message: > The cvs command failed. > Command output: > cvs commit: failed to create lock directory for `/home/CVS/AR' > (/home/CVS/AR/#cvs.lock): No such file or directory cvs commit: lock > failed - giving up cvs [commit aborted]: lock failed - giving up > > > [INFO] > ---------------------------------------------------------------------- > -- > [DEBUG] Trace > org.apache.maven.BuildFailureException: Unable to commit files > Provider message: > The cvs command failed. > Command output: > cvs commit: failed to create lock directory for `/home/CVS/AR' > (/home/CVS/AR/#cvs.lock): No such file or directory cvs commit: lock > failed - giving up cvs [commit aborted]: lock failed - giving up > > > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Default LifecycleExecutor.java:697) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoa l(DefaultLifecycleExecutor.java:551) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultL ifecycleExecutor.java:521) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandle Failures(DefaultLifecycleExecutor.java:369) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments( DefaultLifecycleExecutor.java:266) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifec ycleExecutor.java:181) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:302) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav a:39) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor Impl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at > org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) > at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) > at > org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) > at org.codehaus.classworlds.Launcher.main(Launcher.java:375) > Caused by: org.apache.maven.plugin.MojoFailureException: Unable to > commit files Provider message: > The cvs command failed. > Command output: > cvs commit: failed to create lock directory for `/home/CVS/AR' > (/home/CVS/AR/#cvs.lock): No such file or directory cvs commit: lock > failed - giving up cvs [commit aborted]: lock failed - giving up > > > at > org.apache.maven.plugins.release.PrepareReleaseMojo.execute(PrepareRelea seMojo.java:144) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginMa nager.java:458) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Default LifecycleExecutor.java:676) > ... 16 more > [INFO] > ------------------------------------------------------------------------ > > > > > > -- > David J. M. Karlsen - +47 90 68 22 43 > http://www.davidkarlsen.com > http://mp3.davidkarlsen.com > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- .......................................................... Arnaud HERITIER 12 guidelines to boost your productivity with a Java software factory - http://tinyurl.com/56s9tw .......................................................... OCTO Technology - aheritier AT octo DOT com www.octo.com | blog.octo.com .......................................................... ASF - aheritier AT apache DOT org www.apache.org | maven.apache.org ........................................................... --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
