Re: Maven release plugin question
Ok, I solved this mystery... The reason it wasn't working was because my reactor artifactId was name differently than the folder the reactor pom.xml was sitting in. So my reactor's artifactId was dlm-cwa-reactor and the folder (in svn) which this pom.xml was sitting in was dlm-cwa. Once I changed the reactor artifactId to dlm-cwa, all worked just fine. Thanks everyone for the help. -Yaakov. On Wed, May 4, 2011 at 1:22 PM, Yaakov Chaikin yaakov.chai...@gmail.com wrote: I think I kind of understand what's going on, but not sure how to solve it. What's going is that maven is treating my reactor/root pom.xml as a project with the name dlm-cwa-reactor and when it tries to copy that project to a tag, it fails because no such path actually exists... This is evident from this: *** [INFO] Working directory: C:\Users\yaakov\workspaces\dlm-main\trunk\dlm-cwa [INFO] Tagging release with the label dlm-cwa-reactor-1.0... This line ---[INFO] Executing: cmd.exe /X /C svn --non-interactive copy --file C:\Users\yaakov\AppData\Local\Temp\maven-scm-1505781146.commit --revision 738 https://dev.envieta.com:8443/svn/dlm/trunk/dlm-cwa/dlm-cwa-reactor https://dev.envieta.com:8443/svn/dlm/tags/dlm-cwa-reactor-1.0; [INFO] Working directory: c:\users\yaakov\workspaces\dlm-main\trunk\dlm-cwa [INFO] [ERROR] BUILD FAILURE [INFO] [INFO] Unable to tag SCM Provider message: The svn tag command failed. Command output: svn: Path 'https://dev.envieta.com:8443/svn/dlm/trunk/dlm-cwa/dlm-cwa-reactor' does not exist in revision 738 *** Note that it's trying to copy from https://dev.envieta.com:8443/svn/dlm/trunk/dlm-cwa/dlm-cwa-reactor path, but no such path exists as the reactor pom.xml is sitting in https://dev.envieta.com:8443/svn/dlm/trunk/dlm-cwa/pom.xml. Any idea as to how to make maven understand that? -Yaakov. On Wed, May 4, 2011 at 11:56 AM, Yaakov Chaikin yaakov.chai...@gmail.com wrote: svn info shows this: $ svn info Path: . URL: https://dev.envieta.com:8443/svn/dlm/trunk/dlm-cwa Repository Root: https://dev.envieta.com:8443/svn/dlm I tried a few configurations, but they all end up with some variation of the path .../dlm-cwa-reactor does not exist in revision 730 (or whatever number it is at the moment). When I look at the trasformed parent module's pom.xml, that section looks like this: scm connectionscm:svn:https://dev.envieta.com:8443/svn/dlm/trunk/dlm-cwa/tags/dlm-cwa-reactor-1.0/connection developerConnectionscm:svn:https://dev.envieta.com:8443/svn/dlm/trunk/dlm-cwa/tags/dlm-cwa-reactor-1.0/developerConnection urlhttps://dev.envieta.com:8443/svn/dlm/tags/dlm-cwa-reactor-1.0/dlm-cwa/url /scm To start with, it was this (after I changed it): scm connectionscm:svn:https://dev.envieta.com:8443/svn/dlm/trunk/dlm-cwa/connection developerConnectionscm:svn:https://dev.envieta.com:8443/svn/dlm/trunk/dlm-cwa/developerConnection urlhttps://dev.envieta.com:8443/svn/dlm/trunk/dlm-cwa/url /scm For the connection and developerConnection I tried specifying just https://dev.envieta.com:8443/svn/dlm, but it still didn't work... Any ideas? Thanks for you help! -Yaakov. On Tue, May 3, 2011 at 2:59 PM, Wendy Smoak wsm...@gmail.com wrote: On Tue, May 3, 2011 at 2:45 PM, Yaakov Chaikin yaakov.chai...@gmail.com wrote: Did I configure scm wrong? How does that compare to the output of 'svn info' at the top of your project? Usually a svn url has 'trunk' or 'branches' somewhere in it... The scm url should match the location of your pom.xml (minus the filename). -- Wendy - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven release plugin question
developerConnectionscm:svn:https://dev.envieta.com:8443/svn/dlm}/developerConnection ^ Could it be this closing curly bracket? - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven release plugin question
svn info shows this: $ svn info Path: . URL: https://dev.envieta.com:8443/svn/dlm/trunk/dlm-cwa Repository Root: https://dev.envieta.com:8443/svn/dlm I tried a few configurations, but they all end up with some variation of the path .../dlm-cwa-reactor does not exist in revision 730 (or whatever number it is at the moment). When I look at the trasformed parent module's pom.xml, that section looks like this: scm connectionscm:svn:https://dev.envieta.com:8443/svn/dlm/trunk/dlm-cwa/tags/dlm-cwa-reactor-1.0/connection developerConnectionscm:svn:https://dev.envieta.com:8443/svn/dlm/trunk/dlm-cwa/tags/dlm-cwa-reactor-1.0/developerConnection urlhttps://dev.envieta.com:8443/svn/dlm/tags/dlm-cwa-reactor-1.0/dlm-cwa/url /scm To start with, it was this (after I changed it): scm connectionscm:svn:https://dev.envieta.com:8443/svn/dlm/trunk/dlm-cwa/connection developerConnectionscm:svn:https://dev.envieta.com:8443/svn/dlm/trunk/dlm-cwa/developerConnection urlhttps://dev.envieta.com:8443/svn/dlm/trunk/dlm-cwa/url /scm For the connection and developerConnection I tried specifying just https://dev.envieta.com:8443/svn/dlm, but it still didn't work... Any ideas? Thanks for you help! -Yaakov. On Tue, May 3, 2011 at 2:59 PM, Wendy Smoak wsm...@gmail.com wrote: On Tue, May 3, 2011 at 2:45 PM, Yaakov Chaikin yaakov.chai...@gmail.com wrote: Did I configure scm wrong? How does that compare to the output of 'svn info' at the top of your project? Usually a svn url has 'trunk' or 'branches' somewhere in it... The scm url should match the location of your pom.xml (minus the filename). -- Wendy - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven release plugin question
No, that was just my bad copy/paste. -Yaakov. On Wed, May 4, 2011 at 4:30 AM, Marc Rohlfs pomar...@googlemail.com wrote: developerConnectionscm:svn:https://dev.envieta.com:8443/svn/dlm}/developerConnection ^ Could it be this closing curly bracket? - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven release plugin question
I think I kind of understand what's going on, but not sure how to solve it. What's going is that maven is treating my reactor/root pom.xml as a project with the name dlm-cwa-reactor and when it tries to copy that project to a tag, it fails because no such path actually exists... This is evident from this: *** [INFO] Working directory: C:\Users\yaakov\workspaces\dlm-main\trunk\dlm-cwa [INFO] Tagging release with the label dlm-cwa-reactor-1.0... This line ---[INFO] Executing: cmd.exe /X /C svn --non-interactive copy --file C:\Users\yaakov\AppData\Local\Temp\maven-scm-1505781146.commit --revision 738 https://dev.envieta.com:8443/svn/dlm/trunk/dlm-cwa/dlm-cwa-reactor https://dev.envieta.com:8443/svn/dlm/tags/dlm-cwa-reactor-1.0; [INFO] Working directory: c:\users\yaakov\workspaces\dlm-main\trunk\dlm-cwa [INFO] [ERROR] BUILD FAILURE [INFO] [INFO] Unable to tag SCM Provider message: The svn tag command failed. Command output: svn: Path 'https://dev.envieta.com:8443/svn/dlm/trunk/dlm-cwa/dlm-cwa-reactor' does not exist in revision 738 *** Note that it's trying to copy from https://dev.envieta.com:8443/svn/dlm/trunk/dlm-cwa/dlm-cwa-reactor path, but no such path exists as the reactor pom.xml is sitting in https://dev.envieta.com:8443/svn/dlm/trunk/dlm-cwa/pom.xml. Any idea as to how to make maven understand that? -Yaakov. On Wed, May 4, 2011 at 11:56 AM, Yaakov Chaikin yaakov.chai...@gmail.com wrote: svn info shows this: $ svn info Path: . URL: https://dev.envieta.com:8443/svn/dlm/trunk/dlm-cwa Repository Root: https://dev.envieta.com:8443/svn/dlm I tried a few configurations, but they all end up with some variation of the path .../dlm-cwa-reactor does not exist in revision 730 (or whatever number it is at the moment). When I look at the trasformed parent module's pom.xml, that section looks like this: scm connectionscm:svn:https://dev.envieta.com:8443/svn/dlm/trunk/dlm-cwa/tags/dlm-cwa-reactor-1.0/connection developerConnectionscm:svn:https://dev.envieta.com:8443/svn/dlm/trunk/dlm-cwa/tags/dlm-cwa-reactor-1.0/developerConnection urlhttps://dev.envieta.com:8443/svn/dlm/tags/dlm-cwa-reactor-1.0/dlm-cwa/url /scm To start with, it was this (after I changed it): scm connectionscm:svn:https://dev.envieta.com:8443/svn/dlm/trunk/dlm-cwa/connection developerConnectionscm:svn:https://dev.envieta.com:8443/svn/dlm/trunk/dlm-cwa/developerConnection urlhttps://dev.envieta.com:8443/svn/dlm/trunk/dlm-cwa/url /scm For the connection and developerConnection I tried specifying just https://dev.envieta.com:8443/svn/dlm, but it still didn't work... Any ideas? Thanks for you help! -Yaakov. On Tue, May 3, 2011 at 2:59 PM, Wendy Smoak wsm...@gmail.com wrote: On Tue, May 3, 2011 at 2:45 PM, Yaakov Chaikin yaakov.chai...@gmail.com wrote: Did I configure scm wrong? How does that compare to the output of 'svn info' at the top of your project? Usually a svn url has 'trunk' or 'branches' somewhere in it... The scm url should match the location of your pom.xml (minus the filename). -- Wendy - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven release plugin question
Thanks! That put me on the right path and I think it's working now.
Just for the sake of others reading this later... If you have
dependencies that have to specify a version in the reactor or child
modules, just use ${project.version} instead of ${parent.version}.
Also, you have to make sure to list your parent module in the list of
modules or the autoVersionSubmodules property won't work and it will
still ask you resolve dependencies which have -SNAPSHOT version in
them and it will start with the parent module's pom. To avoid all
this, just list your parent module in the list modules in your
reactor pom.
For a followup question, is there a way to force the release plugin
NOT to run the unit tests. I did -DskipTests=true, but it ignores it
and runs them anyway. In the past, I've tricked the plugin by
specifying a special profile for tests which looked for specially
named classes, rendering the test phase kind of useless. It's a
hack, but I had to do it. For those wondering why I would want to run
this withOUT running the tests? It's because some of the tests are DB
unit tests and require a DB to be present, etc. and all I want to do
is release a previously tested codebase and avoid having to set up
environments just so I can do a release.
Thanks again,
-Yaakov.
On Mon, May 2, 2011 at 3:03 PM, Karl Heinz Marbaise khmarba...@gmx.de wrote:
Hi, you should the configuration for the maven-release-plugin
autoversionsubmodules which can be done either on command as well in the
pom.
In this situation i would suggest to configure the maven-release-plugin in
the parent pomwith it's appropriate configuration...
Furthermore you should prevent using of ${parent.version} in your reactor
pom neither in you modules pom's...you should define the version only via at
the parent pom..
I would suggest also to define the groupId of the project only once in the
parent pom ...
Kind regards
Karl Heinz Marbaise
--
SoftwareEntwicklung Beratung Schulung Tel.: +49 (0) 2405 / 415 893
Dipl.Ing.(FH) Karl Heinz Marbaise ICQ#: 135949029
Hauptstrasse 177 USt.IdNr: DE191347579
52146 Würselen http://www.soebes.de
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven release plugin question
Hmm... Perhaps, I spoke too soon.
Everything goes well during dry run, but committing doesn't work. Any ideas?
*
[INFO] Executing: cmd.exe /X /C svn --non-interactive commit --file
C:\Users\yaakov\AppData\Local\Temp\maven-scm-778463861.commit
--targets C:\Users\yaakov\App
Data\Local\Temp\maven-scm-7812943996577343934-targets
[INFO] Working directory: C:\Users\yaakov\workspaces\dlm-main\trunk\dlm-cwa
[INFO] Tagging release with the label dlm-cwa-reactor-1.0...
[INFO] Executing: cmd.exe /X /C svn --non-interactive copy --file
C:\Users\yaakov\AppData\Local\Temp\maven-scm-1423212193.commit
--revision 722 https://dev.env
ieta.com:8443/svn/dlm/dlm-cwa-reactor
https://dev.envieta.com:8443/svn/dlm/dlm-cwa-reactor/tags/dlm-cwa-reactor-1.0;
[INFO] Working directory: c:\users\yaakov\workspaces\dlm-main\trunk\dlm-cwa
[INFO]
[ERROR] BUILD FAILURE
[INFO]
[INFO] Unable to tag SCM
Provider message:
The svn tag command failed.
Command output:
svn: Path 'https://dev.envieta.com:8443/svn/dlm/dlm-cwa-reactor' does
not exist in revision 722
[INFO]
[INFO] For more information, run Maven with the -e switch
[INFO]
[INFO] Total time: 4 minutes 21 seconds
[INFO] Finished at: Tue May 03 14:42:06 EDT 2011
[INFO] Final Memory: 15M/36M
[INFO]
*
On Tue, May 3, 2011 at 12:23 PM, Yaakov Chaikin
yaakov.chai...@gmail.com wrote:
Thanks! That put me on the right path and I think it's working now.
Just for the sake of others reading this later... If you have
dependencies that have to specify a version in the reactor or child
modules, just use ${project.version} instead of ${parent.version}.
Also, you have to make sure to list your parent module in the list of
modules or the autoVersionSubmodules property won't work and it will
still ask you resolve dependencies which have -SNAPSHOT version in
them and it will start with the parent module's pom. To avoid all
this, just list your parent module in the list modules in your
reactor pom.
For a followup question, is there a way to force the release plugin
NOT to run the unit tests. I did -DskipTests=true, but it ignores it
and runs them anyway. In the past, I've tricked the plugin by
specifying a special profile for tests which looked for specially
named classes, rendering the test phase kind of useless. It's a
hack, but I had to do it. For those wondering why I would want to run
this withOUT running the tests? It's because some of the tests are DB
unit tests and require a DB to be present, etc. and all I want to do
is release a previously tested codebase and avoid having to set up
environments just so I can do a release.
Thanks again,
-Yaakov.
On Mon, May 2, 2011 at 3:03 PM, Karl Heinz Marbaise khmarba...@gmx.de wrote:
Hi, you should the configuration for the maven-release-plugin
autoversionsubmodules which can be done either on command as well in the
pom.
In this situation i would suggest to configure the maven-release-plugin in
the parent pomwith it's appropriate configuration...
Furthermore you should prevent using of ${parent.version} in your reactor
pom neither in you modules pom's...you should define the version only via at
the parent pom..
I would suggest also to define the groupId of the project only once in the
parent pom ...
Kind regards
Karl Heinz Marbaise
--
SoftwareEntwicklung Beratung Schulung Tel.: +49 (0) 2405 / 415 893
Dipl.Ing.(FH) Karl Heinz Marbaise ICQ#: 135949029
Hauptstrasse 177 USt.IdNr: DE191347579
52146 Würselen http://www.soebes.de
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven release plugin question
Did I configure scm wrong?
scm
connectionscm:svn:https://dev.envieta.com:8443/svn/dlm/connection
developerConnectionscm:svn:https://dev.envieta.com:8443/svn/dlm}/developerConnection
urlhttps://dev.envieta.com:8443/svn/dlm/url
/scm
??
-Yaakov.
On Tue, May 3, 2011 at 2:42 PM, Yaakov Chaikin yaakov.chai...@gmail.com wrote:
Hmm... Perhaps, I spoke too soon.
Everything goes well during dry run, but committing doesn't work. Any ideas?
*
[INFO] Executing: cmd.exe /X /C svn --non-interactive commit --file
C:\Users\yaakov\AppData\Local\Temp\maven-scm-778463861.commit
--targets C:\Users\yaakov\App
Data\Local\Temp\maven-scm-7812943996577343934-targets
[INFO] Working directory: C:\Users\yaakov\workspaces\dlm-main\trunk\dlm-cwa
[INFO] Tagging release with the label dlm-cwa-reactor-1.0...
[INFO] Executing: cmd.exe /X /C svn --non-interactive copy --file
C:\Users\yaakov\AppData\Local\Temp\maven-scm-1423212193.commit
--revision 722 https://dev.env
ieta.com:8443/svn/dlm/dlm-cwa-reactor
https://dev.envieta.com:8443/svn/dlm/dlm-cwa-reactor/tags/dlm-cwa-reactor-1.0;
[INFO] Working directory: c:\users\yaakov\workspaces\dlm-main\trunk\dlm-cwa
[INFO]
[ERROR] BUILD FAILURE
[INFO]
[INFO] Unable to tag SCM
Provider message:
The svn tag command failed.
Command output:
svn: Path 'https://dev.envieta.com:8443/svn/dlm/dlm-cwa-reactor' does
not exist in revision 722
[INFO]
[INFO] For more information, run Maven with the -e switch
[INFO]
[INFO] Total time: 4 minutes 21 seconds
[INFO] Finished at: Tue May 03 14:42:06 EDT 2011
[INFO] Final Memory: 15M/36M
[INFO]
*
On Tue, May 3, 2011 at 12:23 PM, Yaakov Chaikin
yaakov.chai...@gmail.com wrote:
Thanks! That put me on the right path and I think it's working now.
Just for the sake of others reading this later... If you have
dependencies that have to specify a version in the reactor or child
modules, just use ${project.version} instead of ${parent.version}.
Also, you have to make sure to list your parent module in the list of
modules or the autoVersionSubmodules property won't work and it will
still ask you resolve dependencies which have -SNAPSHOT version in
them and it will start with the parent module's pom. To avoid all
this, just list your parent module in the list modules in your
reactor pom.
For a followup question, is there a way to force the release plugin
NOT to run the unit tests. I did -DskipTests=true, but it ignores it
and runs them anyway. In the past, I've tricked the plugin by
specifying a special profile for tests which looked for specially
named classes, rendering the test phase kind of useless. It's a
hack, but I had to do it. For those wondering why I would want to run
this withOUT running the tests? It's because some of the tests are DB
unit tests and require a DB to be present, etc. and all I want to do
is release a previously tested codebase and avoid having to set up
environments just so I can do a release.
Thanks again,
-Yaakov.
On Mon, May 2, 2011 at 3:03 PM, Karl Heinz Marbaise khmarba...@gmx.de
wrote:
Hi, you should the configuration for the maven-release-plugin
autoversionsubmodules which can be done either on command as well in the
pom.
In this situation i would suggest to configure the maven-release-plugin in
the parent pomwith it's appropriate configuration...
Furthermore you should prevent using of ${parent.version} in your reactor
pom neither in you modules pom's...you should define the version only via at
the parent pom..
I would suggest also to define the groupId of the project only once in the
parent pom ...
Kind regards
Karl Heinz Marbaise
--
SoftwareEntwicklung Beratung Schulung Tel.: +49 (0) 2405 / 415 893
Dipl.Ing.(FH) Karl Heinz Marbaise ICQ#: 135949029
Hauptstrasse 177 USt.IdNr: DE191347579
52146 Würselen http://www.soebes.de
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven release plugin question
On Tue, May 3, 2011 at 2:45 PM, Yaakov Chaikin yaakov.chai...@gmail.com wrote: Did I configure scm wrong? How does that compare to the output of 'svn info' at the top of your project? Usually a svn url has 'trunk' or 'branches' somewhere in it... The scm url should match the location of your pom.xml (minus the filename). -- Wendy - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Maven release plugin question
Hi all,
I've used the maven release plugin for a long time, but I have always
used it in situations when the room POM was the parent POM at the same
time.
Now, I am a project where that's not an option, but they still want to
use the maven release plugin. Instead, their structure is as follows:
pom.xml --- reactor pom (listing modules)
-- bla-parent (pom.xml lists plugins, dependencies,etc.)
-- bla-model (regular pom.xml)
-- bla-ddl (regular pom.xml)
You get the point.
Here is the reactor's pom.xml:
***
project xmlns=http://maven.apache.org/POM/4.0.0;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation=http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd;
modelVersion4.0.0/modelVersion
groupIdbla/groupId
artifactIdbla-reactor/artifactId
packagingpom/packaging
nameBla Reactor/name
version${parent.version}/version
parent
groupIdbla/groupId
artifactIdbla-parent/artifactId
version1.0-SNAPSHOT/version
relativePathbla-parent/relativePath
/parent
modules
modulebla-ddl/module
modulebla-common/module
modulebla-model/module
modulebla-persistence/module
modulebla-web/module
/modules
/project
***
Here is how moduleOne's pom.xml looks like:
***
project xmlns=http://maven.apache.org/POM/4.0.0;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation=http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd;
modelVersion4.0.0/modelVersion
groupIdbla/groupId
artifactIdbla-model/artifactId
packagingjar/packaging
nameBla Model/name
version${parent.version}/version
parent
groupIdbla/groupId
artifactIdbla-parent/artifactId
version1.0-SNAPSHOT/version
relativePath../bla-parent/relativePath
/parent
***
When I run 'mvn release:prepare' from the root directory (the one that
hosts the reactor POM), I end up with this:
*
...
...
[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: : 1
Dependency 'bla:bla-parent' is a snapshot (1.0-SNAPSHOT)
: Which release version should it be set to? 1.0: :
What version should the dependency be reset to for development? 1.0: :
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: : 1
Dependency 'bla:bla-parent' is a snapshot (1.0-SNAPSHOT)
: Which release version should it be set to? 1.0: :
What version should the dependency be reset to for development? 1.0: :
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: : 1
Dependency 'bla:bla-parent' is a snapshot (1.0-SNAPSHOT)
: Which release version should it be set to? 1.0: :
What version should the dependency be reset to for development? 1.0: :
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: : 1
Dependency 'bla:bla-parent' is a snapshot (1.0-SNAPSHOT)
: Which release version should it be set to? 1.0: :
What version should the dependency be reset to for development? 1.0: :
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: : 1
Dependency 'bla:bla-parent' is a snapshot (1.0-SNAPSHOT)
: Which release version should it be set to? 1.0: :
What version should the dependency be reset to for development? 1.0: :
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: : 1
Dependency 'bla:bla-parent' is a snapshot (1.0-SNAPSHOT)
: Which release version should it be set to? 1.0: :
What version should the dependency be reset to for development? 1.0: :
What is the release version for Bla Reactor? (bla:bla-reactor) 1.0: :
What is SCM release
Re: Maven release plugin question
Hi, you should the configuration for the maven-release-plugin
autoversionsubmodules which can be done either on command as well in the
pom.
In this situation i would suggest to configure the maven-release-plugin
in the parent pomwith it's appropriate configuration...
Furthermore you should prevent using of ${parent.version} in your
reactor pom neither in you modules pom's...you should define the version
only via at the parent pom..
I would suggest also to define the groupId of the project only once in
the parent pom ...
Kind regards
Karl Heinz Marbaise
--
SoftwareEntwicklung Beratung SchulungTel.: +49 (0) 2405 / 415 893
Dipl.Ing.(FH) Karl Heinz MarbaiseICQ#: 135949029
Hauptstrasse 177 USt.IdNr: DE191347579
52146 Würselen http://www.soebes.de
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Maven Release Plugin Question
Can the maven release plugin deploy the war file to external application service/Tomcat after it is finished. The extra goals are added to the goal configuration parameter on the sub-module pom.xml, but the release plugin does not seem to be call the extra goals configured in the module's pom.xml. Ravi -- View this message in context: http://www.nabble.com/Maven-Release-Plugin-Question-tf4816868s177.html#a13780801 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven Release Plugin Question
Your should add the goal to the release plugin ,configuration area like this: goalssite,site:deploy,deploy or whateveryourdeploygoal:is/goals then it gets kicked off when u run release:perform Cheers On Thu, 2007-11-15 at 12:17 -0800, Ravi_116 wrote: Can the maven release plugin deploy the war file to external application service/Tomcat after it is finished. The extra goals are added to the goal configuration parameter on the sub-module pom.xml, but the release plugin does not seem to be call the extra goals configured in the module's pom.xml. Ravi - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
maven release plugin question
Hi all, Current latest version of maven release plugin from ibiblio has errors. As a workaround, I want to force maven to use the older(the version before the latest one)version of this plugin. This plugin related information is not part of my pom file as it is used by Maven automatically. Given this, how and where do I specify to maven to use a particular version of this plugin? Your input is higly appreciated. Thanks in advance. -- View this message in context: http://www.nabble.com/maven-release-plugin-question-tf3903737s177.html#a11067768 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: maven release plugin question
On 6/11/07, srinivas ramgopal [EMAIL PROTECTED] wrote: Current latest version of maven release plugin from ibiblio has errors. It does? Are they in JIRA? As a workaround, I want to force maven to use the older(the version before the latest one)version of this plugin. This plugin related information is not part of my pom file as it is used by Maven automatically. Given this, how and where do I specify to maven to use a particular version of this plugin? You can put it in pluginManagement and specify a version. (It's recommended that you specify a version for every plugin you use, even the ones that you don't otherwise need to configure.) -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: maven release plugin question
just add the plugin with the version you want to the plugin management section of your pom On 6/11/07, srinivas ramgopal [EMAIL PROTECTED] wrote: Hi all, Current latest version of maven release plugin from ibiblio has errors. As a workaround, I want to force maven to use the older(the version before the latest one)version of this plugin. This plugin related information is not part of my pom file as it is used by Maven automatically. Given this, how and where do I specify to maven to use a particular version of this plugin? Your input is higly appreciated. Thanks in advance. -- View this message in context: http://www.nabble.com/maven-release-plugin-question-tf3903737s177.html#a11067768 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: maven release plugin question
Hi I am new to Maven. Current latest version of maven release plugin from ibiblio has errors. It does? Are they in JIRA? There is a mismatch of javadoc.jar from the latest version of the maven-release plugin. I guess there was a new broken version of the javadoc.jar?? I guess that if I use the maven-release plugin 2.0-beta-5 (instead of 2.0-beta-6) in my pom file, I guess I would still need to pick up the broken javadoc.jar?? If so, how do I let Maven to use specific versions of the dependent jars of the plugins? Thanks in advance for your valuable input. Wendy Smoak-3 wrote: On 6/11/07, srinivas ramgopal [EMAIL PROTECTED] wrote: Current latest version of maven release plugin from ibiblio has errors. It does? Are they in JIRA? As a workaround, I want to force maven to use the older(the version before the latest one)version of this plugin. This plugin related information is not part of my pom file as it is used by Maven automatically. Given this, how and where do I specify to maven to use a particular version of this plugin? You can put it in pluginManagement and specify a version. (It's recommended that you specify a version for every plugin you use, even the ones that you don't otherwise need to configure.) -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/maven-release-plugin-question-tf3903737s177.html#a11068618 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Maven release plugin question
Is it required to have SNAPSHOT in the version number of the Maven project in order to use the Maven release plugin with it? For example, if I have a version like 2.0.0 and I would like to create a tag called 2.0.0.0, it looks like I am not able to do this using the plugin. Is this correct? This message (including any attachments) contains confidential information intended for a specific individual and purpose, and is protected by law. If you are not the intended recipient, you should delete this message. Any disclosure, copying, or distribution of this message, or the taking of any action based on it, is strictly prohibited. [v.E.1]
Re: Maven release plugin question
yes, your artifact version must be SNAPSHOT, however your dependencies can not be SNAPSHOT. -D On 11/20/06, Morgovsky, Alexander (US - Glen Mills) [EMAIL PROTECTED] wrote: Is it required to have SNAPSHOT in the version number of the Maven project in order to use the Maven release plugin with it? For example, if I have a version like 2.0.0 and I would like to create a tag called 2.0.0.0, it looks like I am not able to do this using the plugin. Is this correct? This message (including any attachments) contains confidential information intended for a specific individual and purpose, and is protected by law. If you are not the intended recipient, you should delete this message. Any disclosure, copying, or distribution of this message, or the taking of any action based on it, is strictly prohibited. [v.E.1]
