There is a know issue with Git and release plugin 2.4.2 and something to do
with SCM version bundled in Maven 3.1.1? (or maybe 3.1.x) Olivier may know
more.
On 9 December 2013 02:40, Mark Derricutt m...@talios.com wrote:
Hey all,
Just encountered a strange issue with the maven-release-plugin
I was speaking with Olivier on IRC earlier, so far I've managed to work around
the issue by adding a dependency/ on the latest maven-scm-providers-gitexe
inside my maven-release-plugin plugin/ block and that seems to have resolved
the issue.
Simply dropping back to 2.3.2 of the release plugin
/ on the latest
maven-scm-providers-gitexe inside my maven-release-plugin plugin/ block
and that seems to have resolved the issue.
Simply dropping back to 2.3.2 of the release plugin didn't help as that
still picked up the older maven-scm version which was looking for a git
status output starting
On 9 December 2013 20:48, Mark Derricutt m...@talios.com wrote:
I was speaking with Olivier on IRC earlier, so far I've managed to work
around the issue by adding a dependency/ on the latest
maven-scm-providers-gitexe inside my maven-release-plugin plugin/ block and
that seems to have
Hi,
Here's a list of the maven-release-plugin and the matching SCM versions.
m-release-plugin:2.3.2 depends on scm:1.7
m-release-plugin:2.4 depends on scm:1.8 (standard upgrade, incl. SCM-686)
m-release-plugin:2.4.1 depends on scm:1.7 (back due to MRELEASE-830,
SCM-709 )
m-release-plugin
Hey all,
Just encountered a strange issue with the maven-release-plugin, when doing a
release:prepare from my machine using Maven 3.1.1, and maven-release-plugin
2.4.2 I get the following output:
[INFO] Checking in modified POMs...
[INFO] Executing: /bin/sh -c cd
/Users/amrk/IdeaProjects
/GitStatusConsumer.java
I see that the has been using the newer git status --porcelain command
for some time now, however from walking the dependencies of
maven-release-plugin, I appear to find 1.7 being resolved ( at least via
IntellliJ ).
It looks like Olivier Lamy updated the git status support
The Apache Maven team is pleased to announce the release of the Apache
Maven Release Plugin, version 2.4.2
This plugin is used to release a project with Maven, saving a lot of
repetitive, manual work. Releasing a project is made in two steps: prepare
and perform.
http://maven.apache.org
@Bret, as you've figured out already, it works for non-jars. In case of a
war, you just add artifacts type (typewar/type). :-)
@Baptiste, yes, for the release itself. I find it even more practical to
have configuration for maven-release-plugin
autoVersionSubmodulestrue/autoVersionSubmodules
Hi,
I'm using Maven 3.0.3. I have a multi-module project and want to use the
Maven release plugin (through Jenkins). When running release:prepare, the
process dies with the error
Executing Maven: -B -f /scratch/jenkins/workspace/subco/parent/pom.xml
-amd -pl
,
Ziga Gregoric
On Tue, Aug 20, 2013 at 7:53 PM, laredotornado-3 laredotorn...@gmail.comwrote:
Hi,
I'm using Maven 3.0.3. I have a multi-module project and want to use the
Maven release plugin (through Jenkins). When running release:prepare, the
process dies with the error
...@gmail.com
wrote:
Hi,
I'm using Maven 3.0.3. I have a multi-module project and want to use the
Maven release plugin (through Jenkins). When running release:prepare,
the
process dies with the error
Executing Maven: -B -f
/scratch/jenkins/workspace/subco/parent/pom.xml
, laredotornado-3 laredotorn...@gmail.com
wrote:
Hi,
I'm using Maven 3.0.3. I have a multi-module project and want to use
the
Maven release plugin (through Jenkins). When running release:prepare,
the
process dies with the error
Executing Maven: -B -f
/scratch/jenkins
and update all my child poms every time I want to use the Maven release
plugin, which seems to defeat the purpose.
The problematic child module (similar to others) is setup like so …
artifactIdchildModuleA/artifactId
packagingjar/packaging
...
parent
I'm trying to release a multimodule maven project cloned in github. My
project has the parent pom as a submodule of the root aggregator. if i run the
release in dryRun mode it works fine, however if I run it for real this is
what i get near the end
...
[INFO] Checking in modified
http://stackoverflow.com/questions/17766247/maven-release-plugin-pushing-tags-to-wrong-repo/17771493#17771493
will help you.
Robert
Op Sat, 27 Jul 2013 18:13:28 +0200 schreef alejandro.e...@miranda.com:
I'm trying to release a multimodule maven project cloned in github. My
project has
Someone show me a similar issue with the release plugin in a project
using git where the parent/reactor is at the same level than modules
(moreover each modules where git submodules AFAIR )
The usage of relative path with in the reactor breaks the release.
There is an issue in Jira with a patch
-defeated-the-maven-release-plugin-in-a-flat-structured-multi-module-project/
i'm sure adding git submodules makes everything much more complex. This is why
i'm surprised mine doesn't work, my setup is very vanilla so i'm sure there's
hundreds of people trying to do the same thing
Thanks for your
is the referenced blog
http://warpedjavaguy.wordpress.com/2011/08/08/how-i-defeated-the-maven-release-plugin-in-a-flat-structured-multi-module-project/
i'm sure adding git submodules makes everything much more complex. This
is why i'm surprised mine doesn't work, my setup is very vanilla so i'm
sure
.
Arnaud, in the SO question referenced by Robert and in the blog post
referenced in it at least 2 other people managed to make it work with an
explicit relative path. Here is the referenced blog
http://warpedjavaguy.**wordpress.com/2011/08/08/how-**
i-defeated-the-maven-release-**plugin-in-a-flat
people managed to make it work with
an
explicit relative path. Here is the referenced blog
http://warpedjavaguy.**wordpress.com/2011/08/08/how-**
i-defeated-the-maven-release-**plugin-in-a-flat-structured-**
multi-module-project/http://warpedjavaguy.wordpress.com/2011/08/08/how-i-defeated
@maven.apache.org
From: Robert Scholte rfscho...@apache.org
Date: 07/27/2013 03:49PM
Subject: [CAUTION: Suspicious URL content] Re: maven-release-plugin with
github project
Hi,
From which location are you releasing, from master or from jrobocom-parent?
If it's the first, then the scm section should
: maven-release-plugin with
github project
The issue I was referring to was this one :
https://jira.codehaus.org/browse/MRELEASE-581
Arnaud
On Sat, Jul 27, 2013 at 9:49 PM, Robert Scholte rfscho...@apache.orgwrote:
Hi,
From which location are you releasing, from master or from jrobocom-parent
Subject: Re: maven-release-plugin with github project
http://stackoverflow.com/questions/17766247/maven-release-plugin-pushing-tags-to-wrong-repo/17771493#17771493
will help you.
Robert
Op Sat, 27 Jul 2013 18:13:28 +0200 schreef alejandro.e...@miranda.com:
I'm trying to release a multimodule
Hi,
I'm using Maven 3.0.3 with SVN 1.7. I'm trying to use the Maven release
plugin to deploy my artifact, but I repeatedly run into the error, No
connector available to access repository when running
mvn -e release:prepare release:perform
I have included the connector in my pom, adding
section
before...
Also, any reason you are using 1.0-beta-7 of wagon-webdav-jackrabbit rather
than version 1.0?
Regards,
Curtis
On Fri, Jun 28, 2013 at 9:11 AM, laredotornado-3 laredotorn...@gmail.comwrote:
Hi,
I'm using Maven 3.0.3 with SVN 1.7. I'm trying to use the Maven release
plugin
.nabble.com/Having-trouble-using-Maven-release-plugin-to-deploy-artifact-to-a-dav-repo-tp5761093p5761109.html
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
not sure what is wrong with your config, then. You don't have a
snapshotRepository but you are not trying to deploy a snapshot, right?
(Since you are using maven-release-plugin, I assume you are attempting to
deploy a release.)
In case it helps, here is the distributionManagement section of my
projects
fourni.
Date: Fri, 28 Jun 2013 09:10:31 -0700
From: laredotorn...@gmail.com
To: users@maven.apache.org
Subject: Re: Having trouble using Maven release plugin to deploy artifact to
a dav repo
Hi, Per your suggestion, I added a developerConnection alongside the
connection and upgraded
Hello!
I want to release a SNAPSHOT pom and I am using maven-release-plugin
v.2.4.1. GEOPos2-Watcher is a git repo.
[INFO]
[INFO] Building GEOPos2-Watcher
[INFO]task-segment: [release:prepare] (aggregator-style)
[INFO
14:59:29 +0200 schreef proverbio
proverb...@gmail.com:
Hello!
I want to release a SNAPSHOT pom and I am using maven-release-plugin
v.2.4.1. GEOPos2-Watcher is a git repo.
[INFO]
[INFO] Building GEOPos2-Watcher
[INFO
Thanks Robert!
--
View this message in context:
http://maven.40175.n5.nabble.com/maven-release-plugin-is-not-working-properly-tp5759252p5759265.html
Sent from the Maven - Users mailing list archive at Nabble.com
Hi,
I am using the Maven release plugin and I am trying to make a release. When
I am on master (I am using Git) I have SNAPSHOT versions for both my
project (multimodule) and also for my dependencies (also multimodule).
Suppose I want to make a tag from master (skipping the creation of a
branch
with it that you have
the dependency version changed when you release - and even then, you have to do
it by using the ${project.version} property.
- Russ
On Jun 6, 2013, at 8:09 AM, Markos Fragkakis markos.fragka...@gmail.com wrote:
Hi,
I am using the Maven release plugin and I am trying
this message in context:
http://maven.40175.n5.nabble.com/Maven-Release-plugin-tp5756929p5758219.html
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
Hi
Just wondering if there is any way to automatically increment the minor
version in the pom in a multi-module project. For example:
currentVersion :- 1.0.1-SNASHOT
TO
newVersion :- 1.1.1-SNASHOT
Currently, we have the option of achieving the same through:
mvn release:update-versions
Hi,
No, that's not supported, but there's a feature request for it:
https://jira.codehaus.org/browse/MRELEASE-431 (and related issues)
Robert
Op Fri, 24 May 2013 16:22:36 +0200 schreef Sonesh Kumar Malhotra
sonesh.kumar.malho...@ericsson.com:
Hi
Just wondering if there is any way to
the error on scm status command.
Since replease-plug-in works on my laptop this is an issue on
interaction between maven, release-plugin and Jazz build engine
I re-ran the RTC build with -X switch in maven to get detailed log so
we can compare against release.log (one from my
/2013 09:35 AM
Subject:RE: Maven-release-plugin AND IBM RTC build engine...
I did few more experiments...
1) Renamed the RTC component so there is no space in the name.
2) Made sure directory has permission for build account etc.
3) Experimented by replacing maven command to just mvn
[INFO] Executing: cmd.exe /X /C scm status --username srvrtcbuild --password
* --wide
[INFO] Working directory: D:\RTCBuildWorkspace\EI-ITAMTEST\uCMDBPackages
[DEBUG] ErrorConsumer.consumeLine: Problem running 'status':
[DEBUG] ErrorConsumer.consumeLine: Current directory is not shared.
Message-
From: Wayne Fay [mailto:wayne...@gmail.com]
Sent: Friday, May 03, 2013 2:24 PM
To: Maven Users List
Subject: Re: Maven-release-plugin AND IBM RTC build engine...
[INFO] Executing: cmd.exe /X /C scm status --username srvrtcbuild --password
* --wide
[INFO] Working directory: D
.
So it's only via release-plug-in we get the error on scm status command.
Since replease-plug-in works on my laptop this is an issue on interaction between
maven, release-plugin and Jazz build engine
I re-ran the RTC build with -X switch in maven to get detailed log so
we can
.
Nothing to do with the release-plugin itself.
Thanks,
Robert
-Original Message-
From: Eric Kolotyluk [mailto:eric.koloty...@gmail.com]
Sent: Friday, May 03, 2013 4:48 PM
To: users@maven.apache.org
Subject: Re: Maven-release-plugin AND IBM RTC build engine...
Doing a Maven release can
: Friday, May 03, 2013 4:48 PM
To: users@maven.apache.org
Subject: Re: Maven-release-plugin AND IBM RTC build engine...
Doing a Maven release can be tricky if you are having problems with your
SCM plugin. It took me a long time to get release to work with Perforce
(but it still does not work properly
minf...@sharp.fm:
On 30 Apr 2013, at 11:21 PM, Roger Brechbühl rotscher...@gmail.com
wrote:
Maybe somebody is interested in how a release could be built in a more
lightweight and safe way than with the maven-release-plugin. Especially
recommended for nightly releases.
It's not yet
, at 11:21 PM, Roger Brechbühl rotscher...@gmail.com
wrote:
Maybe somebody is interested in how a release could be built in a more
lightweight and safe way than with the maven-release-plugin.
Especially
recommended for nightly releases.
It's not yet released, but basically fully working
maven-releases, or an alternative to the
maven-release-plugin
Hi all
Maybe somebody is interested in how a release could be built in a more
lightweight and safe way than with the maven-release-plugin. Especially
recommended for nightly releases.
It's not yet released, but basically fully
On 30 Apr 2013, at 11:21 PM, Roger Brechbühl rotscher...@gmail.com wrote:
Maybe somebody is interested in how a release could be built in a more
lightweight and safe way than with the maven-release-plugin. Especially
recommended for nightly releases.
It's not yet released, but basically
.
Robert
Op Wed, 01 May 2013 12:44:19 +0200 schreef Graham Leggett
minf...@sharp.fm:
On 30 Apr 2013, at 11:21 PM, Roger Brechbühl rotscher...@gmail.com
wrote:
Maybe somebody is interested in how a release could be built in a more
lightweight and safe way than with the maven-release-plugin
with the maven-release-plugin. Especially
recommended for nightly releases.
It's not yet released, but basically fully working:
*mvn clean install -Dversion.override=1.2.3-S-5*
https://github.com/rotscher/**emerging/tree/version.**
override-with_maven_install-2.**4https://github.com
).
repository local directory =
localRepositoryD:\data\mavenrepo\ei_itam_discovery/localRepository
RTC load directory: load directory = ${BUILDWORKSPACE}\EI-Discovery2
[INFO] --- maven-release-plugin:2.4.1:prepare (default-cli) @ uCMDB-PatternDev
---
[INFO] Verifying that there are no local
[INFO] Executing: cmd.exe /X /C scm status --username srvrtcbuild --password
* --wide
[INFO] Working directory: D:\RTCBuildWorkspace\EI-Discovery2\EI AS-ITAM uCMDB
Pattern DEV
Again, you probably need to ensure that all directories involved in
the build do not have any spaces in the
If IBM were smart they would embrace Maven and do everything possible to
support it well within Jazz. Maven does not really compete with anything
IBM is doing, but it certainly compliments it in a positive way.
I have met a few people in IBM who are sympathetic to better support for
Maven, but I
Consider creating this directory D:\RTCBuildWorkspace\EI-Discovery2\EI
and sharing it, then try again to see if your error message changes. It
might help you to understand whether it's the directory name or the fact
that it's not shared, as the message says.
Shawn
-Original Message-
From: Wayne Fay [mailto:wayne...@gmail.com]
Sent: Tuesday, April 30, 2013 12:09 PM
To: Maven Users List
Subject: Re: Maven-release-plugin AND IBM RTC build engine...
[INFO] Executing: cmd.exe /X /C scm status --username srvrtcbuild --password
* --wide
[INFO
Hi all
Maybe somebody is interested in how a release could be built in a more
lightweight and safe way than with the maven-release-plugin. Especially
recommended for nightly releases.
It's not yet released, but basically fully working:
*mvn clean install -Dversion.override=1.2.3-S-5*
https
What I don't understand is that why would it work on my local laptop
with the same directory names? I realize the working directory on the RTC
build server uses the Component name (RTC term) which does have spaces in it.
I couldn't even begin to guess. Clearly something is different
kind of formats are supported? jar, war etc.
Thanks
nambi
-Original Message-
From: Roger Brechbühl [mailto:rotscher...@gmail.com]
Sent: Tuesday, April 30, 2013 2:22 PM
To: users@maven.apache.org
Subject: Lightweight maven-releases, or an alternative to the
maven-release-plugin
Hi all
Subject: RE: Maven-release-plugin AND IBM RTC build engine...
Everyone,
Thanks for suggestions.
I will try without spaces and reduced length for working directory folder
name...
If I succeed I will post the update...
It seems most people use release plug-in but not with RTC build engine
in
functionality behind open source tools. For all intents, it
practically requires the VENDOR to put in the effort to build/adapt
the plugin for their products. If you have the ability to do so, I'd
open a bug/ticket with IBM and ask them to support the Maven release
plugin, otherwise I doubt
, it
practically requires the VENDOR to put in the effort to build/adapt
the plugin for their products. If you have the ability to do so, I'd
open a bug/ticket with IBM and ask them to support the Maven release
plugin, otherwise I doubt this functionality will ever be added by
anyone else.
Wayne
Hi,
I am having problems making the maven-release-plugin working with local RTC
workspace OR in the build engine.
Trying to find someone who has used maven-release-plugin WITH RTC build engine.
Thanks,
Robert
1) If I run in the build engine I get below error.
I was told it's not maven
I'd recommend using pathnames with no spaces in them, or avoiding Windows
altogether.
On Fri, Apr 19, 2013 at 10:02 AM, Zanzerkia, Robert
robert.zanzer...@fmr.com wrote:
Hi,
I am having problems making the maven-release-plugin working with local
RTC workspace OR in the build engine
n'aura pas n'importe
quel effet légalement obligatoire. Étant donné que les email peuvent facilement
être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité
pour le contenu fourni.
Date: Fri, 19 Apr 2013 11:40:43 -0400
Subject: Re: Maven-release-plugin AND IBM RTC build
Sorry, I cannot stop laughing because the statement is true, but so sad.
While most Windows APIs and UIs have been fixed to handle special
characters, such as spaces, sadly there are still places in Windows that
have not been fixed yet, and likely will never be fixed. Don't get me
started on
-Original Message-
From: Eric Kolotyluk [mailto:eric.koloty...@gmail.com]
Sent: Friday, April 19, 2013 9:26 PM
To: users@maven.apache.org
Subject: Re: Maven-release-plugin AND IBM RTC build engine...
Sorry, I cannot stop laughing because the statement is true, but so sad.
While most
of the
workspace.
Thanks,
Robert
-Original Message-
From: Mirko Friedenhagen [mailto:mfriedenha...@gmail.com]
Sent: Saturday, April 13, 2013 1:44 AM
To: Maven Users List
Subject: Re: Maven-release-plugin error
Third guess, on Windows upper and lower case are ignored, so C:/tm/ucmdb
and naming
] Executing: cmd.exe /X /C scm create snapshot --repository-uri
https://RTCURLHERE/jazz --username x --password * --name
uCMDB-PatternDev-0
.0.6 --description [maven-release-plugin] copy for tag uCMDB-PatternDev-0.0.6
uCMDB-PatternDev-0.0.6
[INFO] Working directory: C:\Documents and Settings
] Working directory: C:\Documents and
Settings\a408072.DMN1\workspace301\EI
AS-ITAM uCMDB Pattern DEV
[INFO] Executing: cmd.exe /X /C scm create snapshot --repository-uri
https://RTCURLHERE/jazz --username x --password * --name
uCMDB-PatternDev-0
.0.6 --description [maven-release-plugin
--repository-uri
https://RTCURLHERE/jazz --username x --password * --name
uCMDB-PatternDev-0
.0.6 --description [maven-release-plugin] copy for tag
uCMDB-PatternDev-0.0.6
uCMDB-PatternDev-0.0.6
[INFO] Working directory: C:\Documents and
Settings\a408072.DMN1\workspace301\EI
AS-ITAM uCMDB
Hi there,
We met an issue recently and maybe you could provide some help for me.
We have project name A, and we have a branch called branchA except the mater
branch for this project.
In sometimes, we also want to release the branchA, but it will cause the
confusion when it was upload the
On 2 April 2013 13:53, Tim Wu T tim.t...@ericsson.com wrote:
Hi there,
We met an issue recently and maybe you could provide some help for me.
We have project name A, and we have a branch called branchA except the
mater branch for this project.
In sometimes, we also want to release the
Hi Barrie,
Thanks.
Br,
Tim
-Original Message-
From: Barrie Treloar [mailto:baerr...@gmail.com]
Sent: Tuesday, April 02, 2013 12:35 PM
To: Maven Users List
Subject: Re: How to curtomize the maven release plugin upload jars?
On 2 April 2013 13:53, Tim Wu T tim.t...@ericsson.com wrote
The Apache Maven team is pleased to announce the release of the Maven
Release Plugin, version 2.4.1
This plugin is used to release a project with Maven, saving a lot of
repetitive, manual work. Releasing a project is made in two steps: prepare
and perform.
http://maven.apache.org/plugins
Robert
1) great, thank you!
2) does it mean 2.4.1 does not blow up with this:
http://jira.codehaus.org/browse/SCM-709
?
Andrei
Original Message
Subject: [ANN] Maven Release Plugin 2.4.1 Released
From: Robert Scholte rfscho...@apache.org
To: annou...@maven.apache.org, users
http://www.sonatype.com/people/2009/09/maven-tips-and-tricks-using-github/
using scm:git:git should do the trick.
/Anders
On Fri, 2013-03-22 at 00:10 +0100, Jeff wrote:
scm
connectionscm:git:ssh://g...@github.com:MyOrg/apps-thor.git/connection
You may try replacing the colon between host and orgname with a slash /.
Regards Mirko
--
Sent from my mobile
On Mar 22, 2013 12:11 AM, Jeff predato...@gmail.com wrote:
My release:prepare is failing when it tries the following:
git push ssh://g...@github.com:MyOrg/apps-thor.git
My release:prepare is failing when it tries the following:
git push ssh://g...@github.com:MyOrg/apps-thor.git
releaseBranch:releaseBranch
With the following error:
ssh: Could not resolve hostname github.com:MyOrg: Name or service not known
It also fails on the command line. If i
would be very welcome.
*Proposal: Modify Jenkins maven release plugin with the following
behavior:*
1.
Add a Cascade release dependent projects checkbox on release page
2.
After the release completes, look for jobs that are explicitly
dependent on the pre
I'm using maven release for a release procedure, following this workflow
1 - release:branch create a release candidate
using version X.X.X-000-SNAPSHOT
(000 stands for build number)
2 - release:prepare release:stage to deploy the
artifact to a staging repository
3 - Repeat step
On Thursday, 31 January 2013, Tonio Caputo wrote:
I'm using maven release for a release procedure, following this workflow
1 - release:branch create a release candidate
using version X.X.X-000-SNAPSHOT
(000 stands for build number)
2 - release:prepare release:stage to deploy the
Stephen,
Really thanks very much for your quick response, really a lot helpfull
!.
And I love the 'poor man's staging' phrase :)
thanks again
tonio
On Thu, Jan 31, 2013 at 5:29 PM, Stephen Connolly
stephen.alan.conno...@gmail.com wrote:
On Thursday, 31 January 2013, Tonio Caputo
The final line seems to explain the reason:
*svn: E170001: COPY of '/!svn/bc/199107/ParentPom': authorization failed:
Could not authenticate to server: rejected Digest challenge (
http://svnbridge.mycompany.com:8083)*
To confirm that it is not a Maven issue, you should try to re-execute the
I don't know if this is related to maven or SVN so hopefully this is
relevant here.
We use TFS as the source control system with SVNBridge non-Microsoft access.
I had a stand-alone Jenkins CI server running on Windows that we had been
using but recently I setup Jenkins on Linux (Ubuntu 12.10) in
Wilson,
Porcupine Tree
On Wed, Dec 19, 2012 at 12:04 PM, Robert Scholte rfscho...@apache.org
(mailto:rfscho...@apache.org)wrote:
The Apache Maven team is pleased to announce the release of the Maven
Release Plugin, version 2.4
This plugin is used to release a project with Maven
the release of the Maven
Release Plugin, version 2.4
This plugin is used to release a project with Maven, saving a lot of
repetitive, manual work. Releasing a project is made in two steps:
prepare
and perform.
http://maven.apache.org/**plugins/maven-release-plugin/http://maven.apache.org/plugins/maven
selfish and arrogant things — Steven Wilson,
Porcupine Tree
On Wed, Dec 19, 2012 at 12:04 PM, Robert Scholte rfscho...@apache.orgwrote:
The Apache Maven team is pleased to announce the release of the Maven
Release Plugin, version 2.4
This plugin is used to release a project with Maven, saving
The Apache Maven team is pleased to announce the release of the Maven
Release Plugin, version 2.4
This plugin is used to release a project with Maven, saving a lot of
repetitive, manual work. Releasing a project is made in two steps: prepare
and perform.
http://maven.apache.org/plugins
This is what you want
http://stackoverflow.com/questions/5558785/maven-release-plugin-git-and-the
-poms-not-at-the-top
On 12/5/12 4:36 PM, Coarr, Matt mco...@mitre.org wrote:
Hello,
I'm able to use mvn release:prepare but I run into an issue when I use
mvn release:perform.
My problem
Bingo! That worked like a charm! Thanks Roy!!
On 2012-12-06 09:49 , Lyons, Roy roy.ly...@cmegroup.com wrote:
This is what you want
http://stackoverflow.com/questions/5558785/maven-release-plugin-git-and-th
e
-poms-not-at-the-top
Hello,
I'm able to use mvn release:prepare but I run into an issue when I use mvn
release:perform.
My problem is that my scm data in my pom points to our git repository which
contains multiple projects.
Is there a way to tell release:perform to only checkout or export a
subdirectory of the
Hello to all,
i just want to know if someone knows about some influences between
the gwt-maven-plugin and the maven-release-plugin ?
may be someone has already some kind of this experience ?
Thanks in advance.
Karl-Heinz Marbaise
--
SoftwareEntwicklung Beratung SchulungTel.: +49 (0) 2405
i just want to know if someone knows about some influences between
the gwt-maven-plugin and the maven-release-plugin ?
missed to add the link to this:
https://groups.google.com/forum/?fromgroups=#!topic/codehaus-mojo-gwt-maven-plugin-users/dExd-zgzs9k
But doesn't the hint have
We have used gwt-maven-plugin in combination with the
maven-release-plugin without problems in the Geomajas project. We do not
use compileSourcesArtifacts though, we always either include the sources
in the jars themselves or include the sources jars as dependency in the
project.
Kind
I've recently upgraded to maven 3.0.4. Things went smoothly, but to
complete the upgrade I wanted to see how my release process worked on top
of the latest maven edition.
I've run into some problems, and I'm in need of some advice. I'm
using maven 3.0.4 with maven-release-plugin 2.3.2
to see how my release process worked on top
of the latest maven edition.
I've run into some problems, and I'm in need of some advice. I'm
using maven 3.0.4 with maven-release-plugin 2.3.2.
My release process uses the maven release plugin in batch mode. I
supply command line arguments
Robert
Thanks you very much for your reply.
Unfortunately, I am still having the same issue with release:prepare goal after
making this change (i.e. utilizing 2.3.2 version of the maven-release-plugin,
AND using the svnjava (maven-scm-plugin) as suggested in my parent pom.
I should have
Hi maven-release users!
Is it possible to checkout certain (non-head) revision of the trunk and use
release:prepare, release:perform on it?
I 've tried and I couldn't but perhaps there 're some parameters I 'm not
seeing.
I 've tried looking for this in the internet but it seems I 'm not
On Thu, Nov 8, 2012 at 2:34 PM, Nicolas Barrera nbarr...@gmail.com wrote:
Hi maven-release users!
Is it possible to checkout certain (non-head) revision of the trunk and use
release:prepare, release:perform on it?
I 've tried and I couldn't but perhaps there 're some parameters I 'm not
Ok, so the maven-release-plugin does not have any way of releasing without
the branch?
Nicolás.-
On Thu, Nov 8, 2012 at 10:38 AM, Thomas Matthijs li...@selckin.be wrote:
On Thu, Nov 8, 2012 at 2:34 PM, Nicolas Barrera nbarr...@gmail.com
wrote:
Hi maven-release users!
Is it possible
101 - 200 of 799 matches
Mail list logo
