[ANN] Apache Maven Deploy Plugin 3.1.2 Released
The Apache Maven team is pleased to announce the release of the Apache Maven Deploy Plugin, version 3.1.2 https://maven.apache.org/plugins/maven-deploy-plugin/ You should specify the version in your project's plugin configuration: org.apache.maven.plugins maven-deploy-plugin 3.1.2 You can download the appropriate sources etc. from the download page: https://maven.apache.org/plugins/maven-deploy-plugin/download.cgi Release Notes - Maven Deploy Plugin - Version 3.1.2 ** Improvement * [MDEPLOY-313] - Upgrade maven-plugin parent to 41 * [MDEPLOY-314] - Include artifactId in messages of DeployMojo#processProject ** Dependency upgrade * [MDEPLOY-316] - Update parent to 42, up prerequisite to 3.6.3 Have fun, -The Apache Maven team
[ANN] Maven Deploy Plugin 3.1.1 released
The Apache Maven team is pleased to announce the release of the Maven Deploy Plugin 3.1.1 https://maven.apache.org/plugins/maven-deploy-plugin/ Release Notes - Maven Deploy Plugin - Version 3.1.1 ** Improvement * [MDEPLOY-308] - Add parameter to lax project validation Have fun! -The Apache Maven team
[ANN] Maven Deploy Plugin 3.1.0 released
The Apache Maven team is pleased to announce the release of the Maven Deploy Plugin 3.1.0! https://maven.apache.org/plugins/maven-deploy-plugin/ You should specify the version in your project's POM: org.apache.maven.plugins maven-deploy-plugin 3.1.0 Release Notes - Maven Deploy Plugin - Version 3.1.0 ** Bug * [MDEPLOY-200] - deployAtEnd fails if the last project to build skip deployment * [MDEPLOY-204] - Must deploy maven-metadata.xml last * [MDEPLOY-224] - Overriding deployAtEnd fails * [MDEPLOY-225] - DeployAtEnd fails when overriding skip * [MDEPLOY-226] - DeployAtEnd fails when module has extension * [MDEPLOY-305] - Improvement in DeployAtEnd ** New Feature * [MDEPLOY-206] - Support parallel deployment at end (needs resolver changes as well) * [MDEPLOY-272] - Add skip capability to deploy-file goal ** Task * [MDEPLOY-282] - Revert MDEPLOY-231 * [MDEPLOY-292] - Require Java 8 * [MDEPLOY-303] - Refresh download page * [MDEPLOY-304] - Clean up ITs Have fun, -The Apache Maven team
[ANN] Maven Deploy Plugin 3.0.0 Released
Howdy, The Apache Maven team is pleased to announce the release of Maven Deploy Plugin 3.0.0. Plugin is Java7 level and compatible with Maven 3.2.5+ Site: https://maven.apache.org/plugins/maven-deploy-plugin/ Release Notes - Maven Deploy Plugin - Version 3.0.0 ** Bug * [MDEPLOY-193] - deployAtEnd does not deploy artifacts for multi-module project with build extensions ** Task * [MDEPLOY-291] - Update POM parent and Maven * [MDEPLOY-296] - Cleanup the plugin Have fun - The Apache Maven Team
[ANN] Maven Deploy Plugin 3.0.0-M2 released
The Apache Maven team is pleased to announce the release of the Maven Deploy Plugin version 3.0.0-M2. https://maven.apache.org/plugins/maven-deploy-plugin/ You should specify the version in your project's plugin configuration: org.apache.maven.plugins maven-deploy-plugin 3.0.0-M2 Release Notes - Maven Deploy Plugin - Version 3.0.0-M2 ** Bug * [MDEPLOY-244] - maven deploy plugin 3.0.0-M1 breaks deploys when alt*DeploymentRepository properties are used * [MDEPLOY-247] - Version 3.0.0-M1 breaks deploy using alt*DeploymentRepository with old syntax on Windows * [MDEPLOY-249] - fix altDeploymentRepository format documentation: no more layout * [MDEPLOY-279] - Missing validation of altDeploymentRepository mojo parameter ** New Feature * [MDEPLOY-267] - add parameters to deploy or not non snapshots or release (-DskipRelease or -DskipSnapshot) ** Improvement * [MDEPLOY-263] - Add .asf.yaml * [MDEPLOY-265] - Allow old alt*DeploymentRepository property format if default layout is used * [MDEPLOY-269] - Make build Reproducible ** Task * [MDEPLOY-243] - Remove JIRA report from generated site * [MDEPLOY-245] - Remove the updateReleaseInfo parameter's leftovers * [MDEPLOY-250] - add documentation on managing network issues ** Dependency upgrade * [MDEPLOY-248] - Update maven-artifact-transfer from 0.10.0 to 0.11.0 * [MDEPLOY-253] - Upgrade plexus-utils to 3.2.0 * [MDEPLOY-264] - Upgrade Maven Artifact Transfer to 0.13.1 * [MDEPLOY-268] - Upgrade maven-plugin-parent to version 34 Enjoy, -The Apache Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven 3.8.1 + maven-deploy-plugin 3.0.0-M1 and still no SHA256/SHA512
Am 2021-04-30 um 07:29 schrieb David Milet: I figured it out... With Maven 3.8.1 and maven-deploy-plugin 3.0.0-M1, need to pass -Daether.checksums.algorithms="SHA256,SHA512" to the maven options Please note that this won't pass Maven Central upload validation. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven 3.8.1 + maven-deploy-plugin 3.0.0-M1 and still no SHA256/SHA512
I figured it out... With Maven 3.8.1 and maven-deploy-plugin 3.0.0-M1, need to pass -Daether.checksums.algorithms="SHA256,SHA512" to the maven options On Thu, Apr 29, 2021 at 8:35 PM David Milet wrote: > Hello, > > Maven 3.8.1 picked up new maven-resolver which supports the generation > (and I suppose, verification) of SHA256 and SHA512 digests. ( > https://issues.apache.org/jira/browse/MRESOLVER-115) > > However it seems that maven-deploy-plugin 3.0.0-M1 still uses > maven-artifact-transfer 0.10.0, which generates MD5 and SHA1 digests > (removed in 0.13.1 it seems > https://issues.apache.org/jira/browse/MSHARED-922). > > When will maven-deploy-plugin be updated to generate the new digests ? > >
Maven 3.8.1 + maven-deploy-plugin 3.0.0-M1 and still no SHA256/SHA512
Hello, Maven 3.8.1 picked up new maven-resolver which supports the generation (and I suppose, verification) of SHA256 and SHA512 digests. ( https://issues.apache.org/jira/browse/MRESOLVER-115) However it seems that maven-deploy-plugin 3.0.0-M1 still uses maven-artifact-transfer 0.10.0, which generates MD5 and SHA1 digests (removed in 0.13.1 it seems https://issues.apache.org/jira/browse/MSHARED-922). When will maven-deploy-plugin be updated to generate the new digests ?
Re: Need help with maven deploy plugin.
Which pom are properties beans.version and rest.version defined?
com.blah.nw.libraries:libraries:1.0.0 or it's parent?
Technically what you're deploying and using looks valid, the consumed
using them should resolve those dependencies and pick up your custom
version property and work it out dynamically.
I've just created a mini project and mine seems to be working how you
want it to do, but i'm deploying to a local directory and not into
artifactory/nexus.
Normally in a multi module project, I collate all dependency version
details into the root multi module parent pom under the
dependencyManagement section. So multi module children only define use
x but never use version y of x.
John
On Wed, 19 Aug 2020 at 08:01, Jai Sharma wrote:
>
> I am trying to upload multiple jar files to artifactory using "mvn deploy"
> command for a multi module project. Problem I am facing is generated pom
> files uploaded with jar files to artifactory contains only property name as
> version.
>
> Example - This is the part of jar file uploaded to artifactory for module
> "configuration-entity".
> When i am using this as dependency in another project I am getting error
> cannot resolve dependencies
> com.blah.infra.libraries:rest:jar:${rest.version}
> com.blah.infra.libraries:beans:jar:${beans.version}
>
>
>
>
> 4.0.0
>
>
> com.blah.nw.libraries
> libraries
> 1.0.0
>
>
> configuration-entity
>
>
>
> com.blah.infra.libraries
> rest
> ${rest.version}
>
>
> com.blah.infra.libraries
> beans
> ${beans.version}
>
>
>
>
> -
> 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
Need help with maven deploy plugin.
I am trying to upload multiple jar files to artifactory using "mvn deploy"
command for a multi module project. Problem I am facing is generated pom files
uploaded with jar files to artifactory contains only property name as version.
Example - This is the part of jar file uploaded to artifactory for module
"configuration-entity".
When i am using this as dependency in another project I am getting error cannot
resolve dependencies
com.blah.infra.libraries:rest:jar:${rest.version}
com.blah.infra.libraries:beans:jar:${beans.version}
4.0.0
com.blah.nw.libraries
libraries
1.0.0
configuration-entity
com.blah.infra.libraries
rest
${rest.version}
com.blah.infra.libraries
beans
${beans.version}
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Apache Maven Deploy Plugin Version 3.0.0-M1 Released
The Apache Maven team is pleased to announce the release of the Apache Maven Deploy Plugin Version 3.0.0-M1. https://maven.apache.org/plugins/maven-deploy-plugin/ Important Note since 3.0.0-M1: * Maven 3.X only * Minimum JDK 7+ * The maven-deploy-plugin will generate the needed checksums during the transfer to your remote repository. Usage Note: * Use the maven-deploy-plugin version 3.0.0-M1 only in combintation with the maven-install-plugin version 3.0.0-M1. You should specify the version in your project's plugin configuration: org.apache.maven.plugins maven-deploy-plugin 3.0.0-M1 You can download the appropriate sources etc. from the download page: https://maven.apache.org/plugins/maven-deploy-plugin/download.cgi Release Notes Maven Deploy Plugin 3.0.0-M1 https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317228=12330476 Bugs: * [MDEPLOY-194] - Deploy SSH external: copy and paste failure in POM snippet comment * [MDEPLOY-211] - uniqueVersion broken (if not supported, should be removed from doc, and warning printed) * [MDEPLOY-212] - deploy-file incorrectly deploys attached artifacts * [MDEPLOY-213] - deploy-file replaces main artifact of a project * [MDEPLOY-215] - Remove link to non-existing Codehaus wiki New Feature: * [MDEPLOY-178] - Use information provided in pom.xml of JAR Improvements: * [MDEPLOY-171] - Remove deprecated readonly parameters * [MDEPLOY-187] - Upgrade to Maven 3.0 compatiblity * [MDEPLOY-205] - MavenProject with only attachments must have packaging "pom" * [MDEPLOY-207] - Remove @Deprecated marked code * [MDEPLOY-222] - Issue Tracking in pom.xml points to outdated Codehaus site * [MDEPLOY-231] - Move checksum generation from install to deploy plugin * [MDEPLOY-232] - Using maven-fluido-skin 1.7 * [MDEPLOY-233] - Remove unused code * [MDEPLOY-240] - Remove updateReleaseInfo parameter Tasks: * [MDEPLOY-203] - Rename package to org.apache.maven.plugins * [MDEPLOY-239] - Add GitHub documentation * [MDEPLOY-242] - Lift JDK minimum to JDK 7 Sub-task: * [MDEPLOY-202] - deploy-file goal insists on deploying source file for previous deploy-file execution Dependency upgrades: * [MDEPLOY-188] - Upgrade plexus-utils to 3.0.18 * [MDEPLOY-191] - Upgrade to maven-plugins parent version 27 * [MDEPLOY-192] - Upgrade maven-plugin-testing-harness to 1.3 * [MDEPLOY-208] - Upgrade plexus-utils to 3.0.24 * [MDEPLOY-209] - Upgrade maven-shared-components parent to version 30 * [MDEPLOY-210] - Upgrade of commons-io to 2.5. * [MDEPLOY-219] - Upgrade maven-artifact-transfer to version 0.9.1 * [MDEPLOY-228] - Upgrade plexus-utils 3.1.0 * [MDEPLOY-230] - Upgrade parent to 31 * [MDEPLOY-235] - Upgrade mave-surefire/failsafe-plugin 2.21.0 * [MDEPLOY-237] - Upgrade maven-plugins parent to version 32 * [MDEPLOY-238] - Upgrade JUnit 4.11 to 4.12 Enjoy - The Apache Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Cannot Deploy From Jenkins to Nexus maven-deploy-plugin:2.7 not found
Hello again Gary, My guesswer is no :-). I’ve personally never been in a situation where there isn’t a version specified for every dependency, plugin, etc. I’m not sure you are allowed to not specify a version completely. Yes, it can be skipped on …, but that is because of … where complete GAV (Group, Artifact, Version) is specified for dependencies. This is usually put high up in a parent pom. Then lower pom’s can just specify the dependency without version. This is to simplify and keep version management in one place. So I believe that you must put a version somewhere, and that there are no standard default versions. If you don’t know what versions are available for some dependency, you can always search in maven central: https://search.maven.org/classic/. Or if your dependencies are in bintrays jcenter you can search for packages here: https://bintray.com/bintray/jcenter. Regards, Tommy Från: Mills, Gary (GE Digital) Svara: Maven Users List Datum: 10 augusti 2018 at 16:22:34 Till: Maven Users List Ämne: Cannot Deploy From Jenkins to Nexus maven-deploy-plugin:2.7 not found Hey Tommy, thanks! Yeah, I get it. I'm really just trying to understand how this all works 😊 . How does Maven determine the default plugin version to use? Let's say you only give Maven the order, "clean deploy", Maven goes out and somehow determines to pull down plugin xxx.x. there has to be something that directs it to a specific base version set? Gary Mills Kind Regards, Cell 630-607-9639 Work 920-390-4806 -Original Message- From: Tommy Svensson Sent: Friday, August 10, 2018 2:14 AM To: Maven Users List Subject: EXT: Re: Cannot Deploy From Jenkins to Nexus maven-deploy-plugin:2.7 not found Hello Gary, I have seen the word LATEST in capitals used as version number, but never tried it myself. It is in general a good idea to know exactly what version you are using, and do controlled upgrades to newer versions. Surprises are seldom good IMHO. Regards, Tommy PÃ¥ 9 augusti 2018 till 21:49:41, Mills, Gary (GE Digital) (gary.l.mi...@ge.com(mailto:gary.l.mi...@ge.com)) skrev: > > > this is my environment. java version "1.8.0_181" Java(TM) SE Runtime > Environment (build 1.8.0_181-b13) Java HotSpot(TM) 64-Bit Server VM (build > 25.181-b13, mixed mode) > > Apache Maven 3.5.4 Nexus 2.14.8-01 Jenkins 2.136 > > my issue is I cannot perform a mvn clean deploy in Jenkins without it issuing > error. the error: > The POM for org.apache.maven.plugins:maven-deploy-plugin:jar:2.7 is missing, > no dependency information available [ERROR] Plugin > org.apache.maven.plugins:maven-deploy-plugin:2.7 or one of its dependencies > could not be resolved: Failure to find > org.apache.maven.plugins:maven-deploy-plugin:jar:2.7 in > http://137.27.68.182:8082/nexus/content/groups/public was cached in the local > repository, resolution will not be reattempted until the update interval of > ge-ip-nexus has elapsed or updates are forced > > > In Nexus Maven Central, I look in Nexus repo, and under Browse Index, the > maven-deploy-plugin:jar:2.7 exists, however, under browse storage, only 2.8.2 > exists. > > I'm not specifying or to my knowledge a specific version and wonder why > doesn't it just use the maven-deploy-plugin:jar:2.8.2 ??? instead of the 2.7. > and I can't find where the 2.7 is being declared. ?? > > thank you any suggestions on how to resolve or explain what the heck is going > on would be much appreciated, > > it keeps looking for maven-deploy-plugin:2.7 when 2.8.2 is available? How can > I make this work? Either use 2.7 or make it use 2.8 ? > > > 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;> > > > > > > /Users/212555427/devel/maven/repositories/ge-ip-jenkins-repository > > > > > false > > > > > > > > com.ge.ip.snapshot.local > > x > > xx > > > > > > > > > > > > > > ge-ip-nexus > > Nexus Repository Manager > > *,!jbossRepos(x) > > http://137.277.686.182:8082/nexus/content/groups/public > > > > > > > > > > > > > > > > > > development > > > > > > > > > > false > > > > com.ge.ip.release > > Release Repository > > http://137.277.686.182:8082/nexus/co
Re: Cannot Deploy From Jenkins to Nexus maven-deploy-plugin:2.7 not found
On Fri, Aug 10, 2018 at 7:22 AM Mills, Gary (GE Digital) < gary.l.mi...@ge.com> wrote: > Hey Tommy, thanks! Yeah, I get it. I'm really just trying to understand > how this all works . > > How does Maven determine the default plugin version to use? Let's say you > only give Maven the order, "clean deploy", Maven goes out and somehow > determines to pull down plugin xxx.x. there has to be something that > directs it to a specific base version set? > Checkout https://maven.apache.org/pom.html#The_Super_POM and its advice "You can take a look at how the Super POM affects your Project Object Model by creating a minimal pom.xml and executing on the command line: mvn help:effective-pom"
Cannot Deploy From Jenkins to Nexus maven-deploy-plugin:2.7 not found
Hey Tommy, thanks! Yeah, I get it. I'm really just trying to understand how this all works . How does Maven determine the default plugin version to use? Let's say you only give Maven the order, "clean deploy", Maven goes out and somehow determines to pull down plugin xxx.x. there has to be something that directs it to a specific base version set? Gary Mills Kind Regards, Cell 630-607-9639 Work 920-390-4806 -Original Message- From: Tommy Svensson Sent: Friday, August 10, 2018 2:14 AM To: Maven Users List Subject: EXT: Re: Cannot Deploy From Jenkins to Nexus maven-deploy-plugin:2.7 not found Hello Gary, I have seen the word LATEST in capitals used as version number, but never tried it myself. It is in general a good idea to know exactly what version you are using, and do controlled upgrades to newer versions. Surprises are seldom good IMHO. Regards, Tommy På 9 augusti 2018 till 21:49:41, Mills, Gary (GE Digital) (gary.l.mi...@ge.com(mailto:gary.l.mi...@ge.com)) skrev: > > > this is my environment. java version "1.8.0_181" Java(TM) SE Runtime > Environment (build 1.8.0_181-b13) Java HotSpot(TM) 64-Bit Server VM (build > 25.181-b13, mixed mode) > > Apache Maven 3.5.4 Nexus 2.14.8-01 Jenkins 2.136 > > my issue is I cannot perform a mvn clean deploy in Jenkins without it issuing > error. the error: > The POM for org.apache.maven.plugins:maven-deploy-plugin:jar:2.7 is missing, > no dependency information available [ERROR] Plugin > org.apache.maven.plugins:maven-deploy-plugin:2.7 or one of its dependencies > could not be resolved: Failure to find > org.apache.maven.plugins:maven-deploy-plugin:jar:2.7 in > http://137.27.68.182:8082/nexus/content/groups/public was cached in the local > repository, resolution will not be reattempted until the update interval of > ge-ip-nexus has elapsed or updates are forced > > > In Nexus Maven Central, I look in Nexus repo, and under Browse Index, the > maven-deploy-plugin:jar:2.7 exists, however, under browse storage, only 2.8.2 > exists. > > I'm not specifying or to my knowledge a specific version and wonder why > doesn't it just use the maven-deploy-plugin:jar:2.8.2 ??? instead of the 2.7. > and I can't find where the 2.7 is being declared. ?? > > thank you any suggestions on how to resolve or explain what the heck is going > on would be much appreciated, > > it keeps looking for maven-deploy-plugin:2.7 when 2.8.2 is available? How can > I make this work? Either use 2.7 or make it use 2.8 ? > > > 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;> > > > > > > /Users/212555427/devel/maven/repositories/ge-ip-jenkins-repository > > > > false > > > > > > > > com.ge.ip.snapshot.local > > x > > xx > > > > > > > > > > > > > > ge-ip-nexus > > Nexus Repository Manager > > *,!jbossRepos(x) > > http://137.277.686.182:8082/nexus/content/groups/public > > > > > > > > > > > > > > > > > > development > > > > > > > > > > false > > > > com.ge.ip.release > > Release Repository > > http://137.277.686.182:8082/nexus/content/groups/public > > > > > > > > > > > > > > true > > > > com.ge.ip.snapshot > > Snapshot Repository > > http://137.277.686.182:8082/nexus/content/groups/public > > > > > > > > > > > > > > > > > > > > > > false > > > > com.ge.ip.plugin.release > > Plugin Release Repository > > http://137.277.686.182:8082/nexus/content/groups/public > > > > > > > > > > > > > > true > > > > com.ge.ip.plugin.snapshot > > Plugin Snapshot Repository > > http://137.277.686.182:8082/nexus/content/groups/public > > > > > > > > > > > > > > > > > > > > development > > > > > > > > Thank you! > > > Sent from Mail<https://go.microsoft.com/fwlink/?LinkId=550986> for Windows 10 >
Re: Cannot Deploy From Jenkins to Nexus maven-deploy-plugin:2.7 not found
Hello Gary, I have seen the word LATEST in capitals used as version number, but never tried it myself. It is in general a good idea to know exactly what version you are using, and do controlled upgrades to newer versions. Surprises are seldom good IMHO. Regards, Tommy På 9 augusti 2018 till 21:49:41, Mills, Gary (GE Digital) (gary.l.mi...@ge.com(mailto:gary.l.mi...@ge.com)) skrev: > > > this is my environment. java version "1.8.0_181" Java(TM) SE Runtime > Environment (build 1.8.0_181-b13) Java HotSpot(TM) 64-Bit Server VM (build > 25.181-b13, mixed mode) > > Apache Maven 3.5.4 Nexus 2.14.8-01 Jenkins 2.136 > > my issue is I cannot perform a mvn clean deploy in Jenkins without it issuing > error. the error: > The POM for org.apache.maven.plugins:maven-deploy-plugin:jar:2.7 is missing, > no dependency information available [ERROR] Plugin > org.apache.maven.plugins:maven-deploy-plugin:2.7 or one of its dependencies > could not be resolved: Failure to find > org.apache.maven.plugins:maven-deploy-plugin:jar:2.7 in > http://137.27.68.182:8082/nexus/content/groups/public was cached in the local > repository, resolution will not be reattempted until the update interval of > ge-ip-nexus has elapsed or updates are forced > > > In Nexus Maven Central, I look in Nexus repo, and under Browse Index, the > maven-deploy-plugin:jar:2.7 exists, however, under browse storage, only 2.8.2 > exists. > > I'm not specifying or to my knowledge a specific version and wonder why > doesn't it just use the maven-deploy-plugin:jar:2.8.2 ??? instead of the 2.7. > and I can't find where the 2.7 is being declared. ?? > > thank you any suggestions on how to resolve or explain what the heck is going > on would be much appreciated, > > it keeps looking for maven-deploy-plugin:2.7 when 2.8.2 is available? How can > I make this work? Either use 2.7 or make it use 2.8 ? > > > 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;> > > > > > > /Users/212555427/devel/maven/repositories/ge-ip-jenkins-repository > > > > false > > > > > > > > com.ge.ip.snapshot.local > > x > > xx > > > > > > > > > > > > > > ge-ip-nexus > > Nexus Repository Manager > > *,!jbossRepos(x) > > http://137.277.686.182:8082/nexus/content/groups/public > > > > > > > > > > > > > > > > > > development > > > > > > > > > > false > > > > com.ge.ip.release > > Release Repository > > http://137.277.686.182:8082/nexus/content/groups/public > > > > > > > > > > > > > > true > > > > com.ge.ip.snapshot > > Snapshot Repository > > http://137.277.686.182:8082/nexus/content/groups/public > > > > > > > > > > > > > > > > > > > > > > false > > > > com.ge.ip.plugin.release > > Plugin Release Repository > > http://137.277.686.182:8082/nexus/content/groups/public > > > > > > > > > > > > > > true > > > > com.ge.ip.plugin.snapshot > > Plugin Snapshot Repository > > http://137.277.686.182:8082/nexus/content/groups/public > > > > > > > > > > > > > > > > > > > > development > > > > > > > > Thank you! > > > Sent from Mail<https://go.microsoft.com/fwlink/?LinkId=550986> for Windows 10 >
Cannot Deploy From Jenkins to Nexus maven-deploy-plugin:2.7 not found
this is my environment. java version "1.8.0_181" Java(TM) SE Runtime Environment (build 1.8.0_181-b13) Java HotSpot(TM) 64-Bit Server VM (build 25.181-b13, mixed mode) Apache Maven 3.5.4 Nexus 2.14.8-01 Jenkins 2.136 my issue is I cannot perform a mvn clean deploy in Jenkins without it issuing error. the error: The POM for org.apache.maven.plugins:maven-deploy-plugin:jar:2.7 is missing, no dependency information available [ERROR] Plugin org.apache.maven.plugins:maven-deploy-plugin:2.7 or one of its dependencies could not be resolved: Failure to find org.apache.maven.plugins:maven-deploy-plugin:jar:2.7 in http://137.27.68.182:8082/nexus/content/groups/public was cached in the local repository, resolution will not be reattempted until the update interval of ge-ip-nexus has elapsed or updates are forced In Nexus Maven Central, I look in Nexus repo, and under Browse Index, the maven-deploy-plugin:jar:2.7 exists, however, under browse storage, only 2.8.2 exists. I'm not specifying or to my knowledge a specific version and wonder why doesn't it just use the maven-deploy-plugin:jar:2.8.2 ??? instead of the 2.7. and I can't find where the 2.7 is being declared. ?? thank you any suggestions on how to resolve or explain what the heck is going on would be much appreciated, it keeps looking for maven-deploy-plugin:2.7 when 2.8.2 is available? How can I make this work? Either use 2.7 or make it use 2.8 ? 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;> /Users/212555427/devel/maven/repositories/ge-ip-jenkins-repository false com.ge.ip.snapshot.local x xx ge-ip-nexus Nexus Repository Manager *,!jbossRepos(x) http://137.277.686.182:8082/nexus/content/groups/public development false com.ge.ip.release Release Repository http://137.277.686.182:8082/nexus/content/groups/public true com.ge.ip.snapshot Snapshot Repository http://137.277.686.182:8082/nexus/content/groups/public false com.ge.ip.plugin.release Plugin Release Repository http://137.277.686.182:8082/nexus/content/groups/public true com.ge.ip.plugin.snapshot Plugin Snapshot Repository http://137.277.686.182:8082/nexus/content/groups/public development Thank you! Sent from Mail<https://go.microsoft.com/fwlink/?LinkId=550986> for Windows 10
Issue with maven deploy plugin
Hi , I am in process of implementing continuous integration. I amUsing GIT repository to manage source code.I've created a project using apache maven . In POM.xml file I've included distribution management tag and specified the path to remote repository where I want to store my builds generated by maven. distributionManagement repository idGIT/id nameGIT repository/name urlhttps://github.com/sameerchandekar/deploy.git/url/repository /distributionManagement now when I execute the deploy goal i get following error INFO] --- maven-deploy-plugin:2.7:deploy (default-deploy) @ KEDB ---Downloading: https://github.com/sameerchandekar/deploy.git/com/kedb/KEDB/0.0.1-SNAPSHOT/maven-metadata.xmlUploading: https://github.com/sameerchandekar/deploy.git/com/kedb/KEDB/0.0.1-SNAPSHOT/KEDB-0.0.1-20141005.131802-1.warUploading: https://github.com/sameerchandekar/deploy.git/com/kedb/KEDB/0.0.1-SNAPSHOT/KEDB-0.0.1-20141005.131802-1.pom[INFO] [INFO] BUILD FAILURE[INFO] [INFO] Total time: 13.868s[INFO] Finished at: Sun Oct 05 01:18:09 GMT-12:00 2014[INFO] Final Memory: 8M/21M[INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.7:deploy (default-deploy) on project KEDB: Failed to deploy artifacts: Could not find artifact com.kedb:KEDB:war:0.0.1-20141005.131802-1 in GIT (https://github.com/sameerchandekar/deploy.git) - [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/MojoExecutionException Here it is unable to download maven-metadata.xml and unable to upload war and pom files.Here the repository I created i.e https://github.com/sameerchandekar/deploy.git is not comtaining any files. This same goal if I execute by specifying the path of repository as local file system path it will work fine.see the logs below for successfull cases where the repository specified is file system path [INFO] --- maven-deploy-plugin:2.7:deploy (default-deploy) @ KEDB ---Downloading: file:///E:/itworkshere/com/kedb/KEDB/0.0.1-SNAPSHOT/maven-metadata.xmlDownloaded: file:///E:/itworkshere/com/kedb/KEDB/0.0.1-SNAPSHOT/maven-metadata.xml (762 B at 74.4 KB/sec)Uploading: file:///E:/itworkshere/com/kedb/KEDB/0.0.1-SNAPSHOT/KEDB-0.0.1-20141005.132612-2.warUploaded: file:///E:/itworkshere/com/kedb/KEDB/0.0.1-SNAPSHOT/KEDB-0.0.1-20141005.132612-2.war (123 KB at 1205.4 KB/sec)Uploading: file:///E:/itworkshere/com/kedb/KEDB/0.0.1-SNAPSHOT/KEDB-0.0.1-20141005.132612-2.pomUploaded: file:///E:/itworkshere/com/kedb/KEDB/0.0.1-SNAPSHOT/KEDB-0.0.1-20141005.132612-2.pom (2 KB at 1418.9 KB/sec)Downloading: file:///E:/itworkshere/com/kedb/KEDB/maven-metadata.xmlDownloaded: file:///E:/itworkshere/com/kedb/KEDB/maven-metadata.xml (272 B at 66.4 KB/sec)Uploading: file:///E:/itworkshere/com/kedb/KEDB/0.0.1-SNAPSHOT/maven-metadata.xmlUploaded: file:///E:/itworkshere/com/kedb/KEDB/0.0.1-SNAPSHOT/maven-metadata.xml (762 B at 372.1 KB/sec)Uploading: file:///E:/itworkshere/com/kedb/KEDB/maven-metadata.xmlUploaded: file:///E:/itworkshere/com/kedb/KEDB/maven-metadata.xml (272 B at 265.6 KB/sec)[INFO] [INFO] BUILD SUCCESS[INFO] [INFO] Total time: 2.082s[INFO] Finished at: Sun Oct 05 01:26:12 GMT-12:00 2014[INFO] Final Memory: 7M/20M[INFO] Please help to resolve this issue . Thanks ,Sameer Chandekar
Problem with maven-deploy-plugin
Hello. I've got repository protected by SSL located on subdomain: https://abc.mysite.com/ When I try to upload my artifact (`mvn deploy`) mvn rises an exception: [ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy (default-deploy) on project test: Failed to retrieve remote metadata abc.com:test:1.0-SNAPSHOT/maven-metadata.xml: Could not transfer metadata abc.com:test:1.0-SNAPSHOT/maven-metadata.xml from/to myMavenRepo.write (https://abc.mysite.com/efg/): hostname in certificate didn't match: abc.mysite.com != mysite.com OR mysite.com OR www.mysite.com - [Help 1] Why does it check main domain instead of subdomain? How can I fix this problem? - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Problem with maven-deploy-plugin
On 14 Sep 2014, at 11:58, Fedor Belov fbe...@gramant.ru wrote: Hello. I've got repository protected by SSL located on subdomain: https://abc.mysite.com/ When I try to upload my artifact (`mvn deploy`) mvn rises an exception: [ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy (default-deploy) on project test: Failed to retrieve remote metadata abc.com:test:1.0-SNAPSHOT/maven-metadata.xml: Could not transfer metadata abc.com:test:1.0-SNAPSHOT/maven-metadata.xml from/to myMavenRepo.write (https://abc.mysite.com/efg/): hostname in certificate didn't match: abc.mysite.com != mysite.com OR mysite.com OR www.mysite.com - [Help 1] Why does it check main domain instead of subdomain? How can I fix this problem? Either there is a server side problem where the cert on the server doesn't match the DNS name you're using, or more likely the server requires SNI, which doesn't seem to work with the httpclient wagon. We use the lightweight http wagon instead, which works with SSL+SNI. Regards, Graham -- - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Apache Maven Deploy Plugin Version 2.8.2 Released
The Apache Maven team is pleased to announce the release of the Apache Maven Deploy Plugin, version 2.8.2 The deploy plugin is primarily used during the deploy phase, to add your artifact(s) to a remote repository for sharing with other developers and projects. This is usually done in an integration or release environment. It can also be used to deploy a particular artifact (e.g. a third party jar like Sun's non redistributable reference implementations). http://maven.apache.org/plugins/maven-deploy-plugin plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-deploy-plugin/artifactId version2.8.2/version /plugin Release Notes - Apache Maven Deploy Version 2.8.2 Bugs: * [MDEPLOY-172] - Concurrency problem with deployAtEnd in parallel builds * [MDEPLOY-174] - [REGRESSION] url not required anymore, causing a NullPointerException Improvements: * [MDEPLOY-185] - MavenProject/MavenSession Injection as a paremeter instead as a component. * [MDEPLOY-186] - Upgrade to Maven 2.2.1 compatiblity Enjo -The Apache Maven team Karl-Heinz Marbaise - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
MDEPLOY-157 deployAtEnd option of maven-deploy-plugin broken after ant-assembly-maven-plugin execution
Hi,
I recently discovered an issue between the deployAtEnd option of
maven-deploy-plugin and the execution of my plugin
ant-assembly-maven-plugin (based on Aether).
I first though it had nothing to do with maven-deploy-plugin and revealed a
more general issue in my implementation, so
I posted on Aether mailing list [0] but Benjamin Bentmann answered it could be
a bug in the maven-deploy-plugin
implementation of deployAtEnd option [1]:
Aether has nothing to do with the way Maven manages class loaders for
plugins, i.e. you should reach out to the Maven
user list instead.
Also, your analysis suggests a bug in the maven-deploy-plugin in that it
relies on the erroneous assumption that a
single class loader is used per plugin through out a multi-module build.
Here it the issue: the deployAtEndoption doesn't work after building a module
involving an execution of
ant-assembly-maven-pluginbecause a new Class realm plugin is then created and
its static fields are reset (in that
case, the org.apache.maven.plugin.deploy.DeployMojo.readyProjectsCounterfield).
Code from maven-deploy-plugin(readyProjectsCounterrestarted to zero will never
equal to reactorProjects.size(),
projectsReadywill be always false):
@Parameter( defaultValue = ${reactorProjects}, required = true, readonly
= true )
private ListMavenProject reactorProjects;
private static final AtomicInteger readyProjectsCounter = new
AtomicInteger();
**org.apache.maven.plugin.deploy.DeployMojo.execute() {
boolean projectsReady = readyProjectsCounter.incrementAndGet() ==
reactorProjects.size();
In the following sample case, the ant-assembly-maven-plugin is called by the
nuxeo-distribution-resources module.
After that, no deployment will ever happen since the static fields of
maven-deploy-plugin are reset, the counter
readyProjectsCounter restarted to zero will never reach the number of
reactorProjects, projectsReady will be
always false:
$ mvn clean deploy -Pqa -DskipTests -pl
nuxeo-functional-tests,nuxeo-launcher,nuxeo-distribution-resources -nsu -X|grep
maven-deploy-plugin
[DEBUG] Goal:
org.apache.maven.plugins:maven-deploy-plugin:2.8.1:deploy (default-deploy)
[INFO] --- maven-deploy-plugin:2.8.1:deploy (default-deploy) @
nuxeo-functional-tests ---
[DEBUG] org.apache.maven.plugins:maven-deploy-plugin:jar:2.8.1:
[DEBUG] *Created new class realm
pluginorg.apache.maven.plugins:maven-deploy-plugin:2.8.1*
[DEBUG] Importing foreign packages into class realm
pluginorg.apache.maven.plugins:maven-deploy-plugin:2.8.1
[DEBUG] Populating class realm
pluginorg.apache.maven.plugins:maven-deploy-plugin:2.8.1
[DEBUG] Included: org.apache.maven.plugins:maven-deploy-plugin:jar:2.8.1
[DEBUG] Configuring mojo
org.apache.maven.plugins:maven-deploy-plugin:2.8.1:deploy from plugin realm
ClassRealm[pluginorg.apache.maven.plugins:maven-deploy-plugin:2.8.1, parent:
sun.misc.Launcher$AppClassLoader@4821e115]
[DEBUG] Configuring mojo
'org.apache.maven.plugins:maven-deploy-plugin:2.8.1:deploy' with basic
configurator --
[DEBUG] Goal:
org.apache.maven.plugins:maven-deploy-plugin:2.8.1:deploy (default-deploy)
[INFO] --- maven-deploy-plugin:2.8.1:deploy (default-deploy) @ nuxeo-launcher
---
[DEBUG] Configuring mojo
org.apache.maven.plugins:maven-deploy-plugin:2.8.1:deploy from plugin realm
ClassRealm[pluginorg.apache.maven.plugins:maven-deploy-plugin:2.8.1, parent:
sun.misc.Launcher$AppClassLoader@4821e115]
[DEBUG] Configuring mojo
'org.apache.maven.plugins:maven-deploy-plugin:2.8.1:deploy' with basic
configurator --
[DEBUG] Goal:
org.apache.maven.plugins:maven-deploy-plugin:2.8.1:deploy (default-deploy)
[INFO] --- maven-deploy-plugin:2.8.1:deploy (default-deploy) @
nuxeo-distribution-resources ---
[DEBUG] org.apache.maven.plugins:maven-deploy-plugin:jar:2.8.1:
[DEBUG] *Created new class realm
pluginorg.apache.maven.plugins:maven-deploy-plugin:2.8.1--724569306*
[DEBUG] Importing foreign packages into class realm
pluginorg.apache.maven.plugins:maven-deploy-plugin:2.8.1--724569306
[DEBUG] Populating class realm
pluginorg.apache.maven.plugins:maven-deploy-plugin:2.8.1--724569306
[DEBUG] Included: org.apache.maven.plugins:maven-deploy-plugin:jar:2.8.1
[DEBUG] Configuring mojo
org.apache.maven.plugins:maven-deploy-plugin:2.8.1:deploy from plugin realm
ClassRealm[pluginorg.apache.maven.plugins:maven-deploy-plugin:2.8.1--724569306,
parent: sun.misc.Launcher$AppClassLoader@4821e115]
[DEBUG] Configuring mojo
'org.apache.maven.plugins:maven-deploy-plugin:2.8.1:deploy' with basic
configurator --
Could someone explain or guess why/when a new class realm
pluginorg.apache.maven.plugins:maven-deploy-plugin is
created (in bold) instead of reusing the previous one?
Is there something wrong in my implementation about that? Or should I rather
create an
http://jira.codehaus.org/browse/MDEPLOY issue related to MDEPLOY-157?
The full log of above reproduction case:
http://ubuntuone.com
Re: MDEPLOY-157 deployAtEnd option of maven-deploy-plugin broken after ant-assembly-maven-plugin execution
Not sure about your questions, but your finding might explain (or be
related) ti what was found by Karl in this thread
http://markmail.org/thread/65b7o4so77i7delc
Thanks,
~t~
On Wed, Mar 12, 2014 at 10:45 AM, Julien CARSIQUE jcarsi...@nuxeo.comwrote:
Hi,
I recently discovered an issue between the deployAtEnd option of
maven-deploy-plugin and the execution of my plugin
ant-assembly-maven-plugin (based on Aether).
I first though it had nothing to do with maven-deploy-plugin and revealed
a more general issue in my implementation, so
I posted on Aether mailing list [0] but Benjamin Bentmann answered it
could be a bug in the maven-deploy-plugin
implementation of deployAtEnd option [1]:
Aether has nothing to do with the way Maven manages class loaders for
plugins, i.e. you should reach out to the Maven
user list instead.
Also, your analysis suggests a bug in the maven-deploy-plugin in that
it relies on the erroneous assumption that a
single class loader is used per plugin through out a multi-module build.
Here it the issue: the deployAtEndoption doesn't work after building a
module involving an execution of
ant-assembly-maven-pluginbecause a new Class realm plugin is then
created and its static fields are reset (in that
case, the
org.apache.maven.plugin.deploy.DeployMojo.readyProjectsCounterfield).
Code from maven-deploy-plugin(readyProjectsCounterrestarted to zero will
never equal to reactorProjects.size(),
projectsReadywill be always false):
@Parameter( defaultValue = ${reactorProjects}, required = true,
readonly = true )
private ListMavenProject reactorProjects;
private static final AtomicInteger readyProjectsCounter = new
AtomicInteger();
**org.apache.maven.plugin.deploy.DeployMojo.execute() {
boolean projectsReady = readyProjectsCounter.incrementAndGet() ==
reactorProjects.size();
In the following sample case, the ant-assembly-maven-plugin is called by
the nuxeo-distribution-resources module.
After that, no deployment will ever happen since the static fields of
maven-deploy-plugin are reset, the counter
readyProjectsCounter restarted to zero will never reach the number of
reactorProjects, projectsReady will be
always false:
$ mvn clean deploy -Pqa -DskipTests -pl
nuxeo-functional-tests,nuxeo-launcher,nuxeo-distribution-resources -nsu
-X|grep maven-deploy-plugin
[DEBUG] Goal:
org.apache.maven.plugins:maven-deploy-plugin:2.8.1:deploy (default-deploy)
[INFO] --- maven-deploy-plugin:2.8.1:deploy (default-deploy) @
nuxeo-functional-tests ---
[DEBUG] org.apache.maven.plugins:maven-deploy-plugin:jar:2.8.1:
[DEBUG] *Created new class realm
pluginorg.apache.maven.plugins:maven-deploy-plugin:2.8.1*
[DEBUG] Importing foreign packages into class realm
pluginorg.apache.maven.plugins:maven-deploy-plugin:2.8.1
[DEBUG] Populating class realm
pluginorg.apache.maven.plugins:maven-deploy-plugin:2.8.1
[DEBUG] Included: org.apache.maven.plugins:maven-deploy-plugin:jar:2.8.1
[DEBUG] Configuring mojo
org.apache.maven.plugins:maven-deploy-plugin:2.8.1:deploy from plugin realm
ClassRealm[pluginorg.apache.maven.plugins:maven-deploy-plugin:2.8.1,
parent: sun.misc.Launcher$AppClassLoader@4821e115]
[DEBUG] Configuring mojo
'org.apache.maven.plugins:maven-deploy-plugin:2.8.1:deploy' with basic
configurator --
[DEBUG] Goal:
org.apache.maven.plugins:maven-deploy-plugin:2.8.1:deploy (default-deploy)
[INFO] --- maven-deploy-plugin:2.8.1:deploy (default-deploy) @
nuxeo-launcher ---
[DEBUG] Configuring mojo
org.apache.maven.plugins:maven-deploy-plugin:2.8.1:deploy from plugin realm
ClassRealm[pluginorg.apache.maven.plugins:maven-deploy-plugin:2.8.1,
parent: sun.misc.Launcher$AppClassLoader@4821e115]
[DEBUG] Configuring mojo
'org.apache.maven.plugins:maven-deploy-plugin:2.8.1:deploy' with basic
configurator --
[DEBUG] Goal:
org.apache.maven.plugins:maven-deploy-plugin:2.8.1:deploy (default-deploy)
[INFO] --- maven-deploy-plugin:2.8.1:deploy (default-deploy) @
nuxeo-distribution-resources ---
[DEBUG] org.apache.maven.plugins:maven-deploy-plugin:jar:2.8.1:
[DEBUG] *Created new class realm
pluginorg.apache.maven.plugins:maven-deploy-plugin:2.8.1--724569306*
[DEBUG] Importing foreign packages into class realm
pluginorg.apache.maven.plugins:maven-deploy-plugin:2.8.1--724569306
[DEBUG] Populating class realm
pluginorg.apache.maven.plugins:maven-deploy-plugin:2.8.1--724569306
[DEBUG] Included: org.apache.maven.plugins:maven-deploy-plugin:jar:2.8.1
[DEBUG] Configuring mojo
org.apache.maven.plugins:maven-deploy-plugin:2.8.1:deploy from plugin realm
ClassRealm[pluginorg.apache.maven.plugins:maven-deploy-plugin:2.8.1--724569306,
parent: sun.misc.Launcher$AppClassLoader@4821e115]
[DEBUG] Configuring mojo
'org.apache.maven.plugins:maven-deploy-plugin:2.8.1:deploy' with basic
configurator --
Could someone explain or guess why/when a new class realm
pluginorg.apache.maven.plugins:maven-deploy-plugin is
created
Re: MDEPLOY-157 deployAtEnd option of maven-deploy-plugin broken after ant-assembly-maven-plugin execution
Indeed. Thanks for pointing at that thread.
That would suggest the behavior comes from my plugin which defines it's own
lifecycle (extensions true), but that the
issue resides in the deployAtEnd implementation in maven-deploy-plugin.
However, a lot of plugins do define their own extensions/lifecycle without the
same effect, isn't it?
Or is there a newer/better way than
https://github.com/nuxeo/ant-assembly-maven-plugin/blob/442c47747d1b32e5cb883cde4233f5b8846ea6f0/src/main/resources/META-INF/plexus/components.xml
?
On 12/03/2014 10:51, Tamás Cservenák wrote:
Not sure about your questions, but your finding might explain (or be
related) ti what was found by Karl in this thread
http://markmail.org/thread/65b7o4so77i7delc
Thanks,
~t~
On Wed, Mar 12, 2014 at 10:45 AM, Julien CARSIQUE jcarsi...@nuxeo.comwrote:
Hi,
I recently discovered an issue between the deployAtEnd option of
maven-deploy-plugin and the execution of my plugin
ant-assembly-maven-plugin (based on Aether).
I first though it had nothing to do with maven-deploy-plugin and revealed
a more general issue in my implementation, so
I posted on Aether mailing list [0] but Benjamin Bentmann answered it
could be a bug in the maven-deploy-plugin
implementation of deployAtEnd option [1]:
Aether has nothing to do with the way Maven manages class loaders for
plugins, i.e. you should reach out to the Maven
user list instead.
Also, your analysis suggests a bug in the maven-deploy-plugin in that
it relies on the erroneous assumption that a
single class loader is used per plugin through out a multi-module build.
Here it the issue: the deployAtEndoption doesn't work after building a
module involving an execution of
ant-assembly-maven-pluginbecause a new Class realm plugin is then
created and its static fields are reset (in that
case, the
org.apache.maven.plugin.deploy.DeployMojo.readyProjectsCounterfield).
Code from maven-deploy-plugin(readyProjectsCounterrestarted to zero will
never equal to reactorProjects.size(),
projectsReadywill be always false):
@Parameter( defaultValue = ${reactorProjects}, required = true,
readonly = true )
private ListMavenProject reactorProjects;
private static final AtomicInteger readyProjectsCounter = new
AtomicInteger();
**org.apache.maven.plugin.deploy.DeployMojo.execute() {
boolean projectsReady = readyProjectsCounter.incrementAndGet() ==
reactorProjects.size();
In the following sample case, the ant-assembly-maven-plugin is called by
the nuxeo-distribution-resources module.
After that, no deployment will ever happen since the static fields of
maven-deploy-plugin are reset, the counter
readyProjectsCounter restarted to zero will never reach the number of
reactorProjects, projectsReady will be
always false:
$ mvn clean deploy -Pqa -DskipTests -pl
nuxeo-functional-tests,nuxeo-launcher,nuxeo-distribution-resources -nsu
-X|grep maven-deploy-plugin
[DEBUG] Goal:
org.apache.maven.plugins:maven-deploy-plugin:2.8.1:deploy (default-deploy)
[INFO] --- maven-deploy-plugin:2.8.1:deploy (default-deploy) @
nuxeo-functional-tests ---
[DEBUG] org.apache.maven.plugins:maven-deploy-plugin:jar:2.8.1:
[DEBUG] *Created new class realm
pluginorg.apache.maven.plugins:maven-deploy-plugin:2.8.1*
[DEBUG] Importing foreign packages into class realm
pluginorg.apache.maven.plugins:maven-deploy-plugin:2.8.1
[DEBUG] Populating class realm
pluginorg.apache.maven.plugins:maven-deploy-plugin:2.8.1
[DEBUG] Included: org.apache.maven.plugins:maven-deploy-plugin:jar:2.8.1
[DEBUG] Configuring mojo
org.apache.maven.plugins:maven-deploy-plugin:2.8.1:deploy from plugin realm
ClassRealm[pluginorg.apache.maven.plugins:maven-deploy-plugin:2.8.1,
parent: sun.misc.Launcher$AppClassLoader@4821e115]
[DEBUG] Configuring mojo
'org.apache.maven.plugins:maven-deploy-plugin:2.8.1:deploy' with basic
configurator --
[DEBUG] Goal:
org.apache.maven.plugins:maven-deploy-plugin:2.8.1:deploy (default-deploy)
[INFO] --- maven-deploy-plugin:2.8.1:deploy (default-deploy) @
nuxeo-launcher ---
[DEBUG] Configuring mojo
org.apache.maven.plugins:maven-deploy-plugin:2.8.1:deploy from plugin realm
ClassRealm[pluginorg.apache.maven.plugins:maven-deploy-plugin:2.8.1,
parent: sun.misc.Launcher$AppClassLoader@4821e115]
[DEBUG] Configuring mojo
'org.apache.maven.plugins:maven-deploy-plugin:2.8.1:deploy' with basic
configurator --
[DEBUG] Goal:
org.apache.maven.plugins:maven-deploy-plugin:2.8.1:deploy (default-deploy)
[INFO] --- maven-deploy-plugin:2.8.1:deploy (default-deploy) @
nuxeo-distribution-resources ---
[DEBUG] org.apache.maven.plugins:maven-deploy-plugin:jar:2.8.1:
[DEBUG] *Created new class realm
pluginorg.apache.maven.plugins:maven-deploy-plugin:2.8.1--724569306*
[DEBUG] Importing foreign packages into class realm
pluginorg.apache.maven.plugins:maven-deploy-plugin:2.8.1--724569306
[DEBUG] Populating class realm
pluginorg.apache.maven.plugins:maven-deploy
Re: Maven deploy plugin 2.8.1 - deploy-file goal - unable to avoid attachedArtifacts from being deployed in execute
/executions
/plugin
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-assembly-plugin/artifactId
version2.4/version
executions
execution
iddeployprofile/id
phasepackage/phase
goals
goalsingle/goal
/goals
configuration
finalName${project.parent.artifactId}-${project.parent.version}
/finalName
outputDirectory${project.build.directory}//outputDirectory
filteringtrue/filtering
descriptors
descriptorassembly/dist.xml/descriptor
/descriptors
/configuration
/execution
/executions
/plugin
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-deploy-plugin/artifactId
executions
execution
idcookbook/id
phasedeploy/phase
goals
goaldeploy-file/goal
/goals
configuration
primaryArtifactfalse/primaryArtifact
repositoryIdartifactory/repositoryId
packagingzip/packaging
url${project.distributionManagement.snapshotRepository.url}/url
generatePomfalse/generatePom
artifactId${project.parent.artifactId}/artifactId
groupId${project.parent.groupId}/groupId
version${project.parent.version}/version
classifierdeploymentfile/classifier
file
${project.build.directory}/${project.parent.artifactId}-${project.parent.version}-deploymentfile.zip
/file
/configuration
/execution
/executions
/plugin
/plugins
/build
/profile
/profiles
/project
Med venlig hilsen
Henrik Skriver Rasmussen
On Thu, Feb 13, 2014 at 2:15 PM, Anders Hammar and...@hammar.net
wrote:
You need to provide more info on what you're doing! Is the
deploy:deploy-file bound to the build lifecycle of a project? How?
/Anders
On Thu, Feb 13, 2014 at 11:06 AM, Henrik Skriver Rasmussen
skrive...@gmail.com wrote:
Hi
I have a question about the expected behaviour of the
deploy:deploy-file
goal in the maven deploy plugin 2.8.1 which I am currently using
to
deploy
one file.
It surprised me that no matter what I did I kept getting more
artifacts
deployed that I asked for and the reason is in the
org.apache.maven.plugin.deploy.DeployFileMojo.execute line 376
where
the
attached artifacts are also deployed.
Is this intended behaviour and if so how can I avoid this from
happening?
The goal name deploy-file indicates that one artifact (possible
incl.
pom/metadata) is to be deployed and not also a throng of other
artifacts.
I will be happy to provide a patch where this is aspect is
removed.
Thank you in advance
regards
Henrik Skriver Rasmussen
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven deploy plugin 2.8.1 - deploy-file goal - unable to avoid attachedArtifacts from being deployed in execute
/properties
build
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-install-plugin/artifactId
version2.5.1/version
configuration
skiptrue/skip
/configuration
/plugin
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-assembly-plugin/artifactId
version2.4/version
configuration
skiptrue/skip
/configuration
/plugin
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-deploy-plugin/artifactId
version2.8.1/version
configuration
skiptrue/skip
/configuration
/plugin
/plugins
/build
profiles
profile
iddeployprofile/id
build
plugins
plugin
groupIdorg.codehaus.mojo/groupId
artifactIdexec-maven-plugin/artifactId
version1.2.1/version
executions
execution
idCopy into target folder and copy service jar into
files/default
/id
phasepackage/phase
goals
goalexec/goal
/goals
configuration
executable${project.basedir}/build_cookbook.sh/executable
arguments
argument${project.parent.artifactId}/argument
argument${project.parent.version}/argument
/arguments
/configuration
/execution
/executions
/plugin
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-assembly-plugin/artifactId
version2.4/version
executions
execution
iddeployprofile/id
phasepackage/phase
goals
goalsingle/goal
/goals
configuration
finalName${project.parent.artifactId}-${project.parent.version}
/finalName
outputDirectory${project.build.directory}//outputDirectory
filteringtrue/filtering
descriptors
descriptorassembly/dist.xml/descriptor
/descriptors
/configuration
/execution
/executions
/plugin
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-deploy-plugin/artifactId
executions
execution
idcookbook/id
phasedeploy/phase
goals
goaldeploy-file/goal
/goals
configuration
primaryArtifactfalse/primaryArtifact
repositoryIdartifactory/repositoryId
packagingzip/packaging
url${project.distributionManagement.
snapshotRepository.url}/url
generatePomfalse/generatePom
artifactId${project.parent.artifactId}/artifactId
groupId${project.parent.groupId}/groupId
version${project.parent.version}/version
classifierdeploymentfile/classifier
file
${project.build.directory}/${project.parent.artifactId}-${
project.parent.version}-deploymentfile.zip
/file
/configuration
/execution
/executions
/plugin
/plugins
/build
/profile
/profiles
/project
Med venlig hilsen
Henrik Skriver Rasmussen
On Thu, Feb 13, 2014 at 2:15 PM, Anders Hammar and...@hammar.net
wrote:
You need to provide more info on what you're doing! Is the
deploy:deploy-file bound to the build lifecycle of a project? How?
/Anders
On Thu, Feb 13, 2014 at 11:06 AM, Henrik Skriver Rasmussen
skrive...@gmail.com wrote:
Hi
I have a question about the expected behaviour of the
deploy:deploy-file
goal in the maven deploy plugin 2.8.1 which I am currently using to
deploy
one file.
It surprised me that no matter what I did I kept getting more
artifacts
deployed that I asked for and the reason is in the
org.apache.maven.plugin.deploy.DeployFileMojo.execute line 376
where
the
attached artifacts are also deployed.
Is this intended behaviour and if so how can I avoid this from
happening?
The goal name deploy-file indicates that one artifact (possible
incl.
pom/metadata) is to be deployed and not also a throng of other
artifacts.
I will be happy to provide a patch where this is aspect is removed.
Thank you in advance
regards
Henrik Skriver Rasmussen
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven deploy plugin 2.8.1 - deploy-file goal - unable to avoid attachedArtifacts from being deployed in execute
/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
parent
groupId/groupId
artifactId/artifactId
version1.1-SNAPSHOT/version
/parent
artifactIdscripts/artifactId
packagingpom/packaging
namescripts/name
description/description
properties
project.build.sourceEncodingUTF-8/project.build.sourceEncoding
project.reporting.outputEncodingUTF-8/project.
reporting.outputEncoding
main.basedir${project.parent.basedir}/main.basedir
/properties
build
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-install-plugin/artifactId
version2.5.1/version
configuration
skiptrue/skip
/configuration
/plugin
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-assembly-plugin/artifactId
version2.4/version
configuration
skiptrue/skip
/configuration
/plugin
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-deploy-plugin/artifactId
version2.8.1/version
configuration
skiptrue/skip
/configuration
/plugin
/plugins
/build
profiles
profile
iddeployprofile/id
build
plugins
plugin
groupIdorg.codehaus.mojo/groupId
artifactIdexec-maven-plugin/artifactId
version1.2.1/version
executions
execution
idCopy into target folder and copy service jar into
files/default
/id
phasepackage/phase
goals
goalexec/goal
/goals
configuration
executable${project.basedir}/build_cookbook.sh/executable
arguments
argument${project.parent.artifactId}/argument
argument${project.parent.version}/argument
/arguments
/configuration
/execution
/executions
/plugin
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-assembly-plugin/artifactId
version2.4/version
executions
execution
iddeployprofile/id
phasepackage/phase
goals
goalsingle/goal
/goals
configuration
finalName${project.parent.artifactId}-${project.parent.version}
/finalName
outputDirectory${project.build.directory}//outputDirectory
filteringtrue/filtering
descriptors
descriptorassembly/dist.xml/descriptor
/descriptors
/configuration
/execution
/executions
/plugin
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-deploy-plugin/artifactId
executions
execution
idcookbook/id
phasedeploy/phase
goals
goaldeploy-file/goal
/goals
configuration
primaryArtifactfalse/primaryArtifact
repositoryIdartifactory/repositoryId
packagingzip/packaging
url${project.distributionManagement.
snapshotRepository.url}/url
generatePomfalse/generatePom
artifactId${project.parent.artifactId}/artifactId
groupId${project.parent.groupId}/groupId
version${project.parent.version}/version
classifierdeploymentfile/classifier
file
${project.build.directory}/${project.parent.artifactId}-${
project.parent.version}-deploymentfile.zip
/file
/configuration
/execution
/executions
/plugin
/plugins
/build
/profile
/profiles
/project
Med venlig hilsen
Henrik Skriver Rasmussen
On Thu, Feb 13, 2014 at 2:15 PM, Anders Hammar and...@hammar.net
wrote:
You need to provide more info on what you're doing! Is the
deploy:deploy-file bound to the build lifecycle of a project? How?
/Anders
On Thu, Feb 13, 2014 at 11:06 AM, Henrik Skriver Rasmussen
skrive...@gmail.com wrote:
Hi
I have a question about the expected behaviour of the
deploy:deploy-file
goal in the maven deploy plugin 2.8.1 which I am currently
using to
deploy
one file.
It surprised me that no matter what I did I kept getting more
artifacts
deployed that I asked for and the reason is in the
org.apache.maven.plugin.deploy.DeployFileMojo.execute line 376
where
the
attached artifacts are also deployed.
Is this intended behaviour and if so how can I avoid this from
happening?
The goal name deploy-file indicates that one artifact (possible
incl.
pom/metadata) is to be deployed and not also a throng of other
artifacts.
I will be happy to provide a patch where this is aspect is
removed.
Thank you in advance
regards
Henrik Skriver Rasmussen
-
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
Re: Maven deploy plugin 2.8.1 - deploy-file goal - unable to avoid attachedArtifacts from being deployed in execute
:
Hi Anders
I have a multi-module project with this structure:
A (root and parent pom project)
- module 1 - builds a jar as artifact
- module 2 - uses module 1 jar artifact in assembly tries to deploy
the
assembled zip file to artifactory.
This is the module 2 pom file with inserted to replace project
specific names.
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
parent
groupId/groupId
artifactId/artifactId
version1.1-SNAPSHOT/version
/parent
artifactIdscripts/artifactId
packagingpom/packaging
namescripts/name
description/description
properties
project.build.sourceEncodingUTF-8/project.build.sourceEncoding
project.reporting.outputEncodingUTF-8/project.
reporting.outputEncoding
main.basedir${project.parent.basedir}/main.basedir
/properties
build
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-install-plugin/artifactId
version2.5.1/version
configuration
skiptrue/skip
/configuration
/plugin
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-assembly-plugin/artifactId
version2.4/version
configuration
skiptrue/skip
/configuration
/plugin
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-deploy-plugin/artifactId
version2.8.1/version
configuration
skiptrue/skip
/configuration
/plugin
/plugins
/build
profiles
profile
iddeployprofile/id
build
plugins
plugin
groupIdorg.codehaus.mojo/groupId
artifactIdexec-maven-plugin/artifactId
version1.2.1/version
executions
execution
idCopy into target folder and copy service jar into
files/default
/id
phasepackage/phase
goals
goalexec/goal
/goals
configuration
executable${project.basedir}/build_cookbook.sh/executable
arguments
argument${project.parent.artifactId}/argument
argument${project.parent.version}/argument
/arguments
/configuration
/execution
/executions
/plugin
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-assembly-plugin/artifactId
version2.4/version
executions
execution
iddeployprofile/id
phasepackage/phase
goals
goalsingle/goal
/goals
configuration
finalName${project.parent.artifactId}-${project.parent.version}
/finalName
outputDirectory${project.build.directory}//outputDirectory
filteringtrue/filtering
descriptors
descriptorassembly/dist.xml/descriptor
/descriptors
/configuration
/execution
/executions
/plugin
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-deploy-plugin/artifactId
executions
execution
idcookbook/id
phasedeploy/phase
goals
goaldeploy-file/goal
/goals
configuration
primaryArtifactfalse/primaryArtifact
repositoryIdartifactory/repositoryId
packagingzip/packaging
url${project.distributionManagement.
snapshotRepository.url}/url
generatePomfalse/generatePom
artifactId${project.parent.artifactId}/artifactId
groupId${project.parent.groupId}/groupId
version${project.parent.version}/version
classifierdeploymentfile/classifier
file
${project.build.directory}/${project.parent.artifactId}-${
project.parent.version}-deploymentfile.zip
/file
/configuration
/execution
/executions
/plugin
/plugins
/build
/profile
/profiles
/project
Med venlig hilsen
Henrik Skriver Rasmussen
On Thu, Feb 13, 2014 at 2:15 PM, Anders Hammar and...@hammar.net
wrote:
You need to provide more info on what you're doing! Is the
deploy:deploy-file bound to the build lifecycle of a project? How?
/Anders
On Thu, Feb 13, 2014 at 11:06 AM, Henrik Skriver Rasmussen
skrive...@gmail.com wrote:
Hi
I have a question about the expected behaviour of the
deploy:deploy-file
goal in the maven deploy plugin 2.8.1 which I am currently using to
deploy
one file.
It surprised me that no matter what I did I kept getting more
artifacts
deployed that I asked for and the reason is in the
org.apache.maven.plugin.deploy.DeployFileMojo.execute line 376
where
the
attached artifacts are also deployed.
Is this intended behaviour and if so how can I avoid this from
happening
Re: Maven deploy plugin 2.8.1 - deploy-file goal - unable to avoid attachedArtifacts from being deployed in execute
? /Anders On Thu, Feb 13, 2014 at 11:06 AM, Henrik Skriver Rasmussen skrive...@gmail.com wrote: Hi I have a question about the expected behaviour of the deploy:deploy-file goal in the maven deploy plugin 2.8.1 which I am currently using to deploy one file. It surprised me that no matter what I did I kept getting more artifacts deployed that I asked for and the reason is in the org.apache.maven.plugin.deploy.DeployFileMojo.execute line 376 where the attached artifacts are also deployed. Is this intended behaviour and if so how can I avoid this from happening? The goal name deploy-file indicates that one artifact (possible incl. pom/metadata) is to be deployed and not also a throng of other artifacts. I will be happy to provide a patch where this is aspect is removed. Thank you in advance regards Henrik Skriver Rasmussen - 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 deploy plugin 2.8.1 - deploy-file goal - unable to avoid attachedArtifacts from being deployed in execute
/execution
/executions
/plugin
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-deploy-plugin/artifactId
executions
execution
idcookbook/id
phasedeploy/phase
goals
goaldeploy-file/goal
/goals
configuration
primaryArtifactfalse/primaryArtifact
repositoryIdartifactory/repositoryId
packagingzip/packaging
url${project.distributionManagement.snapshotRepository.url}/url
generatePomfalse/generatePom
artifactId${project.parent.artifactId}/artifactId
groupId${project.parent.groupId}/groupId
version${project.parent.version}/version
classifierdeploymentfile/classifier
file
${project.build.directory}/${project.parent.artifactId}-${project.parent.version}-deploymentfile.zip
/file
/configuration
/execution
/executions
/plugin
/plugins
/build
/profile
/profiles
/project
Med venlig hilsen
Henrik Skriver Rasmussen
On Thu, Feb 13, 2014 at 2:15 PM, Anders Hammar and...@hammar.net
wrote:
You need to provide more info on what you're doing! Is the
deploy:deploy-file bound to the build lifecycle of a project? How?
/Anders
On Thu, Feb 13, 2014 at 11:06 AM, Henrik Skriver Rasmussen
skrive...@gmail.com wrote:
Hi
I have a question about the expected behaviour of the
deploy:deploy-file
goal in the maven deploy plugin 2.8.1 which I am currently using to
deploy
one file.
It surprised me that no matter what I did I kept getting more
artifacts
deployed that I asked for and the reason is in the
org.apache.maven.plugin.deploy.DeployFileMojo.execute line 376 where
the
attached artifacts are also deployed.
Is this intended behaviour and if so how can I avoid this from
happening?
The goal name deploy-file indicates that one artifact (possible incl.
pom/metadata) is to be deployed and not also a throng of other
artifacts.
I will be happy to provide a patch where this is aspect is removed.
Thank you in advance
regards
Henrik Skriver Rasmussen
Fwd: Maven deploy plugin 2.8.1 - deploy-file goal - unable to avoid attachedArtifacts from being deployed in execute
Hi I have a question about the expected behaviour of the deploy:deploy-file goal in the maven deploy plugin 2.8.1 which I am currently using to deploy one file. It surprised me that no matter what I did I kept getting more artifacts deployed that I asked for and the reason is in the org.apache.maven.plugin.deploy.DeployFileMojo.execute line 376 where the attached artifacts are also deployed. Is this intended behaviour and if so how can I avoid this from happening? The goal name deploy-file indicates that one artifact (possible incl. pom/metadata) is to be deployed and not also a throng of other artifacts. I will be happy to provide a patch where this is aspect is removed. Thank you in advance regards Henrik Skriver Rasmussen
Re: Maven deploy plugin 2.8.1 - deploy-file goal - unable to avoid attachedArtifacts from being deployed in execute
You need to provide more info on what you're doing! Is the deploy:deploy-file bound to the build lifecycle of a project? How? /Anders On Thu, Feb 13, 2014 at 11:06 AM, Henrik Skriver Rasmussen skrive...@gmail.com wrote: Hi I have a question about the expected behaviour of the deploy:deploy-file goal in the maven deploy plugin 2.8.1 which I am currently using to deploy one file. It surprised me that no matter what I did I kept getting more artifacts deployed that I asked for and the reason is in the org.apache.maven.plugin.deploy.DeployFileMojo.execute line 376 where the attached artifacts are also deployed. Is this intended behaviour and if so how can I avoid this from happening? The goal name deploy-file indicates that one artifact (possible incl. pom/metadata) is to be deployed and not also a throng of other artifacts. I will be happy to provide a patch where this is aspect is removed. Thank you in advance regards Henrik Skriver Rasmussen
Re: Maven deploy plugin 2.8.1 - deploy-file goal - unable to avoid attachedArtifacts from being deployed in execute
Hi Anders
I have a multi-module project with this structure:
A (root and parent pom project)
- module 1 - builds a jar as artifact
- module 2 - uses module 1 jar artifact in assembly tries to deploy the
assembled zip file to artifactory.
This is the module 2 pom file with inserted to replace project
specific names.
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
parent
groupId/groupId
artifactId/artifactId
version1.1-SNAPSHOT/version
/parent
artifactIdscripts/artifactId
packagingpom/packaging
namescripts/name
description/description
properties
project.build.sourceEncodingUTF-8/project.build.sourceEncoding
project.reporting.outputEncodingUTF-8/project.reporting.outputEncoding
main.basedir${project.parent.basedir}/main.basedir
/properties
build
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-install-plugin/artifactId
version2.5.1/version
configuration
skiptrue/skip
/configuration
/plugin
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-assembly-plugin/artifactId
version2.4/version
configuration
skiptrue/skip
/configuration
/plugin
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-deploy-plugin/artifactId
version2.8.1/version
configuration
skiptrue/skip
/configuration
/plugin
/plugins
/build
profiles
profile
iddeployprofile/id
build
plugins
plugin
groupIdorg.codehaus.mojo/groupId
artifactIdexec-maven-plugin/artifactId
version1.2.1/version
executions
execution
idCopy into target folder and copy service jar into files/default
/id
phasepackage/phase
goals
goalexec/goal
/goals
configuration
executable${project.basedir}/build_cookbook.sh/executable
arguments
argument${project.parent.artifactId}/argument
argument${project.parent.version}/argument
/arguments
/configuration
/execution
/executions
/plugin
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-assembly-plugin/artifactId
version2.4/version
executions
execution
iddeployprofile/id
phasepackage/phase
goals
goalsingle/goal
/goals
configuration
finalName${project.parent.artifactId}-${project.parent.version}
/finalName
outputDirectory${project.build.directory}//outputDirectory
filteringtrue/filtering
descriptors
descriptorassembly/dist.xml/descriptor
/descriptors
/configuration
/execution
/executions
/plugin
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-deploy-plugin/artifactId
executions
execution
idcookbook/id
phasedeploy/phase
goals
goaldeploy-file/goal
/goals
configuration
primaryArtifactfalse/primaryArtifact
repositoryIdartifactory/repositoryId
packagingzip/packaging
url${project.distributionManagement.snapshotRepository.url}/url
generatePomfalse/generatePom
artifactId${project.parent.artifactId}/artifactId
groupId${project.parent.groupId}/groupId
version${project.parent.version}/version
classifierdeploymentfile/classifier
file
${project.build.directory}/${project.parent.artifactId}-${project.parent.version}-deploymentfile.zip
/file
/configuration
/execution
/executions
/plugin
/plugins
/build
/profile
/profiles
/project
Med venlig hilsen
Henrik Skriver Rasmussen
On Thu, Feb 13, 2014 at 2:15 PM, Anders Hammar and...@hammar.net wrote:
You need to provide more info on what you're doing! Is the
deploy:deploy-file bound to the build lifecycle of a project? How?
/Anders
On Thu, Feb 13, 2014 at 11:06 AM, Henrik Skriver Rasmussen
skrive...@gmail.com wrote:
Hi
I have a question about the expected behaviour of the deploy:deploy-file
goal in the maven deploy plugin 2.8.1 which I am currently using to
deploy
one file.
It surprised me that no matter what I did I kept getting more artifacts
deployed that I asked for and the reason is in the
org.apache.maven.plugin.deploy.DeployFileMojo.execute line 376 where the
attached artifacts are also deployed.
Is this intended behaviour and if so how can I avoid this from happening?
The goal name deploy-file indicates that one artifact (possible incl.
pom/metadata) is to be deployed and not also a throng of other artifacts.
I will be happy to provide a patch where this is aspect is removed.
Thank you in advance
regards
Henrik Skriver Rasmussen
Re: Maven deploy plugin 2.8.1 - deploy-file goal - unable to avoid attachedArtifacts from being deployed in execute
behaviour of the deploy:deploy-file goal in the maven deploy plugin 2.8.1 which I am currently using to deploy one file. It surprised me that no matter what I did I kept getting more artifacts deployed that I asked for and the reason is in the org.apache.maven.plugin.deploy.DeployFileMojo.execute line 376 where the attached artifacts are also deployed. Is this intended behaviour and if so how can I avoid this from happening? The goal name deploy-file indicates that one artifact (possible incl. pom/metadata) is to be deployed and not also a throng of other artifacts. I will be happy to provide a patch where this is aspect is removed. Thank you in advance regards Henrik Skriver Rasmussen
Re: maven-deploy-plugin: exclude specific project artifact(s)?
Hello We use this to prevent deploying ears/wars into our repo. Everything is built but not everything gets deployed. Newer versions of the deploy plugin allow you to skip deployment so within a few specific poms you can add. plugin artifactIdmaven-deploy-plugin/artifactId version2.8.1/version configuration skiptrue/skip /configuration /plugin This should work as long as you assemble each piece separately (each has its own pom.xml) so divide and conquer. Hope this helps. -- Best Regards, Gord Cody Release Manager Zafin Labs Americas Inc. 179 Colonnade Road-Suite 100, Ottawa ON, Canada Phone: +1 (613) 216-2504 Fax: +1 (613) 688-1374 Mobile: +1 613-601-2734 Web: http://zafin.com Email: gordon.c...@zafin.com -- Zafin - Canada -- http://zafin.com http://zafin.com/ -- Connect with us http://www.youtube.com/user/ZafinGlobal http://www.linkedin.com/company/Zafin http://twitter.com/Zafin News and Events Zafin among Top 10 FinTech Companies to Watch in 2014: American Bankerhttp://zafin.com/zafin-among-top-10-fintech-companies-to-watch-in-2014-american-banker/
maven-deploy-plugin: exclude specific project artifact(s)?
I have a simple project that uses the assembly plugin to build a jar-with-dependencies and then a zip file containing the jar-with-dependencies and a shell script. When I run mvn deploy it deploys all three artifacts (the original jar, the jwd and the zip file) to Nexus. Is there a way to prevent deployment of the jar and jwd, and only upload the zip file to Nexus? I've read the maven-deploy-plugin documentation page but there doesn't seem to be a way to prevent those artifacts from being deployed. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: maven-deploy-plugin: exclude specific project artifact(s)?
Hi, Make sure it is not attached to the project. For assembly-plugin, see http://maven.apache.org/plugins/maven-assembly-plugin/single-mojo.html#attach Set this value to false. Robert Op Mon, 20 Jan 2014 21:28:49 +0100 schreef Jim Garrison jim.garri...@nwea.org: I have a simple project that uses the assembly plugin to build a jar-with-dependencies and then a zip file containing the jar-with-dependencies and a shell script. When I run mvn deploy it deploys all three artifacts (the original jar, the jwd and the zip file) to Nexus. Is there a way to prevent deployment of the jar and jwd, and only upload the zip file to Nexus? I've read the maven-deploy-plugin documentation page but there doesn't seem to be a way to prevent those artifacts from being deployed. - 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-deploy-plugin: exclude specific project artifact(s)?
Op Mon, 20 Jan 2014 21:28:49 +0100 schreef Jim Garrison I have a simple project that uses the assembly plugin to build a jar-with-dependencies and then a zip file containing the jar-with-dependencies and a shell script. When I run mvn deploy it deploys all three artifacts (the original jar, the jwd and the zip file) to Nexus. Is there a way to prevent deployment of the jar and jwd, and only upload the zip file to Nexus? I've read the maven-deploy-plugin documentation page but there doesn't seem to be a way to prevent those artifacts from being deployed. From: Robert Scholte Sent: Monday, January 20, 2014 2:00 PM To: Maven Users List Subject: Re: maven-deploy-plugin: exclude specific project artifact(s)? Make sure it is not attached to the project. For assembly-plugin, see http://maven.apache.org/plugins/maven-assembly-plugin/single- mojo.html#attach Set this value to false. I can do that for the jar-with-dependencies but I don't see a way to unattach the primary jar from the project. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
maven deploy plugin fails with artifact-not-found
I’m trying to deploy a snapshot version of the artifact for the first time. Maven deploy fails with error “could not find artifact in the remote repository” Obviously the artifact was never deployed in the remote repository, so it is not available in the remote repository. Tried with various versions of “deploy” plugin, the issue happens in all of them. How to deploy a snapshot version on an empty repository? $mvn org.apache.maven.plugins:maven-deploy-plugin:2.8.1:deploy [INFO] Scanning for projects... [WARNING] [WARNING] Some problems were encountered while building the effective model for com.ebay.platform:platform-root:pom:2.0.0.RC3-SNAPSHOT [WARNING] 'dependencyManagement.dependencies.dependency.(groupId:artifactId:type:classifier)' must be unique: javax.servlet:jstl:jar - version 1.2 vs 1.2_1 @ line 515, column 16 [WARNING] 'dependencyManagement.dependencies.dependency.(groupId:artifactId:type:classifier)' must be unique: com.sun.xml.bind:jaxb-impl:jar - duplicate declaration of version 2.2.3.20110115 @ line 536, column 16 [WARNING] [WARNING] It is highly recommended to fix these problems because they threaten the stability of your build. [WARNING] [WARNING] For this reason, future Maven versions might no longer support building such malformed projects. [WARNING] [INFO] [INFO] [INFO] Building platform root pom 2.0.0.RC3-SNAPSHOT [INFO] [INFO] [INFO] --- maven-deploy-plugin:2.8.1:deploy (default-cli) @ platform-root --- Downloading: http://repocorp.com/content/repositories/snapshots/com/ebay/platform/platform-root/2.0.0.RC3-SNAPSHOT/maven-metadata.xml Uploading: http://repocorp.com/content/repositories/snapshots/com/ebay/platform/platform-root/2.0.0.RC3-SNAPSHOT/platform-root-2.0.0.RC3-20131213.165021-1.pom [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 2.576s [INFO] Finished at: Fri Dec 13 08:50:21 PST 2013 [INFO] Final Memory: 9M/156M [INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.8.1:deploy (default-cli) on project platform-root: Failed to deploy artifacts: Could not find artifact com.platform:platform-root:pom:2.0.0.RC3-20131213.165021-1 in snapshots (http://repocorp.com/content/repositories/snapshots/) - [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/MojoExecutionException
Re: maven deploy plugin fails with artifact-not-found
Hi, I’m trying to deploy a snapshot version of the artifact for the first time. Maven deploy fails with error “could not find artifact in the remote repository” Obviously the artifact was never deployed in the remote repository, so it is not available in the remote repository. Tried with various versions of “deploy” plugin, the issue happens in all of them. How to deploy a snapshot version on an empty repository? $mvn org.apache.maven.plugins:maven-deploy-plugin:2.8.1:deploy You try to deploy something that has to be built first, a step that is skipped in your case. Try mvn deploy instead. HTH Thorsten
Re: maven deploy plugin fails with artifact-not-found
Yes, did try ³mvm deploy². But it fails in an empty repo. This is a parent pom file ( packaging = pom ). This pom contains dependencyManagement section and distributionManagement section that¹s all. On 12/13/13, 10:07 AM, Thorsten Heit thorsten.h...@vkb.de wrote: Hi, I¹m trying to deploy a snapshot version of the artifact for the first time. Maven deploy fails with error ³could not find artifact in the remote repository² Obviously the artifact was never deployed in the remote repository, so it is not available in the remote repository. Tried with various versions of ³deploy² plugin, the issue happens in all of them. How to deploy a snapshot version on an empty repository? $mvn org.apache.maven.plugins:maven-deploy-plugin:2.8.1:deploy You try to deploy something that has to be built first, a step that is skipped in your case. Try mvn deploy instead. HTH Thorsten - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Apache Maven Deploy Plugin 2.8.1 Released
The Apache Maven team is pleased to announce the release of the Apache Maven Deploy Plugin, version 2.8.1 This plugin plugin is primarily used during the deploy phase, to add your artifact(s) to a remote repository for sharing with other developers and projects. http://maven.apache.org/plugins/maven-deploy-plugin/ You should specify the version in your project's plugin configuration: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-deploy-plugin/artifactId version2.8.1/version /plugin Release Notes - Maven Deploy Plugin - Version 2.8.1 ** Bug * [MDEPLOY-169] - deployAtEnd broken with parallel builds * [MDEPLOY-170] - Plugin configuration on module level is ignored when deployAtEnd Enjoy, -The Apache Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Apache Maven Deploy Plugin 2.8 Released
The Apache Maven team is pleased to announce the release of the Apache Maven Deploy Plugin, version 2.8 This plugin is primarily used during the deploy phase, to add your artifact(s) to a remote repository for sharing with other developers and projects. http://maven.apache.org/plugins/maven-deploy-plugin/ You should specify the version in your project's plugin configuration: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-deploy-plugin/artifactId version2.8/version /plugin Release Notes - Maven Deploy Plugin - Version 2.8 ** Bug * [MDEPLOY-68] - altDeploymentRepository allows dangerous deploy processes * [MDEPLOY-145] - Documentation does not list layouts ** Improvement * [MDEPLOY-154] - Rewrite page 'deploy with classifier' ** New Feature * [MDEPLOY-157] - Add deployAtEnd option for multimodule projects ** Task * [MDEPLOY-151] - use maven-plugin-tools' java 5 annotations Enjoy, -The Apache Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Maven Deploy Plugin and Nexus Meta Data update of LATEST failing
Hi all, I've upgraded to the latest maven deploy plugin and hte latest nexus OSS version. I hoped that between the two that the updating of the LATEST meta-data would work when doing a relase (See http://stackoverflow.com/questions/4878808/maven-metadata-xml-is-not-updated-when-deploying-to-nexusas a reference). This doesn't appear to be the case, does anyone else know of another mail thread / JIRA issue tracking this? Cheers, Martijn
Maven deploy plugin
Hi, when using the maven deploy plugin, can I change the name of the file being uploaded to Nexus. ?? Like the maven-ear-plugin has the finalName. Now the file just gets the name artifactId
Re: Maven deploy plugin
The Maven Deploy Plugin has one function: deploying artifacts to a Maven
repository.
A Maven repository has a strict layout:
URL +
groupId.replaceAll('.','/')+/+artifactId+/+version.replace(-\d{8}\.\d{6}-\d+$,-SNAPSHOT)+/+artifactId+-+version+(classifier
== null ? : -+classifier) + . + type
If you want to deploy with a different pattern, you need to use a different
plugin
On 1 May 2013 17:06, Kristian Lind klpc...@gmail.com wrote:
Hi, when using the maven deploy plugin, can I change the name of the file
being uploaded to Nexus. ??
Like the maven-ear-plugin has the finalName.
Now the file just gets the name artifactId
Re: Maven deploy plugin
Hi, when using the maven deploy plugin, can I change the name of the file being uploaded to Nexus. ?? No. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Using the Maven Deploy Plugin
On Sun, Aug 5, 2012 at 6:23 AM, chan channas...@yahoo.com wrote: Hi all, Even I've setup this to local repository for deploy http://localhost:8081/nexus/index.html#view-repoitories BUT it gives me the same 400 error above... What error is that? @I've tried all the solutions suggested before, but nothing worked. Even I deleted the earlier from local file system repository... Any clue? -- View this message in context: http://maven.40175.n5.nabble.com/Using-the-Maven-Deploy-Plugin-tp126828p5716127.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: Using the Maven Deploy Plugin
Hi all, Even I've setup this to local repository for deploy http://localhost:8081/nexus/index.html#view-repositories BUT it gives me the same 400 error above... @I've tried all the solutions suggested before, but nothing worked. Even I deleted the earlier from local file system repository... Any clue? -- View this message in context: http://maven.40175.n5.nabble.com/Using-the-Maven-Deploy-Plugin-tp126828p5716127.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
Maven deploy plugin: altDeploymentRepository: snapshots OK?
If I am deploying a SNAPSHOT artifact, but I wish to supply the altDeploymentRepository property on the command line, is Maven or the plugin smart enough to realize that I'm deploying a SNAPSHOT? I ask because the regular distributionManagement element has *two* entries: one for releases, and one for snapshots. I would have expected a corresponding duality in the properties I could pass (e.g. altDeploymentSnapshotRepository or something). Best, Laird -- http://about.me/lairdnelson
Re: Maven deploy plugin: altDeploymentRepository: snapshots OK?
Use something like
distributionManagement
snapshotRepository
id${distMgmtSnapshotsId}/id
name${distMgmtSnapshotsName}/name
url${distMgmtSnapshotsUrl}/url
/snapshotRepository
/distributionManagement
properties
distMgmtSnapshotsIdSnapshot Repository/distMgmtSnapshotsId
distMgmtSnapshotsNameSnapshot Repository/distMgmtSnapshotsName
distMgmtSnapshotsUrlhttp://host:port/repository/snapshots//distMgmtSnapshotsUrl
/properties
You have correct default values and you can override with -D ...
2012/3/21 Laird Nelson ljnel...@gmail.com:
If I am deploying a SNAPSHOT artifact, but I wish to supply the
altDeploymentRepository property on the command line, is Maven or the
plugin smart enough to realize that I'm deploying a SNAPSHOT?
I ask because the regular distributionManagement element has *two*
entries: one for releases, and one for snapshots.
I would have expected a corresponding duality in the properties I could
pass (e.g. altDeploymentSnapshotRepository or something).
Best,
Laird
--
http://about.me/lairdnelson
--
Olivier Lamy
Talend: http://coders.talend.com
http://twitter.com/olamy | http://linkedin.com/in/olamy
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven deploy plugin: altDeploymentRepository: snapshots OK?
On Wed, Mar 21, 2012 at 2:10 PM, Olivier Lamy ol...@apache.org wrote:
Use something like
distributionManagement
snapshotRepository
id${distMgmtSnapshotsId}/id
name${distMgmtSnapshotsName}/name
url${distMgmtSnapshotsUrl}/url
/snapshotRepository
/distributionManagement
properties
distMgmtSnapshotsIdSnapshot Repository/distMgmtSnapshotsId
distMgmtSnapshotsNameSnapshot Repository/distMgmtSnapshotsName
distMgmtSnapshotsUrlhttp://host:port
/repository/snapshots//distMgmtSnapshotsUrl
/properties
You have correct default values and you can override with -D ...
Oh, DUH, yes, that would do it. Thanks!
For completeness, are you saying that if I tried to simply specify the
altDeploymentRepository with a SNAPSHOT deployment it would fail?
Best,
Laird
--
http://about.me/lairdnelson
Re: Maven deploy plugin: altDeploymentRepository: snapshots OK?
On Wed, Mar 21, 2012 at 19:18, Laird Nelson ljnel...@gmail.com wrote:
On Wed, Mar 21, 2012 at 2:10 PM, Olivier Lamy ol...@apache.org wrote:
Use something like
distributionManagement
snapshotRepository
id${distMgmtSnapshotsId}/id
name${distMgmtSnapshotsName}/name
url${distMgmtSnapshotsUrl}/url
/snapshotRepository
/distributionManagement
properties
distMgmtSnapshotsIdSnapshot Repository/distMgmtSnapshotsId
distMgmtSnapshotsNameSnapshot Repository/distMgmtSnapshotsName
distMgmtSnapshotsUrlhttp://host:port
/repository/snapshots//distMgmtSnapshotsUrl
/properties
You have correct default values and you can override with -D ...
Oh, DUH, yes, that would do it. Thanks!
For completeness, are you saying that if I tried to simply specify the
altDeploymentRepository with a SNAPSHOT deployment it would fail?
No, when your version is a SNAPSHOT *and* your provide the correct
syntax this should work:
Given you have something like this in your pom:
distributionManagement
snapshotRepository
idsonatype-nexus-snapshots/id
urlhttps://oss.sonatype.org/content/repositories/snapshots//url
/snapshotRepository
repository
idsonatype-nexus-staging/id
urlhttps://oss.sonatype.org/service/local/staging/deploy/maven2//url
/repository
/distributionManagement
I use:
mvn -e clean install deploy
-DaltDeploymentRepository=ui-snapshots::default::http://localhost:8081/artifactory/libs-snapshot-local/
to deploy SNAPSHOTs into a locally running artifactory instance. The
id of your repository should be matched by the username/password
entries in your $HOME/.m2/settings.xml.
Regards
Mirko
Regards
Mirko
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: maven-deploy-plugin 2.7
configuration
url${project.distributionManagement.repository.url}/url
repositoryIdsnapshots/repositoryId
file${dist.dir.client}/${client.jar.arnes.name}.jar/file
Generally people are using deploy:deploy-file by specifying all
parameters as -D on the command line. What are you trying to achieve
with this configuration?
Wayne
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
maven-deploy-plugin 2.7
Plugin fail to read url tag as variable:
project.distributionManagement.repository.url
and url is HTTTP based protokol
execution
phasedeploy/phase
goals
goaldeploy-file/goal
/goals
configuration
url${project.distributionManagement.repository.url}/url
repositoryIdsnapshots/repositoryId
file${dist.dir.client}/${client.jar.arnes.name}.jar/file
Error:
The parameters 'file', 'url' for goal
org.apache.maven.plugins:maven-deploy-plugin:2.7:deploy-file are missing or
invalid
Another maven plugin with bad documentation or error output, maven is so
unpredictable building tool.
Regards, Tomaz
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
maven-deploy-plugin: package vs deploy phase
I have a call to maven-deploy-plugin bound to package phase that works correctly when I call maven clean package but if I call maven clean deploy I get: java.lang.IllegalStateException: Cannot add two different pieces of metadata for: project com.thomsonreuters.images:icon-Remove (We are using maven-deploy-plugin to push an image file, icon-Remove-1.0.gif, to our maven repo server, Artifactory.) I'm just wondering if anybody can explain what Maven is tripping over. Thanks, Greg -- View this message in context: http://maven.40175.n5.nabble.com/maven-deploy-plugin-package-vs-deploy-phase-tp4807342p4807342.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: maven-deploy-plugin: package vs deploy phase
Hi Greg, Greg Sandell wrote: I have a call to maven-deploy-plugin bound to package phase that works correctly when I call maven clean package but if I call maven clean deploy I get: java.lang.IllegalStateException: Cannot add two different pieces of metadata for: project com.thomsonreuters.images:icon-Remove (We are using maven-deploy-plugin to push an image file, icon-Remove-1.0.gif, to our maven repo server, Artifactory.) I'm just wondering if anybody can explain what Maven is tripping over. not sure about that. But you may want to look at the build-helper:attach-artifact goal http://mojo.codehaus.org/build-helper-maven-plugin/attach-artifact-mojo.html to push your image. This might be closer to the Maven Way of doing things. Hope this helps. Andreas - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Maven GPG Plugin 1.4 and Maven Deploy Plugin 2.7 Released
Subject: The Maven team is pleased to announce the release of the Maven GPG Plugin, version 1.4 and the Maven Deploy Plugin, version 2.7 The Maven GPG plugin signs all of the project's attached artifacts with GnuPG. The Maven Deploy plugin is primarily used during the deploy phase, to add your artifact(s) to a remote repository for sharing with other developers and projects. This is usually done in an integration or release environment. It can also be used to deploy a particular artifact (e.g. a third party jar like Sun's non redistributable reference implementations). http://maven.apache.org/plugins/maven-gpg-plugin/ http://maven.apache.org/plugins/maven-deploy-plugin/ You should specify the version in your project's plugin configuration: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-gpg-plugin/artifactId version1.4/version /plugin plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-deploy-plugin/artifactId version2.7/version /plugin Release Notes - Maven 2.x and 3.x GPG Plugin - Version 1.4 ** Bug * [MGPG-37] - retryFailedDeploymentCount is actually just plain retry deployment ** New Feature * [MGPG-38] - gpg:sign-and-deploy Allow deployment of multiple side artifacts at the same time via the CLI Release Notes - Maven 2.x and 3.x Deploy Plugin - Version 2.7 ** Bug * [MDEPLOY-127] - Mark deploy plugin as @threadSafe for maven3 * [MDEPLOY-132] - Discrepancy between pom syntax for artifacts and deploy:deploy-file parameters * [MDEPLOY-136] - retryFailedDeploymentCount is actually just plain retry deployment ** Improvement * [MDEPLOY-134] - mvn deploy:deploy-file should allow to add an arbitrary number of attached artifacts not only sources and javadoc ** New Feature * [MDEPLOY-133] - Add a configurable parameter to allow retrying deployment * [MDEPLOY-137] - deploy:file Allow deployment of multiple side artifacts at the same time via the CLI Enjoy, -The Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Maven Deploy Plugin 2.6 Released
The Maven team is pleased to announce the release of the Maven Deploy Plugin, version 2.6 This plugin allows artifacts to be deployed to a Maven repository. See the plugin's site for more details: http://maven.apache.org/plugins/maven-deploy-plugin/ You should specify the version in your project's plugin configuration: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-deploy-plugin/artifactId version2.6/version /plugin Release Notes - Maven 2.x Deploy Plugin - Version 2.6 ** Bug * [MDEPLOY-112] - deployed snapshot name has different build numbers for multiple artifacts of the same build * [MDEPLOY-123] - http://maven.apache.org/plugins/maven-deploy-plugin/usage.html says maven does not support password hashing ** Improvement * [MDEPLOY-48] - deploy:deploy-file does not support deploying sources jars too * [MDEPLOY-106] - Packaging should not always be required. Enjoy, -The Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven deploy plugin increments buildNumber twice during a single invocation of mvn deploy
On 2 October 2010 13:37, Benjamin Bentmann benjamin.bentm...@udo.eduwrote: In case you refer to the pde-maven-plugin ( http://mojo.codehaus.org/pde-maven-plugin/), you should fill this as a bug at http://jira.codehaus.org/browse/MOJO/component/12535, its EclipsePDEAttachMojo.java uses the wrong way to attach the artifact. Thanks Benjamin. I'll file an issue report. Just wanted to check first if anyone else had encountered similar issues, and that I wasn't doing anything stupid! Regards Daniel
Re: Maven deploy plugin increments buildNumber twice during a single invocation of mvn deploy
Daniel Patton wrote: However, the ZIP file (which is the attached artifact produced by the maven-pde-plugin) is given a buildNumber of 4, and if I check the maven-metadata.xml file, the buildNumber has indeed been incremented twice. In case you refer to the pde-maven-plugin (http://mojo.codehaus.org/pde-maven-plugin/), you should fill this as a bug at http://jira.codehaus.org/browse/MOJO/component/12535, its EclipsePDEAttachMojo.java uses the wrong way to attach the artifact. Benjamin - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Maven deploy plugin increments buildNumber twice during a single invocation of mvn deploy
Dear Maven Users,
I am using the maven-deploy-plugin to deploy snapshot builds to a shared
repository. This works fine for all my standard projects, but I have one
project that uses the maven-pde-plugin to build an Eclipse plugin, and this
involves attaching an extra artifact to the build. My POM packaging type
for this project is is pom, mainly because I couldn't get the
maven-pde-plugin to work with any other packaging type. The build process
works fine, and I can install the generated artifacts to my local repository
using mvn install, but as soon as I try mvn deploy to upload the
artifacts to my shared repository, everything goes pear-shaped.
Specifically, there are 2 artifacts produced by the build: a POM file and a
ZIP file. The POM file is given the buildNumber I would expect - e.g. if
the latest buildNumber is 2, it would be given buildNumber 3. However, the
ZIP file (which is the attached artifact produced by the maven-pde-plugin)
is given a buildNumber of 4, and if I check the maven-metadata.xml file, the
buildNumber has indeed been incremented twice.
Sample output from mvn deploy (with company-specific information cunningly
blanked out):
[INFO] [deploy:deploy {execution: default-deploy}]
[INFO] Retrieving previous build number from inhouse_snapshot_xxx
Uploading:
http://123.123.123.123:8081/nexus/content/repositories/snapshots/com/xx/xxx/xxx-eclipse-plugin/xxx-SNAPSHOT/xxx-eclipse-plugin-xxx-20101001.150902-3.pom
4K uploaded (xxx-eclipse-plugin-xxx-20101001.150902-3.pom)
[INFO] Retrieving previous metadata from inhouse_snapshot_xxx
[INFO] Uploading repository metadata for: 'artifact
com.xx.xxx:xxx-eclipse-plugin'
[INFO] Retrieving previous metadata from inhouse_snapshot_xxx
[INFO] Uploading repository metadata for: 'snapshot
com.xx.xxx:xxx-eclipse-plugin:xxx-SNAPSHOT'
[INFO] Retrieving previous build number from inhouse_snapshot_xxx
Uploading:
http://123.123.123.123:8081/nexus/content/repositories/snapshots/com/xx/xxx/xxx-eclipse-plugin/xxx-SNAPSHOT/xxx-eclipse-plugin-xxx-20101001.150902-4.zip
27K uploaded (xxx-eclipse-plugin-xxx-20101001.150902-4.zip)
[INFO] Retrieving previous metadata from inhouse_snapshot_xxx
[INFO] Uploading repository metadata for: 'artifact
com.xx.xxx:xxx-eclipse-plugin'
[INFO] Retrieving previous metadata from inhouse_snapshot_xxx
[INFO] Uploading repository metadata for: 'snapshot
com.xx.xxx:xxx-eclipse-plugin:xxx-SNAPSHOT'
As you can see, the POM file has the suffix -3.pom whereas the ZIP file
has the suffix -4.zip. I've searched the maven-deploy-plugin JIRA for
similar issues and found a few that appear to show the same behaviour
(MDEPLOY-27, MDEPLOY-32 and MDEPLOY-33), but they all appear to have been
marked as Fixed long ago.
Any assistance on this would be greatly appreciated. Thanks in advance.
Regards
Daniel Patton
patton@gmail.com
maven-deploy-plugin hangs when deploying artifacts
Hi all guys,
in the middle of the release process in apache-commons I met a strage
behavior in the maven-deploy-plugin: the scp in people.apache.org
requires interactive password (even if set in settings.xml) so when
trying to upload, it prompts for the password. It nicely works when
deploying stuff on my space ~simonetripodi.
When trying to scp for the commons-digester release, the following
message appears:
[INFO] [INFO] [deploy:deploy {execution: default-deploy}]
[INFO]
[INFO]
[INFO] Note that too many successive login failures will result in further
[INFO] logins from your IP address being blocked. If this happens, contact
[INFO] infrastruct...@apache.org, mentioning your IP address so that it can
[INFO] be unblocked.
[INFO]
[INFO]
[INFO] : Keyboard interactive required, supplied password is ignored
and STOP, the plugin seems to be stalled :( If I type a right or wrong
password it doesn't mind, the execution is suspended. If I type
CTRL+C, so the following message is printed:
^CDestroying 1 processes
Destroying process..
[INFO] Destroyed 1 processes
Password: :
Can anyone help me please? That's going to drive me crazy ;( Many many
thanks in advance
Simo
http://people.apache.org/~simonetripodi/
http://www.99soft.org/
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: maven-deploy-plugin hangs when deploying artifacts
Resolved, just to let you know: invoking the release-plugin with
-DmavenExecutorId=forked-path the prompt won't be lost :)
have a nice day,
Simo
http://people.apache.org/~simonetripodi/
http://www.99soft.org/
On Sat, Sep 11, 2010 at 9:44 AM, Simone Tripodi
simone.trip...@gmail.com wrote:
Hi all guys,
in the middle of the release process in apache-commons I met a strage
behavior in the maven-deploy-plugin: the scp in people.apache.org
requires interactive password (even if set in settings.xml) so when
trying to upload, it prompts for the password. It nicely works when
deploying stuff on my space ~simonetripodi.
When trying to scp for the commons-digester release, the following
message appears:
[INFO] [INFO] [deploy:deploy {execution: default-deploy}]
[INFO]
[INFO]
[INFO] Note that too many successive login failures will result in further
[INFO] logins from your IP address being blocked. If this happens, contact
[INFO] infrastruct...@apache.org, mentioning your IP address so that it can
[INFO] be unblocked.
[INFO]
[INFO]
[INFO] : Keyboard interactive required, supplied password is ignored
and STOP, the plugin seems to be stalled :( If I type a right or wrong
password it doesn't mind, the execution is suspended. If I type
CTRL+C, so the following message is printed:
^CDestroying 1 processes
Destroying process..
[INFO] Destroyed 1 processes
Password: :
Can anyone help me please? That's going to drive me crazy ;( Many many
thanks in advance
Simo
http://people.apache.org/~simonetripodi/
http://www.99soft.org/
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
maven deploy plugin
All mentioned projects inherit from the same parent-POM. I have several maven project which produce small (50k-300k) JAR files. All of these deploy fine to Archiva. I have one maven project that is similar in structure to all the rest that produces a 2M JAR. This project will not deploy to Archiva. It exits with the following exception: [ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.4:deploy (default-deploy) on project nielsenUtilities: Error deploying artifact: Transfer error: The server did not respond within the configured timeout. - [Help 1] I have searched far and wide for a reason/explanation/fix for this error. Has anyone encountered such an issue? I am thinking that it is some kind of timeout on the maven side. Maven does not receive a response within a reasonable amount of time, and exits as though it were an error. -- View this message in context: http://maven.40175.n5.nabble.com/maven-deploy-plugin-tp2265826p2265826.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: maven deploy plugin
of these deploy fine to Archiva. I have one maven project that is similar in structure to all the rest that produces a 2M JAR. This project will not deploy to Archiva. It exits with the following exception: Did you post this on the Archiva list? They may know about a defect either in Maven or Archiva (or their interaction) which is triggering this error. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Problem using maven-deploy-plugin against an https server via proxy
Hi, I am trying to deploy a snapshot of an Apache project to https://repository.apache.org/content/repositories/snapshots. From my point of view, the configuration is correct: I have a server entry in my settings.xml and I have configured an https proxy. (See Adding User-Agent configuration and Using Proxy: ... below.) Nevertheless, the deploy-plugin fails with the following error message: Caused by: java.net.UnknownHostException: repository.apache.org In other words, it seems that the proxy is unused and a direct connection is attempted, which, of course, fails. (We can't even resolve external host names in the corporate network.) Maven version: bash-3.2$ mvn --version Apache Maven 2.2.1 (r801777; 2009-08-06 21:16:01+0200) Any ideas what I might try? Thanks, Jochen -- Germanys national anthem is the most boring in the world - how telling! [INFO] Retrieving previous build number from apache.snapshots.https [DEBUG] Using Wagon implementation lightweight from default mapping for protocol https [DEBUG] Checking for pre-existing User-Agent configuration. [DEBUG] Adding User-Agent configuration. [DEBUG] Connecting to repository: 'apache.snapshots.https' with url: 'https://repository.apache.org/content/repositories/snapshots'. [DEBUG] Using Proxy: 10.175.249.65 [DEBUG] Using Wagon implementation lightweight from default mapping for protocol https [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Error retrieving previous build number for artifact 'org.apache.rat:apache-rat-project:pom': repository metadata for: 'snapshot org.apache.rat:apache-rat-project:0.7-SNAPSHOT' could not be retrieved from repository: apache.snapshots.https due to an error: Error transferring file: repository.apache.org [INFO] [DEBUG] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Error retrieving previous build number for artifact 'org.apache.rat:apache-rat-project:pom': repository metadata for: 'snapshot org.apache.rat:apache-rat-project:0.7-SNAPSHOT' could not be retrieved from repository: apache.snapshots.https due to an error: Error transferring file: repository.apache.org at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:719) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138) at org.apache.maven.cli.MavenCli.main(MavenCli.java:362) at org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.plugin.MojoExecutionException: Error retrieving previous build number for artifact 'org.apache.rat:apache-rat-project:pom': repository metadata for: 'snapshot org.apache.rat:apache-rat-project:0.7-SNAPSHOT' could not be retrieved from repository: apache.snapshots.https due to an error: Error transferring file: repository.apache.org at org.apache.maven.plugin.deploy.DeployMojo.execute(DeployMojo.java:189) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694) ... 17 more Caused by: org.apache.maven.artifact.deployer.ArtifactDeploymentException: Error retrieving previous build number for artifact 'org.apache.rat:apache-rat-project:pom': repository metadata for: 'snapshot org.apache.rat:apache-rat-project:0.7-SNAPSHOT' could not be retrieved from repository: apache.snapshots.https due to an error: Error transferring file: repository.apache.org
maven-deploy-plugin differences between 2.4 and 2.5
I tried to upgrade to version 2.5 and I started to get the following error all projects that we using the assembly to attach artifacts. It works correctly on my jar, war and pom only projects though. Does anyone have any idea why this happening? [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Internal error in the plugin manager executing goal 'org.apache.maven.plugins:maven-deploy-plugin:2.5:deploy': Unable to find the mojo 'deploy' (or one of its required components) in the plugin 'org.apache.maven.plugins:maven-deploy-plugin' Component descriptor cannot be found in the component repository: org.apache.maven.artifact.repository.layout.ArtifactRepositoryLayoutflat . [INFO] [INFO] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Internal error in the plugin manager executing goal 'org.apache.maven.plugins:maven-deploy-plugin:2.5:deploy': Unable to find the mojo 'deploy' (or one of its required components) in the plugin 'org.apache.maven.plugins:maven-deploy-plugin' at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Default LifecycleExecutor.java:698) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifec ycle(DefaultLifecycleExecutor.java:556) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultL ifecycleExecutor.java:535) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandle Failures(DefaultLifecycleExecutor.java:387) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments( DefaultLifecycleExecutor.java:348) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifec ycleExecutor.java:180) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138) at org.apache.maven.cli.MavenCli.main(MavenCli.java:362) at org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav a:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor Impl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.plugin.PluginManagerException: Unable to find the mojo 'deploy' (or one of its required components) in the plugin 'org.apache.maven.plugins:maven-deploy-plugin' at org.apache.maven.plugin.DefaultPluginManager.getConfiguredMojo(DefaultPl uginManager.java:674) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginMa nager.java:468) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Default LifecycleExecutor.java:694) ... 17 more Caused by: org.codehaus.plexus.component.repository.exception.ComponentLookupExcept ion: Unable to lookup component 'org.apache.maven.plugin.Mojoorg.apache.maven.plugins:maven-deploy-plugi n:2.5:deploy', it could not be started at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer .java:339) at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer .java:440) at org.apache.maven.plugin.DefaultPluginManager.getConfiguredMojo(DefaultPl uginManager.java:652) ... 19 more Caused by: org.codehaus.plexus.component.repository.exception.ComponentLifecycleExc eption: Error starting component at org.codehaus.plexus.component.manager.AbstractComponentManager.startComp onentLifecycle(AbstractComponentManager.java:109) at org.codehaus.plexus.component.manager.AbstractComponentManager.createCom ponentInstance(AbstractComponentManager.java:95) at org.codehaus.plexus.component.manager.PerLookupComponentManager.getCompo nent(PerLookupComponentManager.java:48) at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer .java:331) ... 21 more Caused by: org.codehaus.plexus.personality.plexus.lifecycle.phase.PhaseExecutionExc eption: Error composing component at
Re: Error from maven deploy plugin during release:perform
Hi Ron, Did you end up solving this issue or did you perhaps find a workaround? I'm facing exactly the same issue. (The module deploys fine when using mvn deploy, but not when it is deployed during a mvn release:perform) In my case the project is an ear module in a multi module project. What makes it even weirder is that the distributionManagement section is defined in the parent pom, thus shared by all the other modules. And on all the other modules the deploy works during a release:perform as well. Puzzled Kind regards, Stijn rsmith wrote: I'm trying to sign release my project artifacts to a maven repository. I'm currently getting the following error when executing: mvn -e -X release:perform -Dgpg.useagent=true -Darguments=-Dgpg.useagent=true [INFO] [DEBUG] Configuring mojo 'org.apache.maven.plugins:maven-deploy-plugin:2.4:deploy' -- [INFO] [DEBUG] (f) artifact = org.pyant.tasks:pyAntTasks:jar:1.3.1 [INFO] [DEBUG] (f) attachedArtifacts = [org.pyant.tasks:pyAntTasks:java-source:sources:1.3.1, org.pyant.tasks:pyAntTasks:javadoc:javadoc:1.3.1, org.pyant.tasks:pyAntTasks:jar.asc:1.3.1, org.pyant.tasks:pyAntTasks:pom.asc:1.3.1, org.pyant.tasks:pyAntTasks:asc:sources.jar:1.3.1, org.pyant.tasks:pyAntTasks:asc:javadoc.jar:1.3.1] [INFO] [INFO] [INFO] [ERROR] BUILD ERROR [INFO] [INFO] [INFO] [INFO] Failed to configure plugin parameters for: org.apache.maven.plugins:maven-deploy-plugin:2.4 [INFO] [INFO] check that the following section of the pom.xml is present and correct: [INFO] [INFO] distributionManagement [INFO] !-- use the following if you're not using a snapshot version. -- [INFO] repository [INFO] idrepo/id [INFO] nameRepository Name/name [INFO] urlscp://host/path/to/repo/url [INFO] /repository [INFO] !-- use the following if you ARE using a snapshot version. -- [INFO] snapshotRepository [INFO] idrepo/id [INFO] nameRepository Name/name [INFO] urlscp://host/path/to/repo/url [INFO] /snapshotRepository [INFO] /distributionManagement [INFO] [INFO] Cause: Class 'org.apache.maven.artifact.repository.ArtifactRepository' cannot be instantiated [INFO] [INFO] [INFO] [DEBUG] Trace [INFO] org.apache.maven.lifecycle.LifecycleExecutionException: Error configuring: org.apache.maven.plugins:maven-deploy-plugin. Reason: Unable to parse the created DOM for plugin configuration [INFO] at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:723) [INFO] at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556) [INFO] at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535) [INFO] at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387) [INFO] at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348) ... Section of my distributionManagement section: distributionManagement repository idsonatype-nexus-staging/id nameNexus Release Repository/name urlhttp://oss.sonatype.org/service/local/staging/deploy/maven2/url /repository snapshotRepository idsonatype-nexus-snapshots/id nameSonatype Nexus Snapshots/name urlhttp://oss.sonatype.org/service/local/staging/deploy/maven2/url /snapshotRepository /distributionManagement Info on my environment: Apache Maven 2.2.1 (r801777; 2009-08-06 14:16:01-0500) Java version: 1.6.0_17 Java home: /System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Home Default locale: en_US, platform encoding: MacRoman OS name: mac os x version: 10.6.2 arch: x86_64 Family: mac I've searched google/forums for solutions but haven't turned anything up. Anyone seen this before or know what I might try? Regards, Ron -- View this message in context: http://n2.nabble.com/Error-from-maven-deploy-plugin-during-release-perform-tp4822554p4822554.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 -- View this message in context: http://old.nabble.com/Error-from-maven-deploy-plugin-during-release%3Aperform-tp28078671p28618818.html Sent from the Maven - Users mailing list archive at Nabble.com
doubt in maven-deploy plugin : deploy-file goal
Hi, have a doubt in maven-deploy plugin 2.5 version. For deploy-file goal , they make a sanity check to see whether the file to be deployed is present in the local repository and if so they fail the deploy goal. I believe 2.4 version didn't do that. So why is it illegal to deploy artifact from the local repository? (is it because we use this option only to deploy third party artifacts to the repository?) thanks, Srinivas
Re: doubt in maven-deploy plugin : deploy-file goal
Didn't you ask the very same question (twice) yesterday? Please don't spam the mailing list, but allow some days for people to answer. /Anders On Thu, Apr 29, 2010 at 16:53, srinivasa raghavan srinivasaraghava...@gmail.com wrote: Hi, have a doubt in maven-deploy plugin 2.5 version. For deploy-file goal , they make a sanity check to see whether the file to be deployed is present in the local repository and if so they fail the deploy goal. I believe 2.4 version didn't do that. So why is it illegal to deploy artifact from the local repository? (is it because we use this option only to deploy third party artifacts to the repository?) thanks, Srinivas
RE: doubt in maven-deploy plugin : deploy-file goal
Hi Anders. When I sent the first mail I wasn't subscribed to the group. Didn't know the policy of the mailing list whether they allow mails from non-members. So subscribed to the mailing list and sent the mail again. Sorry for it anyways. -Original Message- From: anders.g.ham...@gmail.com [mailto:anders.g.ham...@gmail.com] On Behalf Of Anders Hammar Sent: Friday, April 30, 2010 3:04 PM To: Maven Users List Subject: Re: doubt in maven-deploy plugin : deploy-file goal Didn't you ask the very same question (twice) yesterday? Please don't spam the mailing list, but allow some days for people to answer. /Anders On Thu, Apr 29, 2010 at 16:53, srinivasa raghavan srinivasaraghava...@gmail.com wrote: Hi, have a doubt in maven-deploy plugin 2.5 version. For deploy-file goal , they make a sanity check to see whether the file to be deployed is present in the local repository and if so they fail the deploy goal. I believe 2.4 version didn't do that. So why is it illegal to deploy artifact from the local repository? (is it because we use this option only to deploy third party artifacts to the repository?) thanks, Srinivas - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: doubt in maven-deploy plugin : deploy-file goal
On 30/04/2010 5:39 AM, Ambikapathy, Srinivas wrote: Hi Anders. When I sent the first mail I wasn't subscribed to the group. Didn't know the policy of the mailing list whether they allow mails from non-members. So subscribed to the mailing list and sent the mail again. Sorry for it anyways. Anders may have a better answer to your question, if you give him another week to think about it. I think your problem comes from Maven's view of releases. You can not deploy a release that has already been deployed. Releases are immutable and permanent. If you want to redeploy a release you need to delete the erroneous release in the repo (probably in your local repo as well). This should not happen very often if you use SNAPSHOTS and versions correctly. This is not new as far as I know. Ron -Original Message- From: anders.g.ham...@gmail.com [mailto:anders.g.ham...@gmail.com] On Behalf Of Anders Hammar Sent: Friday, April 30, 2010 3:04 PM To: Maven Users List Subject: Re: doubt in maven-deploy plugin : deploy-file goal Didn't you ask the very same question (twice) yesterday? Please don't spam the mailing list, but allow some days for people to answer. /Anders On Thu, Apr 29, 2010 at 16:53, srinivasa raghavan srinivasaraghava...@gmail.com wrote: Hi, have a doubt in maven-deploy plugin 2.5 version. For deploy-file goal , they make a sanity check to see whether the file to be deployed is present in the local repository and if so they fail the deploy goal. I believe 2.4 version didn't do that. So why is it illegal to deploy artifact from the local repository? (is it because we use this option only to deploy third party artifacts to the repository?) thanks, Srinivas - 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
doubt in maven-deploy plugin : deploy-file goal
Hi, have a doubt in maven-deploy plugin 2.5 version. For deploy-file goal , they make a sanity check to see whether the file to be deployed is present in the local repository and if so they fail the deploy goal. I believe 2.4 version didn't do that. So why is it illegal to deploy artifact from the local repository? (is it because we use this option only to deploy third party artifacts to the repository?) thanks, Srinivas
Error from maven deploy plugin during release:perform
I'm trying to sign release my project artifacts to a maven repository. I'm currently getting the following error when executing: mvn -e -X release:perform -Dgpg.useagent=true -Darguments=-Dgpg.useagent=true [INFO] [DEBUG] Configuring mojo 'org.apache.maven.plugins:maven-deploy-plugin:2.4:deploy' -- [INFO] [DEBUG] (f) artifact = org.pyant.tasks:pyAntTasks:jar:1.3.1 [INFO] [DEBUG] (f) attachedArtifacts = [org.pyant.tasks:pyAntTasks:java-source:sources:1.3.1, org.pyant.tasks:pyAntTasks:javadoc:javadoc:1.3.1, org.pyant.tasks:pyAntTasks:jar.asc:1.3.1, org.pyant.tasks:pyAntTasks:pom.asc:1.3.1, org.pyant.tasks:pyAntTasks:asc:sources.jar:1.3.1, org.pyant.tasks:pyAntTasks:asc:javadoc.jar:1.3.1] [INFO] [INFO] [INFO] [ERROR] BUILD ERROR [INFO] [INFO] [INFO] [INFO] Failed to configure plugin parameters for: org.apache.maven.plugins:maven-deploy-plugin:2.4 [INFO] [INFO] check that the following section of the pom.xml is present and correct: [INFO] [INFO] distributionManagement [INFO] !-- use the following if you're not using a snapshot version. -- [INFO] repository [INFO] idrepo/id [INFO] nameRepository Name/name [INFO] urlscp://host/path/to/repo/url [INFO] /repository [INFO] !-- use the following if you ARE using a snapshot version. -- [INFO] snapshotRepository [INFO] idrepo/id [INFO] nameRepository Name/name [INFO] urlscp://host/path/to/repo/url [INFO] /snapshotRepository [INFO] /distributionManagement [INFO] [INFO] Cause: Class 'org.apache.maven.artifact.repository.ArtifactRepository' cannot be instantiated [INFO] [INFO] [INFO] [DEBUG] Trace [INFO] org.apache.maven.lifecycle.LifecycleExecutionException: Error configuring: org.apache.maven.plugins:maven-deploy-plugin. Reason: Unable to parse the created DOM for plugin configuration [INFO] at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:723) [INFO] at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556) [INFO] at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535) [INFO] at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387) [INFO] at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348) ... Section of my distributionManagement section: distributionManagement repository idsonatype-nexus-staging/id nameNexus Release Repository/name urlhttp://oss.sonatype.org/service/local/staging/deploy/maven2/url /repository snapshotRepository idsonatype-nexus-snapshots/id nameSonatype Nexus Snapshots/name urlhttp://oss.sonatype.org/service/local/staging/deploy/maven2/url /snapshotRepository /distributionManagement Info on my environment: Apache Maven 2.2.1 (r801777; 2009-08-06 14:16:01-0500) Java version: 1.6.0_17 Java home: /System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Home Default locale: en_US, platform encoding: MacRoman OS name: mac os x version: 10.6.2 arch: x86_64 Family: mac I've searched google/forums for solutions but haven't turned anything up. Anyone seen this before or know what I might try? Regards, Ron -- View this message in context: http://n2.nabble.com/Error-from-maven-deploy-plugin-during-release-perform-tp4822554p4822554.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
maven-deploy-plugin — inconsistent unique Version, upload and download issues
Hello,
I had an issue with Nexus not returning the right artifact, apparently
to be due to presence of both -SNAPSHOT and artifacts in its
repositories; this seems to be fixed by emptying the snapshot
repositories and re-deploy.
Before the deletion, Maven was always download -SNAPSHOT artifacts, even
if older than -${timestamp} ones.
But, even after I've set uniqueVersiontrue/uniqueVersion, I still
have those two different behaviors:
http://maven.nuxeo.org/nexus/content/repositories/nuxeo-snapshot/org/nuxeo/ecm/distribution/nuxeo-distribution-dm/5.3.1-SNAPSHOT/
http://maven.in.nuxeo.com/nexus/content/repositories/snapshots/org/nuxeo/ecm/distribution/nuxeo-distribution-dm/5.3.1-SNAPSHOT/
It looks like
http://jira.codehaus.org/browse/MDEPLOY-75 and
http://jira.codehaus.org/browse/MDEPLOY-46
For http://maven.nuxeo.org/, deployment is done with mvn clean deploy
For http://maven.in.nuxeo.com/, deployment is done with either
(depending on the module POM):
- mvn clean deploy -Pqa
- mvn clean deploy -Pqa
-DaltDeploymentRepository=snapshots::default::http://maven.in.nuxeo.com/snapshots;
with the following values for snapshot deployment:
profiles
profile
idqa/id
distributionManagement
snapshotRepository
idsnapshots/id
urlhttp://maven.in.nuxeo.com/snapshots/url
uniqueVersiontrue/uniqueVersion
/snapshotRepository
/distributionManagement
/profile
/profiles
distributionManagement
snapshotRepository
idnuxeo-snapshot/id
urlhttp://maven.nuxeo.org/nexus/content/repositories/nuxeo-snapshot/url
uniqueVersiontrue/uniqueVersion
/snapshotRepository
/distributionManagement
Is there something better I could do ?
Could you explain the difference between maven.nuxeo.org and
maven.in.nuxeo.com ?
Also, why are there ${timestamp} artifacts in local repositories ? Is
there any reason for not having -SNAPSHOT on client side ?
Is all this effectively due to MDEPLOY-46 and 75 ? Will this be fixed
(last update on August 2007 and March 2008 ?!) or will we have to wait
for Maven 3 being released and align our code on it ?
Best regards,
Julien
--
Julien Carsique, Nuxeo (Paris, France) — jcarsi...@nuxeo.com
www.nuxeo.com - The Open Source ECM Platform - www.nuxeo.org
Nuxeo ECM Stack - The Java EE, scalable, standard-based ECM Platform
[ANN] Maven Deploy Plugin 2.5 Released
The Maven team is pleased to announce the release of the Maven Deploy Plugin, version 2.5. This plugin is primarily used during the deploy phase, to add your artifact(s) to a remote repository for sharing with other developers and projects. For more information, see the plugin's site: http://maven.apache.org/plugins/maven-deploy-plugin/ To use the updated plugin in your projects, you need to add the following snippet to the plugins or plugin management section of your POM: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-deploy-plugin/artifactId version2.5/version /plugin Release Notes - Maven 2.x Deploy Plugin - Version 2.5 ** Bug * [MDEPLOY-50] - deploy:deploy fails without distributionManagment despite altDeploymentRepository being specified * [MDEPLOY-59] - deploy:deploy-file deletes the original file on error * [MDEPLOY-78] - Deploy with classifier does not deploy pom * [MDEPLOY-84] - NPE when deploy-file with generatePom=false * [MDEPLOY-88] - Artifacts with invalid id can be deployed with deploy:deploy-file. * [MDEPLOY-89] - Skip won't work if distribution management is not specified ** Improvement * [MDEPLOY-52] - deploy-file doesn't support updateReleaseInfo ** Task * [MDEPLOY-70] - remove copy of plexus-utils' XML encoding support sources * [MDEPLOY-109] - Have plugin itself respect Maven's online/offline mode Enjoy, -The Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Using the Maven Deploy Plugin
Neil, In addition to other responses (use http, not file): 1. Check the repo url in your output. I think the trailing slash in your pom.xml url will result in two slashes in the actual url (id did in mine). 2. I assume the repo entry is a child of distributionManagement and that your id matches settings.xml servers entry or you would get a bad url or auth error - can't tell from what you posted. Post your fix if you get it. I am still struggling with a 400 error myself. Neil Chaudhuri-2 wrote: We have an internal Maven repository that I can view in my browser at http://myserver:8081/nexus/content/repositories/myRepo/. I am simply trying to upload my generated WAR file to this repository. I have set up credentials in settings.xml, and my pom is set up as follows: repository idmy-maven-repo/id nameInternal Maven Repository/name urlfile://myserver:8081/nexus/content/repositories/myRepo//url /repository This work great and I get a BUILD SUCCESSFUL message. The problem is that when I go back to http://myserver:8081/nexus/content/repositories/myRepo/, I can't see it. Any ideas as to what is going on here? Thanks. -- View this message in context: http://old.nabble.com/Using-the-Maven-Deploy-Plugin-tp26325832p26581431.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: Using the Maven Deploy Plugin
Are you trying to redeploy a release artifact that's already there? Nexus 1.4.x has redeployment disabled by default. Otherwise if the file was successfully uploaded you should see it right away in the repository, you may have to refresh the ui or browser. Use the nexus user list for additional assitance: http://nexus.sonatype.org/project-information.html On Thu, Nov 12, 2009 at 4:47 PM, Neil Chaudhuri nchaudh...@potomacfusion.com wrote: I will check out that location to see what I find. In the meantime, I tried http, but then I get the following: [INFO] Error deploying artifact: Failed to transfer file: http://myserver:8081/nexus/content/repositories/myRepo/blah blah. Return code is: 400 Any idea why this might be? Thanks. -Original Message- From: Jamie Whitehouse [mailto:jamie.whiteho...@genesyslab.com] Sent: Thu 11/12/2009 3:40 PM To: Maven Users List Subject: RE: Using the Maven Deploy Plugin No, it's http that you want. Since you used file initially you'll probably see your artifacts on your local disk in a directory like myserver:8081/nexus/content/repositories/myRepo/ -Original Message- From: Neil Chaudhuri [mailto:nchaudh...@potomacfusion.com] Sent: Thursday, November 12, 2009 4:32 PM To: Maven Users List Subject: RE: Using the Maven Deploy Plugin As illuminating as that link is, I have my pom setup in precisely that fashion. The only difference is that I am not using either scp or sftp as my protocol because they are not appropriate in my case. Is file: the correct protocol since the server is not secure? Thanks. -Original Message- From: Stevo Slavic [mailto:ssla...@gmail.com] Sent: Thu 11/12/2009 3:14 PM To: Maven Users List Subject: Re: Using the Maven Deploy Plugin http://maven.apache.org/pom.html#Repository Regards, Stevo. On Thu, Nov 12, 2009 at 9:30 PM, Neil Chaudhuri nchaudh...@potomacfusion.com wrote: We have an internal Maven repository that I can view in my browser at http://myserver:8081/nexus/content/repositories/myRepo/. I am simply trying to upload my generated WAR file to this repository. I have set up credentials in settings.xml, and my pom is set up as follows: repository idmy-maven-repo/id nameInternal Maven Repository/name urlfile://myserver:8081/nexus/content/repositories/myRepo//url /repository This work great and I get a BUILD SUCCESSFUL message. The problem is that when I go back to http://myserver:8081/nexus/content/repositories/myRepo/, I can't see it. Any ideas as to what is going on here? Thanks. --- CONFIDENTIALITY NOTICE: This e-mail and any files attached may contain confidential and proprietary information of Alcatel-Lucent and/or its affiliated entities. Access by the intended recipient only is authorized. Any liability arising from any party acting, or refraining from acting, on any information contained in this e-mail is hereby excluded. If you are not the intended recipient, please notify the sender immediately, destroy the original transmission and its attachments and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Copyright in this e-mail and any attachments belongs to Alcatel-Lucent and/or its affiliated entities. - 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: Using the Maven Deploy Plugin
Sorry, I misread your first email. You can't use the file: protocol to deploy to a remote server. Most likely if you poke around in the root of your disk, you'll find a new folder called myserver that contains the file you thought was deployed to Nexus. You want the http protocol. As far as the 400, make sure you are deploying releases to a release repo and snapshots to a snapshot repo, that's the most likely cause assuming you have your credentials setup correctly, and have permissions on the server to do the deploy. On Mon, Nov 30, 2009 at 5:42 PM, Brian Fox bri...@infinity.nu wrote: Are you trying to redeploy a release artifact that's already there? Nexus 1.4.x has redeployment disabled by default. Otherwise if the file was successfully uploaded you should see it right away in the repository, you may have to refresh the ui or browser. Use the nexus user list for additional assitance: http://nexus.sonatype.org/project-information.html On Thu, Nov 12, 2009 at 4:47 PM, Neil Chaudhuri nchaudh...@potomacfusion.com wrote: I will check out that location to see what I find. In the meantime, I tried http, but then I get the following: [INFO] Error deploying artifact: Failed to transfer file: http://myserver:8081/nexus/content/repositories/myRepo/blah blah. Return code is: 400 Any idea why this might be? Thanks. -Original Message- From: Jamie Whitehouse [mailto:jamie.whiteho...@genesyslab.com] Sent: Thu 11/12/2009 3:40 PM To: Maven Users List Subject: RE: Using the Maven Deploy Plugin No, it's http that you want. Since you used file initially you'll probably see your artifacts on your local disk in a directory like myserver:8081/nexus/content/repositories/myRepo/ -Original Message- From: Neil Chaudhuri [mailto:nchaudh...@potomacfusion.com] Sent: Thursday, November 12, 2009 4:32 PM To: Maven Users List Subject: RE: Using the Maven Deploy Plugin As illuminating as that link is, I have my pom setup in precisely that fashion. The only difference is that I am not using either scp or sftp as my protocol because they are not appropriate in my case. Is file: the correct protocol since the server is not secure? Thanks. -Original Message- From: Stevo Slavic [mailto:ssla...@gmail.com] Sent: Thu 11/12/2009 3:14 PM To: Maven Users List Subject: Re: Using the Maven Deploy Plugin http://maven.apache.org/pom.html#Repository Regards, Stevo. On Thu, Nov 12, 2009 at 9:30 PM, Neil Chaudhuri nchaudh...@potomacfusion.com wrote: We have an internal Maven repository that I can view in my browser at http://myserver:8081/nexus/content/repositories/myRepo/. I am simply trying to upload my generated WAR file to this repository. I have set up credentials in settings.xml, and my pom is set up as follows: repository idmy-maven-repo/id nameInternal Maven Repository/name urlfile://myserver:8081/nexus/content/repositories/myRepo//url /repository This work great and I get a BUILD SUCCESSFUL message. The problem is that when I go back to http://myserver:8081/nexus/content/repositories/myRepo/, I can't see it. Any ideas as to what is going on here? Thanks. --- CONFIDENTIALITY NOTICE: This e-mail and any files attached may contain confidential and proprietary information of Alcatel-Lucent and/or its affiliated entities. Access by the intended recipient only is authorized. Any liability arising from any party acting, or refraining from acting, on any information contained in this e-mail is hereby excluded. If you are not the intended recipient, please notify the sender immediately, destroy the original transmission and its attachments and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Copyright in this e-mail and any attachments belongs to Alcatel-Lucent and/or its affiliated entities. - 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
Using the Maven Deploy Plugin
We have an internal Maven repository that I can view in my browser at http://myserver:8081/nexus/content/repositories/myRepo/. I am simply trying to upload my generated WAR file to this repository. I have set up credentials in settings.xml, and my pom is set up as follows: repository idmy-maven-repo/id nameInternal Maven Repository/name urlfile://myserver:8081/nexus/content/repositories/myRepo//url /repository This work great and I get a BUILD SUCCESSFUL message. The problem is that when I go back to http://myserver:8081/nexus/content/repositories/myRepo/, I can't see it. Any ideas as to what is going on here? Thanks.
Re: Using the Maven Deploy Plugin
http://maven.apache.org/pom.html#Repository Regards, Stevo. On Thu, Nov 12, 2009 at 9:30 PM, Neil Chaudhuri nchaudh...@potomacfusion.com wrote: We have an internal Maven repository that I can view in my browser at http://myserver:8081/nexus/content/repositories/myRepo/. I am simply trying to upload my generated WAR file to this repository. I have set up credentials in settings.xml, and my pom is set up as follows: repository idmy-maven-repo/id nameInternal Maven Repository/name urlfile://myserver:8081/nexus/content/repositories/myRepo//url /repository This work great and I get a BUILD SUCCESSFUL message. The problem is that when I go back to http://myserver:8081/nexus/content/repositories/myRepo/, I can't see it. Any ideas as to what is going on here? Thanks.
RE: Using the Maven Deploy Plugin
As illuminating as that link is, I have my pom setup in precisely that fashion. The only difference is that I am not using either scp or sftp as my protocol because they are not appropriate in my case. Is file: the correct protocol since the server is not secure? Thanks. -Original Message- From: Stevo Slavic [mailto:ssla...@gmail.com] Sent: Thu 11/12/2009 3:14 PM To: Maven Users List Subject: Re: Using the Maven Deploy Plugin http://maven.apache.org/pom.html#Repository Regards, Stevo. On Thu, Nov 12, 2009 at 9:30 PM, Neil Chaudhuri nchaudh...@potomacfusion.com wrote: We have an internal Maven repository that I can view in my browser at http://myserver:8081/nexus/content/repositories/myRepo/. I am simply trying to upload my generated WAR file to this repository. I have set up credentials in settings.xml, and my pom is set up as follows: repository idmy-maven-repo/id nameInternal Maven Repository/name urlfile://myserver:8081/nexus/content/repositories/myRepo//url /repository This work great and I get a BUILD SUCCESSFUL message. The problem is that when I go back to http://myserver:8081/nexus/content/repositories/myRepo/, I can't see it. Any ideas as to what is going on here? Thanks. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
RE: Using the Maven Deploy Plugin
No, it's http that you want. Since you used file initially you'll probably see your artifacts on your local disk in a directory like myserver:8081/nexus/content/repositories/myRepo/ -Original Message- From: Neil Chaudhuri [mailto:nchaudh...@potomacfusion.com] Sent: Thursday, November 12, 2009 4:32 PM To: Maven Users List Subject: RE: Using the Maven Deploy Plugin As illuminating as that link is, I have my pom setup in precisely that fashion. The only difference is that I am not using either scp or sftp as my protocol because they are not appropriate in my case. Is file: the correct protocol since the server is not secure? Thanks. -Original Message- From: Stevo Slavic [mailto:ssla...@gmail.com] Sent: Thu 11/12/2009 3:14 PM To: Maven Users List Subject: Re: Using the Maven Deploy Plugin http://maven.apache.org/pom.html#Repository Regards, Stevo. On Thu, Nov 12, 2009 at 9:30 PM, Neil Chaudhuri nchaudh...@potomacfusion.com wrote: We have an internal Maven repository that I can view in my browser at http://myserver:8081/nexus/content/repositories/myRepo/. I am simply trying to upload my generated WAR file to this repository. I have set up credentials in settings.xml, and my pom is set up as follows: repository idmy-maven-repo/id nameInternal Maven Repository/name urlfile://myserver:8081/nexus/content/repositories/myRepo//url /repository This work great and I get a BUILD SUCCESSFUL message. The problem is that when I go back to http://myserver:8081/nexus/content/repositories/myRepo/, I can't see it. Any ideas as to what is going on here? Thanks. --- CONFIDENTIALITY NOTICE: This e-mail and any files attached may contain confidential and proprietary information of Alcatel-Lucent and/or its affiliated entities. Access by the intended recipient only is authorized. Any liability arising from any party acting, or refraining from acting, on any information contained in this e-mail is hereby excluded. If you are not the intended recipient, please notify the sender immediately, destroy the original transmission and its attachments and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Copyright in this e-mail and any attachments belongs to Alcatel-Lucent and/or its affiliated entities. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
RE: Using the Maven Deploy Plugin
I will check out that location to see what I find. In the meantime, I tried http, but then I get the following: [INFO] Error deploying artifact: Failed to transfer file: http://myserver:8081/nexus/content/repositories/myRepo/blah blah. Return code is: 400 Any idea why this might be? Thanks. -Original Message- From: Jamie Whitehouse [mailto:jamie.whiteho...@genesyslab.com] Sent: Thu 11/12/2009 3:40 PM To: Maven Users List Subject: RE: Using the Maven Deploy Plugin No, it's http that you want. Since you used file initially you'll probably see your artifacts on your local disk in a directory like myserver:8081/nexus/content/repositories/myRepo/ -Original Message- From: Neil Chaudhuri [mailto:nchaudh...@potomacfusion.com] Sent: Thursday, November 12, 2009 4:32 PM To: Maven Users List Subject: RE: Using the Maven Deploy Plugin As illuminating as that link is, I have my pom setup in precisely that fashion. The only difference is that I am not using either scp or sftp as my protocol because they are not appropriate in my case. Is file: the correct protocol since the server is not secure? Thanks. -Original Message- From: Stevo Slavic [mailto:ssla...@gmail.com] Sent: Thu 11/12/2009 3:14 PM To: Maven Users List Subject: Re: Using the Maven Deploy Plugin http://maven.apache.org/pom.html#Repository Regards, Stevo. On Thu, Nov 12, 2009 at 9:30 PM, Neil Chaudhuri nchaudh...@potomacfusion.com wrote: We have an internal Maven repository that I can view in my browser at http://myserver:8081/nexus/content/repositories/myRepo/. I am simply trying to upload my generated WAR file to this repository. I have set up credentials in settings.xml, and my pom is set up as follows: repository idmy-maven-repo/id nameInternal Maven Repository/name urlfile://myserver:8081/nexus/content/repositories/myRepo//url /repository This work great and I get a BUILD SUCCESSFUL message. The problem is that when I go back to http://myserver:8081/nexus/content/repositories/myRepo/, I can't see it. Any ideas as to what is going on here? Thanks. --- CONFIDENTIALITY NOTICE: This e-mail and any files attached may contain confidential and proprietary information of Alcatel-Lucent and/or its affiliated entities. Access by the intended recipient only is authorized. Any liability arising from any party acting, or refraining from acting, on any information contained in this e-mail is hereby excluded. If you are not the intended recipient, please notify the sender immediately, destroy the original transmission and its attachments and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Copyright in this e-mail and any attachments belongs to Alcatel-Lucent and/or its affiliated entities. - 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 deploy plugin
Here is what I added in the maven goal. -e deploy:deploy-file -Dfile=pom.xml -Durl=http://abc001.na.abcglobal.com:8081/nexus/content/repositories/releases -DrepositoryId=releases -DgroupId=com.abc.t3 -DartifactId=t3 -Dversion=1.1 -Dpackaging=pom But this creates incorrect 1.1 version of my project POM. I want to see the actual contents of pom.xml from my version control repository to get deployed to Nexus. Instead the resulting POM is ?xml version=1.0 encoding=UTF-8?project modelVersion4.0.0/modelVersion groupIdcom.abc.t3/groupId artifactIdt3/artifactId packagingpom/packaging version1.1/version /project ~ I was expecting that deploy-file will deploy the actual file i.e pom.xml in this case. What could be wrong here ? Thanks, huser wrote: Hi, I want to deploy a project POM file only. I added maven-deploy plugin as follows. When I run mvn dpeloy:deploy-file It still complains about missing modules directories. I dont want to build the modules. I want to generate the pom file only. How can I do this ? parent groupIdcom.abc/groupId artifactIdabc-parent/artifactId version2.4/version /parent groupIdcom.abc.t3/groupId artifactIdt3/artifactId version1.1/version packagingpom/packaging nameABC T3 /name build plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-deploy-plugin/artifactId version2.4/version /plugin /plugins /build -- View this message in context: http://www.nabble.com/maven-deploy-plugin-tp24902976p24943430.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: maven deploy plugin
On Wed, Aug 12, 2009 at 2:30 PM, husermpinj...@atxg.com wrote: Here is what I added in the maven goal. -e deploy:deploy-file -Dfile=pom.xml -Durl=http://abc001.na.abcglobal.com:8081/nexus/content/repositories/releases -DrepositoryId=releases -DgroupId=com.abc.t3 -DartifactId=t3 -Dversion=1.1 -Dpackaging=pom But this creates incorrect 1.1 version of my project POM. I want to see the actual contents of pom.xml from my version control repository to get deployed to Nexus. Instead the resulting POM is Try using -DpomFile=... on the command line. You may need both -Dfile=... and -DpomFile=... to make it work right. I haven't done this from the command line in a while. I'd also check whether Nexus has a web form where you can upload artifacts, that might be easier. -- Wendy - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: maven deploy plugin
Tried http://maven.apache.org/plugins/maven-deploy-plugin/deploy-file-mojo.html? If no, try this. [?] 2009/8/10 huser mpinj...@atxg.com Hi, I want to deploy a project POM file only. I added maven-deploy plugin as follows. When I run mvn dpeloy:deploy-file It still complains about missing modules directories. I dont want to build the modules. I want to generate the pom file only. How can I do this ? parent groupIdcom.abc/groupId artifactIdabc-parent/artifactId version2.4/version /parent groupIdcom.abc.t3/groupId artifactIdt3/artifactId version1.1/version packagingpom/packaging nameABC T3 /name build plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-deploy-plugin/artifactId version2.4/version /plugin /plugins /build -- View this message in context: http://www.nabble.com/maven-deploy-plugin-tp24902976p24902976.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 -- Regards, Alexander
maven deploy plugin
Hi, I want to deploy a project POM file only. I added maven-deploy plugin as follows. When I run mvn dpeloy:deploy-file It still complains about missing modules directories. I dont want to build the modules. I want to generate the pom file only. How can I do this ? parent groupIdcom.abc/groupId artifactIdabc-parent/artifactId version2.4/version /parent groupIdcom.abc.t3/groupId artifactIdt3/artifactId version1.1/version packagingpom/packaging nameABC T3 /name build plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-deploy-plugin/artifactId version2.4/version /plugin /plugins /build -- View this message in context: http://www.nabble.com/maven-deploy-plugin-tp24902976p24902976.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
Maven error with multiple executions in maven-deploy-plugin
Hi,
I found this nice recipe
http://ionixx.wordpress.com/2008/03/10/running-specified-ant-tasks-within-maven2-outside-the-lifecycle/
and want to use it to deploy some 3rd-party files in our repository
If I do this for one file it works exactly as intended
profiles
profile
iddeploy-libs/id
build
defaultGoaldeploy:deploy-file/defaultGoal
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-deploy-plugin/artifactId
version2.4/version
goals
goaldeploy-file/goal
/goals
configuration
repositoryIdopenscada-external/repositoryId
url${openscada.distrib.repository}/url
file../openscada_opc_dcom/lib/j-interop.jar/file
pomFile../openscada_opc_dcom/lib/j-interop.pom/pomFile
/configuration
/plugin
/plugins
/build
/profile
/profiles
If I use an execution block with multiple executions, it doesn't work.
Is this a bug, or is this intended behavior?
profiles
profile
iddeploy-libs/id
build
defaultGoaldeploy:deploy-file/defaultGoal
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-deploy-plugin/artifactId
version2.4/version
configuration
repositoryIdopenscada-external/repositoryId
url${openscada.distrib.repository}/url
/configuration
executions
execution
idj-interop/id
goals
goaldeploy-file/goal
/goals
configuration
file../openscada_opc_dcom/lib/j-interop.jar/file
pomFile../openscada_opc_dcom/lib/j-interop.pom/pomFile
/configuration
/execution
execution
idj-interopdeps/id
goals
goaldeploy-file/goal
/goals
configuration
file../openscada_opc_dcom/lib/j-interopdeps.jar/file
pomFile../openscada_opc_dcom/lib/j-interopdeps.pom/pomFile
/configuration
/execution
execution
idjcifs/id
goals
goaldeploy-file/goal
/goals
configuration
file../openscada_opc_dcom/lib/jcifs-1.2.9.jar/file
pomFile../openscada_opc_dcom/lib/jcifs-1.2.9.pom/pomFile
/configuration
/execution
/executions
/plugin
/plugins
/build
/profile
/profiles
The error I get is:
[ERROR] BUILD ERROR
[INFO]
[INFO] One or more required plugin parameters are invalid/missing for
'deploy:deploy-file'
[0] Inside the definition for plugin 'maven-deploy-plugin' specify the
following:
configuration
...
fileVALUE/file
/configuration
-OR-
on the command line, specify: '-Dfile=VALUE'
[INFO]
[INFO] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Error
configuring: org.apache.maven.plugins:maven-deploy-plugin. Reason:
Invalid or missing parameters: [Mojo parameter [name: 'file'; alias:
'null']] for mojo:
org.apache.maven.plugins:maven-deploy-plugin:2.4:deploy-file
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:587)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:512)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:482)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:227)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:287)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39
maven deploy plugin help
so I'm attempting to run mvn deploy from a top level pom and I have an issue I was wondering if anyone had the answer to, any help is greatly appreciated. The top level pom builds several child pom modules. Now I want all of the child poms to be deployed except for one or two when I run mvn deploy from the top level directory. I'm wondering if I can specify in my pom which child pom's I want to be deployed or don't want deployed when I run mvn deploy from the top level directory. I want to keep them all building the same but don't want to have them all deployed. Also another potential option is that all of the child projects that I don't want to deploy are deployed as ear or war files. So maybe there is a way to specify that I only want jars to be deployed from the top level pom?
Re: maven deploy plugin help
You can configure the deploy plugin in each of those projects to skip deployment: http://maven.apache.org/plugins/maven-deploy-plugin/deploy-mojo.html#skip 2008/10/9 Shaun Poore [EMAIL PROTECTED]: so I'm attempting to run mvn deploy from a top level pom and I have an issue I was wondering if anyone had the answer to, any help is greatly appreciated. The top level pom builds several child pom modules. Now I want all of the child poms to be deployed except for one or two when I run mvn deploy from the top level directory. I'm wondering if I can specify in my pom which child pom's I want to be deployed or don't want deployed when I run mvn deploy from the top level directory. I want to keep them all building the same but don't want to have them all deployed. Also another potential option is that all of the child projects that I don't want to deploy are deployed as ear or war files. So maybe there is a way to specify that I only want jars to be deployed from the top level pom? -- Brett Porter Blog: http://blogs.exist.com/bporter/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Maven won't run offline (maven-deploy-plugin). Can I use ant for deploy phase?
That doesn't make any sense. Deploy means to push it to a remote repository for sharing with the team. Install will already put it into their own local repo. I suggest you take a look at the maven docs or the maven book: www.sonatype.com/book to get a better idea how everything works. Then you'll understand why we're all confused about what you're trying to do. -Original Message- From: John Brady [mailto:[EMAIL PROTECTED] Sent: Tuesday, September 16, 2008 9:28 AM To: Baptiste MATHUS Cc: Maven Users List Subject: Re: Maven won't run offline (maven-deploy-plugin). Can I use ant for deploy phase? I have looked into option three, but the team is only deploying to their own machines. Therefore, I want everyone developer to have their own full repository so they do not have to download anything and can work fully offline with the ability to deploy a war file to their own machine. Does that make more sense? Option 2 seems feasible and clean. I will look into that. On Mon, Sep 15, 2008 at 4:36 PM, Baptiste MATHUS [EMAIL PROTECTED] wrote: Well, before doing that, did you study a bit how maven works by default? You're speaking about designing an internal repository so that things run faster. * First, do you know that maven already maintains a cached version of what was downloaded? * Second, if you really really want to proceed this way, though it still seems weird to me, why don't you just run mvn so that it would reactivate online bevahiour just to be able to deploy? I guess it'd be far cleaner that dealing with ant call to maven to whatever?!? * Third (last but not least), what you seem to be speaking about: improving downloading time, bandwidth and so on is already a very common use cas for maven. To do that, you usually put a corporate maven repository between you (and your team) and the public ones. To know more about that, just crawl google for words like maven repository manager, maven archiva, maven nexus... I guess this is rather what you should look into, even more if you plan to deploy what you're doing to other machines than yours. HTH. Cheers. 2008/9/15 John Brady [EMAIL PROTECTED] I want to setup an internal repository that each developer will have on their own repository on their machine so that builds will be faster. So basically I ran mvn offline to get all my dependencies and put them in a repository. this repository will be able to be checked into svn if any developer updates and files. But the problem I face is not being able to deploy in offline mode, which leads back to whether or not using ant is the way to go or is there a way to make maven allow the deploy plugin to run in offline mode On Mon, Sep 15, 2008 at 4:09 PM, Baptiste MATHUS [EMAIL PROTECTED] wrote: The answer to your question is no. You obviously don't have to run ant to be able to use the deploy plugin... The real question is: why do you have maven configured to run offline (see http://maven.apache.org/settings.html#Simple_Values to check the documentation if necessary) or why you run mvn -o instead of simply mvn. Check your settings.xml file to see if running offline is really what you want. I guess you should explain why you run offline and how you configured the offline mode. Cheers. 2008/9/15 John Brady [EMAIL PROTECTED] I want to be able to run a deploy goal while offline, however since this is an online task I cannot achieve this. I am wondering if I can use an ant plugin in for maven to achieve this goal On Mon, Sep 15, 2008 at 3:34 PM, Baptiste MATHUS [EMAIL PROTECTED] wrote: Could you please explain what you're trying to achieve? If you followed some tutorial, please explain at least where it fails for you and what *you* expected it to do. Maven WILL run offline as long as you don't ask for an online feature... This is what was already answered. Cheers. 2008/9/15 jbrady3324 [EMAIL PROTECTED] Moved from different list can I use ant to get around this issue? You're telling Maven that you are offline. Deploying is an Online behavior, therefore they are mutually exclusive. Also, this is a user list question as it doesn't relate to the development of Maven itself. -Original Message- From: jbrady3324 [mailto:[EMAIL PROTECTED] Sent: Monday, September 15, 2008 11:15 AM To: [EMAIL PROTECTED] Subject: Cannot run in offline mode -- problem with maven-deploy-plugin ? This is the error I get: [INFO] Installing C:\dev\eclipse\mops2.0\mops\pom.xml to C:\Documents and Settings\jxbrady\.m2\repository\com\putnam\mops\mops\2.0-SNAPSHOT\mops-2 .0-SNAPSHOT.pom altDeploymentRepository = null [ERROR] The following mojo encountered an error while executing: Group-Id: org.apache.maven.plugins Artifact-Id: maven-deploy-plugin Version: 2.3 Mojo: deploy brought in via: packaging: pom While building project: Group-Id: com.putnam.mops Artifact-Id: mops
Re: Maven won't run offline (maven-deploy-plugin). Can I use ant for deploy phase?
If they are only deploying on their own machines then it can hardly be called a deployment in the Maven-sense of the word. Is there a reason you cannot simply use install? If you absolutely insist on going down this road (though its a bit like driving everywhere backwards IMO), I would have a standard settings.xml file that defines a repo which actually exists on everyone's local machines in a common place in their filesystem. Then I would use mirrorOf* to specify that this repo is a mirrorOf Central, and all other repos. Then you should be able to run online which would clear up the issues that generated this email thread. But again, if this is how you're using Maven, you're (probably) doing it wrong. Wayne On Tue, Sep 16, 2008 at 6:27 AM, John Brady [EMAIL PROTECTED] wrote: I have looked into option three, but the team is only deploying to their own machines. Therefore, I want everyone developer to have their own full repository so they do not have to download anything and can work fully offline with the ability to deploy a war file to their own machine. Does that make more sense? Option 2 seems feasible and clean. I will look into that. On Mon, Sep 15, 2008 at 4:36 PM, Baptiste MATHUS [EMAIL PROTECTED] wrote: Well, before doing that, did you study a bit how maven works by default? You're speaking about designing an internal repository so that things run faster. * First, do you know that maven already maintains a cached version of what was downloaded? * Second, if you really really want to proceed this way, though it still seems weird to me, why don't you just run mvn so that it would reactivate online bevahiour just to be able to deploy? I guess it'd be far cleaner that dealing with ant call to maven to whatever?!? * Third (last but not least), what you seem to be speaking about: improving downloading time, bandwidth and so on is already a very common use cas for maven. To do that, you usually put a corporate maven repository between you (and your team) and the public ones. To know more about that, just crawl google for words like maven repository manager, maven archiva, maven nexus... I guess this is rather what you should look into, even more if you plan to deploy what you're doing to other machines than yours. HTH. Cheers. 2008/9/15 John Brady [EMAIL PROTECTED] I want to setup an internal repository that each developer will have on their own repository on their machine so that builds will be faster. So basically I ran mvn offline to get all my dependencies and put them in a repository. this repository will be able to be checked into svn if any developer updates and files. But the problem I face is not being able to deploy in offline mode, which leads back to whether or not using ant is the way to go or is there a way to make maven allow the deploy plugin to run in offline mode On Mon, Sep 15, 2008 at 4:09 PM, Baptiste MATHUS [EMAIL PROTECTED] wrote: The answer to your question is no. You obviously don't have to run ant to be able to use the deploy plugin... The real question is: why do you have maven configured to run offline (see http://maven.apache.org/settings.html#Simple_Values to check the documentation if necessary) or why you run mvn -o instead of simply mvn. Check your settings.xml file to see if running offline is really what you want. I guess you should explain why you run offline and how you configured the offline mode. Cheers. 2008/9/15 John Brady [EMAIL PROTECTED] I want to be able to run a deploy goal while offline, however since this is an online task I cannot achieve this. I am wondering if I can use an ant plugin in for maven to achieve this goal On Mon, Sep 15, 2008 at 3:34 PM, Baptiste MATHUS [EMAIL PROTECTED] wrote: Could you please explain what you're trying to achieve? If you followed some tutorial, please explain at least where it fails for you and what *you* expected it to do. Maven WILL run offline as long as you don't ask for an online feature... This is what was already answered. Cheers. 2008/9/15 jbrady3324 [EMAIL PROTECTED] Moved from different list can I use ant to get around this issue? You're telling Maven that you are offline. Deploying is an Online behavior, therefore they are mutually exclusive. Also, this is a user list question as it doesn't relate to the development of Maven itself. -Original Message- From: jbrady3324 [mailto:[EMAIL PROTECTED] Sent: Monday, September 15, 2008 11:15 AM To: [EMAIL PROTECTED] Subject: Cannot run in offline mode -- problem with maven-deploy-plugin ? This is the error I get: [INFO] Installing C:\dev\eclipse\mops2.0\mops\pom.xml to C:\Documents and Settings\jxbrady\.m2\repository\com\putnam\mops\mops\2.0-SNAPSHOT\mops-2 .0-SNAPSHOT.pom altDeploymentRepository = null [ERROR] The following mojo encountered an error while executing: Group-Id
[ANN] Maven Deploy Plugin version 2.4 Released
The Maven team is pleased to announce the release of the Maven Deploy Plugin, version 2.4. This plugin is used to add artifacts and associated metadata to a remote repository [1]. http://maven.apache.org/plugins/maven-deploy-plugin/ To use this release, specify the version in your project's plugin configuration: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-deploy-plugin/artifactId version2.4/version /plugin Release Notes - Maven 2.x Deploy Plugin - Version 2.4 ** Bug * [MDEPLOY-45] - Classifier not supported by deploy:deploy * [MDEPLOY-56] - Parent version ignored when deploying file with existing pom ** Improvement * [MDEPLOY-66] - add XML encoding support for POM reading/writing ** New Feature * [MDEPLOY-63] - Allow disabling deployment for artifacts that should not be deployed [1] For more information on managing remote repositories, see http://maven.apache.org/repository-management.html Enjoy, -- Wendy Smoak on behalf of the Maven team - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
problem deploying an additional artifact with maven-deploy-plugin (deploy:deploy-file)
Greetings,
I am generating several artifacts from my build; a WAR, a TAR.GZ, and
a JAR -- as required by downstream usage scenarios (embedded,
standalone, or webapp)
I am having trouble deploying the JAR properly. (Note: I had to add an
install:install-file section to my POM to get the JAR deployed locally
in the first place).
I have the project successfully generating all three artifacts (it is
a War project), and installing locally (mvn install). And I can build
dependent projects properly using the locally deployed artifacts
But when deploying the JAR remotely -- during the deploy phase -- the
maven-deploy-plugin is overwriting my POM with a bogus one (see
below) which consists only of project basics; id, version, etc. - no
dependencies. This happens during the deploy:deploy-file phase for the
JAR. (See the POM snippet below). The generated bogus POM causes
downstream dependencies to fail during compilation.
I tried setting the generatePOM element to false, but it throws an
NPE (See below). Does this work?
I do not know how to set the pomFile element. Is there a variable
available for the POM file?? e.g. ${project.pom} ?? Or even a
variable available for the local repository - so I could point at the
file? e.g. {maven.local.repo} ??
I must be messing up the wiring?? But Google Univ. isn't giving me any
leads. ;-)
Anyone have any clues for me??
Thanks,
-- Chris
The snippet from my POM::
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-deploy-plugin/artifactId
inheritedtrue/inherited
configuration
!-- do not create unique binaries for each
snapshot --
uniqueVersionfalse/uniqueVersion
/configuration
executions
execution
phasedeploy/phase
goals
goaldeploy-file/goal
/goals
configuration
packagingjar/packaging
artifactId${project.artifactId}/
artifactId
groupId${project.groupId}/groupId
version${project.version}/version
file
${project.build.directory}/$
{project.artifactId}-${project.version}/WEB-INF/lib/$
{project.artifactId}-${project.version}.jar
/file
repositoryIdcodehaus.org/repositoryId
urldav:https://dav.codehaus.org/snapshots.repository/atomserver/
/url
!-- generatePomfalse/generatePom --
!-- pomFile${project.pom}/pomFile --
/configuration
/execution
/executions
/plugin
The bogus (empty) generated POM
project
modelVersion4.0.0/modelVersion
groupIdorg.atomserver/groupId
artifactIdatomserver/artifactId
version2.0.2-SNAPSHOT/version
/project
The NPE from generatePOMfalse
[INFO] [deploy:deploy-file {execution: default}]
[INFO] Retrieving previous build number from codehaus.org
Uploading:
https://dav.codehaus.org/snapshots.repository/atomserver//org/atomserver/atomserver/2.0.2-SNAPSHOT/atomserver-2.0.2-SNAPSHOT.jar
[INFO] Retrieving previous metadata from codehaus.org
[INFO] Uploading repository metadata for: 'snapshot
org.atomserver:atomserver:2.0.2-SNAPSHOT'
[INFO] Retrieving previous metadata from codehaus.org
[INFO]
[ERROR] FATAL ERROR
[INFO]
[INFO] null
[INFO]
[INFO] Trace
java.lang.NullPointerException
at hidden.org.codehaus.plexus.util.FileUtils.copyFile(FileUtils.java:
899)
at
org
.apache
.maven
.project
.artifact
.ProjectArtifactMetadata
.storeInLocalRepository(ProjectArtifactMetadata.java:86)
at
org
.apache
.maven
.artifact
.repository
.metadata
.DefaultRepositoryMetadataManager
.deploy(DefaultRepositoryMetadataManager.java:428)
at
org
.apache
.maven
.artifact
.deployer.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:
86)
at
org
.apache.maven.plugin.deploy.DeployFileMojo.execute(DeployFileMojo.java:
239)
at
org
.apache
.maven
.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:447)
at
org
.apache
.maven
.lifecycle
.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:
539)
at
org
.apache
.maven
.lifecycle
.DefaultLifecycleExecutor
.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:480)
at
org
.apache
.maven
.lifecycle
.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:459)
at
org
.apache
.maven
problems with the maven-deploy-plugin
Greetings,
I am generating several artifacts from my build; a WAR, a TAR.GZ, and
a JAR -- as required by downstream usage scenarios (embedded,
standalone, or webapp)
The project has WAR packaging. But I need to supply a JAR and TAR.GZ
as well. The TAR.GZ is easy -- using the assembly plugin.
And it is easy to create the JAR (using the archiveClasses in the
maven-war-plugin.
But deploying the JAR is problematic. You have to use both the maven-
install-plugin (the install-file goal). And the maven-deploy-plugin
(the deploy-file goal).
I have all this working (my POM snippet is below). But my deploy-file
solution is less than satisfactory. deploy-file requires the url
parameter, and I do not see how to generically supply this value.
More specifically, we have a deploy url for SNAPSHOTs and for
Releases. And deploy-file only lets us supply one of these. I.e.
url$
{project.distributionManagement.snapshotRepository.url}/url
I do not understand why the deploy-file goal cannot just use the
distributionManagement the way that the deploy goal does??
Can someone show me how to wire this up correctly??
As it is we would have to edit the POM when we create a Release, and
then edit it back -- which is just not right.
Thanks,
-- Chris
The complete POM snippet:
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-deploy-plugin/artifactId
inheritedtrue/inherited
configuration
!-- do not create unique binaries for each
snapshot --
uniqueVersionfalse/uniqueVersion
/configuration
executions
execution
phasedeploy/phase
goals
goaldeploy-file/goal
/goals
configuration
packagingjar/packaging
!-- the Jar is generated by the War, and
so is down in the target webapp --
file
${project.build.directory}/$
{project.artifactId}-${project.version}/WEB-INF/lib/$
{project.artifactId}-${project.version}.jar
/file
repositoryIdcodehaus.org/repositoryId
!-- TODO :: this should not have to be
specific --
url$
{project.distributionManagement.snapshotRepository.url}/url
pomFile
${basedir}/pom.xml
/pomFile
/configuration
/execution
/executions
/plugin
S'all good --- chriswberry at gmail dot com
Re: problems with the maven-deploy-plugin
On Thu, Jul 3, 2008 at 3:40 PM, Chris Berry [EMAIL PROTECTED] wrote: I am generating several artifacts from my build; a WAR, a TAR.GZ, and a JAR -- as required by downstream usage scenarios (embedded, standalone, or webapp) The project has WAR packaging. But I need to supply a JAR and TAR.GZ as well. It sounds like you are trying to do all this from a single module? The general rule with Maven is 'one main artifact per pom.' In this situation you'd have a multi-module project with one module building a jar, another building the war, and a third building the assembly, plus a parent pom to tie it all together. With that setup, 'mvn install' and 'mvn deploy' will do what you want. (That said, there is a new feature of the war plugin that will create an attached artifact containing the classes [1]. And assemblies can be combined with other modules, but I prefer to keep it all separate.) [1] http://jira.codehaus.org/browse/MWAR-131 -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: problems with the maven-deploy-plugin
Hi Wendy, With all due respect, having to build 3 separate projects, all within a multi-project -- so 4 projects where there was once 1 -- certainly doesn't seem to be in line w/ keeping it simple. Especially when all we want is some different packaging for the same raw classes/ resources. So I'll avoid that path if at all possible. I have always found maven multi-projects somewhat problematic -- particularly when generating sites, reports, etc. Thanks for the pointer to the WAR plugin. Much appreciated. I'll take a look. Still what I find confusing is that the deploy plugin is aware of SNAPSHOTs versus Releases -- and it chooses the URL dynamically from distributionManagement -- so it seems that deploy-file could too?? Thanks, -- Chris On Jul 3, 2008, at 5:53 PM, Wendy Smoak wrote: On Thu, Jul 3, 2008 at 3:40 PM, Chris Berry [EMAIL PROTECTED] wrote: I am generating several artifacts from my build; a WAR, a TAR.GZ, and a JAR -- as required by downstream usage scenarios (embedded, standalone, or webapp) The project has WAR packaging. But I need to supply a JAR and TAR.GZ as well. It sounds like you are trying to do all this from a single module? The general rule with Maven is 'one main artifact per pom.' In this situation you'd have a multi-module project with one module building a jar, another building the war, and a third building the assembly, plus a parent pom to tie it all together. With that setup, 'mvn install' and 'mvn deploy' will do what you want. (That said, there is a new feature of the war plugin that will create an attached artifact containing the classes [1]. And assemblies can be combined with other modules, but I prefer to keep it all separate.) [1] http://jira.codehaus.org/browse/MWAR-131 -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] S'all good --- chriswberry at gmail dot com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: problems with the maven-deploy-plugin
On Thu, Jul 3, 2008 at 4:07 PM, Chris Berry [EMAIL PROTECTED] wrote: Still what I find confusing is that the deploy plugin is aware of SNAPSHOTs versus Releases -- and it chooses the URL dynamically from distributionManagement -- so it seems that deploy-file could too?? I've never seen deploy-file used within a pom, it's generally used at the command line to deploy artifacts that were not built with Maven, and you supply the url. It doesn't seem unreasonable, though... you can open an enhancement issue in JIRA if you like. -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: problems with the maven-deploy-plugin
Thanks Wendy. I was going to try out the attachClassestrue/attachClasses for the maven-war-plugin, but I don't know where to get it from?? Do I need to build it myself from the SVN trunk?? So to be clear, if I use attachClasses, will this cause a JAR to be automatically installed in my local repo (for mvn install) and automatically deployed (for mvn deploy) If so, that's exactly what I'm looking for. Thanks much, -- Chris On Jul 3, 2008, at 6:24 PM, Wendy Smoak wrote: On Thu, Jul 3, 2008 at 4:07 PM, Chris Berry [EMAIL PROTECTED] wrote: Still what I find confusing is that the deploy plugin is aware of SNAPSHOTs versus Releases -- and it chooses the URL dynamically from distributionManagement -- so it seems that deploy-file could too?? I've never seen deploy-file used within a pom, it's generally used at the command line to deploy artifacts that were not built with Maven, and you supply the url. It doesn't seem unreasonable, though... you can open an enhancement issue in JIRA if you like. -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] S'all good --- chriswberry at gmail dot com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
