RE: Nexus deployment of a ZIP file...
I found the goal deploy:deploy-file that works to deploy specific file to Nexus. mvn deploy:deploy-file -Durl=$REPO_URL -DrepositoryId=$REPO_ID -DgroupId=org.myorg -DartifactId=myproj -Dversion=1.2.3 -Dpackaging=zip -Dfile=myproj.zip What I don't understand is why do I have to supply url, repositoryID, groupID, artifactID, version on command line if it's already in pom.xml ? Thanks, Robert Zanzerkia Fidelity Investments FTG-OPS Two Contra Way Merrimack, NH 03054 Work: 603-791-3477 Blackberry: 603-320-9682 -Original Message- From: Zanzerkia, Robert Sent: Tuesday, March 19, 2013 12:11 PM To: users@maven.apache.org Subject: Nexus deployment of a ZIP file... Hi, I am trying to deploy a zip file built using Maven to the Nexus repository (internal to our company). When I use mvn deploy it connects to repository and deploys the snapshot except with the default jar file NOT with the zip file I am building as explained below. uCMDB-PatternDev-0.0.1-20130319.143249-1.jar instead of the ZIP I created in target folder : uCMDB-PatternDev-0.0.1-SNAPSHOT-packages.zip I experimented with maven-deploy-plugin which didn't work. Also I rather NOT define file, just want it to copy the output of assembly plugin... Thanks, My project builds a ZIP file using following plugin. (this part works fine). plugin artifactIdmaven-assembly-plugin/artifactId version2.4/version configuration descriptors descriptordistribution.xml/descriptor /descriptors /configuration /plugin Distribution.xml assembly xmlns=http://maven.apache.org/plugins/maven-assembly-plugin/assembly/1.1.2; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=http://maven.apache.org/plugins/maven-assembly-plugin/assembly/1.1.2 http://maven.apache.org/xsd/assembly-1.1.2.xsd; idpackages/id formats formatzip/format /formats repositories repository outputDirectoryrepository/outputDirectory /repository /repositories fileSets fileSet directory./dist/directory includes include**/include /includes excludes exclude./target/exclude exclude./repository/exclude /excludes /fileSet /fileSets /assembly My repository connections are defined as follows in the pom.xml: (commented out URL). distributionManagement repository idnexuspro-prod-release/id urlhttps://nexuspro.../url /repository snapshotRepository idnexuspro-prod-snapshot/id urlhttps://nexuspro.../url /snapshotRepository /distributionManagement Robert Zanzerkia - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Nexus deployment of a ZIP file...
Yup, this is a surprising repetition, agreed, but that's normal. Please file an enhancement request about that, I guess this might be something fixable. But as deploy-file is supposed to be used quite exceptionnally, I guess not a lot of people complained. Btw, if you use Nexus and that deploy very occasionnally, you might want to use its UI to do that graphically instead. Cheers 2013/3/21 Zanzerkia, Robert robert.zanzer...@fmr.com I found the goal deploy:deploy-file that works to deploy specific file to Nexus. mvn deploy:deploy-file -Durl=$REPO_URL -DrepositoryId=$REPO_ID -DgroupId=org.myorg -DartifactId=myproj -Dversion=1.2.3 -Dpackaging=zip -Dfile=myproj.zip What I don't understand is why do I have to supply url, repositoryID, groupID, artifactID, version on command line if it's already in pom.xml ? Thanks, Robert Zanzerkia Fidelity Investments FTG-OPS Two Contra Way Merrimack, NH 03054 Work: 603-791-3477 Blackberry: 603-320-9682 -Original Message- From: Zanzerkia, Robert Sent: Tuesday, March 19, 2013 12:11 PM To: users@maven.apache.org Subject: Nexus deployment of a ZIP file... Hi, I am trying to deploy a zip file built using Maven to the Nexus repository (internal to our company). When I use mvn deploy it connects to repository and deploys the snapshot except with the default jar file NOT with the zip file I am building as explained below. uCMDB-PatternDev-0.0.1-20130319.143249-1.jar instead of the ZIP I created in target folder : uCMDB-PatternDev-0.0.1-SNAPSHOT-packages.zip I experimented with maven-deploy-plugin which didn't work. Also I rather NOT define file, just want it to copy the output of assembly plugin... Thanks, My project builds a ZIP file using following plugin. (this part works fine). plugin artifactIdmaven-assembly-plugin/artifactId version2.4/version configuration descriptors descriptordistribution.xml/descriptor /descriptors /configuration /plugin Distribution.xml assembly xmlns= http://maven.apache.org/plugins/maven-assembly-plugin/assembly/1.1.2; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation= http://maven.apache.org/plugins/maven-assembly-plugin/assembly/1.1.2 http://maven.apache.org/xsd/assembly-1.1.2.xsd; idpackages/id formats formatzip/format /formats repositories repository outputDirectoryrepository/outputDirectory /repository /repositories fileSets fileSet directory./dist/directory includes include**/include /includes excludes exclude./target/exclude exclude./repository/exclude /excludes /fileSet /fileSets /assembly My repository connections are defined as follows in the pom.xml: (commented out URL). distributionManagement repository idnexuspro-prod-release/id urlhttps://nexuspro.../url /repository snapshotRepository idnexuspro-prod-snapshot/id urlhttps://nexuspro.../url /snapshotRepository /distributionManagement Robert Zanzerkia - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- Baptiste Batmat MATHUS - http://batmat.net Sauvez un arbre, Mangez un castor !
Re: FW: Nexus deployment of a ZIP file...
Hi, I would say this is http://jira.codehaus.org/browse/MDEPLOY But if you have a classical maven build, using deploy-file is actually not the way to go. Just do mvn deploy from the command line, and your artifacts should deploy naturally. Cheers 2013/3/21 Zanzerkia, Robert robert.zanzer...@fmr.com Hi, Can you send me link on how to submit enhancement request? Using GUI is not an option as this is part of our nightly maven build that deploys to Nexus repository. Thanks, Robert Zanzerkia Fidelity Investments FTG-OPS Two Contra Way Merrimack, NH 03054 Work: 603-791-3477 Blackberry: 603-320-9682 -Original Message- From: bmat...@gmail.com [mailto:bmat...@gmail.com] On Behalf Of Baptiste MATHUS Sent: Thursday, March 21, 2013 8:18 AM To: Maven Users List Subject: Re: Nexus deployment of a ZIP file... Yup, this is a surprising repetition, agreed, but that's normal. Please file an enhancement request about that, I guess this might be something fixable. But as deploy-file is supposed to be used quite exceptionnally, I guess not a lot of people complained. Btw, if you use Nexus and that deploy very occasionnally, you might want to use its UI to do that graphically instead. Cheers 2013/3/21 Zanzerkia, Robert robert.zanzer...@fmr.com I found the goal deploy:deploy-file that works to deploy specific file to Nexus. mvn deploy:deploy-file -Durl=$REPO_URL -DrepositoryId=$REPO_ID -DgroupId=org.myorg -DartifactId=myproj -Dversion=1.2.3 -Dpackaging=zip -Dfile=myproj.zip What I don't understand is why do I have to supply url, repositoryID, groupID, artifactID, version on command line if it's already in pom.xml ? Thanks, Robert Zanzerkia Fidelity Investments FTG-OPS Two Contra Way Merrimack, NH 03054 Work: 603-791-3477 Blackberry: 603-320-9682 -Original Message- From: Zanzerkia, Robert Sent: Tuesday, March 19, 2013 12:11 PM To: users@maven.apache.org Subject: Nexus deployment of a ZIP file... Hi, I am trying to deploy a zip file built using Maven to the Nexus repository (internal to our company). When I use mvn deploy it connects to repository and deploys the snapshot except with the default jar file NOT with the zip file I am building as explained below. uCMDB-PatternDev-0.0.1-20130319.143249-1.jar instead of the ZIP I created in target folder : uCMDB-PatternDev-0.0.1-SNAPSHOT-packages.zip I experimented with maven-deploy-plugin which didn't work. Also I rather NOT define file, just want it to copy the output of assembly plugin... Thanks, My project builds a ZIP file using following plugin. (this part works fine). plugin artifactIdmaven-assembly-plugin/artifactId version2.4/version configuration descriptors descriptordistribution.xml/descriptor /descriptors /configuration /plugin Distribution.xml assembly xmlns= http://maven.apache.org/plugins/maven-assembly-plugin/assembly/1.1.2; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation= http://maven.apache.org/plugins/maven-assembly-plugin/assembly/1.1.2 http://maven.apache.org/xsd/assembly-1.1.2.xsd; idpackages/id formats formatzip/format /formats repositories repository outputDirectoryrepository/outputDirectory /repository /repositories fileSets fileSet directory./dist/directory includes include**/include /includes excludes exclude./target/exclude exclude./repository/exclude /excludes /fileSet /fileSets /assembly My repository connections are defined as follows in the pom.xml: (commented out URL). distributionManagement repository idnexuspro-prod-release/id urlhttps://nexuspro.../url /repository snapshotRepository idnexuspro-prod-snapshot/id urlhttps://nexuspro.../url /snapshotRepository /distributionManagement Robert Zanzerkia - To unsubscribe, e-mail: users
Re: Re: Nexus deployment of a ZIP file...
Hi, Yup, this is a surprising repetition, agreed, but that's normal. Please file an enhancement request about that, I guess this might be something fixable. I haven't used deploy:deploy-file from the command line for a longer time, but can't you omit groupId, artifactId etc. when you specify a pom.xml as a parameter (-DpomFile=)? See https://maven.apache.org/plugins/maven-deploy-plugin/deploy-file-mojo.html HTH Thorsten
RE: FW: Nexus deployment of a ZIP file...
You're right I would have preferred to use just deploy but I ran into problem. I am using maven-assembly-plugin which creates my zip file. I could not figure out how to deploy that zip file to Nexus right from assembly. Thanks, Robert Zanzerkia Fidelity Investments FTG-OPS Two Contra Way Merrimack, NH 03054 Work: 603-791-3477 Blackberry: 603-320-9682 -Original Message- From: bmat...@gmail.com [mailto:bmat...@gmail.com] On Behalf Of Baptiste MATHUS Sent: Thursday, March 21, 2013 9:01 AM To: Maven Users List Subject: Re: FW: Nexus deployment of a ZIP file... Hi, I would say this is http://jira.codehaus.org/browse/MDEPLOY But if you have a classical maven build, using deploy-file is actually not the way to go. Just do mvn deploy from the command line, and your artifacts should deploy naturally. Cheers 2013/3/21 Zanzerkia, Robert robert.zanzer...@fmr.com Hi, Can you send me link on how to submit enhancement request? Using GUI is not an option as this is part of our nightly maven build that deploys to Nexus repository. Thanks, Robert Zanzerkia Fidelity Investments FTG-OPS Two Contra Way Merrimack, NH 03054 Work: 603-791-3477 Blackberry: 603-320-9682 -Original Message- From: bmat...@gmail.com [mailto:bmat...@gmail.com] On Behalf Of Baptiste MATHUS Sent: Thursday, March 21, 2013 8:18 AM To: Maven Users List Subject: Re: Nexus deployment of a ZIP file... Yup, this is a surprising repetition, agreed, but that's normal. Please file an enhancement request about that, I guess this might be something fixable. But as deploy-file is supposed to be used quite exceptionnally, I guess not a lot of people complained. Btw, if you use Nexus and that deploy very occasionnally, you might want to use its UI to do that graphically instead. Cheers 2013/3/21 Zanzerkia, Robert robert.zanzer...@fmr.com I found the goal deploy:deploy-file that works to deploy specific file to Nexus. mvn deploy:deploy-file -Durl=$REPO_URL -DrepositoryId=$REPO_ID -DgroupId=org.myorg -DartifactId=myproj -Dversion=1.2.3 -Dpackaging=zip -Dfile=myproj.zip What I don't understand is why do I have to supply url, repositoryID, groupID, artifactID, version on command line if it's already in pom.xml ? Thanks, Robert Zanzerkia Fidelity Investments FTG-OPS Two Contra Way Merrimack, NH 03054 Work: 603-791-3477 Blackberry: 603-320-9682 -Original Message- From: Zanzerkia, Robert Sent: Tuesday, March 19, 2013 12:11 PM To: users@maven.apache.org Subject: Nexus deployment of a ZIP file... Hi, I am trying to deploy a zip file built using Maven to the Nexus repository (internal to our company). When I use mvn deploy it connects to repository and deploys the snapshot except with the default jar file NOT with the zip file I am building as explained below. uCMDB-PatternDev-0.0.1-20130319.143249-1.jar instead of the ZIP I created in target folder : uCMDB-PatternDev-0.0.1-SNAPSHOT-packages.zip I experimented with maven-deploy-plugin which didn't work. Also I rather NOT define file, just want it to copy the output of assembly plugin... Thanks, My project builds a ZIP file using following plugin. (this part works fine). plugin artifactIdmaven-assembly-plugin/artifactId version2.4/version configuration descriptors descriptordistribution.xml/descriptor /descriptors /configuration /plugin Distribution.xml assembly xmlns= http://maven.apache.org/plugins/maven-assembly-plugin/assembly/1.1.2; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation= http://maven.apache.org/plugins/maven-assembly-plugin/assembly/1.1.2 http://maven.apache.org/xsd/assembly-1.1.2.xsd; idpackages/id formats formatzip/format /formats repositories repository outputDirectoryrepository/outputDirectory /repository /repositories fileSets fileSet directory./dist/directory includes include**/include /includes excludes exclude./target/exclude exclude./repository/exclude /excludes /fileSet /fileSets /assembly My repository connections are defined as follows
RE: Re: Nexus deployment of a ZIP file...
Yes, I tried the -DpomFile approach but if I don't supply groupID,version etc. it still complained. Robert Zanzerkia Fidelity Investments FTG-OPS Two Contra Way Merrimack, NH 03054 Work: 603-791-3477 Blackberry: 603-320-9682 -Original Message- From: thorsten.h...@vkb.de [mailto:thorsten.h...@vkb.de] Sent: Thursday, March 21, 2013 9:16 AM To: Maven Users List Subject: Re: Re: Nexus deployment of a ZIP file... Hi, Yup, this is a surprising repetition, agreed, but that's normal. Please file an enhancement request about that, I guess this might be something fixable. I haven't used deploy:deploy-file from the command line for a longer time, but can't you omit groupId, artifactId etc. when you specify a pom.xml as a parameter (-DpomFile=)? See https://maven.apache.org/plugins/maven-deploy-plugin/deploy-file-mojo.html HTH Thorsten - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: FW: Nexus deployment of a ZIP file...
One simple way to go is to have a module dedicated to that assembly. Then just mvn deploy it (or even simpler inside the whole multimodule build). Cheers
RE: FW: Nexus deployment of a ZIP file...
Created JIRA improvement request. http://jira.codehaus.org/browse/MDEPLOY-159 Robert Zanzerkia Fidelity Investments FTG-OPS Two Contra Way Merrimack, NH 03054 Work: 603-791-3477 Blackberry: 603-320-9682 -Original Message- From: bmat...@gmail.com [mailto:bmat...@gmail.com] On Behalf Of Baptiste MATHUS Sent: Thursday, March 21, 2013 9:01 AM To: Maven Users List Subject: Re: FW: Nexus deployment of a ZIP file... Hi, I would say this is http://jira.codehaus.org/browse/MDEPLOY But if you have a classical maven build, using deploy-file is actually not the way to go. Just do mvn deploy from the command line, and your artifacts should deploy naturally. Cheers 2013/3/21 Zanzerkia, Robert robert.zanzer...@fmr.com Hi, Can you send me link on how to submit enhancement request? Using GUI is not an option as this is part of our nightly maven build that deploys to Nexus repository. Thanks, Robert Zanzerkia Fidelity Investments FTG-OPS Two Contra Way Merrimack, NH 03054 Work: 603-791-3477 Blackberry: 603-320-9682 -Original Message- From: bmat...@gmail.com [mailto:bmat...@gmail.com] On Behalf Of Baptiste MATHUS Sent: Thursday, March 21, 2013 8:18 AM To: Maven Users List Subject: Re: Nexus deployment of a ZIP file... Yup, this is a surprising repetition, agreed, but that's normal. Please file an enhancement request about that, I guess this might be something fixable. But as deploy-file is supposed to be used quite exceptionnally, I guess not a lot of people complained. Btw, if you use Nexus and that deploy very occasionnally, you might want to use its UI to do that graphically instead. Cheers 2013/3/21 Zanzerkia, Robert robert.zanzer...@fmr.com I found the goal deploy:deploy-file that works to deploy specific file to Nexus. mvn deploy:deploy-file -Durl=$REPO_URL -DrepositoryId=$REPO_ID -DgroupId=org.myorg -DartifactId=myproj -Dversion=1.2.3 -Dpackaging=zip -Dfile=myproj.zip What I don't understand is why do I have to supply url, repositoryID, groupID, artifactID, version on command line if it's already in pom.xml ? Thanks, Robert Zanzerkia Fidelity Investments FTG-OPS Two Contra Way Merrimack, NH 03054 Work: 603-791-3477 Blackberry: 603-320-9682 -Original Message- From: Zanzerkia, Robert Sent: Tuesday, March 19, 2013 12:11 PM To: users@maven.apache.org Subject: Nexus deployment of a ZIP file... Hi, I am trying to deploy a zip file built using Maven to the Nexus repository (internal to our company). When I use mvn deploy it connects to repository and deploys the snapshot except with the default jar file NOT with the zip file I am building as explained below. uCMDB-PatternDev-0.0.1-20130319.143249-1.jar instead of the ZIP I created in target folder : uCMDB-PatternDev-0.0.1-SNAPSHOT-packages.zip I experimented with maven-deploy-plugin which didn't work. Also I rather NOT define file, just want it to copy the output of assembly plugin... Thanks, My project builds a ZIP file using following plugin. (this part works fine). plugin artifactIdmaven-assembly-plugin/artifactId version2.4/version configuration descriptors descriptordistribution.xml/descriptor /descriptors /configuration /plugin Distribution.xml assembly xmlns= http://maven.apache.org/plugins/maven-assembly-plugin/assembly/1.1.2; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation= http://maven.apache.org/plugins/maven-assembly-plugin/assembly/1.1.2 http://maven.apache.org/xsd/assembly-1.1.2.xsd; idpackages/id formats formatzip/format /formats repositories repository outputDirectoryrepository/outputDirectory /repository /repositories fileSets fileSet directory./dist/directory includes include**/include /includes excludes exclude./target/exclude exclude./repository/exclude /excludes /fileSet /fileSets /assembly My repository connections are defined as follows in the pom.xml: (commented out URL). distributionManagement repository idnexuspro-prod-release/id
RE: FW: Nexus deployment of a ZIP file...
Hi, I have one plug-in that creates the zip file. How do I change it to do deploy stage? Normally I do mvn assembly:assembly deploy:deploy-file plugin artifactIdmaven-assembly-plugin/artifactId version2.4/version configuration descriptors descriptordistribution.xml/descriptor /descriptors /configuration /plugin Here is the distribution.xml assembly xmlns=http://maven.apache.org/plugins/maven-assembly-plugin/assembly/1.1.2; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=http://maven.apache.org/plugins/maven-assembly-plugin/assembly/1.1.2 http://maven.apache.org/xsd/assembly-1.1.2.xsd; idpackages/id formats formatzip/format /formats fileSets fileSet directory./dist/directory includes include**/include /includes excludes exclude./target/exclude exclude./repository/exclude /excludes /fileSet /fileSets /assembly Thanks, Robert -Original Message- From: bmat...@gmail.com [mailto:bmat...@gmail.com] On Behalf Of Baptiste MATHUS Sent: Thursday, March 21, 2013 9:40 AM To: Maven Users List Subject: Re: FW: Nexus deployment of a ZIP file... One simple way to go is to have a module dedicated to that assembly. Then just mvn deploy it (or even simpler inside the whole multimodule build). Cheers - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: FW: Nexus deployment of a ZIP file...
well a simpler way would be to bind an execution of the assembply plugin to the lifecycle (probably at the package phase) and then you would just go mvn deploy which will invoke all the plugins bound to phases on or before the deploy phase. IIRC assembly:single the the preferred goal when binding to the lifecycle, so you would just add executions execution idsome-id/id phasepackage/phase goalsgoalsingle/goal/goals /execution /executions to the plugin section for the assembly plugin On 21 March 2013 14:00, Zanzerkia, Robert robert.zanzer...@fmr.com wrote: Hi, I have one plug-in that creates the zip file. How do I change it to do deploy stage? Normally I do mvn assembly:assembly deploy:deploy-file plugin artifactIdmaven-assembly-plugin/artifactId version2.4/version configuration descriptors descriptordistribution.xml/descriptor /descriptors /configuration /plugin Here is the distribution.xml assembly xmlns= http://maven.apache.org/plugins/maven-assembly-plugin/assembly/1.1.2; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation= http://maven.apache.org/plugins/maven-assembly-plugin/assembly/1.1.2 http://maven.apache.org/xsd/assembly-1.1.2.xsd; idpackages/id formats formatzip/format /formats fileSets fileSet directory./dist/directory includes include**/include /includes excludes exclude./target/exclude exclude./repository/exclude /excludes /fileSet /fileSets /assembly Thanks, Robert -Original Message- From: bmat...@gmail.com [mailto:bmat...@gmail.com] On Behalf Of Baptiste MATHUS Sent: Thursday, March 21, 2013 9:40 AM To: Maven Users List Subject: Re: FW: Nexus deployment of a ZIP file... One simple way to go is to have a module dedicated to that assembly. Then just mvn deploy it (or even simpler inside the whole multimodule build). Cheers - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: FW: Nexus deployment of a ZIP file...
Oh and if you want the assembly to be the primary artifact without a classifier, you need to read http://maven.apache.org/plugins/maven-assembly-plugin/faq.html#required-classifiers On 21 March 2013 14:05, Stephen Connolly stephen.alan.conno...@gmail.comwrote: well a simpler way would be to bind an execution of the assembply plugin to the lifecycle (probably at the package phase) and then you would just go mvn deploy which will invoke all the plugins bound to phases on or before the deploy phase. IIRC assembly:single the the preferred goal when binding to the lifecycle, so you would just add executions execution idsome-id/id phasepackage/phase goalsgoalsingle/goal/goals /execution /executions to the plugin section for the assembly plugin On 21 March 2013 14:00, Zanzerkia, Robert robert.zanzer...@fmr.comwrote: Hi, I have one plug-in that creates the zip file. How do I change it to do deploy stage? Normally I do mvn assembly:assembly deploy:deploy-file plugin artifactIdmaven-assembly-plugin/artifactId version2.4/version configuration descriptors descriptordistribution.xml/descriptor /descriptors /configuration /plugin Here is the distribution.xml assembly xmlns= http://maven.apache.org/plugins/maven-assembly-plugin/assembly/1.1.2; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation= http://maven.apache.org/plugins/maven-assembly-plugin/assembly/1.1.2 http://maven.apache.org/xsd/assembly-1.1.2.xsd; idpackages/id formats formatzip/format /formats fileSets fileSet directory./dist/directory includes include**/include /includes excludes exclude./target/exclude exclude./repository/exclude /excludes /fileSet /fileSets /assembly Thanks, Robert -Original Message- From: bmat...@gmail.com [mailto:bmat...@gmail.com] On Behalf Of Baptiste MATHUS Sent: Thursday, March 21, 2013 9:40 AM To: Maven Users List Subject: Re: FW: Nexus deployment of a ZIP file... One simple way to go is to have a module dedicated to that assembly. Then just mvn deploy it (or even simpler inside the whole multimodule build). Cheers - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
RE: FW: Nexus deployment of a ZIP file...
Stephen, Thank you for answering the question and sending below information. I changed my POM.xml (See attached). When I use the command: mvn antrun:run assembly:single deploy (I have external ant command to do other things before creating the zip file). I get below error. [ERROR] Failed to execute goal org.apache.maven.plugins:maven-assembly-plugin:2. 4:assembly (default-cli) on project uCMDB-PatternDev: Error reading assemblies: No assembly descriptors found. - [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e swit ch. [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 rea d the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionEXception However if I do mvn deploy it deploys the jar file... Thanks, Robert PS: I read the classifiers faq and added following to assembly execution configuration. appendAssemblyIdfalse/appendAssemblyId -Original Message- From: Stephen Connolly [mailto:stephen.alan.conno...@gmail.com] Sent: Thursday, March 21, 2013 10:10 AM To: Maven Users List Subject: Re: FW: Nexus deployment of a ZIP file... Oh and if you want the assembly to be the primary artifact without a classifier, you need to read http://maven.apache.org/plugins/maven-assembly-plugin/faq.html#required-classifiers On 21 March 2013 14:05, Stephen Connolly stephen.alan.conno...@gmail.comwrote: well a simpler way would be to bind an execution of the assembply plugin to the lifecycle (probably at the package phase) and then you would just go mvn deploy which will invoke all the plugins bound to phases on or before the deploy phase. IIRC assembly:single the the preferred goal when binding to the lifecycle, so you would just add executions execution idsome-id/id phasepackage/phase goalsgoalsingle/goal/goals /execution /executions to the plugin section for the assembly plugin On 21 March 2013 14:00, Zanzerkia, Robert robert.zanzer...@fmr.comwrote: Hi, I have one plug-in that creates the zip file. How do I change it to do deploy stage? Normally I do mvn assembly:assembly deploy:deploy-file plugin artifactIdmaven-assembly-plugin/artifactId version2.4/version configuration descriptors descriptordistribution.xml/descriptor /descriptors /configuration /plugin Here is the distribution.xml assembly xmlns= http://maven.apache.org/plugins/maven-assembly-plugin/assembly/1.1.2; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation= http://maven.apache.org/plugins/maven-assembly-plugin/assembly/1.1.2 http://maven.apache.org/xsd/assembly-1.1.2.xsd; idpackages/id formats formatzip/format /formats fileSets fileSet directory./dist/directory includes include**/include /includes excludes exclude./target/exclude exclude./repository/exclude /excludes /fileSet /fileSets /assembly Thanks, Robert -Original Message- From: bmat...@gmail.com [mailto:bmat...@gmail.com] On Behalf Of Baptiste MATHUS Sent: Thursday, March 21, 2013 9:40 AM To: Maven Users List Subject: Re: FW: Nexus deployment of a ZIP file... One simple way to go is to have a module dedicated to that assembly. Then just mvn deploy it (or even simpler inside the whole multimodule build). Cheers - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org project xmlns=http://maven.apache.org/POM/4.0.0; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd; modelVersion4.0.0/modelVersion groupIdcom.fmr.itamdiscovery/groupId artifactIduCMDB-PatternDev/artifactId version0.0.1-SNAPSHOT/version nameuCMDBPatternDEV/name descriptionBuild of uCMDB Packages. (ZIP files of folders)./description distributionManagement repository idnexuspro-prod-release/id url/url /repository snapshotRepository idnexuspro-prod-snapshot/id url/url /snapshotRepository /distributionManagement build pluginManagement
Re: FW: Nexus deployment of a ZIP file...
yeah you probably want to bind antrun:run to the lifecycle before the package phase then On 21 March 2013 14:45, Zanzerkia, Robert robert.zanzer...@fmr.com wrote: Stephen, Thank you for answering the question and sending below information. I changed my POM.xml (See attached). When I use the command: mvn antrun:run assembly:single deploy (I have external ant command to do other things before creating the zip file). I get below error. [ERROR] Failed to execute goal org.apache.maven.plugins:maven-assembly-plugin:2. 4:assembly (default-cli) on project uCMDB-PatternDev: Error reading assemblies: No assembly descriptors found. - [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e swit ch. [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 rea d the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionEXception However if I do mvn deploy it deploys the jar file... Thanks, Robert PS: I read the classifiers faq and added following to assembly execution configuration. appendAssemblyIdfalse/appendAssemblyId -Original Message- From: Stephen Connolly [mailto:stephen.alan.conno...@gmail.com] Sent: Thursday, March 21, 2013 10:10 AM To: Maven Users List Subject: Re: FW: Nexus deployment of a ZIP file... Oh and if you want the assembly to be the primary artifact without a classifier, you need to read http://maven.apache.org/plugins/maven-assembly-plugin/faq.html#required-classifiers On 21 March 2013 14:05, Stephen Connolly stephen.alan.conno...@gmail.com wrote: well a simpler way would be to bind an execution of the assembply plugin to the lifecycle (probably at the package phase) and then you would just go mvn deploy which will invoke all the plugins bound to phases on or before the deploy phase. IIRC assembly:single the the preferred goal when binding to the lifecycle, so you would just add executions execution idsome-id/id phasepackage/phase goalsgoalsingle/goal/goals /execution /executions to the plugin section for the assembly plugin On 21 March 2013 14:00, Zanzerkia, Robert robert.zanzer...@fmr.com wrote: Hi, I have one plug-in that creates the zip file. How do I change it to do deploy stage? Normally I do mvn assembly:assembly deploy:deploy-file plugin artifactIdmaven-assembly-plugin/artifactId version2.4/version configuration descriptors descriptordistribution.xml/descriptor /descriptors /configuration /plugin Here is the distribution.xml assembly xmlns= http://maven.apache.org/plugins/maven-assembly-plugin/assembly/1.1.2; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation= http://maven.apache.org/plugins/maven-assembly-plugin/assembly/1.1.2 http://maven.apache.org/xsd/assembly-1.1.2.xsd; idpackages/id formats formatzip/format /formats fileSets fileSet directory./dist/directory includes include**/include /includes excludes exclude./target/exclude exclude./repository/exclude /excludes /fileSet /fileSets /assembly Thanks, Robert -Original Message- From: bmat...@gmail.com [mailto:bmat...@gmail.com] On Behalf Of Baptiste MATHUS Sent: Thursday, March 21, 2013 9:40 AM To: Maven Users List Subject: Re: FW: Nexus deployment of a ZIP file... One simple way to go is to have a module dedicated to that assembly. Then just mvn deploy it (or even simpler inside the whole multimodule build). Cheers - 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: FW: Nexus deployment of a ZIP file...
Stephen,
That solved my problem.
I also had to make sure that id for both plug-in matched.
Also I tried to change id from 'default-cli' to something else and it
didn't work.
After below changes this command worked. It created zip file and
deployed to Nexus without having to use deploy:deploy-file...
mvn antrun:run assembly:single deploy
Here's the POM that worked.
build
pluginManagement
plugins
plugin
artifactIdmaven-assembly-plugin/artifactId
version2.4/version
executions
execution
iddefault-cli/id
phasepackage/phase
goals
goalsingle/goal
/goals
configuration
descriptors
descriptordistribution.xml/descriptor
/descriptors
appendAssemblyIdfalse/appendAssemblyId
/configuration
/execution
/executions
/plugin
plugin
artifactIdmaven-antrun-plugin/artifactId
version1.7/version
executions
execution
iddefault-ci/id
phasecompile/phase
configuration
target
ant
antfile=${project.build.directory}/../maven-build.xml
target name=zip-all-packages /
/ant
/target
/configuration
goals
goalrun/goal
/goals
/execution
/executions
dependencies
dependency
groupIdant-contrib/groupId
artifactIdant-contrib/artifactId
version1.0b3/version
exclusions
exclusion
groupIdant/groupId
artifactIdant/artifactId
/exclusion
/exclusions
/dependency
dependency
groupIdorg.apache.ant/groupId
artifactIdant-nodeps/artifactId
version1.8.1/version
/dependency
/dependencies
/plugin
/plugins
/pluginManagement
/build
Thanks,
-Original Message-
From: Stephen Connolly [mailto:stephen.alan.conno...@gmail.com]
Sent: Thursday, March 21, 2013 11:04 AM
To: Maven Users List
Subject: Re: FW: Nexus deployment of a ZIP file...
yeah you probably want to bind antrun:run to the lifecycle before the
package phase then
On 21 March 2013 14:45, Zanzerkia, Robert robert.zanzer...@fmr.com wrote:
Stephen
Re: Nexus deployment of a ZIP file...
Glad to help. Could probably tidy up that pom but I burned up all my free
time this week writing plugins and blog posts, so you'd need to ask others
if you want to trim it back to lean and no fat ;-)
On Thursday, 21 March 2013, Zanzerkia, Robert wrote:
Stephen,
That solved my problem.
I also had to make sure that id for both plug-in matched.
Also I tried to change id from 'default-cli' to something else and
it didn't work.
After below changes this command worked. It created zip file and
deployed to Nexus without having to use deploy:deploy-file...
mvn antrun:run assembly:single deploy
Here's the POM that worked.
build
pluginManagement
plugins
plugin
artifactIdmaven-assembly-plugin/artifactId
version2.4/version
executions
execution
iddefault-cli/id
phasepackage/phase
goals
goalsingle/goal
/goals
configuration
descriptors
descriptordistribution.xml/descriptor
/descriptors
appendAssemblyIdfalse/appendAssemblyId
/configuration
/execution
/executions
/plugin
plugin
artifactIdmaven-antrun-plugin/artifactId
version1.7/version
executions
execution
iddefault-ci/id
phasecompile/phase
configuration
target
ant antfile=${project.build.directory}/../maven-build.xml
target name=zip-all-packages /
/ant
/target
/configuration
goals
goalrun/goal
/goals
/execution
/executions
dependencies
dependency
groupIdant-contrib/groupId
artifactIdant-contrib/artifactId
version1.0b3/version
exclusions
exclusion
groupIdant/groupId
artifactIdant/artifactId
/exclusion
/exclusions
/dependency
dependency
groupIdorg.apache.ant/groupId
artifactIdant-nodeps/artifactId
version1.8.1/version
/dependency
/dependencies
/plugin
/plugins
/pluginManagement
/build
Thanks,
-Original Message-
From: Stephen Connolly [mailto:stephen.alan.conno...@gmail.comjavascript:;
]
Sent: Thursday, March 21, 2013 11:04 AM
To: Maven Users List
Subject: Re: FW: Nexus deployment of a ZIP file...
yeah you probably want to bind antrun:run to the lifecycle before the
package phase then
On 21 March 2013 14:45, Zanzerkia, Robert robert.zanzer...@fmr.com
wrote:
Stephen,
Thank you for answering the question and sending below
information.
I changed my POM.xml (See attached).
When I use the command:
mvn antrun:run assembly:single deploy
(I have external ant command to do other things before creating
the zip file).
I get below error.
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-assembly-plugin:2.
4:assembly (default-cli) on project uCMDB-PatternDev: Error reading
assemblies:
No assembly descriptors found. - [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the
-e swit
ch.
[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 rea
d the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionEXception
However if I do mvn deploy it deploys the jar file...
Thanks,
Robert
PS: I read
Re: FW: Nexus deployment of a ZIP file...
mvn antrun:run assembly:single deploy Here's the POM that worked. If you are happy with things, then there is nothing more to do! But if you want to further reduce your typing at the command line then you could: 1. change id of default-cli in assembly plugin to something else 2. change id of default-cli in antrun plugin to something else 3. move those plugin declarations out of pluginManagement and into build/plugins directly 4. just run mvn deploy from command line and poof, it should all work as it already does without mentioning the assembly plugin or antrun plugin on the command line at all Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
RE: FW: Nexus deployment of a ZIP file...
Hi Wayne,
Thank you for that hint.
I have a lot to learn about maven :-) (what difference does it make
when plugin is inside pluginManagement vs. outside).
I was able to change id also.
Now my command is very simple (I like it).
mvn deploy
Thanks,
Robert
New POM:
build
plugins
plugin
artifactIdmaven-assembly-plugin/artifactId
version2.4/version
executions
execution
iditamdiscovery-package/id
phasepackage/phase
goals
goalsingle/goal
/goals
configuration
descriptors
descriptordistribution.xml/descriptor
/descriptors
appendAssemblyIdfalse/appendAssemblyId
/configuration
/execution
/executions
/plugin
plugin
artifactIdmaven-antrun-plugin/artifactId
version1.7/version
executions
execution
iditamdiscovery-package/id
phasecompile/phase
configuration
target
ant
antfile=${project.build.directory}/../maven-build.xml
target
name=zip-all-packages /
/ant
/target
/configuration
goals
goalrun/goal
/goals
/execution
/executions
dependencies
dependency
groupIdant-contrib/groupId
artifactIdant-contrib/artifactId
version1.0b3/version
exclusions
exclusion
groupIdant/groupId
artifactIdant/artifactId
/exclusion
/exclusions
/dependency
dependency
groupIdorg.apache.ant/groupId
artifactIdant-nodeps/artifactId
version1.8.1/version
/dependency
/dependencies
/plugin
/plugins
/build
-Original Message-
From: Wayne Fay [mailto:wayne...@gmail.com]
Sent: Thursday, March 21, 2013 3:31 PM
To: Maven Users List
Subject: Re: FW: Nexus deployment of a ZIP file...
mvn antrun:run assembly:single deploy
Here's the POM that worked.
If you are happy with things, then there is nothing more to do!
But if you want to further reduce your typing at the command line then
you could:
1. change id of default-cli in assembly plugin to something else
2. change id of default-cli in antrun plugin to something else
3. move those plugin declarations out of pluginManagement and into
build/plugins directly
4. just run mvn deploy from command line and poof, it should all
work as it already does without mentioning the assembly plugin or
antrun plugin on the command line at all
Wayne
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: FW: Nexus deployment of a ZIP file...
I have a lot to learn about maven :-) (what difference does it make when plugin is inside pluginManagement vs. outside). From Maven documentation: pluginManagement: is an element that is seen along side plugins. Plugin Management contains plugin elements in much the same way, except that rather than configuring plugin information for this particular project build, it is intended to configure project builds that inherit from this one. However, this only configures plugins that are actually referenced within the plugins element in the children. The children have every right to override pluginManagement definitions. More info here on SO: http://stackoverflow.com/questions/10483180/maven-what-is-pluginmanagement And of course, more info on the Maven website and in various documentation, ebooks, blog posts, etc. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Nexus deployment of a ZIP file...
Hi, I am trying to deploy a zip file built using Maven to the Nexus repository (internal to our company). When I use mvn deploy it connects to repository and deploys the snapshot except with the default jar file NOT with the zip file I am building as explained below. uCMDB-PatternDev-0.0.1-20130319.143249-1.jar instead of the ZIP I created in target folder : uCMDB-PatternDev-0.0.1-SNAPSHOT-packages.zip I experimented with maven-deploy-plugin which didn't work. Also I rather NOT define file, just want it to copy the output of assembly plugin... Thanks, My project builds a ZIP file using following plugin. (this part works fine). plugin artifactIdmaven-assembly-plugin/artifactId version2.4/version configuration descriptors descriptordistribution.xml/descriptor /descriptors /configuration /plugin Distribution.xml assembly xmlns=http://maven.apache.org/plugins/maven-assembly-plugin/assembly/1.1.2; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=http://maven.apache.org/plugins/maven-assembly-plugin/assembly/1.1.2 http://maven.apache.org/xsd/assembly-1.1.2.xsd; idpackages/id formats formatzip/format /formats repositories repository outputDirectoryrepository/outputDirectory /repository /repositories fileSets fileSet directory./dist/directory includes include**/include /includes excludes exclude./target/exclude exclude./repository/exclude /excludes /fileSet /fileSets /assembly My repository connections are defined as follows in the pom.xml: (commented out URL). distributionManagement repository idnexuspro-prod-release/id urlhttps://nexuspro.../url /repository snapshotRepository idnexuspro-prod-snapshot/id urlhttps://nexuspro.../url /snapshotRepository /distributionManagement Robert Zanzerkia
Re: Nexus deployment of a ZIP file...
Zanzerkia, Robert robert.zanzer...@fmr.com wrote on 03/19/2013 12:10:33 PM: From: Zanzerkia, Robert robert.zanzer...@fmr.com To: users@maven.apache.org users@maven.apache.org, Date: 03/19/2013 12:12 PM Subject: Nexus deployment of a ZIP file... Hi, I am trying to deploy a zip file built using Maven to the Nexus repository (internal to our company). When I use mvn deploy it connects to repository and deploys the snapshot except with the default jar file NOT with the zip file I am building as explained below. The assemby plugin has an option (attach) to deploy generated assemblies with classifiers.
RE: Nexus deployment of a ZIP file...
Hi there, Your missing phases and goals. Below should get you closer. More information can be found here: http://maven.apache.org/plugins/maven-assembly-plugin/usage.html -Jim plugin artifactIdmaven-assembly-plugin/artifactId version2.4/version executions execution phasepackage/phase goals goalsingle/goal /goals configuration descriptors descriptordistribution.xml/descriptor /descriptors /configuration /execution /executions /plugin -Original Message- From: Zanzerkia, Robert [mailto:robert.zanzer...@fmr.com] Sent: Tuesday, March 19, 2013 11:11 AM To: users@maven.apache.org Subject: Nexus deployment of a ZIP file... Hi, I am trying to deploy a zip file built using Maven to the Nexus repository (internal to our company). When I use mvn deploy it connects to repository and deploys the snapshot except with the default jar file NOT with the zip file I am building as explained below. uCMDB-PatternDev-0.0.1-20130319.143249-1.jar instead of the ZIP I created in target folder : uCMDB-PatternDev-0.0.1-SNAPSHOT-packages.zip I experimented with maven-deploy-plugin which didn't work. Also I rather NOT define file, just want it to copy the output of assembly plugin... Thanks, My project builds a ZIP file using following plugin. (this part works fine). plugin artifactIdmaven-assembly-plugin/artifactId version2.4/version configuration descriptors descriptordistribution.xml/descriptor /descriptors /configuration /plugin Distribution.xml assembly xmlns=http://maven.apache.org/plugins/maven-assembly-plugin/assembly/1.1.2; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=http://maven.apache.org/plugins/maven-assembly-plugin/assembly/1.1.2 http://maven.apache.org/xsd/assembly-1.1.2.xsd; idpackages/id formats formatzip/format /formats repositories repository outputDirectoryrepository/outputDirectory /repository /repositories fileSets fileSet directory./dist/directory includes include**/include /includes excludes exclude./target/exclude exclude./repository/exclude /excludes /fileSet /fileSets /assembly My repository connections are defined as follows in the pom.xml: (commented out URL). distributionManagement repository idnexuspro-prod-release/id urlhttps://nexuspro.../url /repository snapshotRepository idnexuspro-prod-snapshot/id urlhttps://nexuspro.../url /snapshotRepository /distributionManagement Robert Zanzerkia NOTICE: All information in and attached to this email may be proprietary, confidential, privileged and otherwise protected from improper or erroneous disclosure. If you are not the sender's intended recipient, you are not authorized to intercept, read, print, retain, copy, forward, or disseminate this message. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
