Hi,
I'm using Maven 3.0.3 with a Sonatype repository. I'm able to deploy my
artifact to the remote repository the first time, but when i try and deploy
again, using
mvn -e -X clean deploy -s sonatype.xml
It fails with the below error …
Caused by:
2011/7/29 Mark Derricutt m...@talios.com:
Hrm - I still believe that master would be production-ready-state even with
the -SNAPSHOT version,
the code is in a state that ready for production release. If I did a maven
release from there I'd get
the same code built, with the only difference
Could this be a Windows problem?
I tried to perfom a second clone from the local file path with the
generated maven path:
git clone file://D:\dev\projects\maven.master\source\maven.master
This results in:
Cloning into devprojectsmaven.mastersourcemaven.master...
fatal:
hi!
Do you have localCheckout activated?
You might try disabling it, maybe there is a bug with that on windows.
localCheckout is meant to spare bandwith in huge projects by doing a
git-clone file:// from the local git repo instead of cloning the upstream repo
in release:perform.
LieGrue,
strub
Hello Mark,
I see, that you assigned MRELEASE-624. Thank you for the quick reaction!
2011/7/29 Mark Struberg strub...@yahoo.de:
Do you have localCheckout activated?
You might try disabling it, maybe there is a bug with that on windows.
localCheckout is meant to spare bandwith in huge
Hi Lars!
Oki, I understand. Will try to look at it the next week.
LieGrue,
strub
--- On Fri, 7/29/11, Lars Fischer resch...@googlemail.com wrote:
From: Lars Fischer resch...@googlemail.com
Subject: Re: gitflow releases with maven?
To: Maven Users List users@maven.apache.org
Date: Friday,
2011/7/29 Mark Struberg strub...@yahoo.de:
Oki, I understand. Will try to look at it the next week.
Great.
Thank you,
Lars
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail:
maybe try w/o filePermissions and directoryPermissions, and you can take a
look at nexus log to get more details
On Fri, Jul 29, 2011 at 5:29 AM, laredotornado-3 laredotorn...@gmail.comwrote:
Hi,
I'm using Maven 3.0.3 with a Sonatype repository. I'm able to deploy my
artifact to the remote
Your Nexus release repository is not set up to allow redeploying of releases.
Release artifacts should (generally) not be re-deployed, because once they
have been downloaded, they will never be re-downloaded again, unless they
are removed from the local repository.
Be advised.
--
View this
http://maven.apache.org/guides/introduction/introduction-to-profiles.html
Is this trying to tell me that activeByDefault in settings.xml is
unconditional, since it settings.xml isn't 'a pom' and so no other
profile 'in the same pom' can be active?
activeByDefault only works in the pom.xml in the settings.xml you need
to use activeprofiles
On 29 July 2011 13:01, Benson Margulies bimargul...@gmail.com wrote:
http://maven.apache.org/guides/introduction/introduction-to-profiles.html
Is this trying to tell me that activeByDefault in
Cannot make head nor tail of what exactly that page is trying to say
in that regard... needs some rewrite
On 29 July 2011 13:07, Stephen Connolly stephen.alan.conno...@gmail.com wrote:
activeByDefault only works in the pom.xml in the settings.xml you need
to use activeprofiles
On 29 July 2011
Hi all,
I'm using codehaus jboss-packaging-maven-plugin to get a sar. I'm then
deploying this jboss-sar inside an ear.
Pom A:
groupIdpt.nevaco/groupId
artifactIdchildren1/artifactId
version1.0.0-SNAPSHOT/version
packagingjboss-sar/packaging
build
plugins
Try configuring release:prepare to do an 'install' instead of just a
'verify'... There's (still?) a problem with releasing a WAR or EAR
package in Maven...
Roland
On 29.07.2011 15:23, Tiago António Neves wrote:
Hi all,
I’m using codehaus jboss-packaging-maven-plugin to get a sar. I’m then
Hi all,
I'm using codehaus jboss-packaging-maven-plugin to get a sar. I'm then
deploying this jboss-sar inside an ear.
Pom A:
groupIdpt.nevaco/groupId
artifactIdchildren1/artifactId
version1.0.0-SNAPSHOT/version
packagingjboss-sar/packaging
build
plugins
Stephen,
That's not my experience. We've had some profiles in the global
settings.xml for two years that are 'activeByDefault' and are, well,
active.
--benson
On Fri, Jul 29, 2011 at 8:07 AM, Stephen Connolly
stephen.alan.conno...@gmail.com wrote:
activeByDefault only works in the pom.xml in
Thank you very much. That one was driving me mad! Doing mvn release:prepare
-DpreparationGols=clean install did the trick ;)
Tiago Neves
Tiago António da Silva Vaz Neves
Sistemas de Suporte às Operações
SSO4 - Controlo de Processos de Operação
tlm: (+351) 96 911 38 28
fax: (+351)
hello,
my access was denied to archiva and i defined in settings.xml
[INFO] Scanning for projects...
[INFO]
[INFO]
[INFO] Building Parent Sample Pom
The repository IDs in profile does not match the IDs in servers
section, hence, are not picked up. That's why Archiva rejects your
access, but would stand for any other access to remote server/repo
that is protected.
Thanks,
~t~
On Fri, Jul 29, 2011 at 4:36 PM, koppaka pradeep bull...@gmail.com
We're moving around some switching gear to have faster internet access
for Central. Because of this, the ip numbers for the US Central
servers will change. This should not affect most users unless your
corporate IT has firewall rules locked to the old ips. You can see
more details about the change
Hi,
Is there a simple solution for updating your dependent build plugin versions? I
know of versions:display-plugin-updates, but is there anyway to automatically
update them as well? I would love to run a goal on an aggregator POM that would
update all projects build plugins to the most recent
So suppose I have 2 projects: projectLib and projectWar.
Whenever I'm in the projectLib folder where the pom.xml is, I'd like to just
type mvn and have it run the mvn install lifecycle
Whenever I'm in the projectWar folder where the pom.xml is, I'd like to just
type mvn and have it run the mvn
Is there a way to set this default behavior in the pom.xml for each project?
No. But you could write your own mvni.bat and mvnd.bat or
mvnp.bat and other files that would just call the mvn install and
mvn deploy etc for you.
Wayne
Is there a simple solution for updating your dependent build plugin versions?
Most people want their builds to be stable first and foremost, so
this is not a well-supported use case.
I know of versions:display-plugin-updates, but is there anyway to
automatically update them as well?
Not
Thanks for the response. What you mention is exactly my use case, When I decide
I want the new version of a plugin I want to update all projects at once
instead of having to open each pom and change it by hand. From your response I
am guessing it is expected to use properties to control this.
When I decide I want the new version of a plugin I want to update all projects
at once instead of having to open each pom and change it by hand. From
your response I am guessing it is expected to use properties to control this.
Or use pluginManagement in a shared parent...
Wayne
The defaultGoal element can be used.
project
...
build
defaultGoalinstall/defaultGoal
...
/build
/project
On Jul 29, 2011, at 2:33 PM, kanesee wrote:
So suppose I have 2 projects: projectLib and projectWar.
Whenever I'm in the projectLib folder where the pom.xml is, I'd like
Kane,
I believe the defaultGoal property within the project/build element [1]
is what you're looking for.
[1] http://maven.apache.org/ref/3.0.3/maven-model/maven.html#class_build
Ron Gallagher
-Original Message-
From: kanesee [mailto:kane...@gmail.com]
Sent: Friday, July 29, 2011 2:33
The defaultGoal element can be used.
defaultGoalinstall/defaultGoal
Hmm I forgot about that configuration option... never used it.
Wayne
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional
Thanks very much.
--
View this message in context:
http://maven.40175.n5.nabble.com/Is-there-a-way-to-set-a-default-lifecycle-action-tp4647944p4648209.html
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To
30 matches
Mail list logo
