+1
Emmanuel
Brian E. Fox a écrit :
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:
+!
Brian E. Fox 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:
http://people.apache.org/~brianf/staging-repository/
To: Maven Developers List
Subject: Maven release plugin question
Hi All,
Does anyone know why the release plugin requires test scope dependency
resolution? I was looking into this issue:
http://jira.codehaus.org/browse/MRELEASE-285
And I found that if I remove this:
@requiresDependencyResolution
Done.
-Original Message-
From: Paul Gier [mailto:[EMAIL PROTECTED]
Sent: Tuesday, October 23, 2007 3:54 PM
To: Maven Developers List
Cc: Brian E. Fox
Subject: Re: Maven release plugin question
I tested the plugin without the requiresDependencyResolution parameter,
and it
was still able
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/
Release Notes:
+1
Arnaud
On 24/10/2007, 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
On 23 Oct 07, at 6:41 PM 23 Oct 07, Brian E. Fox 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:
Hi All,
Does anyone know why the release plugin requires test scope dependency
resolution? I was looking into this issue:
http://jira.codehaus.org/browse/MRELEASE-285
And I found that if I remove this:
@requiresDependencyResolution test
The issue is resolved and all of the unit tests still
Maybe they want to check that no test dependencies are snapshots either?
-Original Message-
From: Paul Gier [mailto:[EMAIL PROTECTED]
Sent: Monday, October 22, 2007 5:36 PM
To: Maven Developers List
Subject: Maven release plugin question
Hi All,
Does anyone know why the release plugin
Hi Daniel,
I'm not overly familiar with that side of the release plugin, so if
someone else fancies reviewing the changes. Does this affect
MRELEASE-83 at all? Since that's the only unresolved issue scheduled
for 2.0-beta-7.
Cheers,
Mark
On 07/07/07, Daniel Kulp [EMAIL PROTECTED] wrote:
On Monday 09 July 2007 04:37, Mark Hobson wrote:
Hi Daniel,
I'm not overly familiar with that side of the release plugin, so if
someone else fancies reviewing the changes. Does this affect
MRELEASE-83 at all? Since that's the only unresolved issue scheduled
for 2.0-beta-7.
Nope. Doesn't
Mark,
I was looking into the problems with the GPG plugin when run from the
release plugin and the problems seem to entirely be problems of the
release plugin and Plexus utils. They are showing up in the gpg
plugin, but any plugin that tries to do anything interactively would
most likely
Mark,
I just committed a start of a fix for this problem.
To not require a new release of plexus-utils, I copied a little bit out
of CommandLineUtils and into ForkedMavenExecutor for now. Longer term,
that code should go back into plexus-utils (I'm not a committer there).
I've done some
Hi,
There's only one remaining issue, MRELEASE-83, scheduled for
2.0-beta-7 - is anyone likely to work on this soon, or shall we defer
it until beta-8? I would like to see beta-7 released for the release
POM fixes - they're rather unusable in beta-6.
Cheers,
Mark
Hi,
I'm trying to stage 2.0.7 and getting this error from the release
plugin:
[INFO] The artifact (org.apache.maven:maven-error-diagnostics)
requires a different version (2.0.7) than what is found (2.0.7) for
the expression (mavenVersion) in the project (org.apache.maven:maven).
Which
/plugins/maven-release-plugin/prepare-mojo.html)
This remains a workaround though.
Without this step, it is not possible to run release:prepare on an
aggregated project and expect it to always work.
'clean verify' works fine in the majority of case but can't work if a dependency (that is a module
preparationGoals parameter on the prepare mojo
(http://maven.apache.org/plugins/maven-release-plugin/prepare-mojo.html)
Emmanuel
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
On Fri, June 8, 2007 1:57 pm, Emmanuel Venisse wrote:
If you want to install artifacts in your local repo during the prepare
process and don't want to use 'clean verify' goals, you can configure
preparationGoals parameter on the prepare mojo
(http://maven.apache.org/plugins/maven-release
On 01/06/07, Brett Porter [EMAIL PROTECTED] wrote:
Hi Mark,
Sure, jump on in your morning (or grab me on google talk, yahoo,
skype :). I'll still be here. Emmanuel should be around then too, and
he's done the most work on the release plugin recently.
We can post back with what we figure out...
On Tue, June 5, 2007 9:06 pm, Brett Porter wrote:
Right. The reason for not choosing to install by default is that you
end up with a release in your local repository which is not the
final one.
We've run into this problem as well - the version being tested, as far as
I am aware, is the
Hi
On Jun 6, 2007, at 4:41 AM, Graham Leggett wrote:
On Tue, June 5, 2007 9:06 pm, Brett Porter wrote:
Right. The reason for not choosing to install by default is that you
end up with a release in your local repository which is not the
final one.
We've run into this problem as well - the
On Wed, June 6, 2007 4:50 pm, Mark Donszelmann wrote:
The workaround for us to release aggregated projects is like this:
mvn install release:prepare
but this would do the install w/o the poms being changed from 3.3-
SNAPSHOT to 3.3,
so this would not help.
And yet it does help.
I suspect
Hi
well, as far as I can conclude, an aggregated build will calculate
the order in which to generate (and install) the artifacts, so that
any module dependent on them is run later than the one generating
them.
I am still confused though about your command:
mvn install release:prepare
will
On Wed, June 6, 2007 5:25 pm, Mark Donszelmann wrote:
well, as far as I can conclude, an aggregated build will calculate
the order in which to generate (and install) the artifacts, so that
any module dependent on them is run later than the one generating
them.
That won't matter. If you don't
Jason van Zyl wrote:
On 4 Jun 07, at 6:26 PM 4 Jun 07, Dennis Lundberg wrote:
Hi
A user stumbled upon these files in the repo:
http://people.apache.org/repo/m2-ibiblio-rsync-repository/org/apache/maven/plugins/maven-release-plugin/2.0-beta-6/2.0-beta-6.rip/
After fiddling with the stage
. (resets the poms to 3.3-SNAPSHOT)
mvn release:prepare (now find 3.3 artifacts in local repository
mvn release:perform
--
But this cannot be the intended way of releasing.
Am I missing something or is there maybe a problem with the release
plugin.
mvn 2.0.5 and maven-release-plugin-2.0-beta-6
Mark Donszelmann wrote:
Hi
I am using an aggregate project such as:
T
-A
-B
-C
where C and B have a dependency on A
and A, B, C all use T as their parent pom.
When I run mvn install the projects are run in the correct order: T,
A, B, C
and all works fine for lets say
Right. The reason for not choosing to install by default is that you
end up with a release in your local repository which is not the
final one.
Perhaps the release plugin should install, but clean up the installed
artifacts afterwards. We seem to be seeing this problem a little more
Hi
A user stumbled upon these files in the repo:
http://people.apache.org/repo/m2-ibiblio-rsync-repository/org/apache/maven/plugins/maven-release-plugin/2.0-beta-6/2.0-beta-6.rip/
After fiddling with the stage-plugin I realized that these are leftovers
from a failed deployment. I assume
On 4 Jun 07, at 6:26 PM 4 Jun 07, Dennis Lundberg wrote:
Hi
A user stumbled upon these files in the repo:
http://people.apache.org/repo/m2-ibiblio-rsync-repository/org/
apache/maven/plugins/maven-release-plugin/2.0-beta-6/2.0-beta-6.rip/
After fiddling with the stage-plugin I realized
On 30/05/07, Mark Hobson [EMAIL PROTECTED] wrote:
On 29/05/07, Brett Porter [EMAIL PROTECTED] wrote:
So the sequence might need to be:
- resolve the project dependencies, filtering out the reactor projects
- add the reactor projects to the list of resolved artifacts
- iterate through the
Hi Mark,
Sure, jump on in your morning (or grab me on google talk, yahoo,
skype :). I'll still be here. Emmanuel should be around then too, and
he's done the most work on the release plugin recently.
We can post back with what we figure out...
- Brett
On 01/06/2007, at 1:36 AM, Mark
On 29/05/07, Brett Porter [EMAIL PROTECTED] wrote:
Heh. Nice catch! Can you get that into JIRA?
Done: http://jira.codehaus.org/browse/MNG-3015
Sure, I was envisaging that it could be fixed in 2.0.7 after which the
release plugin could have 2.0.7 as a prerequisite.
Still an unreleased
On 25/05/2007, at 6:55 PM, Mark Hobson wrote:
On 25/05/07, Brett Porter [EMAIL PROTECTED] wrote:
On 25/05/2007, at 12:57 AM, Mark Hobson wrote:
Looks like an infinite loop in the first DefaultDownloader.download
method.
Not sure what you're saying - you've tried it and it doesn't work, or
On 25/05/07, Brett Porter [EMAIL PROTECTED] wrote:
On 25/05/2007, at 12:57 AM, Mark Hobson wrote:
Looks like an infinite loop in the first DefaultDownloader.download
method.
Not sure what you're saying - you've tried it and it doesn't work, or
you just looked at the code and saw a problem?
Yes, this issue must be fixed but it isn't blocker for the release, the pb is
in your pom with the trunk/branch scm url that is a sub part of the tagbase.
Emmanuel
WilliamF a écrit :
Emmanuel,
2.0-beta-6 of the release-plugin seems to have the following problem while
rewriting the Poms
On 25/05/07, Mark Hobson [EMAIL PROTECTED] wrote:
Sure, I was envisaging that it could be fixed in 2.0.7 after which the
release plugin could have 2.0.7 as a prerequisite.
I've had a look at the code required to simulate
@requiresDependencyResolution, but it will require 2.0.6 due to the
5 +1 binding votes (Jason Van Zyl, Stephane Nicoll, John Casey, Maria Odea
Ching, Emmanuel Venisse)
2 +1 non-binding vote (Mark Hobson, Stefano Bagnara)
I'm releasing it now.
Emmanuel
Emmanuel Venisse a écrit :
Hi,
I'd like to release the release manager and the release plugin.
These
On 24/05/07, Brett Porter [EMAIL PROTECTED] wrote:
Yep, there's a few examples of plugins that re-use the resolution
mechanism and though I've never used it maven-downloader is meant to
encapsulate that in an easy to use API as well.
Looks like an infinite loop in the first
On 25/05/2007, at 12:57 AM, Mark Hobson wrote:
On 24/05/07, Brett Porter [EMAIL PROTECTED] wrote:
Yep, there's a few examples of plugins that re-use the resolution
mechanism and though I've never used it maven-downloader is meant to
encapsulate that in an easy to use API as well.
Looks like
-manager-1.0-alpha-3-and-maven-release-plugin-2.0-beta-6-tf3800523s177.html#a10796316
Sent from the Maven Developers mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL
+1
Stéphane
On 5/22/07, Emmanuel Venisse [EMAIL PROTECTED] wrote:
Hi,
I'd like to release the release manager and the release plugin.
These versions included some bug fixes, a new goal for the branch creation and
the latest Maven-SCM (1.0)
The Road Map:
On 22/05/07, Emmanuel Venisse [EMAIL PROTECTED] wrote:
Hi,
I'd like to release the release manager and the release plugin.
These versions included some bug fixes, a new goal for the branch creation and
the latest Maven-SCM (1.0)
The Road Map:
+1
-Deng
Emmanuel Venisse wrote:
Hi,
I'd like to release the release manager and the release plugin.
These versions included some bug fixes, a new goal for the branch
creation and the latest Maven-SCM (1.0)
The Road Map:
On 21/05/07, Brett Porter [EMAIL PROTECTED] wrote:
Using the manual resolution would only work if an earlier step in the
release:prepare process had definitely built all the dependencies.
However, there is an alternative: you can combine the reactor
projects (which you should have), with the
+1
On 5/23/07, Maria Odea Ching [EMAIL PROTECTED] wrote:
+1
-Deng
Emmanuel Venisse wrote:
Hi,
I'd like to release the release manager and the release plugin.
These versions included some bug fixes, a new goal for the branch
creation and the latest Maven-SCM (1.0)
The Road Map:
Hi,
I'd like to revert my vote to -1 (non veto) because of the following issue:
http://jira.codehaus.org/browse/MRELEASE-128
It has a high number of votes and does not work on CVS.
Thanks,
Stéphane
On 5/22/07, Emmanuel Venisse [EMAIL PROTECTED] wrote:
Hi,
I'd like to release the release
Team,
What do we do for this issue? Do we move it to the next version or do you want
to see it resolved in 2.0-beta-6?
Emmanuel
Stephane Nicoll a écrit :
Hi,
I'd like to revert my vote to -1 (non veto) because of the following issue:
http://jira.codehaus.org/browse/MRELEASE-128
It has a
Emmanuel Venisse ha scritto:
Team,
What do we do for this issue? Do we move it to the next version or do
you want to see it resolved in 2.0-beta-6?
My preference as *user* is to have 2.0-beta-6 out asap.
If I understood it correctly MRELEASE-128 is not a regression introduced
since
On 23/05/2007, at 8:27 PM, Mark Hobson wrote:
On 21/05/07, Brett Porter [EMAIL PROTECTED] wrote:
Using the manual resolution would only work if an earlier step in the
release:prepare process had definitely built all the dependencies.
However, there is an alternative: you can combine the
Hi,
I'd like to release the release manager and the release plugin.
These versions included some bug fixes, a new goal for the branch creation and
the latest Maven-SCM (1.0)
The Road Map:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11144styleName=Htmlversion=13452
Staging
+1
On 22 May 07, at 5:19 PM 22 May 07, Emmanuel Venisse wrote:
Hi,
I'd like to release the release manager and the release plugin.
These versions included some bug fixes, a new goal for the branch
creation and the latest Maven-SCM (1.0)
The Road Map:
On 01/02/07, Brett Porter [EMAIL PROTECTED] wrote:
Edwin - can we double check the requirement here. I recently removed
this to prevent the problem of it failing if you haven't installed
the project first.
I was planning to reintroduce @requiresDependencyResolution test on
release:prepare to
Using the manual resolution would only work if an earlier step in the
release:prepare process had definitely built all the dependencies.
However, there is an alternative: you can combine the reactor
projects (which you should have), with the artifacts returned from
manual resolution (and
Vote results:
+1 Binding: Emmanuel, Arnaud, Fabrizio, Vincent S., Stéphane
+1 non binding: Daniel Kulp
The release will be available on central at the next sync.
Thanks,
Stéphane
On 5/1/07, Stephane Nicoll [EMAIL PROTECTED] wrote:
Hi,
I'd like to release the maven release plugin which
The Maven team is pleased to announce the release of the Maven Release Plugin,
version 2.0-beta-5
http://maven.apache.org/plugins/maven-release-plugin/
Release Notes - Maven 2.x Release Plugin - Version 2.0-beta-5
** Bug
* [MRELEASE-3] - release:prepare should not require multimodule
+1
Vincent
2007/5/1, Stephane Nicoll [EMAIL PROTECTED]:
Hi,
I'd like to release the maven release plugin which includes the maven
release manager and the maven release parent pom.
The staging bits are available here:
http://people.apache.org/~snicoll/maven-staging/repo/
Release Notes
+1
Tested MRELEASE-209 on a multiproject build and now snapshots versions
are now restored correctly, no regressions found.
fabrizio
On 5/1/07, Stephane Nicoll [EMAIL PROTECTED] wrote:
Hi,
I'd like to release the maven release plugin which includes the maven
release manager and the maven
+1 - LOTS of great stuff here. Thanks for tackling it all.
Dan
On Tuesday 01 May 2007 05:07, Stephane Nicoll wrote:
Hi,
I'd like to release the maven release plugin which includes the maven
release manager and the maven release parent pom.
The staging bits are available here:
http
Nicoll wrote:
Hi,
I'd like to release the maven release plugin which includes the maven
release manager and the maven release parent pom.
The staging bits are available here:
http://people.apache.org/~snicoll/maven-staging/repo/
Release Notes - Maven 2.x Release Plugin - Version 2.0-beta-5
PROTECTED] wrote:
+1 - LOTS of great stuff here. Thanks for tackling it all.
Dan
On Tuesday 01 May 2007 05:07, Stephane Nicoll wrote:
Hi,
I'd like to release the maven release plugin which includes the maven
release manager and the maven release parent pom.
The staging bits
,
I'd like to release the maven release plugin which includes the
maven
release manager and the maven release parent pom.
The staging bits are available here:
http://people.apache.org/~snicoll/maven-staging/repo/
Release Notes - Maven 2.x Release Plugin - Version 2.0-beta-5
not release beta-5 now and then 6 when your
changes are
ready?
-Original Message-
From: Stephane Nicoll [mailto:[EMAIL PROTECTED]
Sent: Thursday, April 19, 2007 10:14 AM
To: Maven Developers List
Subject: Re: Release the maven-release-plugin
Subject: Re: Release the maven-release-plugin?
I think it makes sense to release a beta-5 if the changes are
major
enough. There's nothing that prevents you from releasing
beta-6 or
-rc1 afterwards.
Robert, I'll have a look to the issues now
Hi,
I'd like to release the maven release plugin which includes the maven
release manager and the maven release parent pom.
The staging bits are available here:
http://people.apache.org/~snicoll/maven-staging/repo/
Release Notes - Maven 2.x Release Plugin - Version 2.0-beta-5
** Bug
+1
Emmanuel
Stephane Nicoll a écrit :
Hi,
I'd like to release the maven release plugin which includes the maven
release manager and the maven release parent pom.
The staging bits are available here:
http://people.apache.org/~snicoll/maven-staging/repo/
Release Notes - Maven 2.x Release
+1
Arnaud
On 01/05/07, Emmanuel Venisse [EMAIL PROTECTED] wrote:
+1
Emmanuel
Stephane Nicoll a écrit :
Hi,
I'd like to release the maven release plugin which includes the maven
release manager and the maven release parent pom.
The staging bits are available here:
http
Have you tried releasing many things with it?
Jason.
On 1 May 07, at 5:07 AM 1 May 07, Stephane Nicoll wrote:
Hi,
I'd like to release the maven release plugin which includes the maven
release manager and the maven release parent pom.
The staging bits are available here:
http
Yes, I tried it on few projects (ASF and others) in my svn server.
Emmanuel
Jason van Zyl a écrit :
Have you tried releasing many things with it?
Jason.
On 1 May 07, at 5:07 AM 1 May 07, Stephane Nicoll wrote:
Hi,
I'd like to release the maven release plugin which includes the maven
I tried with success at work (with a snaphot built some days ago)
Arnaud
On 01/05/07, Jason van Zyl [EMAIL PROTECTED] wrote:
Have you tried releasing many things with it?
Jason.
On 1 May 07, at 5:07 AM 1 May 07, Stephane Nicoll wrote:
Hi,
I'd like to release the maven release plugin
On 5/1/07, Jason van Zyl [EMAIL PROTECTED] wrote:
Have you tried releasing many things with it?
I'm using the snapshot for a few weeks. I released 30+ projects.
Stéphane
Jason.
On 1 May 07, at 5:07 AM 1 May 07, Stephane Nicoll wrote:
Hi,
I'd like to release the maven release plugin
, April 19, 2007 10:14 AM
To: Maven Developers List
Subject: Re: Release the maven-release-plugin?
I think it makes sense to release a beta-5 if the changes are
major
enough. There's nothing that prevents you from releasing
beta-6 or
-rc1 afterwards
Developers List
Subject: Re: Release the maven-release-plugin?
I think it makes sense to release a beta-5 if the changes are major
enough. There's nothing that prevents you from releasing beta-6 or
-rc1 afterwards.
Robert, I'll have a look to the issues now
not release beta-5 now and then 6 when your changes are
ready?
-Original Message-
From: Stephane Nicoll [mailto:[EMAIL PROTECTED]
Sent: Thursday, April 19, 2007 10:14 AM
To: Maven Developers List
Subject: Re: Release the maven-release-plugin?
I
Subject: Re: Release the maven-release-plugin?
I think it makes sense to release a beta-5 if the changes are major
enough. There's nothing that prevents you from releasing beta-6 or
-rc1 afterwards.
Robert, I'll have a look to the issues now.
Thanks,
Stéphane
On 4/19/07, Emmanuel Venisse [EMAIL
when your changes are
ready?
-Original Message-
From: Stephane Nicoll [mailto:[EMAIL PROTECTED]
Sent: Thursday, April 19, 2007 10:14 AM
To: Maven Developers List
Subject: Re: Release the maven-release-plugin?
I think it makes sense to release a beta-5 if the changes are major
enough
think?
Best regards,
Robert
2007/4/15, Stephane Nicoll [EMAIL PROTECTED]:
On 4/15/07, Robert Kopco [EMAIL PROTECTED] wrote:
It has been 11 month since the last release of the
maven-release-plugin.
When will the next release of the plugin approximately be?
There are 10 open
think?
Best regards,
Robert
2007/4/15, Stephane Nicoll [EMAIL PROTECTED]:
On 4/15/07, Robert Kopco [EMAIL PROTECTED] wrote:
It has been 11 month since the last release of the
maven-release-plugin.
When will the next release of the plugin approximately be?
There are 10 open
,
Robert
2007/4/15, Stephane Nicoll [EMAIL PROTECTED]:
On 4/15/07, Robert Kopco [EMAIL PROTECTED] wrote:
It has been 11 month since the last release of the
maven-release-plugin.
When will the next release of the plugin approximately be?
There are 10 open issues. For a lot
I agree. Why not release beta-5 now and then 6 when your changes are ready?
-Original Message-
From: Stephane Nicoll [mailto:[EMAIL PROTECTED]
Sent: Thursday, April 19, 2007 10:14 AM
To: Maven Developers List
Subject: Re: Release the maven-release-plugin?
I think it makes sense
It has been 11 month since the last release of the maven-release-plugin.
When will the next release of the plugin approximately be?
There are 10 open issues. For a lot of issues patches have been provided:
MRELEASE-128
MRELEASE-122
MRELEASE-116
MRELEASE-90
MRELEASE-91
MRELEASE-137
Maybe
On 4/15/07, Robert Kopco [EMAIL PROTECTED] wrote:
It has been 11 month since the last release of the maven-release-plugin.
When will the next release of the plugin approximately be?
There are 10 open issues. For a lot of issues patches have been provided:
MRELEASE-128
MRELEASE-122
MRELEASE-116
What is it that you want the release-plugin to do? If you just want to
specify a different version than what is recommended by the plugin when
it prompts them, then it should be safe to do without any problems.
^_^
Guijie (Maggie) Ma wrote:
Hi,
I'm a user of Maven and Maven is very
Hello Edwin,
Thank you for your reply. In the project release for creating the Dev tag,the
release prepare process will prompt you for the revision to be used for the new
Dev tag, and for Trunk. You know the release-plugin can't define the correct
version number, so we must have the correct
I don't think there will be any problems if you put in the configuration
all the versions you will want to use. Continuum have a similar process
too, it prompts the user for all the required information before the
actual release begins. And then sends the release and development
versions
Do you think it is more convenient if the release plugin can deal with the
revision number automatically?
I have attached the snapshot of the release-prepare.
Thanks!
Maggie
Edwin Punzalan [EMAIL PROTECTED] 2/11/2007 8:05 PM
I don't think there will be any problems if you put in the
What do you mean?
Currently, it removes the SNAPSHOT for released versions and increments
with a SNAPSHOT version for development versions.
That's not enough?
Guijie (Maggie) Ma wrote:
Do you think it is more convenient if the release plugin can deal with the
revision number
I mean the release versions and development versions should be input manually
now. I want to know if I want the release-plugin to create the version number
automatically, what could we do?
Thank you!
Maggie
Edwin Punzalan [EMAIL PROTECTED] 2/11/2007 10:03 PM
What do you mean?
Currently,
On 2/12/07, Guijie (Maggie) Ma [EMAIL PROTECTED] wrote:
Do you think it is more convenient if the release plugin can deal with the
revision number automatically?
I have attached the snapshot of the release-prepare.
The attached snapshot was cut by the list.
I am successfully using the
But if there are more than one module and there are dependency between, the
change of one module can lead the version changes of other modules. The change
rule of version number should be different, not all be updated from
0.5.0-SNAPSHOT to 0.5.1-SNAPSHOT, maybe from 0.5.0-SNAPSHOT to
unfortunately, you can't. If in continuum, the user is prompted for all
the versions.
What the plugin does however is suggest a default, which is what it
currently does. Of course, the default isn't always appropriate for all
cases, but generally it should suffice.
If you want a new
On 2/12/07, Guijie (Maggie) Ma [EMAIL PROTECTED] wrote:
But if there are more than one module and there are dependency between, the
change of one module can lead the version changes of other modules. The change
rule of version number should be different, not all be updated from
well although this about Maven and modules *may* be true, the release
plugin can release the modules with a different versions than what is
declared in the parent. That's why the release plugin prompts for the
release/dev versions even though the project will inherit them. If you
specified
Thank you for your reply. I see.
Maggie
Edwin Punzalan [EMAIL PROTECTED] 2/11/2007 11:53 PM
unfortunately, you can't. If in continuum, the user is prompted for all
the versions.
What the plugin does however is suggest a default, which is what it
currently does. Of course, the default
On 12 Feb 07, at 1:04 AM 12 Feb 07, Barrie Treloar wrote:
On 2/12/07, Guijie (Maggie) Ma [EMAIL PROTECTED] wrote:
But if there are more than one module and there are dependency
between, the change of one module can lead the version changes of
other modules. The change rule of version
Yes, for the application of our company, we hope to release different modules
with different version. Could we do any modification to the source code of
Maven release-plugin? What suggestion about that?
Maggie
Jason van Zyl [EMAIL PROTECTED] 2/12/2007 12:52 AM
On 12 Feb 07, at 1:04 AM 12
Hi,
I'm a user of Maven and Maven is very good for my work. But in the use, we have
found a problem: when we do the project release, e.g. mvn release:prepare, we
need input the release version and the new development version manually for
each modules.
I want to know whether release-plugin can
2007
New Revision: 502089
URL: http://svn.apache.org/viewvc?view=revrev=502089
Log:
require dependency resolution so snapshot dependency artifacts
checking will work
Modified:
maven/release/trunk/maven-release-plugin/src/main/java/org/
apache/maven/plugins/release/PrepareReleaseMojo.java
dependency artifacts
checking will work
Modified:
maven/release/trunk/maven-release-plugin/src/main/java/org/apache/maven/plugins/release/PrepareReleaseMojo.java
Modified:
maven/release/trunk/maven-release-plugin/src/main/java/org/apache/maven/plugins/release/PrepareReleaseMojo.java
URL:
http
=revrev=502089
Log:
require dependency resolution so snapshot dependency artifacts
checking will work
Modified:
maven/release/trunk/maven-release-plugin/src/main/java/org/
apache/maven/plugins/release/PrepareReleaseMojo.java
Modified: maven/release/trunk/maven-release-plugin/src/main/java
501 - 600 of 743 matches
Mail list logo
