Hi Baptiste,
Baptiste MATHUS wrote:
Well, from my understanding, this is not a regression.
What Paul says in the end
http://jira.codehaus.org/browse/MNG-4687?focusedCommentId=235494page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-
tabpanel#action_235494is
not a workaround, but
On 17/09/2010, at 2:23 AM, Jörg Schaible wrote:
Hi Baptiste,
Baptiste MATHUS wrote:
Well, from my understanding, this is not a regression.
What Paul says in the end
On 15/09/2010, at 2:26 PM, Mark Derricutt wrote:
Hey guys,
I was wondering what was happening with the new release of the
maven-release-plugin? Things seemed to go quiet on that front this past
week or so...
I see that the SCM plugin got released tho, would be good to get the release
Hey guys,
I was wondering what was happening with the new release of the
maven-release-plugin? Things seemed to go quiet on that front this past
week or so...
I see that the SCM plugin got released tho, would be good to get the release
plugin to come along for the ride as well...
mark
-- Forwarded message --
From: han hongfang hanhongf...@gmail.com
Date: Fri, Aug 27, 2010 at 5:27 PM
Subject: [maven-release-plugin] Is it possible to configure
maven-release-plugin to NOT pull in META-INF/LICENSE and NOTICE
To: us...@maven.apache.org
Hi,
Our project uses maven
Forward to dev list to see if somebody has some advice for me on this
question.
Best regards,
Han Hong Fang
-- Forwarded message --
From: han hongfang hanhongf...@gmail.com
Date: Fri, Aug 27, 2010 at 5:27 PM
Subject: [maven-release-plugin] Is it possible to configure
maven
regards,
Han Hong Fang
-- Forwarded message --
From: han hongfang hanhongf...@gmail.com
Date: Fri, Aug 27, 2010 at 5:27 PM
Subject: [maven-release-plugin] Is it possible to configure
maven-release-plugin to NOT pull in META-INF/LICENSE and NOTICE
To: us...@maven.apache.org
What project are you a committer on?
On Fri, Apr 16, 2010 at 10:42 PM, Delos dait...@gmail.com wrote:
Hi,
I'm trying to set up a staging site with mvn release:perform. The process
seems blocked when I saw the message below.
[INFO] [INFO] Generating Dependency Convergence report.
[INFO]
Hi,
I'm trying to set up a staging site with mvn release:perform. The process
seems blocked when I saw the message below.
[INFO] [INFO] Generating Dependency Convergence report.
[INFO] [INFO] [site:deploy {execution: default-deploy}]
[INFO]
[INFO]
[INFO] Note that too many successive login
The Maven team is pleased to announce the release of the Maven Release
Plugin, version 2.0. This release also includes Maven Release Manager,
version 2.0.
This plugin is used to release a project with Maven, saving a lot of
repetitive, manual work.
http://maven.apache.org/plugins/maven-release
the root cause of the exception. Upgraded
Maven prerequisite to 2.0.9
Modified:
maven/release/trunk/maven-release-plugin/pom.xml
maven/release/trunk/maven-release-plugin/src/main/java/org/apache/maven/plugins/release/BranchReleaseMojo.java
maven/release/trunk/maven-release-plugin
On 27/01/2010, at 2:07 AM, Olivier Lamy wrote:
argh too fast. (I have it locally :-) )
oops, sorry :) Just wanted to get things closed out that are open for the
version. I'll do MRELEASE-3 in the morning.
IMHO we have to align maven version in release-manager too.
Good catch - done.
-
Hi *,
We've been trying to build our internal release tools based on maven-release
infrastructure.
We failed when we tried to add new properties to configuration.
Now we are building maven plugin that will feature a bit extended concept of
ReleasePhase
(added dependencies between phases) and
You may want to take a look at the enforcer plugin and the rules, many
of the release criteria checks are already implemented as enforcer
rules. If you build something that could consume the enforcer rule
api, that would be pretty handy at least for the validation parts of
the release process.
On
Hi All,
I'm a bit new to the whole maven thing so bare with me please.
I'm having issues with the release plugin. I can release my core
library's with out any problems but I'm struggling with the multi module
project.
1. When I do a prepare for my project, the web module fails saying it
cant
, Brian Foxbri...@infinity.nu wrote:
The version in the pom is the locked down version for our plugins to use.
The latest release plugin is 2.0-beta-9:
http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-release-plugin/
You can override that version in your pom if you are releasing a plugin
On Tue, Jun 9, 2009 at 8:11 AM, Brian Foxbri...@infinity.nu wrote:
I would drop the version from the docs if you're concerned of it being
out of date. I don't think we should worry about updating that page
continuously if we change a version in the pom.
I assumed the reason for the version was
The lastest version according to
http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-plugins/
is version 13
Which defines the maven-release-plugin as 2.0-beta-8
But the http://maven.apache.org/developers/release/releasing.html
documentation says to use 2.0-beta-9.
Is the documentation
The version in the pom is the locked down version for our plugins to use.
The latest release plugin is 2.0-beta-9:
http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-release-plugin/
You can override that version in your pom if you are releasing a plugin...we
don't update the parent
On Mon, Jun 8, 2009 at 12:10 AM, Brian Foxbri...@infinity.nu wrote:
The version in the pom is the locked down version for our plugins to use.
The latest release plugin is 2.0-beta-9:
http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-release-plugin/
You can override that version
Is it already possible to do the interpolation of certain properties
inside a plugin? So when I have a Project object I want to ask the API
to interpolate a certain string with the existing project values.
The reason I ask this is to solve MRELEASE-150 by adding interpolation
of %{...} variables
an accepted
situation perhaps ?
It looks not (or not really tested :-) ) because here you have a bad
information in your pom.
Try mvn help:effective-pom I'm not sure the scm information is correct.
btw : can you test with
http://maven.apache.org/plugins/maven-release-plugin/prepare-mojo.html#remoteTagging
On Wed, Apr 1, 2009 at 9:24 AM, Olivier Lamy ol...@apache.org wrote:
Hi,
Is it a release of a project which doesn't have a scm element and use
a released parent project which has one ?
That's the exact situation yes. Is this no longer an accepted
situation perhaps ?
Jorg
: Niall Pemberton [mailto:niall.pember...@gmail.com]
Sent: Saturday, March 28, 2009 5:52 PM
To: Maven Developers List
Subject: Re: [ANN] Maven Release Plugin 2.0-beta-9 Released
The parent pom doesn't seem to have found its way to the public repo
yet, is it on its way?
http://repo1.maven.org
To: Maven Developers List
Subject: Re: [ANN] Maven Release Plugin 2.0-beta-9 Released
The parent pom doesn't seem to have found its way to the public repo
yet, is it on its way?
http://repo1.maven.org/maven2/org/apache/maven/release/maven-release/
Niall
On Sat, Mar 28, 2009 at 5:36 PM, Olivier
/maven-release-plugin/prepare-mojo.html#remoteTagging
set to false ?
yep, added -DremoteTagging=false and now it works.
Should i file an issue for this ?
Thanks,
Jorg
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
.
:-) (in this case IMHO your project is bad : publishing site will
publish bad source info etc.. changelog plugin can not work etc..)
btw : can you test with
http://maven.apache.org/plugins/maven-release-plugin/prepare-mojo.html#remoteTagging
set to false ?
yep, added -DremoteTagging=false and now
...@gmail.com] On Behalf Of
Olivier Lamy
Sent: Saturday, March 28, 2009 6:00 PM
To: Maven Developers List
Subject: Re: [RESULT] [VOTE] Release Maven Release plugin version
2.0-beta-9 and scm 1.2
So it looks they are still issues with groupId
org.apache.maven.release which is not sync.
Can you fix
Hi,
I have use the nexus ui to promote artifacts.
The release plugin is on central repo but not scm artifacts !!
Can someone have a look ?
Other issue : one day after site deploy on p.a.o sites are not yet
sync (release plugin and scm site)
Thanks!
--
Olivier
2009/3/27 Olivier Lamy
Hi,
I have use the nexus ui to promote artifacts.
The release plugin is on central repo but not scm artifacts !!
Can someone have a look ?
Other issue : one day after site deploy on p.a.o sites are not yet
sync (release plugin and scm site)
Thanks!
--
Olivier
2009/3/27 Olivier Lamy
Release plugin version
2.0-beta-9 and scm 1.2
Hi,
I have use the nexus ui to promote artifacts.
The release plugin is on central repo but not scm artifacts !!
Can someone have a look ?
Other issue : one day after site deploy on p.a.o sites are not yet
sync (release plugin and scm site)
Thanks
, March 28, 2009 3:42 AM
To: Maven Developers List; scm-...@maven.apache.org
Subject: Re: [RESULT] [VOTE] Release Maven Release plugin version
2.0-beta-9 and scm 1.2
Hi,
I have use the nexus ui to promote artifacts.
The release plugin is on central repo but not scm artifacts !!
Can someone
Hi,
The Maven team is pleased to announce the release of the Maven Release
Plugin, version 2.0-beta-9.
http://maven.apache.org/plugins/maven-release-plugin/
You should specify the version in your project's plugin configuration:
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven
of the Maven Release
Plugin, version 2.0-beta-9.
http://maven.apache.org/plugins/maven-release-plugin/
You should specify the version in your project's plugin configuration:
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-release-plugin/artifactId
version2.0-beta-9/version
-...@maven.apache.org
Subject: Re: [RESULT] [VOTE] Release Maven Release plugin version
2.0-beta-9 and scm 1.2
Hi,
I have use the nexus ui to promote artifacts.
The release plugin is on central repo but not scm artifacts !!
Can someone have a look ?
Other issue : one day after site deploy on p.a.o
All set.
-Original Message-
From: Niall Pemberton [mailto:niall.pember...@gmail.com]
Sent: Saturday, March 28, 2009 5:52 PM
To: Maven Developers List
Subject: Re: [ANN] Maven Release Plugin 2.0-beta-9 Released
The parent pom doesn't seem to have found its way to the public repo
yet
To: Maven Developers List
Subject: Re: [RESULT] [VOTE] Release Maven Release plugin version
2.0-beta-9 and scm 1.2
So it looks they are still issues with groupId
org.apache.maven.release which is not sync.
Can you fix that too ?
The new release of release plugin is still not usuable.
Thanks
to announce the release of the Maven Release
Plugin, version 2.0-beta-9.
http://maven.apache.org/plugins/maven-release-plugin/
You should specify the version in your project's plugin configuration:
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-release-plugin/artifactId
So my +1 means 2 * +1 :-).
--
Olivier
2009/3/23 Olivier Lamy ol...@apache.org:
Hi,
I'd like to release maven-scm 1.2 and maven-release-plugin 2.0-beta-9.
This two release are in only one vote because they are very dependant
due to a fix for people using subversion version 1.5.0
Hi,
The votes has passed with the following result :
+1 (binding) : Arnaud HERITIER, Jason van Zyl,Emmanuel Venisse, Olivier Lamy
+1 (non-binding) : Marc Struberg
I will move artifacts to central repo and publish the site.
Thanks,
--
Olivier
Hi,
I'd like to release maven-scm 1.2 and maven-release-plugin 2.0-beta-9.
This two release are in only one vote because they are very dependant
due to a fix for people using subversion version 1.5.0.
Concerning maven-scm :
We solved 36 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa
+2
Emmanuel
On Mon, Mar 23, 2009 at 11:55 PM, Olivier Lamy ol...@apache.org wrote:
Hi,
I'd like to release maven-scm 1.2 and maven-release-plugin 2.0-beta-9.
This two release are in only one vote because they are very dependant
due to a fix for people using subversion version 1.5.0
Hi,
I'd like to release maven-scm 1.2 and maven-release-plugin 2.0-beta-9.
This two release are in only one vote because they are very dependant
due to a fix for people using subversion version 1.5.0.
Concerning maven-scm :
We solved 36 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa
...@gmail.com] On Behalf Of Olivier
Lamy
Sent: Monday, March 23, 2009 3:56 PM
To: Maven Developers List; scm-...@maven.apache.org
Subject: [VOTE] Release Maven Scm 1.2 and maven-release-plugin 2.0-beta-9
Hi,
I'd like to release maven-scm 1.2 and maven-release-plugin 2.0-beta-9.
This two release
; scm-...@maven.apache.org
Subject: [VOTE] Release Maven Scm 1.2 and maven-release-plugin 2.0-beta-9
Hi,
I'd like to release maven-scm 1.2 and maven-release-plugin 2.0-beta-9.
This two release are in only one vote because they are very dependant
due to a fix for people using subversion version
Good to hear. :)
-Original Message-
From: oliver.l...@gmail.com [mailto:oliver.l...@gmail.com] On Behalf Of Olivier
Lamy
Sent: Monday, March 23, 2009 4:39 PM
To: Maven Developers List
Subject: Re: [VOTE] Release Maven Scm 1.2 and maven-release-plugin 2.0-beta-9
argh :-)
Just tested
Subject: [VOTE] Release Maven Scm 1.2 and maven-release-plugin 2.0-beta-9
Hi,
I'd like to release maven-scm 1.2 and maven-release-plugin 2.0-beta-9.
This two release are in only one vote because they are very dependant
due to a fix for people using subversion version 1.5.0.
Concerning maven
+1 (non binding)
I successfully did a full release cycle to a git repo.
LieGrue and gn8,
strub
--- Olivier Lamy ol...@apache.org schrieb am Mo, 23.3.2009:
Von: Olivier Lamy ol...@apache.org
Betreff: [VOTE] Release Maven Scm 1.2 and maven-release-plugin 2.0-beta-9
An: Maven Developers List
. :)
-Original Message-
From: oliver.l...@gmail.com [mailto:oliver.l...@gmail.com] On Behalf
Of Olivier Lamy
Sent: Monday, March 23, 2009 3:56 PM
To: Maven Developers List; scm-...@maven.apache.org
Subject: [VOTE] Release Maven Scm 1.2 and maven-release-plugin
2.0-beta-9
Hi,
I'd like
+2
Arnaud
2009/3/23 Olivier Lamy ol...@apache.org
Hi,
I'd like to release maven-scm 1.2 and maven-release-plugin 2.0-beta-9.
This two release are in only one vote because they are very dependant
due to a fix for people using subversion version 1.5.0.
Concerning maven-scm :
We solved 36
Chaffee jason.chaf...@zilliontv.tv:
Good to hear. :)
-Original Message-
From: oliver.l...@gmail.com [mailto:oliver.l...@gmail.com] On Behalf Of
Olivier Lamy
Sent: Monday, March 23, 2009 4:39 PM
To: Maven Developers List
Subject: Re: [VOTE] Release Maven Scm 1.2 and maven-release-plugin
: oliver.l...@gmail.com [mailto:oliver.l...@gmail.com] On Behalf Of
Olivier Lamy
Sent: Monday, March 23, 2009 3:56 PM
To: Maven Developers List; scm-...@maven.apache.org
Subject: [VOTE] Release Maven Scm 1.2 and maven-release-plugin 2.0-beta-9
Hi,
I'd like to release maven-scm 1.2 and maven-release
+2
On 23-Mar-09, at 5:15 PM, Arnaud HERITIER wrote:
+2
Arnaud
2009/3/23 Olivier Lamy ol...@apache.org
Hi,
I'd like to release maven-scm 1.2 and maven-release-plugin 2.0-
beta-9.
This two release are in only one vote because they are very dependant
due to a fix for people using subversion
+2
Emmanuel
On Mon, Mar 23, 2009 at 11:55 PM, Olivier Lamy ol...@apache.org wrote:
Hi,
I'd like to release maven-scm 1.2 and maven-release-plugin 2.0-beta-9.
This two release are in only one vote because they are very dependant
due to a fix for people using subversion version 1.5.0
Hello,
I would like to start a discussion to get the patches of issues MRELEASE-294
and MRELEASE-389 applied. Can the responsible persons for maven-release-manager
and maven-release-plugin review the patches and comment on any issues they see
with the provided patches?
http
issue while using release-plugin. Since I do
parallel builds, I can't rely on ~/.m2/repository for all my builds, so
I must different local repo. Any help is appreciated.
Thanks,
Sahoo
Jane Young wrote:
Hi Release Plugin Gurus,
I want to specify a local maven repo.
Using maven release plugin
, November 10, 2008 9:29 PM
To: Maven Developers List
Subject: maven-release-plugin: useReleaseProfile - how does this work to
add sources and javadocs?
I'm looking at the code for maven-release-plugin and I can't see how
it add sources and javadocs.
RunPerformGoalsPhase is about the only interesting
On Tue, Nov 11, 2008 at 1:23 PM, Brian E. Fox [EMAIL PROTECTED] wrote:
The release profile is built into the superpom.
http://svn.eu.apache.org/viewvc/maven/components/branches/maven-2.1.x/ma
ven-project/src/main/resources/org/apache/maven/project/pom-4.0.0.xml?vi
ew=markup
Thanks.
Now I
I'm looking at the code for maven-release-plugin and I can't see how
it add sources and javadocs.
RunPerformGoalsPhase is about the only interesting place that
isUseReleaseProfile() is used and all it does is add
-DperformRelease=true to additionalArguments which is then passed
this on this
mailing list.
cheers
Arnaud
On Tue, Nov 4, 2008 at 1:59 PM, Peter Nedonosko
[EMAIL PROTECTED] wrote:
Hi guys!
I try to use maven-release-plugin on WindowsXP SP2 with maven 2.0.8, Java
1.5.0_15 and svn 1.5.4.
I cannot run release:branch goal from trunk successful.
Branch
.
cheers
Arnaud
On Tue, Nov 4, 2008 at 1:59 PM, Peter Nedonosko
[EMAIL PROTECTED] wrote:
Hi guys!
I try to use maven-release-plugin on WindowsXP SP2 with maven 2.0.8, Java
1.5.0_15 and svn 1.5.4.
I cannot run release:branch goal from trunk successful.
Branch commit failed on command
problems to create tags with svn 1.5.x. I thought it was
fixed, but I'm not sure. There was several threads about this on this
mailing list.
cheers
Arnaud
On Tue, Nov 4, 2008 at 1:59 PM, Peter Nedonosko
[EMAIL PROTECTED] wrote:
Hi guys!
I try to use maven-release-plugin on WindowsXP SP2
Hi guys!
I try to use maven-release-plugin on WindowsXP SP2 with maven 2.0.8, Java
1.5.0_15 and svn 1.5.4.
I cannot run release:branch goal from trunk successful.
Branch commit failed on command
svn --non-interactive copy --file D:\Tmp\maven-scm-1276451448.commit .
http://svn.exoplatform.org
Hi,
The vote has passed with the following result.
+1 (binding) : Arnaud, Emmanuel, Olivier
+1 (non binding) : Remy, Mark
I will move artifacts to central and publish the web site.
Thanks,
--
Olivier
-
To unsubscribe, e-mail:
The Maven team is pleased to announce the release of the Maven Release
Plugin, version 2.0-beta-8.
http://maven.apache.org/plugins/maven-release-plugin/
You should specify the version in your project's plugin configuration:
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven
+1
Emmanuel
On Mon, Oct 27, 2008 at 8:29 PM, Olivier Lamy [EMAIL PROTECTED] wrote:
Hi,
I'd like to release Maven Release plugin version 2.0-beta-8. (last
release is one year old).
We solved 27 issues :
http://jira.codehaus.org/secure/ReleaseNote.jspa?version=13812styleName=HtmlprojectId
Hi,
I'd like to release Maven Release plugin version 2.0-beta-8. (last
release is one year old).
We solved 27 issues :
http://jira.codehaus.org/secure/ReleaseNote.jspa?version=13812styleName=HtmlprojectId=11144Create=Create
Staging repo:
http://people.apache.org/~olamy/staging-repo/
Staging site
+1 (non-binding)
Thanks
Rémy
+1
Arnaud
On Mon, Oct 27, 2008 at 7:29 PM, Olivier Lamy [EMAIL PROTECTED] wrote:
Hi,
I'd like to release Maven Release plugin version 2.0-beta-8. (last
release is one year old).
We solved 27 issues :
http://jira.codehaus.org/secure/ReleaseNote.jspa?version=13812styleName=HtmlprojectId
tested a full release cycle against a git repo without any problems.
+1 (nonbinding)
LieGrue,
strub
--- Olivier Lamy [EMAIL PROTECTED] schrieb am Mo, 27.10.2008:
Von: Olivier Lamy [EMAIL PROTECTED]
Betreff: [VOTE] Release Maven Release plugin version 2.0-beta-8
An: Maven Developers List
Any comments??? Please 'cc' me in the response as I am not in this alias.
Thanks,
Sahoo
---BeginMessage---
Wendy Smoak wrote:
On Wed, Oct 15, 2008 at 3:50 AM, Sahoo [EMAIL PROTECTED] wrote:
As you can see, it uses a packaging type called distribution-fragment, which
is understood by our
-td19727479.html#a19727479),
is that possible to release maven release plugin ?
Thanks,
Rémy
here in the previous email :-) ).
I can but first I'd like to release invoker plugin 1.3.
Now that maven invoker plugin 1.3 is released (cf.
http://www.nabble.com/-ANN--Maven-Invoker-Plugin-1.3-Released-td19727479.html#a19727479),
is that possible to release maven release plugin ?
Thanks
Alessandro
[EMAIL PROTECTED] wrote:
Olivier Lamy said:
Hi,
Personnaly, I have planned to do it near end of September.
I hope will be so.
Bye
Remy Sanlaville wrote:
Hi,
ping: Someone know when the 2.0-beta-8 of maven release plugin will be
released ?
We are really
On Wed, Sep 24, 2008 at 10:04 AM, Arnaud HERITIER [EMAIL PROTECTED] wrote:
Someone wants to take the lead ?
there are 2 issues to fix in the roadmap
If they are not regressions, and no one is actively working on them,
then let's push them out to the next version and get the work that's
already
wrote:
Hi,
ping: Someone know when the 2.0-beta-8 of maven release plugin will be
released ?
We are really waiting for it.
Thanks,
Rémy
--
View this message in context:
http://www.nabble.com/Maven-release-plugin-tp19269992p19652882.html
Sent from the Maven - Users
PROTECTED] wrote:
Seems that with svn 1.4.4 the maven-release-plugin works just fine...
whats
going on with SVN 1.5.x?
--jason
On Aug 21, 2008, at 2:15 PM, Jason Dillon wrote:
I'm having lots of problems using the maven-release-plugin with SVN
1.5.x
on my Mac. I found this thread
that with svn 1.4.4 the maven-release-plugin works just fine...
whats
going on with SVN 1.5.x?
--jason
On Aug 21, 2008, at 2:15 PM, Jason Dillon wrote:
I'm having lots of problems using the maven-release-plugin with SVN
1.5.x
on my Mac. I found this thread:
http
Anyone?
--jason
On Thu, Aug 21, 2008 at 3:52 PM, Jason Dillon [EMAIL PROTECTED] wrote:
Seems that with svn 1.4.4 the maven-release-plugin works just fine... whats
going on with SVN 1.5.x?
--jason
On Aug 21, 2008, at 2:15 PM, Jason Dillon wrote:
I'm having lots of problems using
I'm having lots of problems using the maven-release-plugin with SVN
1.5.x on my Mac. I found this thread:
http://www.nabble.com/Mac-OS-X-%2B-SVN-1.5.1-%3D-Branch-problem-td19017538.html
Didn't find any solution though... except to use SVN 1.4.x, though
seems like I can't checkout
Seems that with svn 1.4.4 the maven-release-plugin works just fine...
whats going on with SVN 1.5.x?
--jason
On Aug 21, 2008, at 2:15 PM, Jason Dillon wrote:
I'm having lots of problems using the maven-release-plugin with SVN
1.5.x on my Mac. I found this thread:
http
CI did not develop or make release for us ;) So, I think we need to be
developer oriented and not CI oriented.
Then activate the Its in the release, that makes perfect sense. The
point is I don't need long running Its in my face on every build. I
should run them before I commit, when I release
I know I'm not a part of the core team here, but the two tests are
written differently, and send different signals. It's
quiteappropriate to run them on different schedules, and not least
since they're usually slower than Unit Tests. In nearly all of my
clients, they don't have ITs on
Hi Benjamin,
2008/8/7 [EMAIL PROTECTED]:
Author: bentmann
Date: Thu Aug 7 10:41:00 2008
New Revision: 683661
URL: http://svn.apache.org/viewvc?rev=683661view=rev
Log:
o Synced id and activation of integration-tests with core ITs
Modified:
maven/release/trunk/maven-release-plugin
Hi Vincent,
Removing this activation check, ITs will never be been called by
default. Is it really the wanted behaviour?
IMHO I think unit testing implies IT testing. Does I missed something?
Well, it appears to be a personal taste: I am just like you in favor of
running tests (whatever
2008/8/7 Benjamin Bentmann [EMAIL PROTECTED]:
Hi Vincent,
Removing this activation check, ITs will never be been called by
default. Is it really the wanted behaviour?
IMHO I think unit testing implies IT testing. Does I missed something?
Well, it appears to be a personal taste: I am just
Hi,
Agree with Vincent, they must be activated by default (for me it tests
are similar to a junit tests).
And as we have documented in the surefire mojo : skip ... Its use is
NOT RECOMMENDED ..
By the way I can add some extra parameters during my build.
But I can forget and maybe commit
You're right, we have to activate them in the release process.
CI will launch them automatically every 4 hours.
IT's are often very long.
The problem we have actually (see my other thread) is that we develop too
many ITs and not enough UTs.
That's why I would prefer to have a good code coverage
I also think they should be activated by default.
Olivier Lamy wrote:
Hi,
Agree with Vincent, they must be activated by default (for me it tests
are similar to a junit tests).
And as we have documented in the surefire mojo : skip ... Its use is
NOT RECOMMENDED ..
By the way I can add some
(reposted from issues@ once I realized that was for the issue tracker,
sorry about that)
Hi, I'm using 2.0-beta-7 of the maven release plugin, but I could
really use the new support for accepting releaseVersion,
developmentVersion, etc... from -D properties.
Is the release of 2.0-beta-8
SRO on 9628 0556 and
request a copy.
--
View this message in context:
http://www.nabble.com/Maven-Release-Plugin---2.0-beta-7-and-MRELEASE-326-tp17860402p17998598.html
Sent from the Maven Developers mailing list archive at Nabble.com
Is anybody working on this but not updated in JIRA? This problem prevents
any automated use of the plugin.
Thanks,
Ian
Disclaimer: The information transmitted is intended only for the person or
entity to which it is addressed and may contain confidential and/or privileged
material. Any
of the Maven WAR
Plugin, version 2.0 beta-7.
http://maven.apache.org/plugins/maven-release-plugin
Release Notes - Maven 2.x Release Plugin - Version 2.0-beta-7
** Bug
* [MRELEASE-124] - Impossible to depend on a deployed snapshot
* [MRELEASE-240] - release-pom.xml does not contain
On 10/28/07, Arik Kfir [EMAIL PROTECTED] wrote:
There's a mistake in the text - it should read release of the Maven
ReleasePlugin, not the
WAR plugin...
Probably something in the POM plugin configuration that was once
copy-pasted... ;-)
Well No. Brian did the copy pasting for sure since
Oh... :)
On 10/28/07, Stephane Nicoll [EMAIL PROTECTED] wrote:
On 10/28/07, Arik Kfir [EMAIL PROTECTED] wrote:
There's a mistake in the text - it should read release of the Maven
ReleasePlugin, not the
WAR plugin...
Probably something in the POM plugin configuration that was once
Damn, you caught me ;-)
-Original Message-
From: Stephane Nicoll [mailto:[EMAIL PROTECTED]
Sent: Sunday, October 28, 2007 4:26 AM
To: Maven Developers List
Subject: Re: [ANN] Maven Release Plugin 2.0-beta-7 Released
On 10/28/07, Arik Kfir [EMAIL PROTECTED] wrote:
There's a mistake
Just wait till I'll start using it! :)
On 10/28/07, Brian E. Fox [EMAIL PROTECTED] wrote:
Damn, you caught me ;-)
-Original Message-
From: Stephane Nicoll [mailto:[EMAIL PROTECTED]
Sent: Sunday, October 28, 2007 4:26 AM
To: Maven Developers List
Subject: Re: [ANN] Maven Release
-release-plugin 2.0-beta-7
I ran into an issue releasing 2.0.8 due to
http://jira.codehaus.org/browse/MRELEASE-296 and the addition of the
${mavenVersion} in the poms. This release is required for a release of
2.0.8.
Staging repo:
http://people.apache.org/~brianf/staging-repository
+1
Stéphane
On 10/24/07, Brian E. Fox [EMAIL PROTECTED] wrote:
I ran into an issue releasing 2.0.8 due to
http://jira.codehaus.org/browse/MRELEASE-296 and the addition of the
${mavenVersion} in the poms. This release is required for a release of
2.0.8.
Staging repo:
+1
--
Olivier
2007/10/24, Brian E. Fox [EMAIL PROTECTED]:
I ran into an issue releasing 2.0.8 due to
http://jira.codehaus.org/browse/MRELEASE-296 and the addition of the
${mavenVersion} in the poms. This release is required for a release of
2.0.8.
Staging repo:
401 - 500 of 743 matches
Mail list logo
