gt;
> One thing I would like to have is that while doing the `mvn
> release:prepare` have a check that verifies that I have not broken my build
> reproducibility.
> I think this would be the appropriate place to avoid releasing a bad build.
>
> How do I do something like th
Hi,
I'm trying to make my first project conform to the reproducible builds.
One thing I would like to have is that while doing the `mvn
release:prepare` have a check that verifies that I have not broken my build
reproducibility.
I think this would be the appropriate place to avoid releas
scritto:
> >
> > > On Thu 3 Oct 2019 at 16:13, Enrico Olivelli
> wrote:
> > >
> > > > Hello,
> > > > I am going to propose a new release procedure in Apache ZooKeeper
> > project
> > > > in the direction of using the Maven Rele
edure in Apache ZooKeeper
> project
> > > in the direction of using the Maven Release Plugin.
> > > Usually with the Maven Release Plugin you are performing to tasks:
> > >
> > > mvn release:prepare -> change version + create tag
> > > mvn release:pe
t; > Usually with the Maven Release Plugin you are performing to tasks:
> >
> > mvn release:prepare -> change version + create tag
> > mvn release:perform -> create final artifacts and deploy
> >
> > in the specific case of Apache ZooKeeper we have a C-client that
Apache ZooKeeper
> project
> >> in the direction of using the Maven Release Plugin.
> >> Usually with the Maven Release Plugin you are performing to tasks:
> >>
> >> mvn release:prepare -> change version + create tag
> >> mvn release:perform -> cr
procedure in Apache ZooKeeper project
>> in the direction of using the Maven Release Plugin.
>> Usually with the Maven Release Plugin you are performing to tasks:
>>
>> mvn release:prepare -> change version + create tag
>> mvn release:perform -> create final artifacts
On Thu 3 Oct 2019 at 16:13, Enrico Olivelli wrote:
> Hello,
> I am going to propose a new release procedure in Apache ZooKeeper project
> in the direction of using the Maven Release Plugin.
> Usually with the Maven Release Plugin you are performing to tasks:
>
> mvn release
9, at 8:13 AM, Enrico Olivelli
wrote:
>
> Hello,
> I am going to propose a new release procedure in Apache ZooKeeper
project
> in the direction of using the Maven Release Plugin.
> Usually with the Maven Release Plugin you are performing to tasks:
>
> mvn release:prepare -&
direction of using the Maven Release Plugin.
> > Usually with the Maven Release Plugin you are performing to tasks:
> >
> > mvn release:prepare -> change version + create tag
> > mvn release:perform -> create final artifacts and deploy
> >
> > in the sp
ello,
> I am going to propose a new release procedure in Apache ZooKeeper project
> in the direction of using the Maven Release Plugin.
> Usually with the Maven Release Plugin you are performing to tasks:
>
> mvn release:prepare -> change version + create tag
> mvn release:perf
Hello,
I am going to propose a new release procedure in Apache ZooKeeper project
in the direction of using the Maven Release Plugin.
Usually with the Maven Release Plugin you are performing to tasks:
mvn release:prepare -> change version + create tag
mvn release:perform -> create final art
> Date: Sat, 9 Nov 2013 08:31:21 -0500
> Subject: Re: AW: AW: AW: mvn release:prepare does not update parent version
> From: gordon.c...@zafin.com
> To: users@maven.apache.org
>
> You may want to upgrade maven itself once more. It is not just maven itself
> but the c
a
JIRA issue would help.
Robert
[1] https://jira.codehaus.org/browse/MRELEASE-511
Op Sat, 09 Nov 2013 14:17:57 +0100 schreef Martin Gainty
:
From: k...@quipsy.de
To: users@maven.apache.org
Date: Fri, 8 Nov 2013 16:30:30 +0100
Subject: AW: AW: AW: mvn release:prepare does not update par
Message-
> From: Robert Scholte [mailto:rfscho...@apache.org]
> Sent: Freitag, 8. November 2013 18:52
> To: Maven Users List
> Subject: Re: AW: AW: AW: mvn release:prepare does not update parent version
>
> Op Fri, 08 Nov 2013 16:30:30 +0100 schreef Markus Karg :
>
> &g
> From: k...@quipsy.de
> To: users@maven.apache.org
> Date: Fri, 8 Nov 2013 16:30:30 +0100
> Subject: AW: AW: AW: mvn release:prepare does not update parent version
>
> Martin,
>
> thank you for your explanations, but as it turned out the problem is fixed
> si
rt Scholte [mailto:rfscho...@apache.org]
Sent: Freitag, 8. November 2013 18:52
To: Maven Users List
Subject: Re: AW: AW: AW: mvn release:prepare does not update parent version
Op Fri, 08 Nov 2013 16:30:30 +0100 schreef Markus Karg :
> I wonder why someone fixed it but didn
Op Fri, 08 Nov 2013 16:30:30 +0100 schreef Markus Karg :
I wonder why someone fixed it but didn't close
https://jira.codehaus.org/browse/MRELEASE-837...!
Well, is was probably already fixed for a long time. Since you only had a
description it will take some time to fix it, since it must fir
Martin,
thank you for your explanations, but as it turned out the problem is fixed
simply by using version 2.4.2 of the release plugin. I wonder why someone fixed
it but didn't close https://jira.codehaus.org/browse/MRELEASE-837...!
Thanks for all
-Markus
> From: k...@quipsy.de
> To: users@maven.apache.org
> Date: Fri, 8 Nov 2013 08:40:56 +0100
> Subject: AW: AW: mvn release:prepare does not update parent version
>
> Martin,
>
> thanks for your ideas, but...
>
>
> I agree that the docs do not say anything
Martin,
thanks for your ideas, but...
>MG the previous email was an attempt to explain prepare-mojo will update
>current or children artifacts but not parent artifacts
I agree that the docs do not say anything about the parent, but my question is
not about the docs, it is about this question t
> From: k...@quipsy.de
> To: users@maven.apache.org
> Date: Thu, 7 Nov 2013 17:11:32 +0100
> Subject: AW: mvn release:prepare does not update parent version
>
> Sorry for the really long delay, but there had been several urgent projects
> meanwhile.
>
> I
es/releases
snapshots
http://nexus.quipsy.local/nexus/content/repositories/snapshots
Preparing and performing the release:
C:\Users\Markus Karg\workspace\artifact\my-artifact>mvn release:prepare
release:p
Gesendet: Dienstag, 23. Juli 2013 23:24
> An: users@maven.apache.org
> Betreff: RE: mvn release:prepare does not update parent version
>
> Markus
>
>
> Pa
Gesendet: Dienstag, 23. Juli 2013 23:24
An: users@maven.apache.org
Betreff: RE: mvn release:prepare does not update parent version
Markus
Parent.pom
|
ire. Étant donné que les email peuvent facilement
être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité
pour le contenu fourni.
> Subject: RE: mvn release:prepare does not update parent version
> Date: Mon, 22 Jul 2013 22:29:07 +0200
> From: k...@quipsy.de
>
Greetings,
On Tue, Jul 23, 2013 at 7:45 AM, Markus Karg wrote:
> But why is release:prepare explicitly asking me whether I want to update that
> number and what that number is, when it is intended behaviour that it does
> not actually set that number into the POM? I would understand all what yo
. But it
DOES ask.
-Ursprüngliche Nachricht-
Von: Russell Gold [mailto:r...@gold-family.us]
Gesendet: Dienstag, 23. Juli 2013 10:27
An: Maven Users List
Betreff: Re: mvn release:prepare does not update parent version
The example you mention updates the build artifacts only.
When you
@c-ware.de [mailto:christofer.d...@c-ware.de]
Gesendet: Dienstag, 23. Juli 2013 10:10
An: Maven Users List
Betreff: AW: mvn release:prepare does not update parent version
Hi,
is there actually a reason why only the artifacts in the build are updated?
I would agree that without providing versions for artifact
re.de]
Envoyé : mardi 23 juillet 2013 10:10
À : Maven Users List
Objet : AW: mvn release:prepare does not update parent version
Hi,
is there actually a reason why only the artifacts in the build are updated?
I would agree that without providing versions for artifacts manually, this
could cause pro
anually provided a version for, might solve Markus'
> problems.
>
> Chris
>
>
> -Ursprüngliche Nachricht-
> Von: jieryn [mailto:jie...@gmail.com]
> Gesendet: Montag, 22. Juli 2013 20:36
> An: Maven Users List
> Betreff: Re: mvn release:prepare does not update pa
ontag, 22. Juli 2013 20:36
An: Maven Users List
Betreff: Re: mvn release:prepare does not update parent version
Greetings,
On Mon, Jul 22, 2013 at 8:25 AM, Markus Karg wrote:
> When I do mvn release:prepare, Maven asks whether I want to update all
> SNAPSHOT version referenced in the PO
Thanks for picking this up. Please find answers inlined. :-)
> > When I do mvn release:prepare, Maven asks whether I want to update
> all
> > SNAPSHOT version referenced in the POM.
>
> I don't think the language says that at all. I ran a quick build and
> I'
Thanks for picking up this thread!
I am using: Maven 3.0.4 and maven-release-plugin 2.4.1
-Markus
> Hi, which version of Maven and Maven-Release-Plugin are you using?
>
> On Mon, Jul 22, 2013 at 9:25 AM, Markus Karg wrote:
>
> > I'm driving nuts with mvn release:prepar
Greetings,
On Mon, Jul 22, 2013 at 8:25 AM, Markus Karg wrote:
> When I do mvn release:prepare, Maven asks whether I want to update all
> SNAPSHOT version referenced in the POM.
I don't think the language says that at all. I ran a quick build and
I'm not seeing where it say
Hi, which version of Maven and Maven-Release-Plugin are you using?
On Mon, Jul 22, 2013 at 9:25 AM, Markus Karg wrote:
> I'm driving nuts with mvn release:prepare...:
>
> When I do mvn release:prepare, Maven asks whether I want to update all
> SNAPSHOT version referenced in
I'm driving nuts with mvn release:prepare...:
When I do mvn release:prepare, Maven asks whether I want to update all
SNAPSHOT version referenced in the POM.
I say "yes" and confirm all suggested replacement versions unchanged.
When Maven is done, I check the POM.xml.
It is correctl
Hi Markus
using "mvn release:prepare -DautoVersionSubmodules=true" should solve your
problem.
Greetz,
Sandra
Von:"Markus Karg"
An: ,
Datum: 22.07.2013 09:47
Betreff: mvn release:prepare does not update parent version
I'm driving nuts
I'm driving nuts with mvn release:prepare...:
When I do mvn release:prepare, Maven asks whether I want to update all
SNAPSHOT version referenced in the POM.
I say "yes" and confirm all suggested replacement versions unchanged.
When Maven is done, I check the POM.xml.
Don't get confused by the version numbers: plugins written for Maven2
should still work for Maven3. For does depending on deprecated Maven2
code, a new version is often available.
There a list[1] available which of plugin versions which are known to not
be compatible, including the fixed vers
Agreed - I saw that.
You'd have to look at the patch and see how (if) it could be fitted to
the latest release plugin.
It does appear that this is a cygwin git issue, in that some git
commands accept the backslash, while others do not.
I wonder what core.ignoreCygwinFSTricks might do (see
Jörg, I might, but I'd probably just try running the release from a linux
server first.
On Fri, Jun 28, 2013 at 4:21 PM, Jörg Schaible wrote:
> Hi Don,
>
> Don Branson wrote:
>
> > I'm trying to resolve an issue which I've posted at
> >
> http://stackoverflow.com/questions/17367079/with-mvn-rele
Mark, I did see that. It's for Maven 2.x, I'm running 3.0.5. The bug is
marked "Unresolved." Its presence in 3.0.5 seems to confirm that. I'd be
surprised if the patch is still applicable in maven 3.
On Fri, Jun 28, 2013 at 4:22 PM, Mark Eggers wrote:
> Top-posting, which seems to be the style
Top-posting, which seems to be the style for this thread:
Have you looked at:
http://jira.codehaus.org/browse/MRELEASE-581
to see if the proposed patch fixes things for you?
/mde/
On 6/28/2013 2:04 PM, Don Branson wrote:
I'm open to linux/mac, yes, but is my client? Not as much...
I've thou
Hi Don,
Don Branson wrote:
> I'm trying to resolve an issue which I've posted at
> http://stackoverflow.com/questions/17367079/with-mvn-releaseprepare-is-it-possible-to-instruct-maven-to-use-a-forward-slas.
> Is this a known issue with Maven+git+Cygwin? Is there a solution?
Years ago I was in th
I'm open to linux/mac, yes, but is my client? Not as much...
I've thought about using the windows environment for this. I'd have to use
a windows-based git instead of the cygwin one, and may or may not be able
to install that on our locked-down machines. I'll do it if I have to, but
I'm hoping to
I don't suppose you're open to the solution: "use linux or mac"?
I think what you're running into a general cygwin problem: other than those
built it, the tools are mostly windows tools and expect path names to refer to
the windows file system, but cygwin uses its own paths and they don't always
I'm trying to resolve an issue which I've posted at
http://stackoverflow.com/questions/17367079/with-mvn-releaseprepare-is-it-possible-to-instruct-maven-to-use-a-forward-slas.
Is this a known issue with Maven+git+Cygwin? Is there a solution?
--
Don Branson
mes"
> To: Maven Users List ; Martin Lichtin
>
> Cc:
> Sent: Tuesday, November 13, 2012 6:25 PM
> Subject: RE: mvn release:prepare cannot git-commit the pom.xml change
>
> Have you tried with the git windows port rather than Cygwin git.
> That works for me on windows w
November 2012 15:50
To: Maven Users List
Subject: Re: mvn release:prepare cannot git-commit the pom.xml change
Same with version 2.3.2 (many thanks of course for pointing out the old version
I was trying with).
[INFO] Checking in modified POMs...
[INFO] Executing: cmd.exe /X /C "gi
]
Sent: Tuesday, November 13, 2012 11:45 AM
To: Maven Users List; Ron Wheeler
Subject: Re: mvn release:prepare cannot git-commit the pom.xml change
No, pluginManagement. dependencyManagement does not effect plugins.
On Tue, Nov 13, 2012 at 11:06 AM, Ron Wheeler
wrote:
> On 13/11/2012 10:43
te [mailto:rfscho...@apache.org]
>> Sent: Tuesday, November 13, 2012 9:56 AM
>> To: Maven Users List
>> Subject: Re: mvn release:prepare cannot git-commit the pom.xml change
>>
>> The logging says:
>> "org.apache.maven.plugins:maven-release-plugin:2.0:prepare&q
As a dependency it would only apply to the parent.
-Original Message-
From: Robert Scholte [mailto:rfscho...@apache.org]
Sent: Tuesday, November 13, 2012 9:56 AM
To: Maven Users List
Subject: Re: mvn release:prepare cannot git-commit the pom.xml change
The logging
t pom.xml"
fatal: could not read log file 'inuc/C:\cygwin\tmp\commit': No such file or
directory
$ git --version
git version 1.7.9
>
> From: Robert Scholte
>To: Maven Users List
>Sent: Tuesday, November 13, 2012 3:55
I apologize, I replied to the wrong message. Pls disregard.
-Original Message-
From: Ken O'Connell [mailto:koconn...@casenetllc.com]
Sent: Tuesday, November 13, 2012 10:44 AM
To: Maven Users List
Subject: RE: mvn release:prepare cannot git-commit the pom.xml change
I put this versi
I put this version in my parent pom after you first suggested it, but it seems
like it not using that version, as you pointed out.
-Original Message-
From: Robert Scholte [mailto:rfscho...@apache.org]
Sent: Tuesday, November 13, 2012 9:56 AM
To: Maven Users List
Subject: Re: mvn
The logging says:
"org.apache.maven.plugins:maven-release-plugin:2.0:prepare"
This means you're using a pretty old version of the maven-release-plugin.
Try to lock the version on 2.3.2 first.
Robert
Op Tue, 13 Nov 2012 15:17:33 +0100 schreef Martin Lichtin
:
Hi
As a first-time user of th
Hi
As a first-time user of the "release" plugin, I'm running into the following
problem:
[INFO] Checking in modified POMs...
[INFO] Executing: cmd.exe /X /C "git add -- pom.xml"
[INFO] Working directory: C:\Users\mli\nuc\core\master\main\inuc
[INFO] Executing: cmd.exe /X /C "git status"
[INFO] Wo
rent
child relationships in a way that worked with the plugin.
Hope this helps,
Ed
On Tue, Nov 6, 2012 at 10:19 AM, purna chandrarao
wrote:
> Please let me know to which address i need to send the issue.
>
> I am having maven release plugin issue.
>
> mvn release:prepare
>
> t
On Tue, Nov 6, 2012 at 1:19 AM, purna chandrarao
wrote:
> Please let me know to which address i need to send the issue.
>
> I am having maven release plugin issue.
>
> mvn release:prepare
>
> this will create tag inside tags folder.
>
> while creating tag it is pu
http://maven.apache.org/plugins/maven-release-plugin/issue-tracking.html
/Anders
On Tue, Nov 6, 2012 at 1:19 AM, purna chandrarao
wrote:
> Please let me know to which address i need to send the issue.
>
> I am having maven release plugin issue.
>
> mvn release:prepare
>
&g
Hi,
2012/4/20 Karl Heinz Marbaise :
> Hi,
>>
>>
>> svnkit 1.7.4 is available here:
>> http://maven.tmatesoft.com/content/repositories/releases
>
> Yeah i know that svnkit is available from tmatesoft...
>
> But the problem is that only by an update of an SVN Server from 1.6.17 to
> 1.7.3 the taggi
Hi,
svnkit 1.7.4 is available here:
http://maven.tmatesoft.com/content/repositories/releases
Yeah i know that svnkit is available from tmatesoft...
But the problem is that only by an update of an SVN Server from 1.6.17
to 1.7.3 the tagging during the release does not work anymore which i
can
Hi,
svnkit 1.7.4 is available here:
http://maven.tmatesoft.com/content/repositories/releases
2012/4/19 Karl Heinz Marbaise :
> Hello to all,
>
> i have a question concerning creating releases via the
> maven-scm-provider-javasvn:
> I have the following configuration in a pom:
>
>
>
Hello to all,
i have a question concerning creating releases via the
maven-scm-provider-javasvn:
I have the following configuration in a pom:
org.apache.maven.plugins
maven-scm-plugin
1.6
javasvn
s
>
> 4) Added my private key to the putty pageant
>
> 5) Successfully checked out the project using tortuise svn and the
> above putty profile.
>
> 6) Tried to run 'mvn release:prepare' but get the error:
>
>
>
> [ERROR] Failed to execute goal
> or
ettings
4) Added my private key to the putty pageant
5) Successfully checked out the project using tortuise svn and the
above putty profile.
6) Tried to run 'mvn release:prepare' but get the error:
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-release-plugin:2.0:prep
my artifact. The currently released
> version is 2.5.1. The version number in the pom.xml is
> 2.5.1-1-SNAPSHOT. And the artifact is in a standard svn repository.
>
> I run mvn release:prepare and accept all the default options. Things
> seem to work as expected. And then I go
Hi all,
I am having some trouble with the release:prepare goal. I am trying to
release version 2.5.1-1 of my artifact. The currently released
version is 2.5.1. The version number in the pom.xml is
2.5.1-1-SNAPSHOT. And the artifact is in a standard svn repository.
I run mvn release:prepare
rivateDataInstance.java
> > ?
> target\test-classes\com\dp4j\samples\WithAccessibleVarArgsInstance.class
> > ? target\test-classes\com\dp4j\samples\WithAccessibleVarArgsInstance.java
> > ? target\test-classes\com\dp4j\samples\commons.jar
> > ? target\test-classes\com\dp4j\
at ?
> >
> > 2011/2/20 Gabriele Kahlout :
> > > yes, as far as i can tell.
> > >
> > > On Sun, Feb 20, 2011 at 2:59 PM, Olivier Lamy
> wrote:
> > >
> > >> Hello,
> > >> Maybe "stupid" question : have you committed an
e
> >> ?
> >>
> >>
> >> 2011/2/19 Gabriele Kahlout :
> >> > I'm trying:
> >> >
> >> > $ mvn release:prepare
> >> >
> >> > But then it prints a list of class files under my target directory
> which
>
t; ?
>>
>>
>> 2011/2/19 Gabriele Kahlout :
>> > I'm trying:
>> >
>> > $ mvn release:prepare
>> >
>> > But then it prints a list of class files under my target directory which
>> > I've set hg to ignore, and then fails:
&g
yes, as far as i can tell.
On Sun, Feb 20, 2011 at 2:59 PM, Olivier Lamy wrote:
> Hello,
> Maybe "stupid" question : have you committed and pushed your file .hgignore
> ?
>
>
> 2011/2/19 Gabriele Kahlout :
> > I'm trying:
> >
> > $ mvn release
Hello,
Maybe "stupid" question : have you committed and pushed your file .hgignore ?
2011/2/19 Gabriele Kahlout :
> I'm trying:
>
> $ mvn release:prepare
>
> But then it prints a list of class files under my target directory which
> I've set hg to ignore,
I'm trying:
$ mvn release:prepare
But then it prints a list of class files under my target directory which
I've set hg to ignore, and then fails:
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-release-plugin:2.1:prepare
> (default-cli) on project X: C
t; > À : users@maven.apache.org
> > Envoyé le : Lun 7 février 2011, 21h 39min 11s
> > Objet : Re: Unable to get the mvn release:prepare work
> >
> >
> > Hi Anders,
> >
> > I have locally modified files which I committed to my repository but
> s
Hi,
Can you run
> svn status
in your project folder (I asume you are using SVN).
Regards,
Julien
- Message d'origine
> De : ravi_atluri
> À : users@maven.apache.org
> Envoyé le : Lun 7 février 2011, 21h 39min 11s
> Objet : Re: Unable to get the mvn release:pre
ode=3374881&i=0>>
> wrote:
>
> >
> > Hi when I am trying to run the mvn release:prepare for my project it is
> > giving me this error:
> >
> > [INFO]
> >
> > [ERROR] BUIL
un the mvn release:prepare for my project it is
> giving me this error:
>
> [INFO]
>
> [ERROR] BUILD FAILURE
> [INFO]
>
> [IN
Hi when I am trying to run the mvn release:prepare for my project it is
giving me this error:
[INFO]
[ERROR] BUILD FAILURE
[INFO]
[INFO] Cannot
You don't need to specify the version element in the child. If not
specified, the specified parent.version will be used as version. And then
you will not have this issue.
/Anders
On Tue, Jan 4, 2011 at 19:15, Yaakov Chaikin wrote:
> Hi,
>
> Our project has a parent pom that's located as a sister
Hi,
Our project has a parent pom that's located as a sister module to all
the other modules and the root pom is the rector pom that defines
different profiles of different sets of modules to build.
So, here is roughly our structure:
pom.xml (rector pom.xml which references parent pom.xml for its
; >
> > > i configured an scm in my pom.xml file:
> > >
> > >
> > >scm:accurev:@ctcm
> > > :5050:CT_Dev_2.1.0:/Server/WebSec/ct-AutoFp
> > >
> > >scm:accurev:@ctcm
> > >
> :5050
ev:/CT_Dev_2.1.0/Server/WebSec/ct-AutoFp
> >
> >http://ctcm:5050
> >
> >
> > when i run mvn scm:list it works fine, but mvn release:prepare fails:
> >
> >
> > [ERROR] BUILD ERROR
> > [INFO]
> >
rver/WebSec/ct-AutoFp
>
>scm:accurev:@ctcm
> :5050:CT_Dev:/CT_Dev_2.1.0/Server/WebSec/ct-AutoFp
>
>http://ctcm:5050
>
>
> when i run mvn scm:list it works fine, but mvn release:prepare fails:
>
>
> [ERROR] BUILD ERROR
> [INFO]
> --
Hi,
i configured an scm in my pom.xml file:
scm:accurev:@ctcm:5050:CT_Dev_2.1.0:/Server/WebSec/ct-AutoFp
scm:accurev:@ctcm:5050:CT_Dev:/CT_Dev_2.1.0/Server/WebSec/ct-AutoFp
http://ctcm:5050
when i run mvn scm:list it works fine, but mvn release:prepare fails:
[ERROR] BUILD
OK, I've been able to recreate this using a dummy application. I do
think it's a bug, so I've raised an issue on it
http://jira.codehaus.org/browse/MRELEASE-576
It does actually end up building the release and deploying the correct
one. However, in the process, it's checking out the entire cont
More info... I am trying to reorganize my maven projects. Currently,
there is a single pom that declares modules and acts as a parent
project to those sub-modules. When I use this structure, the correct
source is used when creating the SVN tag.
I'm trying to move a bunch of the declarations into
Hi all. Some more info... when I change the developerConnection back
to the URL, it's even worse. The tag reflects the code in the trunk
instead of in the branch (I can tell because the POMs have different
version numbers... the tag has the version number of the trunk instead
of the branch... and
I've got my Maven project checked out from a branch using SVN. The
SVN repository structure is the "standard" one
trunk
tags
branches
I've checked out a working copy from a branch, and have run
release:prepare on it. It all works, but then the release:perform
fails. When I look at the tag in S
h/to/file -Durl=[url] -Dre
positoryId=[id]
[INFO]
[INFO] Path to dependency:
[INFO] 1) com.acme:commons.distribution:pom:0.0.6
[INFO] 2) com.acme:commons.util.test:jar:0.0.6
Note that building the assembly runs fine. Only when the
build is started in the context of mvn releas
-Original Message-
> From: Markus Muenkel [mailto:markus.muen...@fernuni-hagen.de]
> Sent: Tuesday, May 18, 2010 6:54 AM
> To: Maven Users List
> Subject: Re: mvn release:prepare fails with missing artifacts
> when project to be released runs an assembly
>
> Am T
mbly (zip archive). The artifacts to be assembled are
>>>>>>> specified
>>>>>>> via dependencies in the POM. They point to modules contained in the
>>>>>>> same
>>>>>>> multi-module project.
>>>>>>>
&g
ild an assembly (zip archive). The artifacts to be
assembled are
specified
via dependencies in the POM. They point to modules
contained in the
same
multi-module project.
When running mvn release:prepare on the multi-module
project, the build
of
the assembly project fails with the message that th
ild an assembly (zip archive). The artifacts to be
assembled are
specified
via dependencies in the POM. They point to modules
contained in the
same
multi-module project.
When running mvn release:prepare on the multi-module
project, the build
of
the assembly project fails with the message that th
t; to
>>>>> build an assembly (zip archive). The artifacts to be assembled are
>>>>> specified
>>>>> via dependencies in the POM. They point to modules contained in the
>>>>> same
>>>>> multi-module project.
>>>
ules
contained in the same
multi-module project.
When running mvn release:prepare on the multi-module
project, the build
of
the assembly project fails with the message that the
dependencies cannot
be
resolved. These dependencies are reported with the
version that should be
released, e.g
The artifacts to be assembled are
>>> specified
>>> via dependencies in the POM. They point to modules contained in the same
>>> multi-module project.
>>>
>>> When running mvn release:prepare on the multi-module project, the build
>>> of
&
s
contained in the same
multi-module project.
When running mvn release:prepare on the multi-module
project, the build of
the assembly project fails with the message that the
dependencies cannot be
resolved. These dependencies are reported with the
version that should be
released, e.g. 0.0.3. Bef
1 - 100 of 134 matches
Mail list logo
