Has anybody tried switching from neon to serf as the repository access
method???
I read on the svn list that 1.5.1+ WC-URL tagging for http/https
repositories works with serf but not neon
I have not been able to try this yet as it would mean recompiling my client.
This is a client only setting
To: Maven Users List
Subject: Re: [ANN] Maven Release Plugin 2.0-beta-9 Released
Has anybody tried switching from neon to serf as the
repository access method???
I read on the svn list that 1.5.1+ WC-URL tagging for
http/https repositories works with serf but not neon
I have not been able
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
Hello,
I am trying to automate the branching for a few hundred Maven
projects. The automation of creating a release works great using the
-DreleaseVersion and -DdevelopmentVersion properties using the prepare
goal. The documentation of the branch goals states this: The branch
goal can use the
Hi,
The vote (maven-scm and maven-release-plugin) has started 2 days ago.
(vote thread : [1])
I'm currently waiting the end of the release process to push artifacts
on the central repo (the end for me is today 11H55 PM Paris Time )
BTW you can try with the staged artifacts.
HTH,
--
Olivier
[1
Hello maven users,
In maven-release-plugin recently an important issue (
http://jira.codehaus.org/browse/MRELEASE-375 ) has been resolved. Without
this fix, release plug-in can not be used on a multi-module project (with
svn 1.5.0+ client) - dunno about others, but I rarely work on a single
Great! Thanks for quick reply!
2009/3/26 Olivier Lamy ol...@apache.org
Hi,
The vote (maven-scm and maven-release-plugin) has started 2 days ago.
(vote thread : [1])
I'm currently waiting the end of the release process to push artifacts
on the central repo (the end for me is today 11H55 PM
in context:
http://www.nabble.com/Maven-release-plugin-issue--Error-code-401-tp22729480p22729480.html
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
[INFO] Error deploying artifact: Failed to transfer file:
http://fpsvn00
1.na.coglobal.com:8081/nexus/content/repositories/releases/com/co/maven/co-m
aven/1.0/co-maven-1.0.pom. Return code is: 401
HTTP Error 401 is... Unauthorized, right? Solve that, and deploy will
proceed. Check
Eric,
2009/3/16 Eric B. ebe...@hotmail.com:
Hi,
How can I use the release:perform goal in the maven-release-plugin to build
my module located in a CVS branch?
I have tried mvn release:perform -DtagBase=B_2_0_0 hoping / expect that it
would pass the tagBase command along to CVS to checkout
Ringo De Smet ringo.des...@gmail.com wrote in message
news:e20d07ca0903170558v19147b9av5f1848e1af0f5...@mail.gmail.com...
Eric,
2009/3/16 Eric B. ebe...@hotmail.com:
Hi,
How can I use the release:perform goal in the maven-release-plugin to
build
my module located in a CVS branch
Hi,
How can I use the release:perform goal in the maven-release-plugin to build
my module located in a CVS branch?
I have tried mvn release:perform -DtagBase=B_2_0_0 hoping / expect that it
would pass the tagBase command along to CVS to checkout the sources from
that tag. Unfortunately
Hi there,
I'd like to see either an additional goal (e.g., release:deploy) added
to the release plugin or perhaps it can be achieved via properties.
Essentially, as far as I understand it, the release plugin requires
access to an scm repository to commit changes to in addition to
ehhh what's wrong with mvn deploy... that will deploy the current version
(which should be a -SNAPSHOT)... in all other cases you should be using a
qualifier that identifies you as the builder...
for example if I want to deploy my own version of something that is
currently 5.0.0-SNAPSHOT I would
On 10/03/2009, at 9:06 PM, Stephen Connolly wrote:
ehhh what's wrong with mvn deploy... that will deploy the current
version
(which should be a -SNAPSHOT)...
Because, quite simply, I don't want to link my projects against a
snapshot. The svn version is repeatable.
in all other cases
edit the version in thepom andjust run mvn deploy
On 10/03/2009, Lachlan Deck lachlan.d...@gmail.com wrote:
On 10/03/2009, at 9:06 PM, Stephen Connolly wrote:
ehhh what's wrong with mvn deploy... that will deploy the current
version
(which should be a -SNAPSHOT)...
Because, quite simply, I
On 11/03/2009, at 9:12 AM, Stephen Connolly wrote:
edit the version in thepom andjust run mvn deploy
More work? Sure I can create an ant-file that will recursively follow
the modules down editing all of them to do this - but that's what the
release plugin does already right? A bit of
99% of the code you need is in a shared component that you can reuse
write a maven plugin to do this for you if you really see a need.
IMHO there is no need as people should just release correctly or else
just deploy the ant built artifacts without maven
On 10/03/2009, Lachlan Deck
Message-
From: James Bowkett [mailto:jbowk...@cygnanegra.co.uk]
Sent: 25 February 2009 16:21
To: users@maven.apache.org
Subject: Re: missing dependency with aggregator and modular builds in
maven-release-plugin in maven 2
(I have updated my super pom accordingly, thanks, Ive not re-run the
release
Hi,
I have seen similar problems elsewhere on the web, but the solutions don't
seem to work for me. I have the following:
A super pom.xml project that specifies javac version etc
A number of modules that inherit from the super pom with interdependancies
between them
When I run mvn
On 26/02/2009, at 2:09 AM, James Bowkett wrote:
I have tried adding preparationGoalsclean install
deploy/preparationGoals
you should only need clean install here, firstly deploy runs install
as well so this doubles up, and secondly you don't want to deploy on
preparation, just on perform.
(I have updated my super pom accordingly, thanks, Ive not re-run the
release since, but I can do if you think this is the root cause of the
problem)
My reactor output is as follows:
[INFO] Reactor build order:
[INFO] Main ß Main super pom
[INFO] commons
[INFO]
Hi All
Is it possible to disable ceritificate verification for SCM server during
release?
Thanks
Erkin
://jira.codehaus.org/browse/SCM-428 .
HTH,
--
Olivier
[1] http://github.com/olamy/
2009/2/12 Mark Derricutt m...@talios.com:
Hi all,
Does anyone know if the maven release plugin will (or can be made to work
with) git-svn based checkouts when using subversion? I'm suspecting not.
Mark
.
HTH,
--
Olivier
[1] http://github.com/olamy/
2009/2/12 Mark Derricutt m...@talios.com:
Hi all,
Does anyone know if the maven release plugin will (or can be made to
work
with) git-svn based checkouts when using subversion? I'm suspecting
not.
Mark
...and then Buffy
[1] http://github.com/olamy/
2009/2/12 Mark Derricutt m...@talios.com:
Hi all,
Does anyone know if the maven release plugin will (or can be made to work
with) git-svn based checkouts when using subversion? I'm suspecting not.
Mark
...and then Buffy staked Edward. The End
Hi all,
Does anyone know if the maven release plugin will (or can be made to work
with) git-svn based checkouts when using subversion? I'm suspecting not.
Mark
...and then Buffy staked Edward. The End.
anyone know if the maven release plugin will (or can be made to work
with) git-svn based checkouts when using subversion? I'm suspecting not.
Mark
...and then Buffy staked Edward. The End.
-
To unsubscribe, e-mail: users
Is there any way to stop the release:perform from generating any
reports at all?
I would looking for an option that just does the subversion tagging
commits, and the artifactory uploads.
-tb
-
To unsubscribe, e-mail:
will do 'deploy site-deploy' if you have a
distributionManagement/site/url configured.
http://maven.apache.org/plugins/maven-release-plugin/perform-mojo.html
If you're trying to avoid the 'site-deploy', configure the plugin to
only run 'deploy'.
There's an example of changing the goals here:
http
Hi,
configure release plugin goals element as described in
http://maven.apache.org/plugins/maven-release-plugin/examples/perform-release.html
- markku
Terry Bell wrote:
Is there any way to stop the release:perform from generating any
reports at all?
I would looking for an option
-
De : Stephane Nicoll [mailto:stephane.nic...@gmail.com]
Envoyé : samedi 24 janvier 2009 10:50
À : Maven Users List
Objet : Re: [MAVEN RELEASE PLUGIN] NoSuchMethodError:
org.apache.maven.settings.Settings.getRuntimeInfo() for goal prepare
Well it looks like an embedder issue. Install maven
-parent-pom:1.0.1-SNAPSHOT @
F:\bar.boo\Eclipse\Java\bar-parent-pom\pom.xml]
[DEBUG] (f) resume = true
[DEBUG] (f) scmCommentPrefix = [maven-release-plugin]
[DEBUG] (f) settings = org.apache.maven.settings.setti...@e99ce5
[DEBUG] (f) updateDependencies = true
[DEBUG] (f) useEditMode
) scmCommentPrefix = [maven-release-plugin]
[DEBUG] (f) settings = org.apache.maven.settings.setti...@1cfb802
[DEBUG] (f) updateDependencies = true
[DEBUG] (f) useEditMode = false
[DEBUG] -- end configuration --
[INFO] [release:prepare]
[DEBUG] Setting context classloader for plugin
:1.0.1-SNAPSHOT @
F:\bar.boo\Eclipse\Java\bar-parent-pom\pom.xml]
[DEBUG] (f) resume = true
[DEBUG] (f) scmCommentPrefix = [maven-release-plugin]
[DEBUG] (f) settings = org.apache.maven.settings.setti...@e99ce5
[DEBUG] (f) updateDependencies = true
[DEBUG] (f) useEditMode = false
[DEBUG
Hi Release Plugin Gurus,
I want to specify a local maven repo.
Using maven release plugin 2.0-beta-8, I tried the combinations of
-Darguments=-Dmaven.repo.local=..., -Darguments=-Dmaven.home...,
-DlocalRepoDirectory=... and/or -DmavenHome=..., it always return
current-directory/.m2
.
Using maven release plugin 2.0-beta-8, I tried the combinations of
-Darguments=-Dmaven.repo.local=..., -Darguments=-Dmaven.home...,
-DlocalRepoDirectory=... and/or -DmavenHome=..., it always return
current-directory/.m2/repository not found.
Is this a known issue? Is there a workaround
What do you think of this bug I started?
http://jira.codehaus.org/browse/MRELEASE-399
There I propose to resolve the real versions of parent and dependencies
declared with the RELEASE keyword as version.
This is because if not, my releases are left with the RELEASE keyword on a
dependency
I'm afraid I don't have a test case in-hand at this time, but I wanted
to ask the community. Is there a known problem with
maven-release-plugin reporting a false successful build? I didn't see
anything that seemed to indicate that in JIRA. My team has noticed a
couple of events in which we
is coming back.
- Brett
On 23/12/2008, at 4:45 AM, David C. Hicks wrote:
I'm afraid I don't have a test case in-hand at this time, but I
wanted to ask the community. Is there a known problem with maven-
release-plugin reporting a false successful build? I didn't see
anything that seemed
afraid I don't have a test case in-hand at this time, but I
wanted to ask the community. Is there a known problem with
maven-release-plugin reporting a false successful build? I didn't see
anything that seemed to indicate that in JIRA. My team has noticed a
couple of events in which we had
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
svn --non-interactive copy --file D:\Tmp\maven-scm-1276451448.commit .
http
I
have for now is to downgrade to SVN 1.5.0; last I heard this is still an
issue with maven-release-plugin 2.0-beta-8 and SVN 1.5.4.
- John
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL
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
You have to use svn 1.5.0
2008/11/4 Peter Nedonosko [EMAIL PROTECTED]
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.
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
://n2.nabble.com/Best-Practices-Maven-release-plugin-multimodule-with-module-dependencies---tp1397646p1402207.html
Sent from the maven users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED
Issue #255 has been fixed in maven-release-plugin version 2.0-beta-8 and
that indeed fixed my issue.
Thanks,
Sahoo
Wim Deblauwe wrote:
A quick search in jira makes you think it should have been fixed:
http://jira.codehaus.org/browse/MRELEASE-255, although this related bug (
http
what I want.
I'm pretty sure it's not the best practices but I didn't find a solution to
solve the version increment dependence.
Thanks in advance for your answer
Lionel
--
View this message in context:
http://n2.nabble.com/Best-Practices-Maven-release-plugin-multimodule-with-module-dependencies
My pom.xml looks like this:
?xml version=1.0 encoding=UTF-8?
!--
/*
* DO NOT ALTER OR REMOVE COPYRIGHT NOTICES OR THIS HEADER.
*
...
--
project xmlns=http://maven.apache.org/POM/4.0.0;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
-release-plugin-multimodule-with-module-dependencies---tp1397646p1397646.html
Sent from the maven users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL
A quick search in jira makes you think it should have been fixed:
http://jira.codehaus.org/browse/MRELEASE-255, although this related bug (
http://jira.codehaus.org/browse/MRELEASE-266) is still open.
Not sure if all comments are left alone or just specific things?
regards,
Wim
2008/10/30
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
Hi all,
another relase plugin question,
before calling the release:perform goal i have to add a scm element to the
POM
and commit the POM.
scm
connectionscm:svn:svn://subversionserver/repo/project/tags/builds/1.0.0-SN
APSHOT/BUILD-2/connection
/scm
Is there a way to add the scm from
On Wed, Oct 29, 2008 at 9:19 AM, von Janowsky, Simon
[EMAIL PROTECTED] wrote:
another relase plugin question,
before calling the release:perform goal i have to add a scm element to the
POM
and commit the POM.
scm
connectionscm:svn:svn://subversionserver/repo/project/tags/builds/1.0.0-SN
that.
Thanks a lot for your help,
Simon.
-Ursprüngliche Nachricht-
Von: Wendy Smoak [mailto:[EMAIL PROTECTED]
Gesendet: Mittwoch, 29. Oktober 2008 17:34
An: Maven Users List
Betreff: Re: maven release plugin, set scm from commandline
On Wed, Oct 29, 2008 at 9:19 AM, von Janowsky, Simon
[EMAIL
:
I use the maven-release-plugin, the two goals prepare and perform. But I
don't want Maven generate the pom for the next iteration how can I do
that ?
I want simply to pass from the snapshots to the releases.
Thanks.
Rémy.
--
View this message in context:
http://www.nabble.com/maven-release
can be of more help.
cheers,
Craig
On Tue, Oct 28, 2008 at 10:25 AM, Rémy [EMAIL PROTECTED]
wrote:
I use the maven-release-plugin, the two goals prepare and perform. But I
don't want Maven generate the pom for the next iteration how can I do
that ?
I want simply to pass from
I noticed some talk in Sept that the next version of the maven release plugin
should be released at the end of Sept. But I don't see that is has.
When will it be released? I am needing the improvement
http://jira.codehaus.org/browse/MRELEASE-173
--
View this message in context:
http://n2
Hi,
Have a look to this thread
http://www.nabble.com/Re%3A-Maven-release-plugin-td19653492.html
Rémy
I use the maven-release-plugin, the two goals prepare and perform. But I
don't want Maven generate the pom for the next iteration how can I do that ?
I want simply to pass from the snapshots to the releases.
Thanks.
Rémy.
--
View this message in context:
http://www.nabble.com/maven-release
PROTECTED] wrote:
I use the maven-release-plugin, the two goals prepare and perform. But I
don't want Maven generate the pom for the next iteration how can I do that ?
I want simply to pass from the snapshots to the releases.
Thanks.
Rémy.
--
View this message in context:
http://www.nabble.com
I use the maven-release-plugin, the two goals prepare and perform.
But I don't want Maven generate the pom for the next iteration how
can I do that ? I want simply to pass from the snapshots to the
releases.
Take note of Craig's excellent points. The idea is for the release
plugin to do
with the maven-release-plugin and
ClearCase (using Snapshot views)
I´m using maven-release-plugin:2.0-beta-7
The first Snapshotview (Developer SnapshotView) actually resides at
C:\LocalViews\username_pcname_viewname\VOB_name\projectname
In the pom.xml I have:
...
scm
Hi,
I am having problems using maven-release-plugin and I need some help
urgently. While doing a release:prepare, maven is not able to locate an
extension. I am using maven 2.0.7 on JDK 1.5. Given below are the
essential details of the pom.xml that's facing the issue:
parent
Hi,
Appreciate any suggestion to solve this problem. I am stuck because of
this issue.
Thanks,
Sahoo
---BeginMessage---
Hi,
I am having problems using maven-release-plugin and I need some help
urgently. While doing a release:prepare, maven is not able to locate an
extension. I am using
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 own extension called
org.glassfish.build:maven-glassfish-extension. We build the extension as
part of the same reactor.
Try
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 own extension called
org.glassfish.build:maven-glassfish-extension. We build the extension as
part of the same
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
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 waiting for it.
Thanks,
Rémy
--
View
Someone know when the 2.0-beta-8 of maven release plugin will be released ?
Regards
Alex.
--
View this message in context:
http://www.nabble.com/Maven-release-plugin-tp19269992p19269992.html
Sent from the Maven - Users mailing list archive at Nabble.com
Hi,
Personnaly, I have planned to do it near end of September.
--
Olivier
2008/9/2 Zucchi Alessandro [EMAIL PROTECTED]:
Someone know when the 2.0-beta-8 of maven release plugin will be released ?
Regards
Alex.
--
View this message in context:
http://www.nabble.com/Maven-release-plugin
+1
The list of open Jiras is long, so we should start working on this asap.
LieGrü,
strub
--- Olivier Lamy [EMAIL PROTECTED] schrieb am Di, 2.9.2008:
Von: Olivier Lamy [EMAIL PROTECTED]
Betreff: Re: Maven release plugin
An: Maven Users List users@maven.apache.org
Datum: Dienstag, 2
Not possbile at the begin of September?
Bye
Olivier Lamy wrote:
Hi,
Personnaly, I have planned to do it near end of September.
--
Olivier
2008/9/2 Zucchi Alessandro [EMAIL PROTECTED]:
Someone know when the 2.0-beta-8 of maven release plugin will be
released ?
Regards
Alex
]:
Someone know when the 2.0-beta-8 of maven release plugin will be
released ?
Regards
Alex.
--
View this message in context:
http://www.nabble.com/Maven-release-plugin-tp19269992p19269992.html
Sent from the Maven - Users mailing list archive at Nabble.com
On Tue, Sep 2, 2008 at 6:12 AM, Zucchi Alessandro
[EMAIL PROTECTED] wrote:
Someone know when the 2.0-beta-8 of maven release plugin will be released ?
Regards
Is there a particular issue you're interested in?
Release is on the top of the list of plugins with bugs that are
already fixed, have
I'm interested in particulary to new future MRELEASE-321,
but the real problem (for me) is that I must apply my patch (MRELEASE-323
not and I think will never be fixed) to a stable version and not to a
snapshot version to use maven-release-plugin in my factory.
Bye
Wendy Smoak-3 wrote
I think I found a solution:
Before issuing the 'mvn release:prepare' command, an 'svn update' on
the parent directory of the directory renamed (or at the top level) will
update the SubVersion metadata. The update command doesn't print
anything so it appears like it doesn't do anything, but
Ken Tanaka wrote:
Before issuing the 'mvn release:prepare' command, an 'svn update' on
the parent directory of the directory renamed (or at the top level) will
update the SubVersion metadata. The update command doesn't print
anything so it appears like it doesn't do anything, but it's
BE SURE that it really has the contentyou thought of.
LieGrue,
strub
--- Ken Tanaka [EMAIL PROTECTED] schrieb am Mo, 25.8.2008:
Von: Ken Tanaka [EMAIL PROTECTED]
Betreff: Re: Having trouble with Maven release plugin using SubVersion
An: Maven Users List users@maven.apache.org
CC: [EMAIL
BE SURE that it really has the contentyou thought of.
LieGrue,
strub
--- Ken Tanaka [EMAIL PROTECTED] schrieb am Mo, 25.8.2008:
Von: Ken Tanaka [EMAIL PROTECTED]
Betreff: Re: Having trouble with Maven release plugin using SubVersion
An: Maven Users List users@maven.apache.org
CC: [EMAIL
version: 2.0.9
##Java version: 1.6.0_03
##OS name: linux version: 2.6.18-92.1.10.el5 arch: amd64
Family: unix
##svn, version 1.4.2 (r22196)
##
## For reference I'm going by:
## http://maven.apache.org/plugins/maven-release-plugin/
##
## Summary of the standard Maven directory layout
version: 1.6.0_03
##OS name: linux version: 2.6.18-92.1.10.el5 arch: amd64
Family: unix
##svn, version 1.4.2 (r22196)
##
## For reference I'm going by:
## http://maven.apache.org/plugins/maven-release-plugin/
##
## Summary of the standard Maven directory layout:
## myProject
I did use 'svn move src/main/conf src/main/config' for the rename.
(Although I have been caught by using the regular mv before.)
-Ken
Dennis Lundberg wrote:
Did you use the 'svn move ...' command to rename the directory or did
you do it directly on the file system for your working copy?
If
Hello,
Is there a way to use the release plugin in batch mode, when using a
snapshot version of this plugin ?
In interactive mode, the plugin asks for a confirmation when it detects
that a snapshot version is being used :
This project relies on a SNAPSHOT of the release plugin. This may be
I don't believe so - for this purpose it's probably best to host your
own release of the release plugin.
2008/8/20 HUE Edouard IT[EMAIL PROTECTED] [EMAIL PROTECTED]:
Hello,
Is there a way to use the release plugin in batch mode, when using a
snapshot version of this plugin ?
In interactive
I thought about it, but it remains a short term fix. Same problem will
occure each time one will want to use a snapshot version of the plugin.
I hoped there would be a switch to skip this check...
Brett Porter a écrit :
I don't believe so - for this purpose it's probably best to host your
own
Since you are using a snapshot version of the plugin that you've
built, could you change the source to change the default also?
- Brett
2008/8/21 HUE Edouard IT[EMAIL PROTECTED] [EMAIL PROTECTED]:
I thought about it, but it remains a short term fix. Same problem will
occure each time one will
I didn't build it myself, I got it from Apache's snapshot repository at
http://people.apache.org/repo/m2-snapshot-repository/ :) I think I will
submit a feature request.
Edouard
Brett Porter a écrit :
Since you are using a snapshot version of the plugin that you've
built, could you change
Hi Todd,
I´m actually using the maven-release-plugin with Base ClearCase, but with
some (known) limitations:
- i could only release modules within a tree, not a flat directory
hierarchy
- i could only release modules at the main branch; releasing at a branch
is not possible due
Hi,
I´m actually using the maven-release-plugin with Base ClearCase, but with
some (known) limitations:
- i could only release modules within a tree, not a flat directory
hierarchy
- i could only release modules at the main branch; releasing at a branch
is not possible due to the configspec
I would be nice to cut a new release. beta-7 was out since May 2007
Thanks
-Dan
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Hello List!
This is my first post to this list so bare with me if I'm viloating
any rules. I have trouble with the maven release plugin and I hope to
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail
hi,
i am using maven-release plugin to create branches. updating its own version
and creating project in scm works fine.
what i do miss is that the update of snapshot versions of dependencies is
not asked for.
but when branching sometimes the actual branch should update snapshot
dependencies
Hello Manuel,
I'm not surprised that the maven-release-plugin doesn't interfere with
the versions of dependencies in a project.
IMHO you should change your expectations of the release:branche. The
maven-release-plugin works on the current artifact. Whether or not other
artifacts have been
-packages by maven multimodule
concept. so far we didn't go for it for historic and IDE plugin reasons, but
we are thinking to migrate soon.
Beelen, M. - SPLXL wrote:
Hello Manuel,
I'm not surprised that the maven-release-plugin doesn't interfere with
the versions of dependencies in a project
Greetings Alex,
I met the same problem and so I googled Your question (m2, svn) yesterday.
Hi all,
I have a multi-module project that I'm trying to run the release
plugin against.
scm connections are configured in the POMs and so is the tagBase.
Checkin of POMs with updated release numbers
Hi all,
Spent an hour or so to discover why subversion fails to commit the
pom.xml during a release:prepare...
If the pom.xml file contains CDATA sections (as required by few plugins,
such as the maven-eclipse-plugin), then the end of line sequence of
these lines is changed to LF.
The only
501 - 600 of 799 matches
Mail list logo
