Trouble deploying to remote repository after the first time (400 error)
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: org.apache.maven.wagon.TransferFailedException: Failed to transfer file: http://sonatype.myco.com/nexus/content/repositories/releases/com/nna/parent/1.0/parent-1.0.pom. Return code is: 400 at org.apache.maven.wagon.providers.http.LightweightHttpWagon.finishPutTransfer(LightweightHttpWagon.java:205) at org.apache.maven.wagon.AbstractWagon.putTransfer(AbstractWagon.java:413) at org.apache.maven.wagon.AbstractWagon.transfer(AbstractWagon.java:392) at org.apache.maven.wagon.AbstractWagon.putTransfer(AbstractWagon.java:365) at org.apache.maven.wagon.StreamWagon.put(StreamWagon.java:163) at org.sonatype.aether.connector.wagon.WagonRepositoryConnector$PutTask.run(WagonRepositoryConnector.java:825) at org.sonatype.aether.connector.wagon.WagonRepositoryConnector.put(WagonRepositoryConnector.java:465) Here is what is in my sonatype.xml file … settings xmlns=http://maven.apache.org/SETTINGS/1.0.0; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=http://maven.apache.org/SETTINGS/1.0.0 http://maven.apache.org/xsd/settings-1.0.0.xsd; servers server idsonatype-nexus/id usernameusername/username passwordpassword/password filePermissions664/filePermissions directoryPermissions775/directoryPermissions /server /servers /settings and here is the relevant section from my pom.xml … distributionManagement repository idsonatype-nexus/id urlhttp://sonatype.myco.com/nexus/content/repositories/releases//url /repository /distributionManagement Anyway, any insights are greatly appreciated on why I'm getting the 400 error. Thanks, - Dave -- View this message in context: http://maven.40175.n5.nabble.com/Trouble-deploying-to-remote-repository-after-the-first-time-400-error-tp4644301p4644301.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: gitflow releases with maven?
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 being the version number. If I checked out master and did a maven install, I'd expect to get a SNAPSHOT and not something that's going to overwrite existing released artifacts. It must not match the maven repo, but there should not be a SNAPSHOT-pom on HEAD As above I beg to differ. Hmm, this is what I understand from the gitflow documentation and what results, when performing a manual release without the maven-release-plugin. But you are right, ignoring this restriction is no real problem. [...] [INFO] --- maven-release-plugin:2.2:perform (default-cli) @ master --- [INFO] Checking out the project to perform the release ... [INFO] Performing a LOCAL checkout from scm:git:file://D:\dev\projects\maven.master\source\maven.master [INFO] Executing: cmd.exe /X /C git clone file://D\dev\projects\maven.master\source\maven.master D:\dev\projects\maven.master\source\maven.master\target\checkout Interesting - I see you have maven.master mentioned twice in the path - what do you have in your SCM settings element? scm connectionscm:git:ssh://git@myserver:22/maven.master.git/connection developerConnectionscm:git:ssh://git@myserver:22/maven.master.git/developerConnection /scm And what is the root path of the git repo The file path to the local clone is: D:\dev\projects\maven.master\source\maven.master There are two maven.master, because I organize my projects in subfolders with eclipse workspace folders parallel to the source folders (e.g. D:\dev\projects\maven.master\workspace). and are you releasing from that directory? Both, the git and mvn commands are executed from D:\dev\projects\maven.master\source\maven.master 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: 'd:devprojectsmaven.mastersourcemaven.master' does not appear to be a git repository fatal: The remote end hung up unexpectedly When using a different path with slashes git clone file:///d:/dev/projects/maven.master/source/maven.master/ everything works fine. Regards, Lars - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: gitflow releases with maven?
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: 'd:devprojectsmaven.mastersourcemaven.master' does not appear to be a git repository fatal: The remote end hung up unexpectedly When using a different path with slashes git clone file:///d:/dev/projects/maven.master/source/maven.master/ everything works fine. Looks like I hit this issue: http://jira.codehaus.org/browse/MRELEASE-624 Regards, Lars - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: gitflow releases with maven?
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 --- 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, July 29, 2011, 8:03 AM 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 being the version number. If I checked out master and did a maven install, I'd expect to get a SNAPSHOT and not something that's going to overwrite existing released artifacts. It must not match the maven repo, but there should not be a SNAPSHOT-pom on HEAD As above I beg to differ. Hmm, this is what I understand from the gitflow documentation and what results, when performing a manual release without the maven-release-plugin. But you are right, ignoring this restriction is no real problem. [...] [INFO] --- maven-release-plugin:2.2:perform (default-cli) @ master --- [INFO] Checking out the project to perform the release ... [INFO] Performing a LOCAL checkout from scm:git:file://D:\dev\projects\maven.master\source\maven.master [INFO] Executing: cmd.exe /X /C git clone file://D\dev\projects\maven.master\source\maven.master D:\dev\projects\maven.master\source\maven.master\target\checkout Interesting - I see you have maven.master mentioned twice in the path - what do you have in your SCM settings element? scm connectionscm:git:ssh://git@myserver:22/maven.master.git/connection developerConnectionscm:git:ssh://git@myserver:22/maven.master.git/developerConnection /scm And what is the root path of the git repo The file path to the local clone is: D:\dev\projects\maven.master\source\maven.master There are two maven.master, because I organize my projects in subfolders with eclipse workspace folders parallel to the source folders (e.g. D:\dev\projects\maven.master\workspace). and are you releasing from that directory? Both, the git and mvn commands are executed from D:\dev\projects\maven.master\source\maven.master 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: 'd:devprojectsmaven.mastersourcemaven.master' does not appear to be a git repository fatal: The remote end hung up unexpectedly When using a different path with slashes git clone file:///d:/dev/projects/maven.master/source/maven.master/ everything works fine. Regards, Lars - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: gitflow releases with maven?
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 projects by doing a git-clone file:// from the local git repo instead of cloning the upstream repo in release:perform. Yes, localCheckout=true and pushChanges=false are used, because the maven-release-plugin should perform only local changes. Gitflow has to do additional branching / merging, which has to be pushed outside the maven-release-plugin. Regards, Lars - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: gitflow releases with maven?
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, July 29, 2011, 8:34 AM 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 projects by doing a git-clone file:// from the local git repo instead of cloning the upstream repo in release:perform. Yes, localCheckout=true and pushChanges=false are used, because the maven-release-plugin should perform only local changes. Gitflow has to do additional branching / merging, which has to be pushed outside the maven-release-plugin. Regards, Lars - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: gitflow releases with maven?
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: users-h...@maven.apache.org
Re: Trouble deploying to remote repository after the first time (400 error)
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 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: org.apache.maven.wagon.TransferFailedException: Failed to transfer file: http://sonatype.myco.com/nexus/content/repositories/releases/com/nna/parent/1.0/parent-1.0.pom . Return code is: 400 at org.apache.maven.wagon.providers.http.LightweightHttpWagon.finishPutTransfer(LightweightHttpWagon.java:205) at org.apache.maven.wagon.AbstractWagon.putTransfer(AbstractWagon.java:413) at org.apache.maven.wagon.AbstractWagon.transfer(AbstractWagon.java:392) at org.apache.maven.wagon.AbstractWagon.putTransfer(AbstractWagon.java:365) at org.apache.maven.wagon.StreamWagon.put(StreamWagon.java:163) at org.sonatype.aether.connector.wagon.WagonRepositoryConnector$PutTask.run(WagonRepositoryConnector.java:825) at org.sonatype.aether.connector.wagon.WagonRepositoryConnector.put(WagonRepositoryConnector.java:465) Here is what is in my sonatype.xml file … settings xmlns=http://maven.apache.org/SETTINGS/1.0.0; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=http://maven.apache.org/SETTINGS/1.0.0 http://maven.apache.org/xsd/settings-1.0.0.xsd; servers server idsonatype-nexus/id usernameusername/username passwordpassword/password filePermissions664/filePermissions directoryPermissions775/directoryPermissions /server /servers /settings and here is the relevant section from my pom.xml … distributionManagement repository idsonatype-nexus/id urlhttp://sonatype.myco.com/nexus/content/repositories/releases//url /repository /distributionManagement Anyway, any insights are greatly appreciated on why I'm getting the 400 error. Thanks, - Dave -- View this message in context: http://maven.40175.n5.nabble.com/Trouble-deploying-to-remote-repository-after-the-first-time-400-error-tp4644301p4644301.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Trouble deploying to remote repository after the first time (400 error)
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 message in context: http://maven.40175.n5.nabble.com/Trouble-deploying-to-remote-repository-after-the-first-time-400-error-tp4644301p4646447.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
clarification on activeByDefault
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? - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: clarification on activeByDefault
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 settings.xml is unconditional, since it settings.xml isn't 'a pom' and so no other profile 'in the same pom' can be active? - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: clarification on activeByDefault
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 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 settings.xml is unconditional, since it settings.xml isn't 'a pom' and so no other profile 'in the same pom' can be active? - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Maven release plugin with jboss packaging maven plugin
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
plugin
groupIdorg.codehaus.mojo/groupId
artifactIdjboss-packaging-maven-plugin/artifactId
version2.1.1/version
extensionstrue/extensions
/plugin
/plugins
/build
Pom B:
groupIdpt.nevaco/groupId
artifactIdchildren2/artifactId
version1.0.0-SNAPSHOT/version
packagingear/packaging
dependencies
dependency
groupIdpt.nevaco/groupId
artifactIdchildren1/artifactId
version${version}/version
/dependency
/dependencies
build
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-ear-plugin/artifactId
version2.5/version
configuration
displayNameNevaco EAR/displayName
version1.4/version
fileNameMappingno-version/fileNameMapping
modules
sarModule
groupIdpt.nevaco/groupId
artifactIdchildren1/artifactId
/sarModule
/modules
/configuration
/plugin
/plugins
/build
The problem is that when I run mvn release:prepare it seems to don't understand
that the sar is from my project and tries to download it from the repos
[INFO] [INFO]
[INFO] [ERROR] BUILD ERROR
[INFO] [INFO]
[INFO] [INFO] Failed to resolve artifact.
[INFO]
[INFO] Missing:
[INFO] --
[INFO] 1) pt.nevaco:children1:sar:1.0.0
[INFO]
[INFO] Try downloading the file manually from the project website.
[INFO]
[INFO] Then, install it using the command:
[INFO] mvn install:install-file -DgroupId=pt.nevaco
-DartifactId=children1 -Dversion=1.0.0 -Dpackaging=sar -Dfile=/path/to/file
[INFO]
[INFO] Alternatively, if you host your own repository you can deploy the file
there:
[INFO] mvn deploy:deploy-file -DgroupId=pt.nevaco -DartifactId=children1
-Dversion=1.0.0 -Dpackaging=sar -Dfile=/path/to/file -Durl=[url]
-DrepositoryId=[id]
[INFO]
[INFO] Path to dependency:
[INFO] 1) pt.nevaco:children2:ear:1.0.0
[INFO] 2) pt.nevaco:children1:sar:1.0.0
[INFO]
[INFO] --
[INFO] 1 required artifact is missing.
[INFO]
[INFO] for artifact:
[INFO] pt.nevaco:children2:ear:1.0.0
[INFO]
[INFO] from the specified remote repositories:
[INFO] central (http://xxx/xxx-releases),
[INFO] repo (http://xxx/repo),
[INFO] snapshots (http://xxx/xxx-snapshots)
[INFO]
[INFO]
[INFO]
[INFO] [INFO]
[INFO] [INFO] For more information, run Maven with the -e switch
[INFO] [INFO]
[INFO] [INFO] Total time: 12 seconds
[INFO] [INFO] Finished at: Fri Jul 29 13:35:02 BST 2011
[INFO] [INFO] Final Memory: 42M/362M
[INFO] [INFO]
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Maven execution failed, exit code: '1'
[INFO]
Any ideas/workaround
Tiago Neves
[cid:image001.jpg@01CC4DF7.F96E0660]
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) 234 403 588
tiago-a-ne...@ptinovacao.ptmailto:tiago-a-ne...@ptinovacao.pt
Re: Maven release plugin with jboss packaging maven plugin
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
deploying this jboss-sar inside an ear.
Pom A:
groupIdpt.nevaco/groupId
artifactIdchildren1/artifactId
version1.0.0-SNAPSHOT/version
packagingjboss-sar/packaging
build
plugins
plugin
groupIdorg.codehaus.mojo/groupId
artifactIdjboss-packaging-maven-plugin/artifactId
version2.1.1/version
extensionstrue/extensions
/plugin
/plugins
/build
Pom B:
groupIdpt.nevaco/groupId
artifactIdchildren2/artifactId
version1.0.0-SNAPSHOT/version
packagingear/packaging
dependencies
dependency
groupIdpt.nevaco/groupId
artifactIdchildren1/artifactId
version${version}/version
/dependency
/dependencies
build
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-ear-plugin/artifactId
version2.5/version
configuration
displayNameNevaco EAR/displayName
version1.4/version
fileNameMappingno-version/fileNameMapping
modules
sarModule
groupIdpt.nevaco/groupId
artifactIdchildren1/artifactId
/sarModule
/modules
/configuration
/plugin
/plugins
/build
The problem is that when I run mvn release:prepare it seems to don’t
understand that the sar is from my project and tries to download it from
the repos
[INFO] [INFO]
[INFO] [ERROR] BUILD ERROR
[INFO] [INFO]
[INFO] [INFO] Failed to resolve artifact.
[INFO]
[INFO] Missing:
[INFO] --
[INFO] 1) pt.nevaco:children1:sar:1.0.0
[INFO]
[INFO] Try downloading the file manually from the project website.
[INFO]
[INFO] Then, install it using the command:
[INFO] mvn install:install-file -DgroupId=pt.nevaco
-DartifactId=children1 -Dversion=1.0.0 -Dpackaging=sar -Dfile=/path/to/file
[INFO]
[INFO] Alternatively, if you host your own repository you can deploy the
file there:
[INFO] mvn deploy:deploy-file -DgroupId=pt.nevaco -DartifactId=children1
-Dversion=1.0.0 -Dpackaging=sar -Dfile=/path/to/file -Durl=[url]
-DrepositoryId=[id]
[INFO]
[INFO] Path to dependency:
[INFO] 1) pt.nevaco:children2:ear:1.0.0
[INFO] 2) pt.nevaco:children1:sar:1.0.0
[INFO]
[INFO] --
[INFO] 1 required artifact is missing.
[INFO]
[INFO] for artifact:
[INFO] pt.nevaco:children2:ear:1.0.0
[INFO]
[INFO] from the specified remote repositories:
[INFO] central (http://xxx/xxx-releases),
[INFO] repo (http://xxx/repo),
[INFO] snapshots (http://xxx/xxx-snapshots)
[INFO]
[INFO]
[INFO]
[INFO] [INFO]
[INFO] [INFO] For more information, run Maven with the -e switch
[INFO] [INFO]
[INFO] [INFO] Total time: 12 seconds
[INFO] [INFO] Finished at: Fri Jul 29 13:35:02 BST 2011
[INFO] [INFO] Final Memory: 42M/362M
[INFO] [INFO]
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Maven execution failed, exit code: '1'
[INFO]
Any ideas/workaround
Tiago Neves
cid:image001.jpg@01CB84E5.0C98AA60
**
*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) 234 403 588
tiago-a-ne...@ptinovacao.pt mailto:tiago-a-ne...@ptinovacao.pt
--
Roland Asmann
Senior Software Engineer
adesso Austria GmbH
Floridotower 26. Stock T +43 1 2198790-27
Floridsdorfer Hauptstr. 1 F +43 1 2198790-927
A-1210 Wien M +43 664 88657566
E roland.asm...@adesso.at
W www.adesso.at
-
business. people. technology.
-
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Maven release plugin with jboss packaging maven plugin
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
plugin
groupIdorg.codehaus.mojo/groupId
artifactIdjboss-packaging-maven-plugin/artifactId
version2.1.1/version
extensionstrue/extensions
/plugin
/plugins
/build
Pom B:
groupIdpt.nevaco/groupId
artifactIdchildren2/artifactId
version1.0.0-SNAPSHOT/version
packagingear/packaging
dependencies
dependency
groupIdpt.nevaco/groupId
artifactIdchildren1/artifactId
version${version}/version
/dependency
/dependencies
build
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-ear-plugin/artifactId
version2.5/version
configuration
displayNameNevaco EAR/displayName
version1.4/version
fileNameMappingno-version/fileNameMapping
modules
sarModule
groupIdpt.nevaco/groupId
artifactIdchildren1/artifactId
/sarModule
/modules
/configuration
/plugin
/plugins
/build
The problem is that when I run mvn release.prepare it seems to don't understand
that the sar is from my project and tries to download it from the repos
[INFO] [INFO]
[INFO] [ERROR] BUILD ERROR
[INFO] [INFO]
[INFO] [INFO] Failed to resolve artifact.
[INFO]
[INFO] Missing:
[INFO] --
[INFO] 1) pt.nevaco:children1:sar:1.0.0
[INFO]
[INFO] Try downloading the file manually from the project website.
[INFO]
[INFO] Then, install it using the command:
[INFO] mvn install:install-file -DgroupId=pt.nevaco
-DartifactId=children1 -Dversion=1.0.0 -Dpackaging=sar -Dfile=/path/to/file
[INFO]
[INFO] Alternatively, if you host your own repository you can deploy the file
there:
[INFO] mvn deploy:deploy-file -DgroupId=pt.nevaco -DartifactId=children1
-Dversion=1.0.0 -Dpackaging=sar -Dfile=/path/to/file -Durl=[url]
-DrepositoryId=[id]
[INFO]
[INFO] Path to dependency:
[INFO] 1) pt.nevaco:children2:ear:1.0.0
[INFO] 2) pt.nevaco:children1:sar:1.0.0
[INFO]
[INFO] --
[INFO] 1 required artifact is missing.
[INFO]
[INFO] for artifact:
[INFO] pt.nevaco:children2:ear:1.0.0
[INFO]
[INFO] from the specified remote repositories:
[INFO] central (http://xxx/xxx-releases),
[INFO] repo (http://xxx/repo),
[INFO] snapshots (http://xxx/xxx-snapshots)
[INFO]
[INFO]
[INFO]
[INFO] [INFO]
[INFO] [INFO] For more information, run Maven with the -e switch
[INFO] [INFO]
[INFO] [INFO] Total time: 12 seconds
[INFO] [INFO] Finished at: Fri Jul 29 13:35:02 BST 2011
[INFO] [INFO] Final Memory: 42M/362M
[INFO] [INFO]
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Maven execution failed, exit code: '1'
[INFO]
Any ideas/workaround
Tiago Neves
[cid:image001.jpg@01CC4DF7.F96E0660]
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) 234 403 588
tiago-a-ne...@ptinovacao.ptmailto:tiago-a-ne...@ptinovacao.pt
Re: clarification on activeByDefault
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 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 settings.xml is unconditional, since it settings.xml isn't 'a pom' and so no other profile 'in the same pom' can be active? - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
RE: Maven release plugin with jboss packaging maven plugin
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) 234 403 588
tiago-a-ne...@ptinovacao.pt
-Original Message-
From: Asmann, Roland [mailto:roland.asm...@adesso.at]
Sent: Friday, July 29, 2011 14:28
To: users@maven.apache.org
Subject: Re: Maven release plugin with jboss packaging maven plugin
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
deploying this jboss-sar inside an ear.
Pom A:
groupIdpt.nevaco/groupId
artifactIdchildren1/artifactId
version1.0.0-SNAPSHOT/version
packagingjboss-sar/packaging
build
plugins
plugin
groupIdorg.codehaus.mojo/groupId
artifactIdjboss-packaging-maven-plugin/artifactId
version2.1.1/version
extensionstrue/extensions
/plugin
/plugins
/build
Pom B:
groupIdpt.nevaco/groupId
artifactIdchildren2/artifactId
version1.0.0-SNAPSHOT/version
packagingear/packaging
dependencies
dependency
groupIdpt.nevaco/groupId
artifactIdchildren1/artifactId
version${version}/version
/dependency
/dependencies
build
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-ear-plugin/artifactId
version2.5/version
configuration
displayNameNevaco EAR/displayName
version1.4/version
fileNameMappingno-version/fileNameMapping
modules
sarModule
groupIdpt.nevaco/groupId
artifactIdchildren1/artifactId
/sarModule
/modules
/configuration
/plugin
/plugins
/build
The problem is that when I run mvn release:prepare it seems to don't
understand that the sar is from my project and tries to download it from
the repos
[INFO] [INFO]
[INFO] [ERROR] BUILD ERROR
[INFO] [INFO]
[INFO] [INFO] Failed to resolve artifact.
[INFO]
[INFO] Missing:
[INFO] --
[INFO] 1) pt.nevaco:children1:sar:1.0.0
[INFO]
[INFO] Try downloading the file manually from the project website.
[INFO]
[INFO] Then, install it using the command:
[INFO] mvn install:install-file -DgroupId=pt.nevaco
-DartifactId=children1 -Dversion=1.0.0 -Dpackaging=sar -Dfile=/path/to/file
[INFO]
[INFO] Alternatively, if you host your own repository you can deploy the
file there:
[INFO] mvn deploy:deploy-file -DgroupId=pt.nevaco -DartifactId=children1
-Dversion=1.0.0 -Dpackaging=sar -Dfile=/path/to/file -Durl=[url]
-DrepositoryId=[id]
[INFO]
[INFO] Path to dependency:
[INFO] 1) pt.nevaco:children2:ear:1.0.0
[INFO] 2) pt.nevaco:children1:sar:1.0.0
[INFO]
[INFO] --
[INFO] 1 required artifact is missing.
[INFO]
[INFO] for artifact:
[INFO] pt.nevaco:children2:ear:1.0.0
[INFO]
[INFO] from the specified remote repositories:
[INFO] central (http://xxx/xxx-releases),
[INFO] repo (http://xxx/repo),
[INFO] snapshots (http://xxx/xxx-snapshots)
[INFO]
[INFO]
[INFO]
[INFO] [INFO]
[INFO] [INFO] For more information, run Maven with the -e switch
[INFO] [INFO]
[INFO] [INFO] Total time: 12 seconds
[INFO] [INFO] Finished at: Fri Jul 29 13:35:02 BST 2011
[INFO] [INFO] Final Memory: 42M/362M
[INFO] [INFO]
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Maven execution failed, exit code: '1'
[INFO]
Any ideas/workaround
Tiago Neves
cid:image001.jpg@01CB84E5.0C98AA60
**
*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) 234 403 588
tiago-a-ne...@ptinovacao.pt mailto:tiago-a-ne...@ptinovacao.pt
--
Roland Asmann
Senior Software Engineer
adesso Austria GmbH
Floridotower 26. Stock T +43 1 2198790-27
Floridsdorfer Hauptstr. 1 F +43 1 2198790-927
A-1210 Wien M +43 664 88657566
E roland.asm...@adesso.at
W www.adesso.at
-
business. people. technology.
does Maven 3 supports use of archiva 1.3.5
hello, my access was denied to archiva and i defined in settings.xml [INFO] Scanning for projects... [INFO] [INFO] [INFO] Building Parent Sample Pom 0.0.1-SNAPSHOT [INFO] Downloading: http://localhost:8080/archiva/repository/internal/org/apache/maven/plugins/maven-install-plugin/2.3.1/maven-install-plugin-2.3.1.pom [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 0.284s [INFO] Finished at: Fri Jul 29 19:51:12 IST 2011 [INFO] Final Memory: 2M/50M [INFO] [ERROR] Plugin org.apache.maven.plugins:maven-install-plugin:2.3.1 or one of its dependencies could not be resolved: Failed to read artifact descriptor for org.apache.maven.plugins:maven-install-plugin:jar:2.3.1: Could not transfer artifact org.apache.maven.plugins:maven-install-plugin:pom:2.3.1 from/to archiva.default (http://localhost:8080/archiva/repository/internal/): Access denied to: http://localhost:8080/archiva/repository/internal/org/apache/maven/plugins/maven-install-plugin/2.3.1/maven-install-plugin-2.3.1.pom - [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/PluginResolutionException I followed the guide in configuring but i am not able to please tell me the complete template for configuring archiva..in maven3 settings.xml i am pasting my settings.xml for better idea...please guide me.. i am new to maven..i am behind a proxy ?xml version=1.0 encoding=UTF-8? proxies proxy idMyproxy/id activetrue/active protocolhttp/protocol usernameuser/username password*/password hostproxy.mycompany.com/host port8080/port nonProxyHostslocal.net|some.host.com/nonProxyHosts /proxy /proxies servers server idarchiva.internal/id usernameadmin/username passwordarchiva123/password /server server idarchiva.snapshots/id usernameadmin/username passwordarchiva123/password /server /servers profiles profile idday-central/id activation activeByDefaulttrue/activeByDefault /activation repositories repository idinternal/id nameArchiva Managed Internal Repository/name urlhttp://localhost:8080/archiva/repository/internal//url releases enabledtrue/enabled /releases snapshots enabledfalse/enabled /snapshots /repository repository idsnapshots/id nameArchiva Managed Snapshot Repository/name urlhttp://localhost:8080/archiva/repository/snapshots//url releases enabledfalse/enabled /releases snapshots enabledtrue/enabled /snapshots /repository /repositories pluginRepositories pluginRepository idinternal/id nameMy Company Archiva Repository/name urlhttp://localhost:8080/archiva/repository/internal/url layoutdefault/layout /pluginRepository /pluginRepositories /profile /profiles /settings your help would be appreciated mirrors mirror idarchiva.default/id urlhttp://localhost:8080/archiva/repository/internal//url mirrorOf*/mirrorOf /mirror /mirrors profiles profile idday-central/id activation activeByDefaulttrue/activeByDefault /activation repositories repository idinternal/id nameArchiva Managed Internal Repository/name urlhttp://localhost:8080/archiva/repository/internal//url releases enabledtrue/enabled /releases snapshots enabledfalse/enabled /snapshots /repository repository idsnapshots/id nameArchiva Managed Snapshot Repository/name urlhttp://localhost:8080/archiva/repository/snapshots//url releases enabledfalse/enabled /releases snapshots enabledtrue/enabled /snapshots /repository /repositories pluginRepositories pluginRepository idinternal/id nameMy Company Archiva Repository/name urlhttp://localhost:8080/archiva/repository/internal/url layoutdefault/layout /pluginRepository /pluginRepositories /profile
Re: does Maven 3 supports use of archiva 1.3.5
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 wrote: hello, my access was denied to archiva and i defined in settings.xml [INFO] Scanning for projects... [INFO] [INFO] [INFO] Building Parent Sample Pom 0.0.1-SNAPSHOT [INFO] Downloading: http://localhost:8080/archiva/repository/internal/org/apache/maven/plugins/maven-install-plugin/2.3.1/maven-install-plugin-2.3.1.pom [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 0.284s [INFO] Finished at: Fri Jul 29 19:51:12 IST 2011 [INFO] Final Memory: 2M/50M [INFO] [ERROR] Plugin org.apache.maven.plugins:maven-install-plugin:2.3.1 or one of its dependencies could not be resolved: Failed to read artifact descriptor for org.apache.maven.plugins:maven-install-plugin:jar:2.3.1: Could not transfer artifact org.apache.maven.plugins:maven-install-plugin:pom:2.3.1 from/to archiva.default (http://localhost:8080/archiva/repository/internal/): Access denied to: http://localhost:8080/archiva/repository/internal/org/apache/maven/plugins/maven-install-plugin/2.3.1/maven-install-plugin-2.3.1.pom - [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/PluginResolutionException I followed the guide in configuring but i am not able to please tell me the complete template for configuring archiva..in maven3 settings.xml i am pasting my settings.xml for better idea...please guide me.. i am new to maven..i am behind a proxy ?xml version=1.0 encoding=UTF-8? proxies proxy idMyproxy/id activetrue/active protocolhttp/protocol usernameuser/username password*/password hostproxy.mycompany.com/host port8080/port nonProxyHostslocal.net|some.host.com/nonProxyHosts /proxy /proxies servers server idarchiva.internal/id usernameadmin/username passwordarchiva123/password /server server idarchiva.snapshots/id usernameadmin/username passwordarchiva123/password /server /servers profiles profile idday-central/id activation activeByDefaulttrue/activeByDefault /activation repositories repository idinternal/id nameArchiva Managed Internal Repository/name urlhttp://localhost:8080/archiva/repository/internal//url releases enabledtrue/enabled /releases snapshots enabledfalse/enabled /snapshots /repository repository idsnapshots/id nameArchiva Managed Snapshot Repository/name urlhttp://localhost:8080/archiva/repository/snapshots//url releases enabledfalse/enabled /releases snapshots enabledtrue/enabled /snapshots /repository /repositories pluginRepositories pluginRepository idinternal/id nameMy Company Archiva Repository/name urlhttp://localhost:8080/archiva/repository/internal/url layoutdefault/layout /pluginRepository /pluginRepositories /profile /profiles /settings your help would be appreciated mirrors mirror idarchiva.default/id urlhttp://localhost:8080/archiva/repository/internal//url mirrorOf*/mirrorOf /mirror /mirrors profiles profile idday-central/id activation activeByDefaulttrue/activeByDefault /activation repositories repository idinternal/id nameArchiva Managed Internal Repository/name urlhttp://localhost:8080/archiva/repository/internal//url releases enabledtrue/enabled /releases snapshots enabledfalse/enabled /snapshots /repository repository idsnapshots/id nameArchiva Managed Snapshot Repository/name urlhttp://localhost:8080/archiva/repository/snapshots//url releases enabledfalse/enabled /releases snapshots enabledtrue/enabled /snapshots /repository /repositories pluginRepositories
Central IP number changes
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 here: http://www.sonatype.com/people/2011/07/the-central-repository-is-getting-faster-are-you-ready-for-the-new-ips/ Thanks, Brian - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Automatic Update of Build Plugin Versions?
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 version (or specify a subset of groupId/artifactId plugins to update). Or is this usually just handled by a property in the aggregator POM? Thanks in advance, Daniel Johnson - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Is there a way to set a default lifecycle action?
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 package or mvn deploy lifecycle Is there a way to set this default behavior in the pom.xml for each project? Thanks, Kane -- View this message in context: http://maven.40175.n5.nabble.com/Is-there-a-way-to-set-a-default-lifecycle-action-tp4647944p4647944.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Is there a way to set a default lifecycle action?
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 - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Automatic Update of Build Plugin Versions?
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 that I am aware of. But I don't bump plugin versions unless I suddenly need some new functionality or a specific bug-fix. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Automatic Update of Build Plugin Versions?
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. Thanks, Dan On Jul 29, 2011, at 11:50 AM, Wayne Fay wrote: I know of versions:display-plugin-updates, but is there anyway to automatically update them as well? Not that I am aware of. But I don't bump plugin versions unless I suddenly need some new functionality or a specific bug-fix. Wayne
Re: Automatic Update of Build Plugin Versions?
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 - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Is there a way to set a default lifecycle action?
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 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 package or mvn deploy lifecycle Is there a way to set this default behavior in the pom.xml for each project? Thanks, Kane -- View this message in context: http://maven.40175.n5.nabble.com/Is-there-a-way-to-set-a-default-lifecycle-action-tp4647944p4647944.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org Thanks, Jason -- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl - To do two things at once is to do neither. -—Publilius Syrus, Roman slave, first century B.C.
RE: Is there a way to set a default lifecycle action?
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 PM To: users@maven.apache.org Subject: Is there a way to set a default lifecycle action? 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 package or mvn deploy lifecycle Is there a way to set this default behavior in the pom.xml for each project? Thanks, Kane -- View this message in context: http://maven.40175.n5.nabble.com/Is-there-a-way-to-set-a-default-lifecyc le-action-tp4647944p4647944.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Is there a way to set a default lifecycle action?
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 commands, e-mail: users-h...@maven.apache.org
Re: Is there a way to set a default lifecycle action?
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 unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
