Maven release:prepare command to associate work item
Hello, I need the command to associate a work item while commit code option with Jazz using maven release plugin. Command used: mven release:prepare. Error: Failed to attach work item. Please share the command used to attach the work item id as an input to Release plugin. Thank You. Best regards, Rahamathullah Anisha RBEI/ETB2 Tel. +91 422 676-2621
Re: Maven release:prepare
the trick for such scenarios is easy: don't use the release-plugin. Am Samstag, den 05.01.2013, 13:29 +0100 schrieb Sundeep Reddy : Hi All, The maven release:prepare does the following things: release: prepare – Performs a number of operations - Checks to make sure that there are no uncommitted changes. - Ensures that there are no SNAPSHOT dependencies in the POM file, - Changes the version of the application and removes SNAPSHOT from the version. ie 1.0.3-SNAPSHOT becomes 1.0.3 - Run project tests against modified POMs - Commit the modified POM - Tag the code in Subversion - Increment the version number and append SNAPSHOT. ie 1.0.3 becomes 1.0.4-SNAPSHOT - Commit modified POM Is there way where we could skip the last 2 steps i,e increment of the version number and appending the SNAPSHOT . In a way just want to convert the snapshot to a release,no further development version. Thanks Sundeep - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: AW: Maven release:prepare
Does the versions-maven-plugin happen to have a goal for you here?
On Sat, Jan 5, 2013 at 12:01 PM, Robert Scholte wrote:
> Hi,
>
> Since version 2.4 the developmentVersion MUST be a SNAPSHOT, so that trick
> will fail nowadays.
>
> I don't see any reason why to skip these last steps.
> IMHO: in the tag the version must always be a non-SNAPSHOT, in both trunk
> and branches the version should always be a SNAPSHOT (expect in that
> twilight-period right before tagging...)
> If you don't want to continue development on the project, it should have
> been a branch, so it can be removed once tagged.
>
> Robert
>
>
> Op Sat, 05 Jan 2013 17:39:33 +0100 schreef christofer.d...@c-ware.de <
> christofer.d...@c-ware.de>:
>
>
> Hi Sundeep,
>>
>> I doubt you can skip the last 2 steps, but you could configure the plugin
>> to "change" the development version to exactly the same version as the
>> release version. Haven't tried this though:
>>
>> mvn release:prepare -DreleaseVersion={release-**version}
>> -DdevelopmentVersion={release-**version}
>>
>> The result should be the same as if the last two steps were skipped.
>> As I mentioned ... haven't actually tried this :-)
>>
>> Chris
>>
>> -Ursprüngliche Nachricht-
>> Von: Sundeep Reddy [mailto:sundeep.i...@gmail.com**]
>> Gesendet: Samstag, 5. Januar 2013 13:30
>> An: users@maven.apache.org
>> Betreff: Maven release:prepare
>>
>> Hi All,
>>
>> The maven release:prepare does the following things:
>>
>> release: prepare - Performs a number of operations
>>
>>- Checks to make sure that there are no uncommitted changes.
>>- Ensures that there are no SNAPSHOT dependencies in the POM file,
>>- Changes the version of the application and removes SNAPSHOT from the
>>version. ie 1.0.3-SNAPSHOT becomes 1.0.3
>>- Run project tests against modified POMs
>>- Commit the modified POM
>>- Tag the code in Subversion
>>
>>
>>- Increment the version number and append SNAPSHOT. ie 1.0.3 becomes
>>1.0.4-SNAPSHOT
>>- Commit modified POM
>>
>> Is there way where we could skip the last 2 steps i,e increment of the
>> version number and appending the SNAPSHOT . In a way just want to convert
>> the snapshot to a release,no further development version.
>>
>>
>>
>> Thanks
>>
>> Sundeep
>>
>> --**--**-
>> To unsubscribe, e-mail:
>> users-unsubscribe@maven.**apache.org
>> For additional commands, e-mail: users-h...@maven.apache.org
>>
>
> --**--**-
> To unsubscribe, e-mail:
> users-unsubscribe@maven.**apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>
Re: AW: Maven release:prepare
Hi,
Since version 2.4 the developmentVersion MUST be a SNAPSHOT, so that trick
will fail nowadays.
I don't see any reason why to skip these last steps.
IMHO: in the tag the version must always be a non-SNAPSHOT, in both trunk
and branches the version should always be a SNAPSHOT (expect in that
twilight-period right before tagging...)
If you don't want to continue development on the project, it should have
been a branch, so it can be removed once tagged.
Robert
Op Sat, 05 Jan 2013 17:39:33 +0100 schreef christofer.d...@c-ware.de
:
Hi Sundeep,
I doubt you can skip the last 2 steps, but you could configure the
plugin to "change" the development version to exactly the same version
as the release version. Haven't tried this though:
mvn release:prepare -DreleaseVersion={release-version}
-DdevelopmentVersion={release-version}
The result should be the same as if the last two steps were skipped.
As I mentioned ... haven't actually tried this :-)
Chris
-Ursprüngliche Nachricht-
Von: Sundeep Reddy [mailto:sundeep.i...@gmail.com]
Gesendet: Samstag, 5. Januar 2013 13:30
An: users@maven.apache.org
Betreff: Maven release:prepare
Hi All,
The maven release:prepare does the following things:
release: prepare - Performs a number of operations
- Checks to make sure that there are no uncommitted changes.
- Ensures that there are no SNAPSHOT dependencies in the POM file,
- Changes the version of the application and removes SNAPSHOT from the
version. ie 1.0.3-SNAPSHOT becomes 1.0.3
- Run project tests against modified POMs
- Commit the modified POM
- Tag the code in Subversion
- Increment the version number and append SNAPSHOT. ie 1.0.3 becomes
1.0.4-SNAPSHOT
- Commit modified POM
Is there way where we could skip the last 2 steps i,e increment of the
version number and appending the SNAPSHOT . In a way just want to
convert the snapshot to a release,no further development version.
Thanks
Sundeep
-
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
AW: Maven release:prepare
Hi Sundeep,
I doubt you can skip the last 2 steps, but you could configure the plugin to
"change" the development version to exactly the same version as the release
version. Haven't tried this though:
mvn release:prepare -DreleaseVersion={release-version}
-DdevelopmentVersion={release-version}
The result should be the same as if the last two steps were skipped.
As I mentioned ... haven't actually tried this :-)
Chris
-Ursprüngliche Nachricht-
Von: Sundeep Reddy [mailto:sundeep.i...@gmail.com]
Gesendet: Samstag, 5. Januar 2013 13:30
An: users@maven.apache.org
Betreff: Maven release:prepare
Hi All,
The maven release:prepare does the following things:
release: prepare - Performs a number of operations
- Checks to make sure that there are no uncommitted changes.
- Ensures that there are no SNAPSHOT dependencies in the POM file,
- Changes the version of the application and removes SNAPSHOT from the
version. ie 1.0.3-SNAPSHOT becomes 1.0.3
- Run project tests against modified POMs
- Commit the modified POM
- Tag the code in Subversion
- Increment the version number and append SNAPSHOT. ie 1.0.3 becomes
1.0.4-SNAPSHOT
- Commit modified POM
Is there way where we could skip the last 2 steps i,e increment of the version
number and appending the SNAPSHOT . In a way just want to convert the snapshot
to a release,no further development version.
Thanks
Sundeep
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven release:prepare
> Is there way where we could skip the last 2 steps i,e increment of the > version number and appending the SNAPSHOT . In a way just want to convert > the snapshot to a release,no further development version. I am unaware of any such configuration of the plugin which would permit this. But you could simply delete the unneeded pom file(s) from SCM and you'd have the same end result, right? Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Maven release:prepare
Hi All, The maven release:prepare does the following things: release: prepare – Performs a number of operations - Checks to make sure that there are no uncommitted changes. - Ensures that there are no SNAPSHOT dependencies in the POM file, - Changes the version of the application and removes SNAPSHOT from the version. ie 1.0.3-SNAPSHOT becomes 1.0.3 - Run project tests against modified POMs - Commit the modified POM - Tag the code in Subversion - Increment the version number and append SNAPSHOT. ie 1.0.3 becomes 1.0.4-SNAPSHOT - Commit modified POM Is there way where we could skip the last 2 steps i,e increment of the version number and appending the SNAPSHOT . In a way just want to convert the snapshot to a release,no further development version. Thanks Sundeep
Re: Difference in Maven release:prepare and install jars when using jython
> net.sf.mavenjython > jython-compile-maven-plugin You probably need to find someone else in the world who is using this plugin and see if they can give you specific help with it. Possibly even the author of the plugin. BTW I searched Github and found zero hits for "jython-compile-maven-plugin" which is not a good sign. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Difference in Maven release:prepare and install jars when using jython
Hi, I am using Maven 3.0.4 along with Jython 2.5.2 and Pygments 1.5 (via an egg). I have configured the jython-compile-maven-plugin as, net.sf.mavenjython jython-compile-maven-plugin 1.2 package jython Pygments Running *mvn install* the created JAR contains the *Pygments* library embedded inside in a *Lib* folder. This makes sure that all my code works fine. The problem starts when I run a *mvn release:prepare* command. In this case, only my code gets inside the JAR, and the *Pygments* library gets left out. If I take a look inside the *target/classes* folder, it contains both my code and the needed pygments library. Any idea on what I may be missing or doing wrong? I have also posted the question to StackOverflow: http://stackoverflow.com/questions/11623619/difference-in-maven-releaseprepare-and-install-jars-when-using-jython Regards, Sandeep Gupta
Re: Maven release:prepare and NOT creating SNAPSHOTs
On Tue, Jun 21, 2011 at 9:19 AM, Neil Hart wrote: > I was hoping to just cut the release and not create the snapshot for a > couple of reasons. > > I have version 1.0-SNAPSHOT. I'm done developing so I want to create > version 1.0, Get that into our mvn repo and update our hg repo. At this > point, I do know that I am done with version 10., but I don't know if my > next release will be version 2.0, 1.1, or 1.0.1. I'd like to stop the > process after it updates the hg repo with the 1.0 version. Well.. you don't want to leave 'trunk' sitting there with a non-snapshot version number. Anyone who checks it out and builds it (CI server perhaps?) will re-create that version in their local repo, (and maybe even try to deploy it) which might not match the real released version, causing all sorts of havoc. If you're not sure what the next version is... set it to TBD-SNAPSHOT or something. -- Wendy - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven release:prepare and NOT creating SNAPSHOTs
I was hoping to just cut the release and not create the snapshot for a couple of reasons. I have version 1.0-SNAPSHOT. I'm done developing so I want to create version 1.0, Get that into our mvn repo and update our hg repo. At this point, I do know that I am done with version 10., but I don't know if my next release will be version 2.0, 1.1, or 1.0.1. I'd like to stop the process after it updates the hg repo with the 1.0 version. Once I know what version I will be working on, I'd like to create a branch in hg and create a SNAPSHOT release in mvn. Thanks Neil On Mon, Jun 20, 2011 at 8:11 PM, Barrie Treloar wrote: > On Tue, Jun 21, 2011 at 9:14 AM, Wendy Smoak wrote: > > On Mon, Jun 20, 2011 at 3:46 PM, Neil Hart wrote: > >> I would like to run release:prepare without creating a new development > >> version. I don't always know the next version number when versioning > the > >> current build. Later I could run release:branch (perhaps). This is > using > >> Maven 2.2.1. > > > > Did you try setting developmentVersion? That seems to control the > > 'next snapshot'. > > http://maven.apache.org/plugins/maven-release-plugin/prepare-mojo.html > > > > FWIW I think it's a valid request. Sometimes I have 1.0-SNAPSHOT and > > I release 1.0-test then go back to 1.0-SNAPSHOT. I can test the > > release process without disrupting the developers. > > Ahh fair enough. > I assumed that he would be releasing the non snapshot version, not > choosing a new version like your example, which makes sense to do. > > If this is what he is doing, and he is running release:prepare > incrementally you can always just type in the version number you want. > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > >
Re: Maven release:prepare and NOT creating SNAPSHOTs
On Tue, Jun 21, 2011 at 9:14 AM, Wendy Smoak wrote: > On Mon, Jun 20, 2011 at 3:46 PM, Neil Hart wrote: >> I would like to run release:prepare without creating a new development >> version. I don't always know the next version number when versioning the >> current build. Later I could run release:branch (perhaps). This is using >> Maven 2.2.1. > > Did you try setting developmentVersion? That seems to control the > 'next snapshot'. > http://maven.apache.org/plugins/maven-release-plugin/prepare-mojo.html > > FWIW I think it's a valid request. Sometimes I have 1.0-SNAPSHOT and > I release 1.0-test then go back to 1.0-SNAPSHOT. I can test the > release process without disrupting the developers. Ahh fair enough. I assumed that he would be releasing the non snapshot version, not choosing a new version like your example, which makes sense to do. If this is what he is doing, and he is running release:prepare incrementally you can always just type in the version number you want. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven release:prepare and NOT creating SNAPSHOTs
On Mon, Jun 20, 2011 at 3:46 PM, Neil Hart wrote: > I would like to run release:prepare without creating a new development > version. I don't always know the next version number when versioning the > current build. Later I could run release:branch (perhaps). This is using > Maven 2.2.1. Did you try setting developmentVersion? That seems to control the 'next snapshot'. http://maven.apache.org/plugins/maven-release-plugin/prepare-mojo.html FWIW I think it's a valid request. Sometimes I have 1.0-SNAPSHOT and I release 1.0-test then go back to 1.0-SNAPSHOT. I can test the release process without disrupting the developers. -- Wendy - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven release:prepare and NOT creating SNAPSHOTs
On Tue, Jun 21, 2011 at 5:16 AM, Neil Hart wrote: > I would like to run release:prepare without creating a new development > version. I don't always know the next version number when versioning the > current build. Later I could run release:branch (perhaps). This is using > Maven 2.2.1. > > I've tried a few of the properties in the release plugin without success. > Do I need to override the maven-release-manager some how? Can this be > done? The next snapshot is just a best guess at the version number. It doesn't really mean anything definite. I'm not sure why you are trying to do this. At release time, or some time later in development you might decide that your change set requires a change in the major or minor version numbers (i.e. its not just a patch update) See http://semver.org/ The best guess that maven-release-plugin uses is the version number (Major.Minor.Patch) upgraded to Patch+1-SNAPSHOT What you DEFINITELY don't want to do is NOT increase the version number. Once you release your artifact it SHALL NEVER CHANGE. If its borked, you need to spin a new release but never override the just released one. If you want to give some sort of "QA" or sanity check on a release before letting it loose in the wild, then you need to consider a repository manager that uses a staging area. You release to the staging area, the people doing the sanity check pull in from your temporary staging area, do their checks, and once the green light is given the artifact is promoted out of staging into the proper release area. This lets you re-spin with the same version number because you never publicly released the artifact. Hopefully this helps. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Maven release:prepare and NOT creating SNAPSHOTs
I would like to run release:prepare without creating a new development version. I don't always know the next version number when versioning the current build. Later I could run release:branch (perhaps). This is using Maven 2.2.1. I've tried a few of the properties in the release plugin without success. Do I need to override the maven-release-manager some how? Can this be done? Thanks Neil
Re: Inter-module dependencies on additional assemblies during a Maven release:prepare
You're most likely using Maven 2.x, which doesn't correctly handle dependencies within a multi-module build unless the artifacts are deployed to the repo. The default goal for release:prepare is "verify" and thus the issue. Either upgrade to Maven 3 (I recommend!) or reconfigure the goal to be executed. /Anders On Fri, Mar 18, 2011 at 08:13, Thomas Woelfle wrote: > Hi all, > > we have a multi module project with following modules: > > - Database > - Persistence > - Business > - Application > > The 'Database' project is a jar project that creates an additional assembly > using the 'maven-assembly-plugin'. This additional assembly contains the > database schema. > > The plugin configuration is as follows: > > > >org.apache.maven.plugins >maven-assembly-plugin >2.2.1 > > >attach-schema >package > > single > > > >db-schema-descriptor.xml > > > > > > > The 'Application' project creates a zipped version of the the application > directory structure. Therefore it references the schema assembly in order > to > extract and copy it to the appropriate location in the application > directory > structure. The reference is expressed as ordinary maven dependency: > > > my.application > persistence > 0.0.1-SNAPSHOT > db-schema > > > At least there is a multi module project that aggregates the 4 sub modules > in order to build the application in one step. > > Running 'mvn deploy' on the aggregate project works fine. The database > schema assembly is extracted and copied. But when running a 'mvn > release:prepare' on the aggregate project building the 'Application' > project > fails with the error notification that maven is unable to find the schema > assembly with version '0.0.1'. The log file states that the 'Persistence' > project has been built before the 'Application' project and that the > 'database schema' assembly has been built. > > Anyone an idea what I am doing wrong? > > > Thanks in advance, > > Thomas >
Inter-module dependencies on additional assemblies during a Maven release:prepare
Hi all, we have a multi module project with following modules: - Database - Persistence - Business - Application The 'Database' project is a jar project that creates an additional assembly using the 'maven-assembly-plugin'. This additional assembly contains the database schema. The plugin configuration is as follows: org.apache.maven.plugins maven-assembly-plugin 2.2.1 attach-schema package single db-schema-descriptor.xml The 'Application' project creates a zipped version of the the application directory structure. Therefore it references the schema assembly in order to extract and copy it to the appropriate location in the application directory structure. The reference is expressed as ordinary maven dependency: my.application persistence 0.0.1-SNAPSHOT db-schema At least there is a multi module project that aggregates the 4 sub modules in order to build the application in one step. Running 'mvn deploy' on the aggregate project works fine. The database schema assembly is extracted and copied. But when running a 'mvn release:prepare' on the aggregate project building the 'Application' project fails with the error notification that maven is unable to find the schema assembly with version '0.0.1'. The log file states that the 'Persistence' project has been built before the 'Application' project and that the 'database schema' assembly has been built. Anyone an idea what I am doing wrong? Thanks in advance, Thomas
Problem with Maven release:prepare
Hi,
i've got the following project:
https://github.com/khmarbaise/license-verifier
If i try to do a mvn -B release:prepare
i got the following messages:
mac:license-verifier km$ mvn -B release:prepare
Using Java version: 1.6.0
[INFO] Scanning for projects...
..
[INFO] License Verifier :: Reactor
[INFO] License Verifier :: Licenses Model
[INFO] License Verifier :: Licenses-Verifier
..
...
[INFO] Ignoring artifact version update for expression: ${project.version}
[INFO] Not generating release POMs
[INFO] Executing goals 'clean verify'...
[INFO] [WARNING]
[INFO] [WARNING] Some problems were encountered while building the
effective settings
[INFO] [WARNING] Failed to use environment variables for interpolation:
env: not found @
[INFO] [WARNING]
...
[INFO] [INFO] Reactor Summary:
[INFO] [INFO]
[INFO] [INFO] License Verifier :: Reactor ...
FAILURE [1.569s]
[INFO] [INFO] License Verifier :: Licenses Model SKIPPED
[INFO] [INFO] License Verifier :: Licenses-Verifier . SKIPPED
[INFO] [INFO]
[INFO] [INFO] BUILD FAILURE
[INFO] [INFO]
[INFO] [INFO] Total time: 1.801s
[INFO] [INFO] Finished at: Tue Feb 01 21:15:01 CET 2011
[INFO] [INFO] Final Memory: 4M/8M
[INFO] [INFO]
[INFO] [ERROR] Failed to execute goal
org.apache.maven.plugins:maven-site-plugin:3.0-beta-3:attach-descriptor
(attach-descriptor) on project licenses-verifier-reactor: Error when
interpolating site descriptor: IOException: cannot interpolate
environment properties: env: not found -> [Help 1]
[INFO] [ERROR]
[INFO] [ERROR] To see the full stack trace of the errors, re-run Maven
with the -e switch.
[INFO] [ERROR] Re-run Maven using the -X switch to enable full debug
logging.
[INFO] [ERROR]
[INFO] [ERROR] For more information about the errors and possible
solutions, please read the following articles:
[INFO] [ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
[INFO]
[INFO] Reactor Summary:
[INFO]
[INFO] License Verifier :: Reactor ... FAILURE [5.773s]
[INFO] License Verifier :: Licenses Model SKIPPED
[INFO] License Verifier :: Licenses-Verifier . SKIPPED
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 6.904s
[INFO] Finished at: Tue Feb 01 21:15:01 CET 2011
[INFO] Final Memory: 9M/528M
[INFO]
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-release-plugin:2.1:prepare (default-cli)
on project licenses-verifier-reactor: Maven execution failed, exit code:
'1' -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the
-e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions,
please read the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
So does someone has seen something similar like the above ?
BTW: I'm working on a Mac OS X (10.5.8)
mac:license-verifier km$ java -version
java version "1.6.0_22"
Java(TM) SE Runtime Environment (build 1.6.0_22-b04-307-9M3263)
Java HotSpot(TM) 64-Bit Server VM (build 17.1-b03-307, mixed mode)
I'm running MVN:
mac:license-verifier km$ mvn --version
Using Java version: 1.6.0
Apache Maven 3.0.2 (r1056850; 2011-01-09 01:58:10+0100)
Java version: 1.6.0_22, vendor: Apple Inc.
Java home: /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home
Default locale: en_US, platform encoding: MacRoman
OS name: "mac os x", version: "10.5.8", arch: "x86_64", family: "mac"
If someone has an idea or a hint that would be nice...
Many thanks in advance..
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:prepare - creates file with svn inconsistent line ending style for CDATA sections
Has anyone else had problems with svn inconsistent line ending style and mvn release:prepare? This would should up only on windows as the block in question only has LF not CR LF. I suspect because it uses \n instead of System.getProperty( line.separator ); I haven't spent any time investigating it. Besides google and checking JIRA. The problem occurs in the CDATA section of the maven-eclipse-plugin - when setting the contents of the .checkstyle file. org.apache.maven.plugins maven-eclipse-plugin true com.atlassw.tools.eclipse.checkstyle.CheckstyleBuilder com.atlassw.tools.eclipse.checkstyle.CheckstyleNature .checkstyle - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
maven release:prepare
Hi All, I am new to Maven and have figured out how to use most plugins that I require. However, I am now trying to use the maven release:prepare plugin. For the most part I have figured out how to do what I require, but I am having trouble getting the update dependencies to work in batch mode. I have a pom file that contains a dependency to a snapshot version of another pproject. When I execute release:prepare in interactive mode, it checks for dependency snapshots and prompts me if I want to resolve them now. The default is no. This is my problem, in batch mode, the defaults are selected, thus the dependecies are not resolved and the build fails. Is there any way I can set this default value to yes so that when run in batch mode it will resolve the dependencies for me? Any help would be greatly appreciated. Thanks:confused: -- View this message in context: http://www.nabble.com/maven-release%3Aprepare-tf4320725s177.html#a12304158 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
