Re: Maven not getting latest artefact after deploy:deploy-file
On 03-08-17 17:57, Mehul Sanghvi wrote: I will do my best to illustrate with as simple an example as I can. Hopefully I don't miss anything by simplifying it. Project-A: com.my.dept dept-artefact 11.3.0.1.0-SNAPSHOT The above is uploaded to Nexus using deploy:deploy-file Project-B depends on Project-A artefact and so has the following in its POM file. com.my.dept dept-artefact 11.3.0.1.0-SNAPSHOT Nexus is setup to keep the latest 5 versions of the SNAPSHOTS. So I see the following before the upload: com/my/dept/dept-artefact/11.3.0.1.0-SNAPSHOT/dept-artefact-11.3.0.1.0--5-all.zip com/my/dept/dept-artefact/11.3.0.1.0-SNAPSHOT/dept-artefact-11.3.0.1.0--4-all.zip com/my/dept/dept-artefact/11.3.0.1.0-SNAPSHOT/dept-artefact-11.3.0.1.0--3-all.zip com/my/dept/dept-artefact/11.3.0.1.0-SNAPSHOT/dept-artefact-11.3.0.1.0--2-all.zip com/my/dept/dept-artefact/11.3.0.1.0-SNAPSHOT/dept-artefact-11.3.0.1.0--1-all.zip I have not shown the POM file and the MD5 and SHA1 files above, but they also exist with similar names. Now when I run Project-A, and it deploys a new build of the artefact to Nexus, then from the above list of files the -1-all.zip file gets deleted, and a -6-all.zip file is added, which is the latest version. When a build of Project-B is triggered, it will pick up the -5-all.zip rather than the -6-all.zip. I have to manually update the metadata in order for Project-B to pick up the latest snapshot. this reads like a bug in Nexus, or maybe it can't keep up. there is no way to control nexus from mvn deploy unless you use a nexus specific plugin or extension. You may want to look into using an up-2-date Nexus, current is 2.14.5-02 and upgrading is only 10mins work - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven not getting latest artefact after deploy:deploy-file
I will do my best to illustrate with as simple an example as I can.
Hopefully I don't miss anything by simplifying it.
Project-A:
com.my.dept
dept-artefact
11.3.0.1.0-SNAPSHOT
The above is uploaded to Nexus using deploy:deploy-file
Project-B depends on Project-A artefact and so has the following in its POM
file.
com.my.dept
dept-artefact
11.3.0.1.0-SNAPSHOT
Nexus is setup to keep the latest 5 versions of the SNAPSHOTS.
So I see the following before the upload:
com/my/dept/dept-artefact/11.3.0.1.0-SNAPSHOT/dept-artefact-11.3.0.1.0--5-all.zip
com/my/dept/dept-artefact/11.3.0.1.0-SNAPSHOT/dept-artefact-11.3.0.1.0--4-all.zip
com/my/dept/dept-artefact/11.3.0.1.0-SNAPSHOT/dept-artefact-11.3.0.1.0--3-all.zip
com/my/dept/dept-artefact/11.3.0.1.0-SNAPSHOT/dept-artefact-11.3.0.1.0--2-all.zip
com/my/dept/dept-artefact/11.3.0.1.0-SNAPSHOT/dept-artefact-11.3.0.1.0--1-all.zip
I have not shown the POM file and the MD5 and SHA1 files above, but they
also exist with similar names.
Now when I run Project-A, and it deploys a new build of the artefact to
Nexus, then from the above list of files the -1-all.zip file gets deleted,
and a -6-all.zip file is added, which is the latest version.
When a build of Project-B is triggered, it will pick up the -5-all.zip
rather than the -6-all.zip. I have to manually update
the metadata in order for Project-B to pick up the latest snapshot.
We also have scheduled tasks in Nexus that periodically run to rebuild the
metadata and the indexes, mainly due to
the level of activity we see.
Hope this helps illustrates a little better what I am running into.
cheers,
mehul
On Thu, Aug 3, 2017 at 3:19 AM, Yaron Golan wrote:
> The issue of getting the correct version when downloading is what written
> in the pom.xml file.
> It has nothing to do with whatever version you uploaded.
>
>
> Yaron Golan
>
>
> -Original Message-
> From: Mehul Sanghvi [mailto:mehul.sang...@gmail.com]
> Sent: Wednesday, August 02, 2017 7:28 PM
> To: ML Maven Users
> Subject: Maven not getting latest artefact after deploy:deploy-file
>
> Maven: 3.3.3
> Nexus: OSS 2.14.0-1
>
> We have a build process that explicitly uploads a few artefacts using
> deploy:deploy-file. Subsequent builds in the chain, will than download
> these artefacts, but they never end up getting the latest artefact from
> Nexus.
>
> We can see the artefact is available in Nexus, but I always have to do a
> manual rebuilding of the metadata in Nexus before I am able to have the
> subsequent builds pick up the latest version.
>
> Here is what we use for uploading with deploy:deploy-file:
>
> ${mvn} deploy:deploy-file -B -V --quiet -s ${settings_file}
> -P${mvn_profile} ${maven_options} ${deploy_file_options}
> -DrepositoryId=${repo_id} -Durl=${repo_url} -DgroupId=${group_id}
> -Dversion=${version} -DartifactId=${artifact_id} -Dfile=${artefact}
>
> The above is run in a bash for-loop after the variables are setup via a
> case-esac statement.
>
>
> For downloading it is just "mvn clean install -B -V -U" followed by
> locations for security settings file and maven local repo.
>
>
>
> Any thoughts or suggestion ? Let me know if more information is required.
>
> cheers,
>
> mehul
>
>
> --
> Mehul N. Sanghvi
> email: mehul.sang...@gmail.com
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
--
Mehul N. Sanghvi
email: mehul.sang...@gmail.com
RE: Maven not getting latest artefact after deploy:deploy-file
The issue of getting the correct version when downloading is what written in
the pom.xml file.
It has nothing to do with whatever version you uploaded.
Yaron Golan
-Original Message-
From: Mehul Sanghvi [mailto:mehul.sang...@gmail.com]
Sent: Wednesday, August 02, 2017 7:28 PM
To: ML Maven Users
Subject: Maven not getting latest artefact after deploy:deploy-file
Maven: 3.3.3
Nexus: OSS 2.14.0-1
We have a build process that explicitly uploads a few artefacts using
deploy:deploy-file. Subsequent builds in the chain, will than download these
artefacts, but they never end up getting the latest artefact from Nexus.
We can see the artefact is available in Nexus, but I always have to do a manual
rebuilding of the metadata in Nexus before I am able to have the subsequent
builds pick up the latest version.
Here is what we use for uploading with deploy:deploy-file:
${mvn} deploy:deploy-file -B -V --quiet -s ${settings_file} -P${mvn_profile}
${maven_options} ${deploy_file_options} -DrepositoryId=${repo_id}
-Durl=${repo_url} -DgroupId=${group_id} -Dversion=${version}
-DartifactId=${artifact_id} -Dfile=${artefact}
The above is run in a bash for-loop after the variables are setup via a
case-esac statement.
For downloading it is just "mvn clean install -B -V -U" followed by locations
for security settings file and maven local repo.
Any thoughts or suggestion ? Let me know if more information is required.
cheers,
mehul
--
Mehul N. Sanghvi
email: mehul.sang...@gmail.com
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Maven not getting latest artefact after deploy:deploy-file
Maven: 3.3.3
Nexus: OSS 2.14.0-1
We have a build process that explicitly uploads a few artefacts using
deploy:deploy-file. Subsequent builds in the chain, will than download
these artefacts, but they never end up getting the latest artefact from
Nexus.
We can see the artefact is available in Nexus, but I always have to do a
manual rebuilding of the metadata in Nexus before I am able to have the
subsequent builds pick up the latest version.
Here is what we use for uploading with deploy:deploy-file:
${mvn} deploy:deploy-file -B -V --quiet -s ${settings_file}
-P${mvn_profile} ${maven_options} ${deploy_file_options}
-DrepositoryId=${repo_id} -Durl=${repo_url} -DgroupId=${group_id}
-Dversion=${version} -DartifactId=${artifact_id} -Dfile=${artefact}
The above is run in a bash for-loop after the variables are setup via a
case-esac statement.
For downloading it is just "mvn clean install -B -V -U" followed by
locations for security settings file and maven local repo.
Any thoughts or suggestion ? Let me know if more information is required.
cheers,
mehul
--
Mehul N. Sanghvi
email: mehul.sang...@gmail.com
RE: [EXTERNAL] Re: mvn deploy:deploy-file with same groupId & artifactId but different classifiers
OK, so Maven only sees the most recent one uploaded because on Archiva, the "maven-metadata.xml" file is updated each time with the timestamp of the most recent one (either *-linux or *-win). But the 2 qualified artifacts do not share the same timestamp so one of those is not found leading to build failed. Conclusion: I will declare 2 different artifacts for now and, when I have time, I will create a meta jenkins task launching the build on windows and linux simultaneously and uploading both at the same time to Archiva. -- View this message in context: http://maven.40175.n5.nabble.com/mvn-deploy-deploy-file-with-same-groupId-artifactId-but-different-classifiers-tp5838931p5839126.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: [EXTERNAL] Re: mvn deploy:deploy-file with same groupId & artifactId but different classifiers
OK all, so I've taken the "not so clean but should solve my problem faster" road... I publish the 2 zips separatly on Archiva. But now, my main build that declare dependencies on them both (as 'runtime') seems to randomly fail, looking for one or the other. If I publish one of the 2, the main build starts passing again. It's strange and I fell like it has to do something with the time. Any idea ? my tests are always made using -U to force updates of dependencies -- View this message in context: http://maven.40175.n5.nabble.com/mvn-deploy-deploy-file-with-same-groupId-artifactId-but-different-classifiers-tp5838931p5839121.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: [EXTERNAL] Re: mvn deploy:deploy-file with same groupId & artifactId but different classifiers
Regardless of using Maven, I've always felt that for a multi-platform codebase, a build isn't successful/publishable/shippable if it hasn't succeeded on all required platforms (if the fix requires a change in the source code). So I've always favored the gather-and-deploy approach. > -Original Message- > From: Francois Marot [mailto:francois.ma...@gmail.com] > Sent: Monday, June 29, 2015 9:50 AM > To: Maven Users List > Subject: [EXTERNAL] Re: mvn deploy:deploy-file with same groupId & > artifactId but different classifiers > > @Jeff, thank you I think I'll try that. I thnink it will solve my "problem" > @Wolf: you're totally right. That is the only solution I thought of before > Jeff's. > It's the cleaner solution, but as I'm in the middle of a migration, I will > take > some shortcuts to finish sooner. But at the same time I fear the "obscure > behaviour". Hope I won't face it soon ;) > @Sandra: no problem, at least thanks for helping ! > > On a more general discussion, what do you people think ? Is Wolf's solution > the closest to The Maven Way™ or is Jeff's solution totally acceptable (even > if > it's not, I'll take it for now !) ? > > > > - - - - - > > > *François Marot06-50-91-96-38* > > On 29 June 2015 at 11:18, Jeff MAURY wrote: > > > I think you should have a look at the generatePom parameter ( > > > > https://maven.apache.org/plugins/maven-deploy-plugin/deploy-file- > mojo. > > html#generatePom > > ) > > which is true by default and should be false for the second call. > > > > Jeff > > > > On Mon, Jun 29, 2015 at 11:11 AM, Francois Marot > > > > > > wrote: > > > > > Thanks Sandra, > > > > > > but I'm not sure I understand: I already use the -Dclassifier= > > > parameter > > in > > > the 2 command I copy/pasted above. > > > Do you mean setting "linux"/"windows" instead of > > > "natives-linux"/"natives-win" would change something ? I think > > classifiers > > > are "form-free" and I kind of need the prefix "native-" in front of > > > it so that other parts of the build can handle those dependencies as > > > native > > ones > > > (for example this plugni: https://code.google.com/p/mavennatives/) > > > > > > > > > > > > - - - - - > > > > > > > > > *François Marot06-50-91-96-38* > > > > > > On 29 June 2015 at 09:57, Sandra Parsick wrote: > > > > > > > Hi, > > > > > > > > you can use the property -Dclassifier. For the Linux build I would > > > > use -Dclassifier=linux and for the Windows build -Dclassifier=win. > > > > > > > > Best regards, > > > > > > > > Sandra > > > > > > > > Am 29.06.2015 um 09:53 schrieb Francois MAROT: > > > > > Hello all, > > > > > > > > > > I'm in the process of converting an existing build to Maven. I > > > > > have > > > > > 2 Jenkins jobs building the same native library on 2 different > > > > > systems (win / lin). At the end of each one, I want to deploy > > > > > them on my Archiva repo. So I execute the following commands : > > > > > > > > > > On a Linux computer: mvn deploy:deploy-file > > > > > -Dfile=myLib-x64-natives-linux.zip -Dclassifier=natives-linux > > > > > -DgroupId=com.myCompany -DartifactId=myLib -Dversion=1.0.0 > > > > > -DrepositoryId=archiva.internal > > > > > -Durl=http://centos-dev:8090/repository/internal/ > > > > > > > > > > On a Windows computer: mvn deploy:deploy-file > > > > > -Dfile=jre-x64-natives-win.zip -Dclassifier=natives-win > > > > > -DgroupId=com.myCompany -DartifactId=myLib -Dversion=1.0.0 > > > > > -DrepositoryId=archiva.internal > > > > > -Durl=http://centos-dev:8090/repository/internal/ > > > > > > > > > > Problem is the second command leads to a "build failed" because > > > > > the pom of the project in version 1.0.0 is already deployed... > > > > > BUT, I am lucky because the artifact with classifier > > > > > "natives-win" has already been uploaded so both artifact end up > > > > > on the server correctly. So bui
Re: mvn deploy:deploy-file with same groupId & artifactId but different classifiers
@Jeff, thank you I think I'll try that. I thnink it will solve my "problem" @Wolf: you're totally right. That is the only solution I thought of before Jeff's. It's the cleaner solution, but as I'm in the middle of a migration, I will take some shortcuts to finish sooner. But at the same time I fear the "obscure behaviour". Hope I won't face it soon ;) @Sandra: no problem, at least thanks for helping ! On a more general discussion, what do you people think ? Is Wolf's solution the closest to The Maven Way™ or is Jeff's solution totally acceptable (even if it's not, I'll take it for now !) ? - - - - - *François Marot06-50-91-96-38* On 29 June 2015 at 11:18, Jeff MAURY wrote: > I think you should have a look at the generatePom parameter ( > > https://maven.apache.org/plugins/maven-deploy-plugin/deploy-file-mojo.html#generatePom > ) > which is true by default and should be false for the second call. > > Jeff > > On Mon, Jun 29, 2015 at 11:11 AM, Francois Marot > > wrote: > > > Thanks Sandra, > > > > but I'm not sure I understand: I already use the -Dclassifier= parameter > in > > the 2 command I copy/pasted above. > > Do you mean setting "linux"/"windows" instead of > > "natives-linux"/"natives-win" would change something ? I think > classifiers > > are "form-free" and I kind of need the prefix "native-" in front of it so > > that other parts of the build can handle those dependencies as native > ones > > (for example this plugni: https://code.google.com/p/mavennatives/) > > > > > > > > - - - - - > > > > > > *François Marot06-50-91-96-38* > > > > On 29 June 2015 at 09:57, Sandra Parsick wrote: > > > > > Hi, > > > > > > you can use the property -Dclassifier. For the Linux build I would use > > > -Dclassifier=linux and for the Windows build -Dclassifier=win. > > > > > > Best regards, > > > > > > Sandra > > > > > > Am 29.06.2015 um 09:53 schrieb Francois MAROT: > > > > Hello all, > > > > > > > > I'm in the process of converting an existing build to Maven. I have > > > > 2 Jenkins jobs building the same native library on 2 different > > > > systems (win / lin). At the end of each one, I want to deploy them > > > > on my Archiva repo. So I execute the following commands : > > > > > > > > On a Linux computer: mvn deploy:deploy-file > > > > -Dfile=myLib-x64-natives-linux.zip -Dclassifier=natives-linux > > > > -DgroupId=com.myCompany -DartifactId=myLib -Dversion=1.0.0 > > > > -DrepositoryId=archiva.internal > > > > -Durl=http://centos-dev:8090/repository/internal/ > > > > > > > > On a Windows computer: mvn deploy:deploy-file > > > > -Dfile=jre-x64-natives-win.zip -Dclassifier=natives-win > > > > -DgroupId=com.myCompany -DartifactId=myLib -Dversion=1.0.0 > > > > -DrepositoryId=archiva.internal > > > > -Durl=http://centos-dev:8090/repository/internal/ > > > > > > > > Problem is the second command leads to a "build failed" because the > > > > pom of the project in version 1.0.0 is already deployed... BUT, I > > > > am lucky because the artifact with classifier "natives-win" has > > > > already been uploaded so both artifact end up on the server > > > > correctly. So builds depending on them can retreive them correctly > > > > and everything is fine... ... except that I don't want to base my > > > > build on luck and would like to know what is the correct way to > > > > deploy 2 artifacts with everything being the same except the > > > > qualifier. > > > > > > > > How do you pepole deploy a same artifact but built by different > > > > computers, architectures ? > > > > > > > > I'm using Maven 3.3.1 & Apache Archiva 2.1.1 > > > > > > > > > > > > > > > > -- View this message in context: > > > > > > > > > > http://maven.40175.n5.nabble.com/mvn-deploy-deploy-file-with-same-groupId-artifactId-but-different-classifiers-tp5838931.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 > > > > > > > > > > > > -- > Jeff MAURY > > > "Legacy code" often differs from its suggested alternative by actually > working and scaling. > - Bjarne Stroustrup > > http://www.jeffmaury.com > http://riadiscuss.jeffmaury.com > http://www.twitter.com/jeffmaury >
Re: mvn deploy:deploy-file with same groupId & artifactId but different classifiers
I think you should have a look at the generatePom parameter ( https://maven.apache.org/plugins/maven-deploy-plugin/deploy-file-mojo.html#generatePom) which is true by default and should be false for the second call. Jeff On Mon, Jun 29, 2015 at 11:11 AM, Francois Marot wrote: > Thanks Sandra, > > but I'm not sure I understand: I already use the -Dclassifier= parameter in > the 2 command I copy/pasted above. > Do you mean setting "linux"/"windows" instead of > "natives-linux"/"natives-win" would change something ? I think classifiers > are "form-free" and I kind of need the prefix "native-" in front of it so > that other parts of the build can handle those dependencies as native ones > (for example this plugni: https://code.google.com/p/mavennatives/) > > > > - - - - - > > > *François Marot06-50-91-96-38* > > On 29 June 2015 at 09:57, Sandra Parsick wrote: > > > Hi, > > > > you can use the property -Dclassifier. For the Linux build I would use > > -Dclassifier=linux and for the Windows build -Dclassifier=win. > > > > Best regards, > > > > Sandra > > > > Am 29.06.2015 um 09:53 schrieb Francois MAROT: > > > Hello all, > > > > > > I'm in the process of converting an existing build to Maven. I have > > > 2 Jenkins jobs building the same native library on 2 different > > > systems (win / lin). At the end of each one, I want to deploy them > > > on my Archiva repo. So I execute the following commands : > > > > > > On a Linux computer: mvn deploy:deploy-file > > > -Dfile=myLib-x64-natives-linux.zip -Dclassifier=natives-linux > > > -DgroupId=com.myCompany -DartifactId=myLib -Dversion=1.0.0 > > > -DrepositoryId=archiva.internal > > > -Durl=http://centos-dev:8090/repository/internal/ > > > > > > On a Windows computer: mvn deploy:deploy-file > > > -Dfile=jre-x64-natives-win.zip -Dclassifier=natives-win > > > -DgroupId=com.myCompany -DartifactId=myLib -Dversion=1.0.0 > > > -DrepositoryId=archiva.internal > > > -Durl=http://centos-dev:8090/repository/internal/ > > > > > > Problem is the second command leads to a "build failed" because the > > > pom of the project in version 1.0.0 is already deployed... BUT, I > > > am lucky because the artifact with classifier "natives-win" has > > > already been uploaded so both artifact end up on the server > > > correctly. So builds depending on them can retreive them correctly > > > and everything is fine... ... except that I don't want to base my > > > build on luck and would like to know what is the correct way to > > > deploy 2 artifacts with everything being the same except the > > > qualifier. > > > > > > How do you pepole deploy a same artifact but built by different > > > computers, architectures ? > > > > > > I'm using Maven 3.3.1 & Apache Archiva 2.1.1 > > > > > > > > > > > > -- View this message in context: > > > > > > http://maven.40175.n5.nabble.com/mvn-deploy-deploy-file-with-same-groupId-artifactId-but-different-classifiers-tp5838931.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 > > > > > -- Jeff MAURY "Legacy code" often differs from its suggested alternative by actually working and scaling. - Bjarne Stroustrup http://www.jeffmaury.com http://riadiscuss.jeffmaury.com http://www.twitter.com/jeffmaury
Re: mvn deploy:deploy-file with same groupId & artifactId but different classifiers
Thanks Sandra, but I'm not sure I understand: I already use the -Dclassifier= parameter in the 2 command I copy/pasted above. Do you mean setting "linux"/"windows" instead of "natives-linux"/"natives-win" would change something ? I think classifiers are "form-free" and I kind of need the prefix "native-" in front of it so that other parts of the build can handle those dependencies as native ones (for example this plugni: https://code.google.com/p/mavennatives/) - - - - - *François Marot06-50-91-96-38* On 29 June 2015 at 09:57, Sandra Parsick wrote: > Hi, > > you can use the property -Dclassifier. For the Linux build I would use > -Dclassifier=linux and for the Windows build -Dclassifier=win. > > Best regards, > > Sandra > > Am 29.06.2015 um 09:53 schrieb Francois MAROT: > > Hello all, > > > > I'm in the process of converting an existing build to Maven. I have > > 2 Jenkins jobs building the same native library on 2 different > > systems (win / lin). At the end of each one, I want to deploy them > > on my Archiva repo. So I execute the following commands : > > > > On a Linux computer: mvn deploy:deploy-file > > -Dfile=myLib-x64-natives-linux.zip -Dclassifier=natives-linux > > -DgroupId=com.myCompany -DartifactId=myLib -Dversion=1.0.0 > > -DrepositoryId=archiva.internal > > -Durl=http://centos-dev:8090/repository/internal/ > > > > On a Windows computer: mvn deploy:deploy-file > > -Dfile=jre-x64-natives-win.zip -Dclassifier=natives-win > > -DgroupId=com.myCompany -DartifactId=myLib -Dversion=1.0.0 > > -DrepositoryId=archiva.internal > > -Durl=http://centos-dev:8090/repository/internal/ > > > > Problem is the second command leads to a "build failed" because the > > pom of the project in version 1.0.0 is already deployed... BUT, I > > am lucky because the artifact with classifier "natives-win" has > > already been uploaded so both artifact end up on the server > > correctly. So builds depending on them can retreive them correctly > > and everything is fine... ... except that I don't want to base my > > build on luck and would like to know what is the correct way to > > deploy 2 artifacts with everything being the same except the > > qualifier. > > > > How do you pepole deploy a same artifact but built by different > > computers, architectures ? > > > > I'm using Maven 3.3.1 & Apache Archiva 2.1.1 > > > > > > > > -- View this message in context: > > > http://maven.40175.n5.nabble.com/mvn-deploy-deploy-file-with-same-groupId-artifactId-but-different-classifiers-tp5838931.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: mvn deploy:deploy-file with same groupId & artifactId but different classifiers
Hi Francois, in my experience you will need to deploy from a single machine in a single call to deploy:deploy-file, attaching all the artifacts you need to deploy with qualifiers, e.g.: Use a single free form jenkins job to - synchronously trigger a multiconfiguration job in jenkins to build the native libraries (mvn install there, not mvn deploy!), - and then collect the artifacts generated from the multiconfiguration job and deploy them to your repository: mvn deploy:deploy-file \ -Durl=http://centos-dev:8090/repository/internal/ \ -DrepositoryId=archiva.internal \ -DgroupId=com.myCompany -DartifactId=myLib \ -Dversion=1.0.0 \ -Dtypes=zip,zip \ -Dclassifiers=x64-natives-linux,x64-natives-win \ -Dfiles=myLib-x64-natives-linux.zip,jre-x64-natives-win.zip \ -Dfile=some_file You will need to make up a main artifact (some_file) to deploy (cant' remember whether you could use the pom file) - I usually use a file created by combining all the machine dependent stuff into one big archive which also allows me to use a single artifact as dependency in further builds. Doing it this way avoids at least two pitfalls: - "mvn deploy" is not atomic (have a look at the output of mvn deploy to see what it does) and deploying the same artifact from two machines to the same repo is asking for trouble (like: losing one or the other from time to time) - Even if the repository manager you are using does not enforce a "deploy once" strategy (e.g. for -SNAPSHOT releases) you will end up with *multiple* versions instead of one, which can lead to really obscure behaviour when the repository manager cleans up stuff it consideres no longer necessary. Hth & Cheers, Wolf On 29.06.2015 09:53, Francois MAROT wrote: > Hello all, > > I'm in the process of converting an existing build to Maven. > I have 2 Jenkins jobs building the same native library on 2 different > systems (win / lin). At the end of each one, I want to deploy them on my > Archiva repo. > So I execute the following commands : > > On a Linux computer: > mvn deploy:deploy-file -Dfile=myLib-x64-natives-linux.zip > -Dclassifier=natives-linux -DgroupId=com.myCompany -DartifactId=myLib > -Dversion=1.0.0 -DrepositoryId=archiva.internal > -Durl=http://centos-dev:8090/repository/internal/ > > On a Windows computer: > mvn deploy:deploy-file -Dfile=jre-x64-natives-win.zip > -Dclassifier=natives-win -DgroupId=com.myCompany -DartifactId=myLib > -Dversion=1.0.0 -DrepositoryId=archiva.internal > -Durl=http://centos-dev:8090/repository/internal/ > > Problem is the second command leads to a "build failed" because the pom of > the project in version 1.0.0 is already deployed... > BUT, I am lucky because the artifact with classifier "natives-win" has > already been uploaded so both artifact end up on the server correctly. So > builds depending on them can retreive them correctly and everything is > fine... > ... except that I don't want to base my build on luck and would like to know > what is the correct way to deploy 2 artifacts with everything being the same > except the qualifier. > > How do you pepole deploy a same artifact but built by different computers, > architectures ? > > I'm using Maven 3.3.1 & Apache Archiva 2.1.1 > > > > -- > View this message in context: > http://maven.40175.n5.nabble.com/mvn-deploy-deploy-file-with-same-groupId-artifactId-but-different-classifiers-tp5838931.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: mvn deploy:deploy-file with same groupId & artifactId but different classifiers
Hi, you can use the property -Dclassifier. For the Linux build I would use -Dclassifier=linux and for the Windows build -Dclassifier=win. Best regards, Sandra Am 29.06.2015 um 09:53 schrieb Francois MAROT: > Hello all, > > I'm in the process of converting an existing build to Maven. I have > 2 Jenkins jobs building the same native library on 2 different > systems (win / lin). At the end of each one, I want to deploy them > on my Archiva repo. So I execute the following commands : > > On a Linux computer: mvn deploy:deploy-file > -Dfile=myLib-x64-natives-linux.zip -Dclassifier=natives-linux > -DgroupId=com.myCompany -DartifactId=myLib -Dversion=1.0.0 > -DrepositoryId=archiva.internal > -Durl=http://centos-dev:8090/repository/internal/ > > On a Windows computer: mvn deploy:deploy-file > -Dfile=jre-x64-natives-win.zip -Dclassifier=natives-win > -DgroupId=com.myCompany -DartifactId=myLib -Dversion=1.0.0 > -DrepositoryId=archiva.internal > -Durl=http://centos-dev:8090/repository/internal/ > > Problem is the second command leads to a "build failed" because the > pom of the project in version 1.0.0 is already deployed... BUT, I > am lucky because the artifact with classifier "natives-win" has > already been uploaded so both artifact end up on the server > correctly. So builds depending on them can retreive them correctly > and everything is fine... ... except that I don't want to base my > build on luck and would like to know what is the correct way to > deploy 2 artifacts with everything being the same except the > qualifier. > > How do you pepole deploy a same artifact but built by different > computers, architectures ? > > I'm using Maven 3.3.1 & Apache Archiva 2.1.1 > > > > -- View this message in context: > http://maven.40175.n5.nabble.com/mvn-deploy-deploy-file-with-same-groupId-artifactId-but-different-classifiers-tp5838931.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
mvn deploy:deploy-file with same groupId & artifactId but different classifiers
Hello all, I'm in the process of converting an existing build to Maven. I have 2 Jenkins jobs building the same native library on 2 different systems (win / lin). At the end of each one, I want to deploy them on my Archiva repo. So I execute the following commands : On a Linux computer: mvn deploy:deploy-file -Dfile=myLib-x64-natives-linux.zip -Dclassifier=natives-linux -DgroupId=com.myCompany -DartifactId=myLib -Dversion=1.0.0 -DrepositoryId=archiva.internal -Durl=http://centos-dev:8090/repository/internal/ On a Windows computer: mvn deploy:deploy-file -Dfile=jre-x64-natives-win.zip -Dclassifier=natives-win -DgroupId=com.myCompany -DartifactId=myLib -Dversion=1.0.0 -DrepositoryId=archiva.internal -Durl=http://centos-dev:8090/repository/internal/ Problem is the second command leads to a "build failed" because the pom of the project in version 1.0.0 is already deployed... BUT, I am lucky because the artifact with classifier "natives-win" has already been uploaded so both artifact end up on the server correctly. So builds depending on them can retreive them correctly and everything is fine... ... except that I don't want to base my build on luck and would like to know what is the correct way to deploy 2 artifacts with everything being the same except the qualifier. How do you pepole deploy a same artifact but built by different computers, architectures ? I'm using Maven 3.3.1 & Apache Archiva 2.1.1 -- View this message in context: http://maven.40175.n5.nabble.com/mvn-deploy-deploy-file-with-same-groupId-artifactId-but-different-classifiers-tp5838931.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: newbie problem with deploy:deploy-file
many many thanks
Andy
On Jun 17, 2014, at 11:28 AM, Robert Scholte wrote:
> Hi Andy,
>
> First of all: welcome in the world of Apache Maven!
> I won't go into detail too much right now, I'd suggest to do some
> getting-started tutorials[2] to understand the basics.
>
> Let's start with:
> With Maven you can call 2 things: a phase of a lifecycle[1] or a goal from a
> specific plugin.
> if you're running 'mvn deploy:deploy-file' you're only executing 1 goal.
> And 'mvn deploy' means you're executing all phases up to deploy, representing
> a chain of goals.
>
> Since you're using an execution-block I assume you just want to call 'mvn
> deploy'.
>
> thanks,
> Robert
>
> [1]
> http://maven.apache.org/guides/introduction/introduction-to-the-lifecycle.html
> [2] http://maven.apache.org/guides/index.html
>
> Op Tue, 17 Jun 2014 00:51:21 +0200 schreef Andrew Davidson
> :
>
>> Hi
>>
>> I recently joined an existing project that uses the maven ant plug into to
>> build artifacts that we need to distribute. I am trying to add support for
>> deploy-file
>>
>> $ mvn deploy:deploy-file -DskipTests 2>&1 | tee mvn.deploy-file.out
>> [ERROR] Failed to execute goal
>> org.apache.maven.plugins:maven-deploy-plugin:2.8:deploy-file (default-cli)
>> on project mary-aide-dist: The parameters 'file' for goal
>> org.apache.maven.plugins:maven-deploy-plugin:2.8:deploy-file are missing or
>> invalid -> [Help 1]
>> [ERROR]
>>
>> I have tried using -X and -e how ever I can still can not figure out what
>> the problem is.
>>
>> any idea what I am doing wrong?
>>
>> thanks
>>
>> Andy
>>
>>
>> …
>>
>>
>>
>> mary-aide-proxy-${project.version}
>>
>> libs-release
>>
>> http://maryx01-c.bogco.com:8081/artifactory/libs-release-local/
>>
>>
>> libs-snapshot
>>
>> http://maryx01-c.bigco.com:8081/artifactory/libs-snapshot-local/
>>
>>
>>
>>
>>
>> org.apache.maven.plugins
>> maven-deploy-plugin
>>
>>
>>
>> mary-aide-proxy
>> deploy
>>
>> deploy-file
>>
>>
>>
>> target/${mary-aide-proxy.tar}.tar.gz
>>
>> ${release.repositoryId}
>> ${release.url}
>> ${project.parent.groupId}
>>
>> ${project.parent.artifactId}
>> ${project.parent.version}
>> false
>> tar.gz
>>
>>
>>
>
> -
> 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: newbie problem with deploy:deploy-file
Hi Andy,
First of all: welcome in the world of Apache Maven!
I won't go into detail too much right now, I'd suggest to do some
getting-started tutorials[2] to understand the basics.
Let's start with:
With Maven you can call 2 things: a phase of a lifecycle[1] or a goal from
a specific plugin.
if you're running 'mvn deploy:deploy-file' you're only executing 1 goal.
And 'mvn deploy' means you're executing all phases up to deploy,
representing a chain of goals.
Since you're using an execution-block I assume you just want to call 'mvn
deploy'.
thanks,
Robert
[1]
http://maven.apache.org/guides/introduction/introduction-to-the-lifecycle.html
[2] http://maven.apache.org/guides/index.html
Op Tue, 17 Jun 2014 00:51:21 +0200 schreef Andrew Davidson
:
Hi
I recently joined an existing project that uses the maven ant plug into
to build artifacts that we need to distribute. I am trying to add
support for deploy-file
$ mvn deploy:deploy-file -DskipTests 2>&1 | tee mvn.deploy-file.out
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-deploy-plugin:2.8:deploy-file
(default-cli) on project mary-aide-dist: The parameters 'file' for goal
org.apache.maven.plugins:maven-deploy-plugin:2.8:deploy-file are missing
or invalid -> [Help 1]
[ERROR]
I have tried using -X and -e how ever I can still can not figure out
what the problem is.
any idea what I am doing wrong?
thanks
Andy
…
mary-aide-proxy-${project.version}
libs-release
http://maryx01-c.bogco.com:8081/artifactory/libs-release-local/
libs-snapshot
http://maryx01-c.bigco.com:8081/artifactory/libs-snapshot-local/
org.apache.maven.plugins
maven-deploy-plugin
mary-aide-proxy
deploy
deploy-file
target/${mary-aide-proxy.tar}.tar.gz
${release.repositoryId}
${release.url}
${project.parent.groupId}
${project.parent.artifactId}
${project.parent.version}
false
tar.gz
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
newbie problem with deploy:deploy-file
Hi
I recently joined an existing project that uses the maven ant plug into to
build artifacts that we need to distribute. I am trying to add support for
deploy-file
$ mvn deploy:deploy-file -DskipTests 2>&1 | tee mvn.deploy-file.out
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-deploy-plugin:2.8:deploy-file (default-cli) on
project mary-aide-dist: The parameters 'file' for goal
org.apache.maven.plugins:maven-deploy-plugin:2.8:deploy-file are missing or
invalid -> [Help 1]
[ERROR]
I have tried using -X and -e how ever I can still can not figure out what the
problem is.
any idea what I am doing wrong?
thanks
Andy
…
mary-aide-proxy-${project.version}
libs-release
http://maryx01-c.bogco.com:8081/artifactory/libs-release-local/
libs-snapshot
http://maryx01-c.bigco.com:8081/artifactory/libs-snapshot-local/
org.apache.maven.plugins
maven-deploy-plugin
mary-aide-proxy
deploy
deploy-file
target/${mary-aide-proxy.tar}.tar.gz
${release.repositoryId}
${release.url}
${project.parent.groupId}
${project.parent.artifactId}
${project.parent.version}
false
tar.gz
Re: Deploy a txt file with mvn deploy:deploy-file?
Perhaps you spelled the name of the file incorrectly? On Thu, Apr 12, 2012 at 9:59 AM, DK wrote: > Hi, > > I need to deploy a txt file with license info to a remote Nexus repository. > Can this be done with mvn deploy:deploy-file > > mvn deploy:deploy-file -DgroupId=com.xyz -DartifactId=zyx-component > -Dversion=1.0.0 -Dfile=C:/licesne.txt -Dpackaging=txt > -Durl=http://my.nexus.url > > I tried the above but packaging is obviously incorrect. Any suggestions? > > -- > View this message in context: > http://maven.40175.n5.nabble.com/Deploy-a-txt-file-with-mvn-deploy-deploy-file-tp5635723p5635723.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
Deploy a txt file with mvn deploy:deploy-file?
Hi, I need to deploy a txt file with license info to a remote Nexus repository. Can this be done with mvn deploy:deploy-file mvn deploy:deploy-file -DgroupId=com.xyz -DartifactId=zyx-component -Dversion=1.0.0 -Dfile=C:/licesne.txt -Dpackaging=txt -Durl=http://my.nexus.url I tried the above but packaging is obviously incorrect. Any suggestions? -- View this message in context: http://maven.40175.n5.nabble.com/Deploy-a-txt-file-with-mvn-deploy-deploy-file-tp5635723p5635723.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: Issue with deploy:deploy-file
Thank you for the tip! Effective pom has two definitions of "maven-deploy-plugin": one is profile and one is "plugins" section. Second definition has two "execution". First execution is generated by Maven. It runs the goal "deploy" and has "configuration/skip = true" (I set this parameter it in my profile). Second execution came from profile. Could it be an issue in "deploy" plugin? Igor On 6 February 2012 18:16, Wayne Fay [via Maven] wrote: >> I disabled "deploy" plugin using "skip" parameter and I created profile >> for >> snapshots deploys: >> ... >> For some reason the artifact is uploaded twice: > > Check mvn help:effective-pom to be sure that Maven's generated model > matches what you are expecting after evaluation of your profiles. > > Wayne > > - > To unsubscribe, e-mail: [hidden email] > For additional commands, e-mail: [hidden email] > > > > > If you reply to this email, your message will be added to the discussion > below: > http://maven.40175.n5.nabble.com/Issue-with-deploy-deploy-file-tp5459611p5460471.html > To unsubscribe from Issue with deploy:deploy-file, click here. > NAML -- View this message in context: http://maven.40175.n5.nabble.com/Issue-with-deploy-deploy-file-tp5459611p5460910.html Sent from the Maven - Users mailing list archive at Nabble.com.
Re: Issue with deploy:deploy-file
> I disabled "deploy" plugin using "skip" parameter and I created profile for > snapshots deploys: > ... > For some reason the artifact is uploaded twice: Check mvn help:effective-pom to be sure that Maven's generated model matches what you are expecting after evaluation of your profiles. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Issue with deploy:deploy-file
Hello,
I would like to set up non-trivial configuration of deploy plugin. Sometimes
it is necessary to deploy the snapshot of the artifact into public
repository and it is not needed to deploy snapshots into private repository
at all.
I disabled "deploy" plugin using "skip" parameter and I created profile for
snapshots deploys:
org.apache.maven.plugins
maven-deploy-plugin
2.7
true
...
publish-snapshot
org.apache.maven.plugins
maven-deploy-plugin
2.7
deploy-snapshot
deploy
deploy-file
http://repos.zeroturnaround.com/nexus/content/repositories/zt-public-snapshots/
zt-public-snapshots
${project.build.directory}/${zt-license-server.finalName}.zip
${project.version}
${project.groupId}
${project.artifactId}
false
zip
To upload the artifact I use the following command:
mvn clean deploy -Ppublish-snapshot
For some reason the artifact is uploaded twice:
[INFO]
[INFO] --- maven-deploy-plugin:2.7:deploy (default-deploy) @
jr-license-server-runner ---
[INFO] Skipping artifact deployment
[INFO]
[INFO] --- maven-deploy-plugin:2.7:deploy-file (deploy-snapshot) @
jr-license-server-runner ---
Downloading:
http://repos.zeroturnaround.com/nexus/content/repositories/zt-public-snapshots/com/zeroturnaround/jr-license-server/jr-license-server-runner/1.4.4-SNAPSHOT/maven-metadata.xml
Uploading:
http://repos.zeroturnaround.com/nexus/content/repositories/zt-public-snapshots/com/zeroturnaround/jr-license-server/jr-license-server-runner/1.4.4-SNAPSHOT/jr-license-server-runner-1.4.4-20120206.063112-1.zip
Uploaded:
http://repos.zeroturnaround.com/nexus/content/repositories/zt-public-snapshots/com/zeroturnaround/jr-license-server/jr-license-server-runner/1.4.4-SNAPSHOT/jr-license-server-runner-1.4.4-20120206.063112-1.zip
(32025 KB at 507.4 KB/sec)
Downloading:
http://repos.zeroturnaround.com/nexus/content/repositories/zt-public-snapshots/com/zeroturnaround/jr-license-server/jr-license-server-runner/maven-metadata.xml
Uploading:
http://repos.zeroturnaround.com/nexus/content/repositories/zt-public-snapshots/com/zeroturnaround/jr-license-server/jr-license-server-runner/1.4.4-SNAPSHOT/maven-metadata.xml
Uploaded:
http://repos.zeroturnaround.com/nexus/content/repositories/zt-public-snapshots/com/zeroturnaround/jr-license-server/jr-license-server-runner/1.4.4-SNAPSHOT/maven-metadata.xml
(637 B at 1.1 KB/sec)
Uploading:
http://repos.zeroturnaround.com/nexus/content/repositories/zt-public-snapshots/com/zeroturnaround/jr-license-server/jr-license-server-runner/maven-metadata.xml
Uploaded:
http://repos.zeroturnaround.com/nexus/content/repositories/zt-public-snapshots/com/zeroturnaround/jr-license-server/jr-license-server-runner/maven-metadata.xml
(320 B at 0.4 KB/sec)
Uploading:
http://repos.zeroturnaround.com/nexus/content/repositories/zt-public-snapshots/com/zeroturnaround/jr-license-server/jr-license-server-runner/1.4.4-SNAPSHOT/jr-license-server-runner-1.4.4-20120206.063112-1.zip
Uploaded:
http://repos.zeroturnaround.com/nexus/content/repositories/zt-public-snapshots/com/zeroturnaround/jr-license-server/jr-license-server-runner/1.4.4-SNAPSHOT/jr-license-server-runner-1.4.4-20120206.063112-1.zip
(32025 KB at 922.0 KB/sec)
Uploading:
http://repos.zeroturnaround.com/nexus/content/repositories/zt-public-snapshots/com/zeroturnaround/jr-license-server/jr-license-server-runner/1.4.4-SNAPSHOT/maven-metadata.xml
Uploaded:
http://repos.zeroturnaround.com/nexus/content/repositories/zt-public-snapshots/com/zeroturnaround/jr-license-server/jr-license-server-runner/1.4.4-SNAPSHOT/maven-metadata.xml
(637 B at 1.3 KB/sec)
[INFO]
[INFO] BUILD SUCCESS
[INFO]
Why it happens?
--
View this message in context:
http://maven.40175.n5.nabble.com/Issue-with-deploy-deploy-file-tp5459611p5459611.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 3, deploy:deploy-file and dav:http
Hi all,
I am struggling with the issue again (we previously fixed it using the
file:/ protocol, which we can't use any more, and I got webdav to work, but
we can't use it now as well...). I am trying the example maven recipe by
Jason van Zyl (using $maven_home/lib/ext) and it seems to work only for
servers with ssh and PasswordAuthentication set to 'yes'. If this is turned
off, and only PublicKeyAuthentication is allowed, it fails with 'Auth fail':
Caused by: org.apache.maven.wagon.authentication.AuthenticationException:
Cannot connect. Reason: Auth fail
at
org.apache.maven.wagon.providers.ssh.jsch.AbstractJschWagon.openConnectionInternal(AbstractJschWagon.java:264)
at
org.apache.maven.wagon.AbstractWagon.openConnection(AbstractWagon.java:105)
at org.apache.maven.wagon.AbstractWagon.connect(AbstractWagon.java:207)
at
org.sonatype.aether.connector.wagon.WagonRepositoryConnector.connectWagon(WagonRepositoryConnector.java:338)
at
org.sonatype.aether.connector.wagon.WagonRepositoryConnector.pollWagon(WagonRepositoryConnector.java:378)
at
org.sonatype.aether.connector.wagon.WagonRepositoryConnector$PutTask.run(WagonRepositoryConnector.java:817)
at
org.sonatype.aether.connector.wagon.WagonRepositoryConnector.put(WagonRepositoryConnector.java:465)
... 26 more
Caused by: com.jcraft.jsch.JSchException: Auth fail
at com.jcraft.jsch.Session.connect(Session.java:451)
at com.jcraft.jsch.Session.connect(Session.java:149)
at
org.apache.maven.wagon.providers.ssh.jsch.AbstractJschWagon.openConnectionInternal(AbstractJschWagon.java:236)
... 32 more
My config in ~/.m2/settings.xml:
...
test
test
/home/test/.ssh/id_dsa
secret
...
and the call:
mvn deploy:deploy-file -Durl=scp://test/home/test/Dev/maven_repo
-DrepositoryId=test -Dfile=upload-1.0.jar -DgroupId=test -DartifactId=test
-Dversion=1.0 -Dpackaging=jar
I can normally connect using 'ssh -l test test', so the keys and everything
is correct.
I noticed one thing: the wagon keeps asking me to accept the new unknown
server, which is well known and used by me a multitude of time, and its key
is already accepted. Upon closer look, it turns out that with 'pure' ssh the
key shown is ECDSA, and the wagon keeps asking me to accept the RSA key. My
private / public key pair is DSA - can that be, that the wagon only works
with RSA keys? This site: http://maven.apache.org/settings.html says the
default key is '${user.home}/.ssh/id_dsa)', but this somehow can't be right,
as the wagon doesn't even ask me for the passphrase (when I remove the
entry from settings.xml). Could anybody help with this?
wujek
--
View this message in context:
http://maven.40175.n5.nabble.com/maven-3-deploy-deploy-file-and-dav-http-tp3370548p5012875.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 3, deploy:deploy-file and dav:http
Go for it. I won't be using the maven site plugin anytime soon. On Aug 29, 2011, at 12:30 PM, Stephen Connolly wrote: > Jason. it would be great if we had this documented somewhere in the maven > site. > > - Stephen > > --- > Sent from my Android phone, so random spelling mistakes, random nonsense > words and other nonsense are a direct result of using swype to type on the > screen > On 29 Aug 2011 08:30, "Jason van Zyl" wrote: >> You can either use the ext/ directory in the Maven installation, or use > the extension classpath property so that the scp wagon will load. I created > a little recipe with an example of each method: >> >> > https://github.com/jvanzyl/maven-recipes/tree/master/deploy-with-scp-extension >> >> On Aug 29, 2011, at 9:18 AM, mihxil wrote: >> >>> >>> Maxime Gréau wrote: >>>> >>>> In all cases (I mean if you have an existing pom.xml or not), there will >>>> be >>>> a pom.xml with the artifact in the remote repository. >>>> >>>> If you want to deploy an existing file (jar, war...) in a remote >>>> repository, >>>> you have 2 choices : >>>> - use deploy:deploy-file goal, this goal can be execute with or without > a >>>> pom.xml [1] >>>> >>> The point is that we don't understand how you can add an extension to the >>> pom without a pom. Because you need one now to be able to connect with > ssh. >>> >>> >>> -- >>> View this message in context: > http://maven.40175.n5.nabble.com/maven-3-deploy-deploy-file-and-dav-http-tp3370548p4746131.html >>> Sent from the Maven - Users mailing list archive at Nabble.com. >>> >>> - >>> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org >>> For additional commands, e-mail: users-h...@maven.apache.org >>> >> >> Thanks, >> >> Jason >> >> -- >> Jason van Zyl >> Founder, Apache Maven >> http://twitter.com/jvanzyl >> - >> >> >> >> Thanks, Jason -- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl - A man enjoys his work when he understands the whole and when he is responsible for the quality of the whole -- Christopher Alexander, A Pattern Language
Re: maven 3, deploy:deploy-file and dav:http
Jason. it would be great if we had this documented somewhere in the maven site. - Stephen --- Sent from my Android phone, so random spelling mistakes, random nonsense words and other nonsense are a direct result of using swype to type on the screen On 29 Aug 2011 08:30, "Jason van Zyl" wrote: > You can either use the ext/ directory in the Maven installation, or use the extension classpath property so that the scp wagon will load. I created a little recipe with an example of each method: > > https://github.com/jvanzyl/maven-recipes/tree/master/deploy-with-scp-extension > > On Aug 29, 2011, at 9:18 AM, mihxil wrote: > >> >> Maxime Gréau wrote: >>> >>> In all cases (I mean if you have an existing pom.xml or not), there will >>> be >>> a pom.xml with the artifact in the remote repository. >>> >>> If you want to deploy an existing file (jar, war...) in a remote >>> repository, >>> you have 2 choices : >>> - use deploy:deploy-file goal, this goal can be execute with or without a >>> pom.xml [1] >>> >> The point is that we don't understand how you can add an extension to the >> pom without a pom. Because you need one now to be able to connect with ssh. >> >> >> -- >> View this message in context: http://maven.40175.n5.nabble.com/maven-3-deploy-deploy-file-and-dav-http-tp3370548p4746131.html >> Sent from the Maven - Users mailing list archive at Nabble.com. >> >> - >> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org >> For additional commands, e-mail: users-h...@maven.apache.org >> > > Thanks, > > Jason > > -- > Jason van Zyl > Founder, Apache Maven > http://twitter.com/jvanzyl > - > > > >
Re: maven 3, deploy:deploy-file and dav:http
You can either use the ext/ directory in the Maven installation, or use the extension classpath property so that the scp wagon will load. I created a little recipe with an example of each method: https://github.com/jvanzyl/maven-recipes/tree/master/deploy-with-scp-extension On Aug 29, 2011, at 9:18 AM, mihxil wrote: > > Maxime Gréau wrote: >> >> In all cases (I mean if you have an existing pom.xml or not), there will >> be >> a pom.xml with the artifact in the remote repository. >> >> If you want to deploy an existing file (jar, war...) in a remote >> repository, >> you have 2 choices : >> - use deploy:deploy-file goal, this goal can be execute with or without a >> pom.xml [1] >> > The point is that we don't understand how you can add an extension to the > pom without a pom. Because you need one now to be able to connect with ssh. > > > -- > View this message in context: > http://maven.40175.n5.nabble.com/maven-3-deploy-deploy-file-and-dav-http-tp3370548p4746131.html > Sent from the Maven - Users mailing list archive at Nabble.com. > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > Thanks, Jason -- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl -
Re: maven 3, deploy:deploy-file and dav:http
Just create a pom.xml with dummy coords and run from the directory with that pom using deploy:deploy-file 4.0.0 localdomain.localhost dummy 1-SNAPSHOT mvn deploy:deploy-file -DgroupId=my.groupId -DartifactId=my-artifact -Dversion=62.65 -Dfile=... -Dpackaging=... -DgeneratePom=true -Durl=... On 29 August 2011 14:18, mihxil wrote: > > Maxime Gréau wrote: >> >> In all cases (I mean if you have an existing pom.xml or not), there will >> be >> a pom.xml with the artifact in the remote repository. >> >> If you want to deploy an existing file (jar, war...) in a remote >> repository, >> you have 2 choices : >> - use deploy:deploy-file goal, this goal can be execute with or without a >> pom.xml [1] >> > The point is that we don't understand how you can add an extension to the > pom without a pom. Because you need one now to be able to connect with ssh. > > > -- > View this message in context: > http://maven.40175.n5.nabble.com/maven-3-deploy-deploy-file-and-dav-http-tp3370548p4746131.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: maven 3, deploy:deploy-file and dav:http
Maxime Gréau wrote: > > In all cases (I mean if you have an existing pom.xml or not), there will > be > a pom.xml with the artifact in the remote repository. > > If you want to deploy an existing file (jar, war...) in a remote > repository, > you have 2 choices : > - use deploy:deploy-file goal, this goal can be execute with or without a > pom.xml [1] > The point is that we don't understand how you can add an extension to the pom without a pom. Because you need one now to be able to connect with ssh. -- View this message in context: http://maven.40175.n5.nabble.com/maven-3-deploy-deploy-file-and-dav-http-tp3370548p4746131.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 3, deploy:deploy-file and dav:http
In all cases (I mean if you have an existing pom.xml or not), there will be a pom.xml with the artifact in the remote repository. If you want to deploy an existing file (jar, war...) in a remote repository, you have 2 choices : - use deploy:deploy-file goal, this goal can be execute with or without a pom.xml [1] - use a repository manager (like Nexus) and upload your file with the UI [1] http://maven.apache.org/plugins/maven-deploy-plugin/file-deployment.html Maxime Gréau. mgreau.com *Auteur du livre **Apache Maven - Maîtriser l'infrastructure d'un projet Java EE* <http://mvnbook.mgreau.com/> 2011/6/10 mihxil > > Maxime Gréau wrote: > > > > > > > > 2) If you want to use an other protocol like DAV (or SCP, FTP...), you > > have > > to add an extension in your POM, this is the example for DAV : > > > > What if you don't have a pom? I have some jars produced by other means and > want to push it to a maven repository to have it available in other > projects > which do use maven. > > > > -- > View this message in context: > http://maven.40175.n5.nabble.com/maven-3-deploy-deploy-file-and-dav-http-tp3370548p4475557.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 3, deploy:deploy-file and dav:http
Maxime Gréau wrote: > > > > 2) If you want to use an other protocol like DAV (or SCP, FTP...), you > have > to add an extension in your POM, this is the example for DAV : > What if you don't have a pom? I have some jars produced by other means and want to push it to a maven repository to have it available in other projects which do use maven. -- View this message in context: http://maven.40175.n5.nabble.com/maven-3-deploy-deploy-file-and-dav-http-tp3370548p4475557.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 3, deploy:deploy-file and dav:http
Hi, Since Maven 3.0, by default, you can only use HTTP protocol to deploy artefacts in a remote repository. 1) If you want to use HTTP protocol, you have to ensure that - your remote repository allow HTTP PUT method - your credentials are ok 2) If you want to use an other protocol like DAV (or SCP, FTP...), you have to add an extension in your POM, this is the example for DAV : org.apache.maven.wagon wagon-webdav-jackrabbit 1.0-beta-7 Maxime Gréau. http://mgreau.com 2011/2/4 wujek > > Hi. I am trying to deploy a custom artifact to our internal repo using > maven > 3.0.2: > mvn deploy:deploy-file -Dfile=file.jar -Dversion=1.0.0 > -DgroupId=com.example >-DartifactId=artifact -Dpackaging=jar -DrepositoryId=internal >-Durl=dav:http://10.1.1.7/maven_repo > > where a corresponding element with id internal is in my > settings.xml, and it has a username and password corresponding to a local > user on the machine I am trying to deploy to. This doesn't work, I get: > > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-deploy-plugin:2.5:deploy-file (default-cli) > on project standalone-pom: Failed to deploy artifacts/metadata: No > connector > available to access repository remote-repository (dav: > http://10.1.1.7/maven) > of type default using the available factories > WagonRepositoryConnectorFactory -> [Help 1] > > When I remove the dav prefix, I get: > > Uploading: http://10.1.1.7/maven/com/test/test/1/test-1.jar > Uploading: http://10.1.1.7/maven/com/test/test/1/test-1.pom > [INFO] > > [INFO] BUILD FAILURE > [INFO] > > [INFO] Total time: 1.312s > [INFO] Finished at: Fri Feb 04 08:15:35 CET 2011 > [INFO] Final Memory: 4M/117M > [INFO] > > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-deploy-plugin:2.5:deploy-file (default-cli) > on project standalone-pom: Failed to deploy artifacts: Could not transfer > artifact com.test:test:jar:1 from/to remote-repository > (http://10.1.1.7/maven): Access denied to: > http://10.1.1.7/maven/com/test/test/1/test-1.jar -> [Help 1] > > Which I think it means it tries to upload, but there is something wrong > with > the credentials? > > How can I configure this correctly? > > In maven 2, the first approach used to work, with the dav:http protocol, it > all changed in maven 3, or at least is seems so. > > Thanks. > > > -- > View this message in context: > http://maven.40175.n5.nabble.com/maven-3-deploy-deploy-file-and-dav-http-tp3370548p3370548.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 3, deploy:deploy-file and dav:http
Hi. I am trying to deploy a custom artifact to our internal repo using maven 3.0.2: mvn deploy:deploy-file -Dfile=file.jar -Dversion=1.0.0 -DgroupId=com.example -DartifactId=artifact -Dpackaging=jar -DrepositoryId=internal -Durl=dav:http://10.1.1.7/maven_repo where a corresponding element with id internal is in my settings.xml, and it has a username and password corresponding to a local user on the machine I am trying to deploy to. This doesn't work, I get: [ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.5:deploy-file (default-cli) on project standalone-pom: Failed to deploy artifacts/metadata: No connector available to access repository remote-repository (dav:http://10.1.1.7/maven) of type default using the available factories WagonRepositoryConnectorFactory -> [Help 1] When I remove the dav prefix, I get: Uploading: http://10.1.1.7/maven/com/test/test/1/test-1.jar Uploading: http://10.1.1.7/maven/com/test/test/1/test-1.pom [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 1.312s [INFO] Finished at: Fri Feb 04 08:15:35 CET 2011 [INFO] Final Memory: 4M/117M [INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.5:deploy-file (default-cli) on project standalone-pom: Failed to deploy artifacts: Could not transfer artifact com.test:test:jar:1 from/to remote-repository (http://10.1.1.7/maven): Access denied to: http://10.1.1.7/maven/com/test/test/1/test-1.jar -> [Help 1] Which I think it means it tries to upload, but there is something wrong with the credentials? How can I configure this correctly? In maven 2, the first approach used to work, with the dav:http protocol, it all changed in maven 3, or at least is seems so. Thanks. -- View this message in context: http://maven.40175.n5.nabble.com/maven-3-deploy-deploy-file-and-dav-http-tp3370548p3370548.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: deploy:deploy-file plugin
Yes, absolutely works like a charm. ..and it was in the documentation. Just couldn't find it (tree, forest). Thanks. On 10/25/10 3:28 PM, Anders Hammar wrote: Make sure to have the repositoryId param specified: http://maven.apache.org/plugins/maven-deploy-plugin/deploy-file-mojo.html#repositoryId Define the credentials matching this id in your settings.xml. /Anders On Mon, Oct 25, 2010 at 15:04, Gerard Weatherbywrote: I'm trying to use the Maven deploy plugin to upload an additional file to our online public repository. When I specify sftp://gerardw,conn...@frs.sourceforge.net: /home/groups/c/co/connjur/htdocs/m2_repo in the distributionManagement section of my pm, maven reads the necessary authentication info from settings.xml and everything works great. When I attempt the same specification in the maven-deploy-plugin configuration, it appears to ignore the user name and tries to login into frs.sourceforge.net using my local username. Is their a way to specify a user name to the maven deploy plugin? - 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: deploy:deploy-file plugin
Make sure to have the repositoryId param specified: http://maven.apache.org/plugins/maven-deploy-plugin/deploy-file-mojo.html#repositoryId Define the credentials matching this id in your settings.xml. /Anders On Mon, Oct 25, 2010 at 15:04, Gerard Weatherby wrote: > I'm trying to use the Maven deploy plugin to upload an additional file to > our online public repository. > > When I specify > sftp://gerardw,conn...@frs.sourceforge.net: > /home/groups/c/co/connjur/htdocs/m2_repo > > in the distributionManagement section of my pm, maven reads the necessary > authentication info from settings.xml and everything works great. > > When I attempt the same specification in the maven-deploy-plugin > configuration, it appears to ignore the user name and tries to login into > frs.sourceforge.net using my local username. > > Is their a way to specify a user name to the maven deploy plugin? > > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > >
deploy:deploy-file plugin
I'm trying to use the Maven deploy plugin to upload an additional file to our online public repository. When I specify sftp://gerardw,conn...@frs.sourceforge.net:/home/groups/c/co/connjur/htdocs/m2_repo in the distributionManagement section of my pm, maven reads the necessary authentication info from settings.xml and everything works great. When I attempt the same specification in the maven-deploy-plugin configuration, it appears to ignore the user name and tries to login into frs.sourceforge.net using my local username. Is their a way to specify a user name to the maven deploy plugin? - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Cannot run mvn deploy:deploy-file
I am trying to run mvn deploy:deploy-file using PSCP using maven 3 on windows 7. I have made it work without using maven using the following command: pscp bob.txt m...@repository:/var/lib/tomcat5.5/webapps/p2/deploytest/bob.txt but when I try to run the following maven goal: mvn deploy:deploy-file -Durl=pscp://repository/var/lib/tomcat5.5/webapps/p2/deploytest/ -DrepositoryId=ssh-repository -DgroupId=javax.j2ee -DartifactId=javaee -Dversion=5.0.FCS -Dpackaging=jar -Dfile=bob.txt I just get the error: [ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.5:deploy-file (default-cli) on project standalone-pom: Failed to deploy artifacts/metadata: No connector available to access repository 'ssh-repository' (pscp://repository/var/lib/tomcat5.5/webapps/p2/deploytest/) of type 'default' -> [Help 1] In .m2/settings.xml I have: ssh-repository mm mypass 700 700 plink pscp any ideas on how to make pscp work with maven? - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: deploy:deploy-file does not update local repository fully
Thank you very much! I choose to use mvn install:install-file and it works! I tried build with -U, It didn't work,because the metadata file in local repo was updated. the maven client compared the md5sum in it with the remote server, and found them matched. then didn't download the correct file. I will try turn off uniqueVersion later :) On Fri, Aug 27, 2010 at 4:59 PM, Stephen Connolly < stephen.alan.conno...@gmail.com> wrote: > deploy:deploy-file is deploying a timestamped snapshot, to update the > non-timestamped -SNAPSHOT you have three choices: > > 1. turn off uniqueVersion > 2. run install:install-file at the same time, e.g. mvn install:install-file > deploy:deploy-file -D. > 3. run the next build with -U > > Not really a bug (though I am suprised that deploy:deploy-file touches the > local repo, it makes sense to save your bandwidth, as what you upload > should > be the same as what you might download) > > -Stephen > > On 27 August 2010 09:11, Isaac wrote: > > > deploy:deploy-file does not update local repository fully. > > Let me show it to us, and ask for help too :) > > > > step 1. delete isaac_test** file in local repository > > step 2. use mvn compile command to update artifact(i get a project > dependen > > on isaac_test), list local repository directory below: > > 2010-08-27 15:56 221,105 > isaac_test-1.0.0-20100827.073702-45.jar > > 2010-08-27 15:5640 > > isaac_test-1.0.0-20100827.073702-45.jar.sha1 > > > > 2010-08-27 15:56 400 > isaac_test-1.0.0-20100827.073702-45.pom > > 2010-08-27 15:5640 > > isaac_test-1.0.0-20100827.073702-45.pom.sha1 > > > > 2010-08-27 15:56 221,105 isaac_test-1.0.0-SNAPSHOT.jar > > 2010-08-27 15:56 400 isaac_test-1.0.0-SNAPSHOT.pom > > 2010-08-27 15:56 355 maven-metadata-mqq.xml > > 2010-08-27 15:5640 maven-metadata-mqq.xml.sha1 > > > > step 3. upate the jar,then use command(i deloy it *twice *with different > > file ): > > mvn org.apache.maven.plugins:maven-deploy-plugin:2.5:deploy-file > > -Dfile=isaac_test-1.0.0-SNAPSHOT.jar -Durl=dav:http://xxx/repository/xx > > -DrepositoryId=xx <http://xxx/repository/xx%0A-DrepositoryId=xx > >-DpomFile=isaac_test-1.0.0-SNAPSHOT.pom.xml > > to deploy it to the server. > > > > step 4.list local repositoy: > > 2010-08-27 15:56 221,105 > isaac_test-1.0.0-20100827.073702-45.jar > > 2010-08-27 15:5640 > > isaac_test-1.0.0-20100827.073702-45.jar.sha1 > > > > 2010-08-27 15:56 400 > isaac_test-1.0.0-20100827.073702-45.pom > > 2010-08-27 15:5640 > > isaac_test-1.0.0-20100827.073702-45.pom.sha1 > > > > 2010-08-27 16:01 221,105 > isaac_test-1.0.0-20100827.080157-46.jar > > 2010-08-27 16:01 400 > isaac_test-1.0.0-20100827.080157-46.pom > > 2010-08-27 16:03 137,286 > isaac_test-1.0.0-20100827.080352-47.jar > > 2010-08-27 16:03 400 > isaac_test-1.0.0-20100827.080352-47.pom > > 2010-08-27 15:56 221,105 isaac_test-1.0.0-SNAPSHOT.jar > > 2010-08-27 15:56 400 isaac_test-1.0.0-SNAPSHOT.pom > > 2010-08-27 16:03 355 maven-metadata-mqq.xml > > 2010-08-27 16:0340 maven-metadata-mqq.xml.sha1 > > > > finally,compile two list of the local repository. I found the > > isaac_test-1.0.0-SNAPSHOT.jar > > DOES NOTE UPDATED! And then use mvn dependency:copy-dependency to copy > the > > newest jar, I get an old one. > > > > This problem played me both on windows xp and SUSE linux. > > >
Re: deploy:deploy-file does not update local repository fully
deploy:deploy-file is deploying a timestamped snapshot, to update the non-timestamped -SNAPSHOT you have three choices: 1. turn off uniqueVersion 2. run install:install-file at the same time, e.g. mvn install:install-file deploy:deploy-file -D. 3. run the next build with -U Not really a bug (though I am suprised that deploy:deploy-file touches the local repo, it makes sense to save your bandwidth, as what you upload should be the same as what you might download) -Stephen On 27 August 2010 09:11, Isaac wrote: > deploy:deploy-file does not update local repository fully. > Let me show it to us, and ask for help too :) > > step 1. delete isaac_test** file in local repository > step 2. use mvn compile command to update artifact(i get a project dependen > on isaac_test), list local repository directory below: > 2010-08-27 15:56 221,105 isaac_test-1.0.0-20100827.073702-45.jar > 2010-08-27 15:5640 > isaac_test-1.0.0-20100827.073702-45.jar.sha1 > > 2010-08-27 15:56 400 isaac_test-1.0.0-20100827.073702-45.pom > 2010-08-27 15:5640 > isaac_test-1.0.0-20100827.073702-45.pom.sha1 > > 2010-08-27 15:56 221,105 isaac_test-1.0.0-SNAPSHOT.jar > 2010-08-27 15:56 400 isaac_test-1.0.0-SNAPSHOT.pom > 2010-08-27 15:56 355 maven-metadata-mqq.xml > 2010-08-27 15:5640 maven-metadata-mqq.xml.sha1 > > step 3. upate the jar,then use command(i deloy it *twice *with different > file ): > mvn org.apache.maven.plugins:maven-deploy-plugin:2.5:deploy-file > -Dfile=isaac_test-1.0.0-SNAPSHOT.jar -Durl=dav:http://xxx/repository/xx > -DrepositoryId=xx > <http://xxx/repository/xx%0A-DrepositoryId=xx>-DpomFile=isaac_test-1.0.0-SNAPSHOT.pom.xml > to deploy it to the server. > > step 4.list local repositoy: > 2010-08-27 15:56 221,105 isaac_test-1.0.0-20100827.073702-45.jar > 2010-08-27 15:5640 > isaac_test-1.0.0-20100827.073702-45.jar.sha1 > > 2010-08-27 15:56 400 isaac_test-1.0.0-20100827.073702-45.pom > 2010-08-27 15:5640 > isaac_test-1.0.0-20100827.073702-45.pom.sha1 > > 2010-08-27 16:01 221,105 isaac_test-1.0.0-20100827.080157-46.jar > 2010-08-27 16:01 400 isaac_test-1.0.0-20100827.080157-46.pom > 2010-08-27 16:03 137,286 isaac_test-1.0.0-20100827.080352-47.jar > 2010-08-27 16:03 400 isaac_test-1.0.0-20100827.080352-47.pom > 2010-08-27 15:56 221,105 isaac_test-1.0.0-SNAPSHOT.jar > 2010-08-27 15:56 400 isaac_test-1.0.0-SNAPSHOT.pom > 2010-08-27 16:03 355 maven-metadata-mqq.xml > 2010-08-27 16:0340 maven-metadata-mqq.xml.sha1 > > finally,compile two list of the local repository. I found the > isaac_test-1.0.0-SNAPSHOT.jar > DOES NOTE UPDATED! And then use mvn dependency:copy-dependency to copy the > newest jar, I get an old one. > > This problem played me both on windows xp and SUSE linux. >
deploy:deploy-file does not update local repository fully
deploy:deploy-file does not update local repository fully. Let me show it to us, and ask for help too :) step 1. delete isaac_test** file in local repository step 2. use mvn compile command to update artifact(i get a project dependen on isaac_test), list local repository directory below: 2010-08-27 15:56 221,105 isaac_test-1.0.0-20100827.073702-45.jar 2010-08-27 15:5640 isaac_test-1.0.0-20100827.073702-45.jar.sha1 2010-08-27 15:56 400 isaac_test-1.0.0-20100827.073702-45.pom 2010-08-27 15:5640 isaac_test-1.0.0-20100827.073702-45.pom.sha1 2010-08-27 15:56 221,105 isaac_test-1.0.0-SNAPSHOT.jar 2010-08-27 15:56 400 isaac_test-1.0.0-SNAPSHOT.pom 2010-08-27 15:56 355 maven-metadata-mqq.xml 2010-08-27 15:5640 maven-metadata-mqq.xml.sha1 step 3. upate the jar,then use command(i deloy it *twice *with different file ): mvn org.apache.maven.plugins:maven-deploy-plugin:2.5:deploy-file -Dfile=isaac_test-1.0.0-SNAPSHOT.jar -Durl=dav:http://xxx/repository/xx -DrepositoryId=xx -DpomFile=isaac_test-1.0.0-SNAPSHOT.pom.xml to deploy it to the server. step 4.list local repositoy: 2010-08-27 15:56 221,105 isaac_test-1.0.0-20100827.073702-45.jar 2010-08-27 15:5640 isaac_test-1.0.0-20100827.073702-45.jar.sha1 2010-08-27 15:56 400 isaac_test-1.0.0-20100827.073702-45.pom 2010-08-27 15:5640 isaac_test-1.0.0-20100827.073702-45.pom.sha1 2010-08-27 16:01 221,105 isaac_test-1.0.0-20100827.080157-46.jar 2010-08-27 16:01 400 isaac_test-1.0.0-20100827.080157-46.pom 2010-08-27 16:03 137,286 isaac_test-1.0.0-20100827.080352-47.jar 2010-08-27 16:03 400 isaac_test-1.0.0-20100827.080352-47.pom 2010-08-27 15:56 221,105 isaac_test-1.0.0-SNAPSHOT.jar 2010-08-27 15:56 400 isaac_test-1.0.0-SNAPSHOT.pom 2010-08-27 16:03 355 maven-metadata-mqq.xml 2010-08-27 16:0340 maven-metadata-mqq.xml.sha1 finally,compile two list of the local repository. I found the isaac_test-1.0.0-SNAPSHOT.jar DOES NOTE UPDATED! And then use mvn dependency:copy-dependency to copy the newest jar, I get an old one. This problem played me both on windows xp and SUSE linux.
Re: deploy:deploy-file using Snapshots - timestamp/version issue
Solved my issue, if your interested see StackOverFlow:
http://stackoverflow.com/questions/2606106/maven-deploydeploy-file-not-found-due-to-version-timestamp-appended-to-jar
Regards.
On 9 April 2010 09:36, James Clinton wrote:
> I'm have a problem using deploy:deploy-file with snapshots I'd like some
> advice on please.
>
> I have 2 projects; 1) Ant based and 2) Maven based that consumes the jars
> of the other project via Archiva.
>
> I've added a target to the Ant project to deploy snapshots on every
> successful build during our iteration.
>
> The problem is the Maven project cannot find them because the name of the
> dependency has a timestamp appended like so:
>
> someJar-1.0-20100407.171211-1.jar
>
> Here is the Ant target:
>
>
>
>
>
>
>value="-Dfile=../lib/${ant.project.name}-${manifest.implementation.version}-SNAPSHOT.jar"
> />
> http://archiva.patsystems.com/archiva/repository/snapshots"; />
>
>
>
> Does anyone know what this happens or where I am going wrong?
>
> Other pure Maven projects which deploy snapshosts via mvn deploy work
> fine.
>
> Thanks
>
> James
>
--
James Clinton
Software Consultant
Avexa Consulting Ltd
james.clin...@avexa.co.uk
07941 561599
deploy:deploy-file using Snapshots - timestamp/version issue
I'm have a problem using deploy:deploy-file with snapshots I'd like some advice on please. I have 2 projects; 1) Ant based and 2) Maven based that consumes the jars of the other project via Archiva. I've added a target to the Ant project to deploy snapshots on every successful build during our iteration. The problem is the Maven project cannot find them because the name of the dependency has a timestamp appended like so: someJar-1.0-20100407.171211-1.jar Here is the Ant target: http://archiva.patsystems.com/archiva/repository/snapshots"; /> Does anyone know what this happens or where I am going wrong? Other pure Maven projects which deploy snapshosts via mvn deploy work fine. Thanks James
RE: Help on using -DpomFile option in "mvn deploy:deploy-file" command
Hi Dennis, Thanks for your response. The issue is with the pomFile=<...> option. If I run the command from the same location as pom.xml, without using the -DpomFile=<...> option, it works fine and the files are properly uploaded. However if I move 1 directory up and specify the same pom.xml file using the pomFile option, it fails. For the time being, I am cd-ing to the pom.xml location and uploading the files. It would be nice to have the pomFile option working as then I can make the uploading generic. Thanks Surendra -Original Message- From: Dennis Lundberg [mailto:denn...@apache.org] Sent: Thursday, April 16, 2009 3:45 PM To: Maven Users List Subject: Re: Help on using -DpomFile option in "mvn deploy:deploy-file" command You can find the documentation for the parameters of this plugin goal at this URL: http://maven.apache.org/plugins/maven-deploy-plugin/deploy-file-mojo.htm l You need to supply both the "url" and "file" parameters. surendra.na...@verizonwireless.com wrote: > Hi, > > While using the upload to nexus repository, used the following command > and it worked fine: > mvn -e deploy:deploy-file -DfilePath=testDir -DartifactId=test > -Dpackaging.type=ear In this case the pom.xml containg the repository > details is in the same directory. > > To make it more generic I tried to run this from another directory and > specified the pom.xml using the -DpomFile option The command I used > was: > mvn -e deploy:deploy-file -DpomFile=maven/pom.xml -DfilePath=testDir > -DartifactId=test -Dpackaging.type=ear > > Basically I moved the pom.xml to another location. However this fails > with the following message: > > [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: > > > ... > VALUE > > > -OR- > > on the command line, specify: '-Dfile=VALUE' > > [1] Inside the definition for plugin 'maven-deploy-plugin' specify the > following: > > > ... > VALUE > > > -OR- > > on the command line, specify: '-Durl=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'], Mojo parameter [name: 'url'; alias: 'null']] for mojo: > org.apache.maven.plugins:maven-deploy-plugin:2.4:deploy-file > > > Greatly appreciate any help in resolving this issue > > Thanks > > Surendra > > > The information contained in this message and any attachment may be > proprietary, confidential, and privileged or subject to the work > product doctrine and thus protected from disclosure. If the reader of > this message is not the intended recipient, or an employee or agent > responsible for delivering this message to the intended recipient, you > are hereby notified that any dissemination, distribution or copying of > this communication is strictly prohibited. > If you have received this communication in error, please notify me > immediately by replying to this message and deleting it and all copies > and backups thereof. Thank you. > > -- Dennis Lundberg - 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: Help on using -DpomFile option in "mvn deploy:deploy-file" command
You can find the documentation for the parameters of this plugin goal at this URL: http://maven.apache.org/plugins/maven-deploy-plugin/deploy-file-mojo.html You need to supply both the "url" and "file" parameters. surendra.na...@verizonwireless.com wrote: > Hi, > > While using the upload to nexus repository, used the following command > and it worked fine: > mvn -e deploy:deploy-file -DfilePath=testDir -DartifactId=test > -Dpackaging.type=ear > In this case the pom.xml containg the repository details is in the same > directory. > > To make it more generic I tried to run this from another directory and > specified the pom.xml using the -DpomFile option > The command I used was: > mvn -e deploy:deploy-file -DpomFile=maven/pom.xml > -DfilePath=testDir -DartifactId=test -Dpackaging.type=ear > > Basically I moved the pom.xml to another location. However this fails > with the following message: > > [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: > > > ... > VALUE > > > -OR- > > on the command line, specify: '-Dfile=VALUE' > > [1] Inside the definition for plugin 'maven-deploy-plugin' specify the > following: > > > ... > VALUE > > > -OR- > > on the command line, specify: '-Durl=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'], Mojo parameter [name: 'url'; alias: 'null']] for mojo: > org.apache.maven.plugins:maven-deploy-plugin:2.4:deploy-file > > > Greatly appreciate any help in resolving this issue > > Thanks > > Surendra > > > The information contained in this message and any attachment may be > proprietary, confidential, and privileged or subject to the work > product doctrine and thus protected from disclosure. If the reader > of this message is not the intended recipient, or an employee or > agent responsible for delivering this message to the intended > recipient, you are hereby notified that any dissemination, > distribution or copying of this communication is strictly prohibited. > If you have received this communication in error, please notify me > immediately by replying to this message and deleting it and all > copies and backups thereof. Thank you. > > -- Dennis Lundberg - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Help on using -DpomFile option in "mvn deploy:deploy-file" command
Hi, While using the upload to nexus repository, used the following command and it worked fine: mvn -e deploy:deploy-file -DfilePath=testDir -DartifactId=test -Dpackaging.type=ear In this case the pom.xml containg the repository details is in the same directory. To make it more generic I tried to run this from another directory and specified the pom.xml using the -DpomFile option The command I used was: mvn -e deploy:deploy-file -DpomFile=maven/pom.xml -DfilePath=testDir -DartifactId=test -Dpackaging.type=ear Basically I moved the pom.xml to another location. However this fails with the following message: [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: ... VALUE -OR- on the command line, specify: '-Dfile=VALUE' [1] Inside the definition for plugin 'maven-deploy-plugin' specify the following: ... VALUE -OR- on the command line, specify: '-Durl=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'], Mojo parameter [name: 'url'; alias: 'null']] for mojo: org.apache.maven.plugins:maven-deploy-plugin:2.4:deploy-file Greatly appreciate any help in resolving this issue Thanks Surendra The information contained in this message and any attachment may be proprietary, confidential, and privileged or subject to the work product doctrine and thus protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify me immediately by replying to this message and deleting it and all copies and backups thereof. Thank you.
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 element to false, but it throws an
NPE (See below). Does this work?
I do not know how to set the 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::
org.apache.maven.plugins
maven-deploy-plugin
true
false
deploy
deploy-file
jar
${project.artifactId}artifactId>
${project.groupId}
${project.version}
${project.build.directory}/$
{project.artifactId}-${project.version}/WEB-INF/lib/$
{project.artifactId}-${project.version}.jar
codehaus.org
dav:https://dav.codehaus.org/snapshots.repository/atomserver/
The bogus (empty) generated POM
4.0.0
org.atomserver
atomserver
2.0.2-SNAPSHOT
The NPE from false
[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
.lifecycle
.DefaultLifecycleExecutor
.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311)
at
org
.apache
.maven
.lifecycle
.DefaultLifecycleExecutor
.executeTaskSegments(DefaultLifecycleExecutor.java:278)
at
org
.apache
.maven
.lifecycle
.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:333)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:126)
at org.apache.maven.cli.MavenCli.main(MavenCli.ja
Re: problem deploying an additional artifact with maven-deploy-plugin (deploy:deploy-file)
I figured most of it out. The corrected POM snippet is below
I still have one final question; Is there a better way to write this
line :
$
{project.distributionManagement.snapshotRepository.url}
We should not have to be specific about which repo it is using.
And we should only have to set the varible in one place.
So there must be a better way to get the element??
The corrected POM snippet ::
org.apache.maven.plugins
maven-deploy-plugin
true
false
deploy
deploy-file
jar
${project.build.directory}/$
{project.artifactId}-${project.version}/WEB-INF/lib/$
{project.artifactId}-${project.version}.jar
codehaus.org
$
{project.distributionManagement.snapshotRepository.url}
${basedir}/pom.xml
On Jul 2, 2008, at 9:52 PM, Chris Berry wrote:
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 element to false, but it throws an
NPE (See below). Does this work?
I do not know how to set the 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::
org.apache.maven.plugins
maven-deploy-plugin
true
false
deploy
deploy-file
jar
${project.artifactId}artifactId>
${project.groupId}
${project.version}
${project.build.directory}/$
{project.artifactId}-${project.version}/WEB-INF/lib/$
{project.artifactId}-${project.version}.jar
codehaus.org
dav:https://dav.codehaus.org/snapshots.repository/atomserver/
The bogus (empty) generated POM
4.0.0
org.atomserver
atomserver
2.0.2-SNAPSHOT
The NPE from false
[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
.
Re: How to preserve the file name running deploy:deploy-file ?
No. You cannot change the repository layout. The file name of an artifact is part of that layout. On Sat, Apr 26, 2008 at 7:58 PM, Stefano Nichele <[EMAIL PROTECTED]> wrote: > Hi all, > running: > > mvn deploy:deploy-file -Durl=myurl -Dfile=my-file.tgz -Dpackaging=tgz > -DgroupId=mygroup -DartifactId=myartifact -Dersion=3.5.1 > -DrepositoryId=private > > the file my-file.tgz is deployed, but in the repository I have: > > mygroup > |myartifact > | 3.5.1 > | myartifact-3.5.1.tgz > > that is the artifcatId is used also as filename. > > Is there a way to change the file name ? I would like to preserve the > original one (my-file.tgz) > > Thnaks in advance > Ste > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
How to preserve the file name running deploy:deploy-file ?
Hi all, running: mvn deploy:deploy-file -Durl=myurl -Dfile=my-file.tgz -Dpackaging=tgz -DgroupId=mygroup -DartifactId=myartifact -Dersion=3.5.1 -DrepositoryId=private the file my-file.tgz is deployed, but in the repository I have: mygroup |myartifact | 3.5.1 | myartifact-3.5.1.tgz that is the artifcatId is used also as filename. Is there a way to change the file name ? I would like to preserve the original one (my-file.tgz) Thnaks in advance Ste - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Problem by deploying WAR to Tomcat by using "mvn deploy:deploy-file..."
Hi all, I have a WAR and I have no problem to deploy it to Tomcat manually. Then I try using "mvn tomcat:stop -Dmaven.tomcat.url=http://localhost:8585/manager"; to deploy it. Normally the WAR and all the directories and files will be copied to the webapps. But it's by me not the case. I can't find it in the application table in the "Tomcat Application Manager" page, I can't find the WAR under webapps, though the result says "the WAR is copy to Tomcat..." and "BUILD SUCCESSFULL". What I can find under webapps is only subdir of WEB-INF. Someone knows what's wrong? Regards Thomas - Jetzt Mails schnell in einem Vorschaufenster überfliegen. Dies und viel mehr bietet das neue Yahoo! Mail.
"deploy:deploy-file" with URL just "http://"
I found in wagon doc. that it does not support deployment for HTTP (and HTTP lightweight). It makes sense with URL like "dav:http://";, "file://" or "scpexe:" with explicit protocol. What happen if it is just plain "http://";? Which protocol will be used between maven and the remote repository? I have Proximity to host the remote repostoritory, I found that I can do both: mvn -deploy:deploy-file -DrepositoryId=xxxx -Durl=http://.. and mvn -deploy:deploy-file -DrepositoryId= -Durl=dav:http://.. I just not sure why both of them work? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: maven goal deploy:deploy-file skips the authentication?
On Mon, Nov 26, 2007 at 12:28:44PM +0100, Nicole Lacoste wrote: > Please don't address the list as gentlemen! It isn't nice for the > gentlewomen who are on the list too :-) Ouch, please excuse me, I didn't mind to offend you ;) Probably I had to use "Gentlehomo"? ;) -- Eugene N Dzhurinsky pgps0BJpxfU0B.pgp Description: PGP signature
Re: maven goal deploy:deploy-file skips the authentication?
On Mon, Nov 26, 2007 at 11:13:43AM +0100, [EMAIL PROTECTED] wrote: > If I recall correctly, there is a bug in the settings. > > When you have a repository and a server with the same id, Maven gets confused. > > So, do you also have a repository configured with id ourrepository? > > Normally I postfix every server id with .server, so in this case the server > id becomes ourrepository.server. No, I don't have any repository with same ID defined in settings.xml. -- Eugene N Dzhurinsky pgpg8Az7XaaMT.pgp Description: PGP signature
Re: maven goal deploy:deploy-file skips the authentication?
Please don't address the list as gentlemen! It isn't nice for the gentlewomen who are on the list too :-) Nicole On 26/11/2007, Eugeny N Dzhurinsky <[EMAIL PROTECTED]> wrote: > > Hello, gentlemen, we are using Artifactory to hold the modules we're using > in > Maven, for some weird reason we can't upload an artifact to the > repository. > > For example I want to deploy the artifact with such command: > > mvn deploy:deploy-file -DgroupId=org.apache.hadoop \ >-DartifactId=hadoop-core \ >-Dversion=0.14.3 \ >-Dpackaging=jar \ >-Dfile=hadoop-0.14.3-core.jar \ >-DpomFile=/home/user/tmp/hadoop-0.14.3/hadoop-pom.xml \ >-DrepositoryId=ourrepository \ >-Durl=http://our.domain.com:8080/artifactory/[EMAIL PROTECTED] > > in the ~/.m2/settings.xml I have: > > > > >ourrepository >username >password > > > > > and when doing the dump of server request/response I can see following: > > request== > PUT /artifactory/[EMAIL PROTECTED] > /org/apache/hadoop/hadoop-core/0.14.3/hadoop-core-0.14.3.jar HTTP/1.1 > User-Agent: Java/1.6.0_03-p3 > Host: our.domain.com:8080 > Accept: text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2 > Connection: keep-alive > Content-Length: 1360922 > /request= > > ===response== > HTTP/1.1 401 Authentication_is_required > WWW-Authenticate: Basic realm="Artifactory Realm" > Content-Type: text/html; charset=iso-8859-1 > Content-Length: 1481 > Server: Jetty(6.1.4) > > > > > Error 401 > > HTTP ERROR: 401Authentication is required. > RequestURI=/artifactory/[EMAIL PROTECTED] > /org/apache/hadoop/hadoop-core/0.14.3/hadoop-core-0.14.3.jar< > p>http://jetty.mortbay.org/";>Powered by > Jetty:// > ===/response= > > So it looks like the authentication credentials were not even sent to the > server. I double checked the repositoryId used in the command line and in > the > settings.xml and found there's no typo. So could somebody please explain > what > else I could miss and how to fix the problem or what do I need to do to > provide more details? > > Thank you in advance! > > -- > Eugene N Dzhurinsky > >
RE: maven goal deploy:deploy-file skips the authentication?
If I recall correctly, there is a bug in the settings. When you have a repository and a server with the same id, Maven gets confused. So, do you also have a repository configured with id ourrepository? Normally I postfix every server id with .server, so in this case the server id becomes ourrepository.server. Hth, Nick Stolwijk -Original Message- From: Eugeny N Dzhurinsky [mailto:[EMAIL PROTECTED] Sent: Mon 11/26/2007 11:07 AM To: users@maven.apache.org Subject: maven goal deploy:deploy-file skips the authentication? Hello, gentlemen, we are using Artifactory to hold the modules we're using in Maven, for some weird reason we can't upload an artifact to the repository. For example I want to deploy the artifact with such command: mvn deploy:deploy-file -DgroupId=org.apache.hadoop \ -DartifactId=hadoop-core \ -Dversion=0.14.3 \ -Dpackaging=jar \ -Dfile=hadoop-0.14.3-core.jar \ -DpomFile=/home/user/tmp/hadoop-0.14.3/hadoop-pom.xml \ -DrepositoryId=ourrepository \ -Durl=http://our.domain.com:8080/artifactory/[EMAIL PROTECTED] in the ~/.m2/settings.xml I have: ourrepository username password and when doing the dump of server request/response I can see following: request== PUT /artifactory/[EMAIL PROTECTED]/org/apache/hadoop/hadoop-core/0.14.3/hadoop-core-0.14.3.jar HTTP/1.1 User-Agent: Java/1.6.0_03-p3 Host: our.domain.com:8080 Accept: text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2 Connection: keep-alive Content-Length: 1360922 /request= ===response== HTTP/1.1 401 Authentication_is_required WWW-Authenticate: Basic realm="Artifactory Realm" Content-Type: text/html; charset=iso-8859-1 Content-Length: 1481 Server: Jetty(6.1.4) Error 401 HTTP ERROR: 401Authentication is required. RequestURI=/artifactory/[EMAIL PROTECTED]/org/apache/hadoop/hadoop-core/0.14.3/hadoop-core-0.14.3.jar< p>http://jetty.mortbay.org/";>Powered by Jetty:// ===/response= So it looks like the authentication credentials were not even sent to the server. I double checked the repositoryId used in the command line and in the settings.xml and found there's no typo. So could somebody please explain what else I could miss and how to fix the problem or what do I need to do to provide more details? Thank you in advance! -- Eugene N Dzhurinsky
maven goal deploy:deploy-file skips the authentication?
Hello, gentlemen, we are using Artifactory to hold the modules we're using in Maven, for some weird reason we can't upload an artifact to the repository. For example I want to deploy the artifact with such command: mvn deploy:deploy-file -DgroupId=org.apache.hadoop \ -DartifactId=hadoop-core \ -Dversion=0.14.3 \ -Dpackaging=jar \ -Dfile=hadoop-0.14.3-core.jar \ -DpomFile=/home/user/tmp/hadoop-0.14.3/hadoop-pom.xml \ -DrepositoryId=ourrepository \ -Durl=http://our.domain.com:8080/artifactory/[EMAIL PROTECTED] in the ~/.m2/settings.xml I have: ourrepository username password and when doing the dump of server request/response I can see following: request== PUT /artifactory/[EMAIL PROTECTED]/org/apache/hadoop/hadoop-core/0.14.3/hadoop-core-0.14.3.jar HTTP/1.1 User-Agent: Java/1.6.0_03-p3 Host: our.domain.com:8080 Accept: text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2 Connection: keep-alive Content-Length: 1360922 /request= ===response== HTTP/1.1 401 Authentication_is_required WWW-Authenticate: Basic realm="Artifactory Realm" Content-Type: text/html; charset=iso-8859-1 Content-Length: 1481 Server: Jetty(6.1.4) Error 401 HTTP ERROR: 401Authentication is required. RequestURI=/artifactory/[EMAIL PROTECTED]/org/apache/hadoop/hadoop-core/0.14.3/hadoop-core-0.14.3.jar< p>http://jetty.mortbay.org/";>Powered by Jetty:// ===/response= So it looks like the authentication credentials were not even sent to the server. I double checked the repositoryId used in the command line and in the settings.xml and found there's no typo. So could somebody please explain what else I could miss and how to fix the problem or what do I need to do to provide more details? Thank you in advance! -- Eugene N Dzhurinsky pgpXBkjmsNAXE.pgp Description: PGP signature
Re: [Maven2] deploy:deploy-file
you should be more specific when asking for info: just saying "it fails" wont help. Also you must realize that when you run a maven command, one of the first thing maven will do is probably look for a pom. therefore even though deploy:deploy-file can be run independently from any project pom, it still is a Maven deploy plugin's goal, and I guess the answer is no: you cant tell maven to disregard its possible pom environment :-) Christian-Luc Angel Todorov wrote: > > Hi guys, > > i am executing deploy:deploy-file , but I am doing this from a directory > where there are pom files and so on... Is there any way to tell maven to > disregard the contents of the directory from where I execute > deploy:deploy-file ? I ask this because if i execute deploy:deploy-file > from > somewhere that doesn't have any maven2 related things (such as POMs) in > it, > it works fine, but when i execute it from a directory that contains a POM, > it fails. > > Thanks very much in advance. > > Regards, > Angel > > -- View this message in context: http://www.nabble.com/-Maven2--deploy%3Adeploy-file-tf4566135s177.html#a13048748 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Maven2] deploy:deploy-file
Hi guys, i am executing deploy:deploy-file , but I am doing this from a directory where there are pom files and so on... Is there any way to tell maven to disregard the contents of the directory from where I execute deploy:deploy-file ? I ask this because if i execute deploy:deploy-file from somewhere that doesn't have any maven2 related things (such as POMs) in it, it works fine, but when i execute it from a directory that contains a POM, it fails. Thanks very much in advance. Regards, Angel
Re: Heap overflow in deploy:deploy-file
At least on *nix, you can set MAVEN_OPTS in ~/.mavenrc On Fri, 2007-09-07 at 11:16 +0200, Jo Vandermeeren wrote: > Have you tried increasing the max heap size for maven by setting > MAVEN_OPTS? > > On Fri, 2007-09-07 at 02:08 -0700, Larry Suto wrote: > > > Hi I am trying to upload an artifact to Maven repository with > > deploy:deploy-file. I am getting a java.lang.OutOfMemoryError > > . The file is about 42mb in size. I am using Maven 2.07. Has anyone else > > come across this problem. > > > > Thanks, > > > > Larry - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Heap overflow in deploy:deploy-file
Thanks it works On 9/7/07, ossi petz <[EMAIL PROTECTED]> wrote: > > hallo > > outofmemory yes, but with reports. > > set an env varaiable: > > MAVEN_OPTS=-Xms128m -Xmx512m > > to allow maven to use more memory. that should do the trick > > > regards > ossi > > > > Larry Suto schrieb: > > Hi I am trying to upload an artifact to Maven repository with > > deploy:deploy-file. I am getting a java.lang.OutOfMemoryError > > . The file is about 42mb in size. I am using Maven 2.07. Has anyone else > > come across this problem. > > > > Thanks, > > > > Larry > > > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
Re: Heap overflow in deploy:deploy-file
Have you tried increasing the max heap size for maven by setting MAVEN_OPTS? On Fri, 2007-09-07 at 02:08 -0700, Larry Suto wrote: > Hi I am trying to upload an artifact to Maven repository with > deploy:deploy-file. I am getting a java.lang.OutOfMemoryError > . The file is about 42mb in size. I am using Maven 2.07. Has anyone else > come across this problem. > > Thanks, > > Larry
Re: Heap overflow in deploy:deploy-file
hallo outofmemory yes, but with reports. set an env varaiable: MAVEN_OPTS=-Xms128m -Xmx512m to allow maven to use more memory. that should do the trick regards ossi Larry Suto schrieb: Hi I am trying to upload an artifact to Maven repository with deploy:deploy-file. I am getting a java.lang.OutOfMemoryError . The file is about 42mb in size. I am using Maven 2.07. Has anyone else come across this problem. Thanks, Larry - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Heap overflow in deploy:deploy-file
Hi I am trying to upload an artifact to Maven repository with deploy:deploy-file. I am getting a java.lang.OutOfMemoryError . The file is about 42mb in size. I am using Maven 2.07. Has anyone else come across this problem. Thanks, Larry
The mvn deploy:deploy-file command gives 409 "Parent doesn't exist"
Hi, I have filed an issue with WebDAV here.. Have I missed anything obvious? http://jira.codehaus.org/browse/MRM-408 Damon. -- View this message in context: http://www.nabble.com/The-mvn-deploy%3Adeploy-file-command-gives-409-%22Parent-doesn%27t-exist%22-tf3846842.html#a10895032 Sent from the archiva-users mailing list archive at Nabble.com.
Installing a jar and its source jar with deploy:deploy-file
Hi! What is the correct way for deploying a jar file and its source jar with deploy:deploy-file? I am having trouble installing a jar file and its source jar into my remote repository with deploy:deploy-file. The following commands are being used for deployment of the files: mvn deploy:deploy-file -DgroupId=myGroupId -Dversion=1.3.2-SNAPSHOT -Dpackaging=jar -Durl=scpexe://... -DartifactId=myArtifactId -Dfile=/my-jar.jar mvn deploy:deploy-file -DgroupId=myGroupId -Dversion=1.3.2-SNAPSHOT -Dpackaging=jar -Durl=scpexe://... -DartifactId=myArtifactId -Dclassifier=sources -Dfile=/my-jar-src.jar The following jars are added to the repository after the deployment commands have been run: myArtifactId-1.3.2-20070312.115122-1.jar myArtifactId-1.3.2-20070312.115133-2-sources.jar The problem seems to be that the jar and source jar have different timestamps and build numbers. Deployment of the source jar also increases the buildNumber and lastUpdated elements in the maven-metadata.xml file in the repository: 20070312.115133 2 20070312115133 When I add groupId=myGroupId, artifactId=myArtifactId, version=1.3.2-SNAPSHOT as a dependency in a Maven project Maven tries to download the non-existant myArtifactId-1.3.2-20070312.115133-2.jar from the repository. Thanks, -- Stig Inge Lea Bjørnsen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
About deploy:deploy-file
I creaded my remote repository in 10.10.100.22/app/opt/Apache2/htdocs/maven,and I can accessed it with http://10.10.100.22/mavne. now I want put a jar into it .First I added the following code in the settings.xml: maven.repo maven mavne then I used the cmd : C:\Documents and Settings\Administrator\.m2\nfa\nfa\1.0.0>mvn -X deploy:deploy-file -Dfile=nfa-1.0.0 .jar -Durl=http://10.10.100.22/mavne -DrepositoryId=maven.repo -DgroupId=nfa -DartifactId=nfa -Dve rsion=1.0.0 -Dpackaging=jar + Error stacktraces are turned on. Maven version: 2.0.4 [DEBUG] Building Maven user-level plugin registry from: 'C:\Documents and Settings\Administrator\.m2 \plugin-registry.xml' [DEBUG] Building Maven global-level plugin registry from: 'C:\Program Files\Apache Software Foundati on\maven2\bin\..\conf\plugin-registry.xml' [INFO] Scanning for projects... [INFO] Searching repository for plugin with prefix: 'deploy'. [DEBUG] maven-deploy-plugin: resolved to version 2.2.1 from repository central [DEBUG] Retrieving parent-POM: org.apache.maven.plugins:maven-plugins::1 for project: null:maven-dep loy-plugin:maven-plugin:2.2.1 from the repository. [DEBUG] Retrieving parent-POM: org.apache.maven:maven-parent::1 for project: org.apache.maven.plugin s:maven-plugins:pom:1 from the repository. [DEBUG] Retrieving parent-POM: org.apache:apache::1 for project: org.apache.maven:maven-parent:pom:1 from the repository. [INFO] [INFO] Building Maven Default Project [INFO]task-segment: [deploy:deploy-file] (aggregator-style) [INFO] [DEBUG] org.apache.maven.plugins:maven-deploy-plugin:maven-plugin:2.2.1:runtime (selected for runtim e) [DEBUG] Retrieving parent-POM: org.apache.maven:maven::2.0 for project: org.apache.maven:maven-artif act-manager:jar:2.0 from the repository. [DEBUG] org.apache.maven:maven-artifact-manager:jar:2.0:runtime (selected for runtime) [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.4:runtime (selected for runtime) [DEBUG] org.codehaus.plexus:plexus-container-default:jar:1.0-alpha-8:runtime (selected for runti me) [DEBUG] classworlds:classworlds:jar:1.1-alpha-2:runtime (selected for runtime) [DEBUG] junit:junit:jar:3.8.1:runtime (selected for runtime) [DEBUG] Retrieving parent-POM: org.apache.maven:maven::2.0 for project: org.apache.maven:maven-artif act:jar:2.0 from the repository. [DEBUG] org.apache.maven:maven-artifact:jar:2.0:runtime (selected for runtime) [DEBUG] Retrieving parent-POM: org.apache.maven:maven::2.0 for project: org.apache.maven:maven-repos itory-metadata:jar:2.0 from the repository. [DEBUG] org.apache.maven:maven-repository-metadata:jar:2.0:runtime (selected for runtime) [DEBUG] org.apache.maven.wagon:wagon-provider-api:jar:1.0-alpha-5:runtime (selected for runtime) [DEBUG] Retrieving parent-POM: org.apache.maven:maven::2.0 for project: null:maven-project:jar:2.0 f rom the repository. [DEBUG] org.apache.maven:maven-project:jar:2.0:runtime (selected for runtime) [DEBUG] Retrieving parent-POM: org.apache.maven:maven::2.0 for project: org.apache.maven:maven-model :jar:2.0 from the repository. [DEBUG] org.apache.maven:maven-model:jar:2.0:runtime (selected for runtime) [DEBUG] Retrieving parent-POM: org.apache.maven:maven::2.0 for project: null:maven-profile:jar:2.0 f rom the repository. [DEBUG] org.apache.maven:maven-profile:jar:2.0:runtime (selected for runtime) [DEBUG] Retrieving parent-POM: org.apache.maven:maven::2.0 for project: org.apache.maven:maven-core: jar:2.0 from the repository. [DEBUG] org.apache.maven:maven-core:jar:2.0:runtime (selected for runtime) [DEBUG] Retrieving parent-POM: org.apache.maven:maven::2.0 for project: null:maven-plugin-parameter- documenter:jar:2.0 from the repository. [DEBUG] org.apache.maven:maven-plugin-parameter-documenter:jar:2.0:runtime (selected for runtime ) [DEBUG] Retrieving parent-POM: org.apache.maven:maven::2.0 for project: null:maven-error-diagnostics :jar:2.0 from the repository. [DEBUG] org.apache.maven:maven-error-diagnostics:jar:2.0:runtime (selected for runtime) [DEBUG] Retrieving parent-POM: org.apache.maven:maven::2.0 for project: org.apache.maven:maven-monit or:jar:2.0 from the repository. [DEBUG] org.apache.maven:maven-monitor:jar:2.0:runtime (selected for runtime) [DEBUG] org.codehaus.plexus:plexus-interactivity-api:jar:1.0-alpha-4:runtime (selected for runti me) [DEBUG] Retrieving parent-POM: org.apache.maven:maven::2.0 for project: null:maven-settings:jar:2.0 from the repository. [DEBUG] org.apache.maven:maven-settings:jar:2.0:runtime (selected for runtime) [DEBUG] org.apache.maven.wagon:wagon-http-lightweight:jar:1.0-alpha-5:runtime (selected for runt ime) [DEBUG] org.apache.maven.wagon:wagon-file:jar:1.0-alpha-5:runtime (selected for runtime) [DEBUG] Retrieving p
having trouble using deploy:deploy-file to upload sources and javadoc
I'm having trouble using deploy:deploy-file to upload sources and javadoc. I've set up an internal repository via SCP and have uploaded DWR version 2.0m4 to it. When I use the mvn command below for either the javadoc or sources jar, I get the NullPointerException. Am I using the command correctly? Thanks in advance! ,chris (My RSA key fingerprints don't seem to be remembered either, but I expect that's unrelated.) mvn deploy:deploy-file \ -DgroupId=dwr \ -DartifactId=dwr \ -Dversion=2.0m4 \ -Dpackaging=jar \ -DgeneratePom=false \ -Dclassifier=javadoc \ -Dfile=dwr-2.0m4-javadoc.jar \ -DrepositoryId=my.org-repository \ -Durl=scp://my.org/repository = [INFO] Scanning for projects... [INFO] Searching repository for plugin with prefix: 'deploy'. [INFO] [INFO] Building Maven Default Project [INFO] task-segment: [deploy:deploy-file] (aggregator-style) [INFO] -------- [INFO] [deploy:deploy-file] The authenticity of host 'my.org' can't be established. RSA key fingerprint is 63:0c:30:95:81:ff:6c:ff:23:f6:73:71:c1:0e:fa:7b. Are you sure you want to continue connecting? (yes/no): yes Uploading: scp://my.org/repository/dwr/dwr/2.0m4/dwr-2.0m4-javadoc.jar 1134K uploaded [INFO] Retrieving previous metadata from my.org-repository The authenticity of host 'my.org' can't be established. RSA key fingerprint is 63:0c:30:95:81:ff:6c:ff:23:f6:73:71:c1:0e:fa:7b. Are you sure you want to continue connecting? (yes/no): yes [INFO] [ERROR] FATAL ERROR [INFO] [INFO] null [INFO] [INFO] Trace java.lang.NullPointerException at java.io.FileInputStream.(FileInputStream.java:103) at java.io.FileReader.(FileReader.java:55) at org.apache.maven.project.artifact.ProjectArtifactMetadata.storeInLocalRepository (ProjectArtifactMetadata.java:89) at org.apache.maven.artifact.repository.metadata.DefaultRepositoryMetadataManager.deploy (DefaultRepositoryMetadataManager.java:420) at org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy (DefaultArtifactDeployer.java:83) at org.apache.maven.plugin.deploy.DeployFileMojo.execute( DeployFileMojo.java:236) at org.apache.maven.plugin.DefaultPluginManager.executeMojo( DefaultPluginManager.java:412) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals( DefaultLifecycleExecutor.java:534) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal( DefaultLifecycleExecutor.java:488) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal( DefaultLifecycleExecutor.java:458) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures (DefaultLifecycleExecutor.java:306) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments( DefaultLifecycleExecutor.java:219) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute( DefaultLifecycleExecutor.java:140) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115) at org.apache.maven.cli.MavenCli.main(MavenCli.java:256) 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:585) 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) [INFO] [INFO] Total time: 9 seconds [INFO] Finished at: Mon Oct 09 16:48:17 PDT 2006 [INFO] Final Memory: 3M/5M [INFO]
RE: Deploy:deploy-file with sources
Thanks - Original message - From: "Jörg Schaible" <[EMAIL PROTECTED]> To: "Maven Users List" Date: Fri, 22 Sep 2006 16:02:13 +0200 Subject: RE: Deploy:deploy-file with sources Martin Gilday wrote on Friday, September 22, 2006 11:43 AM: > I am trying to deploy spring rc4 to our organisation repo. > Using deploy:deploy-file is fine, but how do also deploy the > api and source? I have them jarred up but there does not seem > to be any properties listed in the docs to specify these > along with the artifact. Is this possible? Thanks, Martin. add -Dclassifier=sources and set -DgeneratePom=false - Jörg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Deploy:deploy-file with sources
Martin Gilday wrote on Friday, September 22, 2006 11:43 AM: > I am trying to deploy spring rc4 to our organisation repo. > Using deploy:deploy-file is fine, but how do also deploy the > api and source? I have them jarred up but there does not seem > to be any properties listed in the docs to specify these > along with the artifact. Is this possible? Thanks, Martin. add -Dclassifier=sources and set -DgeneratePom=false - Jörg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Deploy:deploy-file with sources
I am trying to deploy spring rc4 to our organisation repo. Using deploy:deploy-file is fine, but how do also deploy the api and source? I have them jarred up but there does not seem to be any properties listed in the docs to specify these along with the artifact. Is this possible? Thanks, Martin.
Re: deploy a source jar using deploy:deploy-file
eclipse:eclipse has a configuration that trigger the download automatically -D On 9/12/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: Is there a predefined classifier value that will trigger the Eclipse plugin to consider this "source" when setting the "download source" checkbox? Or do I need to then add a dependency tag to my POM with the matching classifier and scope of "compile" and then attach the source myself in eclipse? --Rudy -Original Message- From: dan tran [mailto:[EMAIL PROTECTED] Sent: Tuesday, September 12, 2006 5:24 PM To: Maven Users List Subject: Re: deploy a source jar using deploy:deploy-file yes, try to set the CLASSIFIER -D On 9/12/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > Anyone know if it is possible to deploy a source jar using > deploy:deploy-file? > > I have the src for a third party jar I want to deploy into our local > repository. > > --Rudy > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: deploy a source jar using deploy:deploy-file
Is there a predefined classifier value that will trigger the Eclipse plugin to consider this "source" when setting the "download source" checkbox? Or do I need to then add a dependency tag to my POM with the matching classifier and scope of "compile" and then attach the source myself in eclipse? --Rudy -Original Message- From: dan tran [mailto:[EMAIL PROTECTED] Sent: Tuesday, September 12, 2006 5:24 PM To: Maven Users List Subject: Re: deploy a source jar using deploy:deploy-file yes, try to set the CLASSIFIER -D On 9/12/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > Anyone know if it is possible to deploy a source jar using > deploy:deploy-file? > > I have the src for a third party jar I want to deploy into our local > repository. > > --Rudy > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: deploy a source jar using deploy:deploy-file
yes, try to set the CLASSIFIER -D On 9/12/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: Anyone know if it is possible to deploy a source jar using deploy:deploy-file? I have the src for a third party jar I want to deploy into our local repository. --Rudy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
deploy a source jar using deploy:deploy-file
Anyone know if it is possible to deploy a source jar using deploy:deploy-file? I have the src for a third party jar I want to deploy into our local repository. --Rudy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[m2] deploy:deploy-file zeroing out the file to be deployed
When I try to 'mvn deploy:deploy-file' a 3rd party jar to our internal repo from my local repo the jar file that I'm trying to deploy is being zeroed out (the size) on my local box and thus on the internal repo. Has anyone seen this before? This is the command I'm executing: mvn deploy:deploy-file -DpomFile=./test-4.6.1-SNAPSHOT.pom -Dfile=./test-4.6.1-SNAPSHOT.jar -DrepositoryId=ftp-repo -Durl=sftp://192.168.1.15/maven2/ -DuniqueVersion=false TIA, Scott Williams J2EE Specialist Founder and CTO Taylor Solutions, Inc. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [m2] mvn deploy:deploy-file
Great! That's just what I need. Now I ditch the profile from my settings.xml. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of ben short Sent: 05 June 2006 23:10 To: Maven Users List Subject: Re: [m2] mvn deploy:deploy-file Adam, You can use the deploy:deploy-file to deploy via scp. use url scp://url.to.repo Then in your settings.xml you specify a server element that has the usrname and password to use. eg: internal mvn mvn Ben On 6/5/06, Adam Hardy <[EMAIL PROTECTED]> wrote: > It's not on an ftp server because I'm serving it using maven-proxy. People have to scp to the linux box and add it all manually. > > > > Kathryn Huxtable on 05/06/06 18:47, wrote: > > So can't you add the internal repository anyway for deployment purposes? -K > > > > > > On 6/5/06 12:38 PM, "Adam Hardy" <[EMAIL PROTECTED]> wrote: > > > >> I have a question about mvn deploy:deploy-file. I would like to be able > >> to specify the repository URL on its own, because I am using maven-proxy > >> as a method of serving our company repository to the team. Therefore I > >> don't need an entry in the settings.xml. > >> > >> If I don't specify the repository in my settings.xml though, maven > >> complains and demands that I give the id from the settings.xml. > >> > >> > >> mvn deploy:deploy-file -DgroupId=com.mycompany.cortex > >> -DartifactId=soa-services > >> -Dfile=target/soa_services.jar > >> -DgeneratePom=true > >> -Dpackaging=jar > >> -Durl=file:///ctxtools/jar-repository/company-repo/ > >> -DrepositoryId=company > >> -Dversion=1.0 > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] mvn deploy:deploy-file
Adam, You can use the deploy:deploy-file to deploy via scp. use url scp://url.to.repo Then in your settings.xml you specify a server element that has the usrname and password to use. eg: internal mvn mvn Ben On 6/5/06, Adam Hardy <[EMAIL PROTECTED]> wrote: It's not on an ftp server because I'm serving it using maven-proxy. People have to scp to the linux box and add it all manually. Kathryn Huxtable on 05/06/06 18:47, wrote: > So can't you add the internal repository anyway for deployment purposes? -K > > > On 6/5/06 12:38 PM, "Adam Hardy" <[EMAIL PROTECTED]> wrote: > >> I have a question about mvn deploy:deploy-file. I would like to be able >> to specify the repository URL on its own, because I am using maven-proxy >> as a method of serving our company repository to the team. Therefore I >> don't need an entry in the settings.xml. >> >> If I don't specify the repository in my settings.xml though, maven >> complains and demands that I give the id from the settings.xml. >> >> >> mvn deploy:deploy-file -DgroupId=com.mycompany.cortex >> -DartifactId=soa-services >> -Dfile=target/soa_services.jar >> -DgeneratePom=true >> -Dpackaging=jar >> -Durl=file:///ctxtools/jar-repository/company-repo/ >> -DrepositoryId=company >> -Dversion=1.0 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] mvn deploy:deploy-file
It's not on an ftp server because I'm serving it using maven-proxy. People have to scp to the linux box and add it all manually. Kathryn Huxtable on 05/06/06 18:47, wrote: So can't you add the internal repository anyway for deployment purposes? -K On 6/5/06 12:38 PM, "Adam Hardy" <[EMAIL PROTECTED]> wrote: I have a question about mvn deploy:deploy-file. I would like to be able to specify the repository URL on its own, because I am using maven-proxy as a method of serving our company repository to the team. Therefore I don't need an entry in the settings.xml. If I don't specify the repository in my settings.xml though, maven complains and demands that I give the id from the settings.xml. mvn deploy:deploy-file -DgroupId=com.mycompany.cortex -DartifactId=soa-services -Dfile=target/soa_services.jar -DgeneratePom=true -Dpackaging=jar -Durl=file:///ctxtools/jar-repository/company-repo/ -DrepositoryId=company -Dversion=1.0 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] mvn deploy:deploy-file
So can't you add the internal repository anyway for deployment purposes? -K On 6/5/06 12:38 PM, "Adam Hardy" <[EMAIL PROTECTED]> wrote: > I have a question about mvn deploy:deploy-file. I would like to be able > to specify the repository URL on its own, because I am using maven-proxy > as a method of serving our company repository to the team. Therefore I > don't need an entry in the settings.xml. > > If I don't specify the repository in my settings.xml though, maven > complains and demands that I give the id from the settings.xml. > > > mvn deploy:deploy-file -DgroupId=com.mycompany.cortex > -DartifactId=soa-services > -Dfile=target/soa_services.jar > -DgeneratePom=true > -Dpackaging=jar > -Durl=file:///ctxtools/jar-repository/company-repo/ > -DrepositoryId=company > -Dversion=1.0 > > > Thanks > Adam > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[m2] mvn deploy:deploy-file
I have a question about mvn deploy:deploy-file. I would like to be able to specify the repository URL on its own, because I am using maven-proxy as a method of serving our company repository to the team. Therefore I don't need an entry in the settings.xml. If I don't specify the repository in my settings.xml though, maven complains and demands that I give the id from the settings.xml. mvn deploy:deploy-file -DgroupId=com.mycompany.cortex -DartifactId=soa-services -Dfile=target/soa_services.jar -DgeneratePom=true -Dpackaging=jar -Durl=file:///ctxtools/jar-repository/company-repo/ -DrepositoryId=company -Dversion=1.0 Thanks Adam - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Deploying 3rd party artifacts with mvn deploy:deploy-file
Hello, I have added the element and appropriate inner elements (at least I think I did) to my settings.xml - thx for the help. But, I am still being prompted for my password. I want to use a different uid not the one I am logged in with. Here is my settings.xml file scm.bpsserver.com scm somepwd 444 755 This is the output: linux: mvn -e deploy:deploy-file -Durl=scp://[EMAIL PROTECTED]:/data/maven/repository -DrepositoryId=bpsRepository -DgeneratePom=true -DartifactId=acegi-security -DgroupId=acegi -Dversion=v0.7.0 -Dpackaging=jar -Dfile=acegi-security-v0.7.0.jar + Error stacktraces are turned on. [INFO] Scanning for projects... [INFO] Searching repository for plugin with prefix: 'deploy'. [INFO] [INFO] Building Maven Quick Start Archetype [INFO]task-segment: [deploy:deploy-file] (aggregator-style) [INFO] ---- [INFO] [deploy:deploy-file] Password for [EMAIL PROTECTED]: linux: I just do not understand what I need to do to use a different uid :-( Thx again for all the help ... -- Regards, Douglas WF Acheson On Tue, 2006-04-25 at 06:55 -0700, Wendy Smoak wrote: > On 4/25/06, Douglas WF Acheson <[EMAIL PROTECTED]> wrote: > > > I expected to be prompted for the password for the user www, but I was > > prompted for my password, h. So my question is, how do I specify > > the uid and password or key (for ssh) for this goal? > > In ~/.m2/settings.xml, add a for dwfa. > > Here's the model: http://maven.apache.org/maven-settings/settings.html > > The 'Suggested Settings' section here has an example of using a private key: >http://wiki.apache.org/struts/StrutsMaintenanceMaven > > HTH, > -- > Wendy > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Deploying 3rd party artifacts with mvn deploy:deploy-file
On 4/25/06, Douglas WF Acheson <[EMAIL PROTECTED]> wrote: > I expected to be prompted for the password for the user www, but I was > prompted for my password, h. So my question is, how do I specify > the uid and password or key (for ssh) for this goal? In ~/.m2/settings.xml, add a for dwfa. Here's the model: http://maven.apache.org/maven-settings/settings.html The 'Suggested Settings' section here has an example of using a private key: http://wiki.apache.org/struts/StrutsMaintenanceMaven HTH, -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Deploying 3rd party artifacts with mvn deploy:deploy-file
Hello, I am (really) new to Maven (using maven 2), and having trouble with a few things regarding deploying 3rd party artifacts to a remote repository (owned by me). I would like to deploy an artifact to my http server (using apache) using the http protocol. Accroding to my understanding I would do something like this: mvn deploy:deploy-file -DartifactId=spring-mock \ -Dfile=spring-mock-v1.2.4.jar \ -DgeneratePom=true \ -DgroupId=org.springframework \ -Dversion=1.2.4 \ -Dpackaging=jar \ -Durl=http://10.0.0.200/repository \ -DrepositoryId=dwfa I tried this and got a 405 response, which sorta makes sense to me as I do not have a cgi (or something of the like) application to receive the artifacts and store it in the correct location. So my question is, is there such a server-side process to handle this? Secondly, I thought I would try using scp to push the artifacts to the location where the http server is serving up the repository. I tried the following: mvn deploy:deploy-file -DartifactId=spring-mock \ -Dfile=spring-mock-v1.2.4.jar \ -DgeneratePom=true \ -DgroupId=org.springframework \ -Dversion=1.2.4 \ -Dpackaging=jar \ -Durl=scp://[EMAIL PROTECTED]:/home/www/repository/html \ -DrepositoryId=dwfa I expected to be prompted for the password for the user www, but I was prompted for my password, h. So my question is, how do I specify the uid and password or key (for ssh) for this goal? BTW, I have the file protocol working -). I have searched through the mailing list and did not find any articles that could help me (prolly entering wrong keyword search). I am using maven 2.0.4, running under Linux FC4 -- Regards, Douglas WF Acheson - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Problem with downloading files created with maven deploy:deploy-file CHECKSUM FAILED
When you upload the files using deploy-file, it is creating the files with following persmission. -rw-rw. If I change permission to -rw-rw-r-- (664) it is able to download the file. Thanks Gautham Pamu On 3/7/06, Carlos Sanchez <[EMAIL PROTECTED]> wrote: > > Please create an issue at http://jira.codehaus.org/browse/MDEPLOY if > it's not already there, with as much information as you can (eg. > attach files and checksum) > > On 3/7/06, Gautham Pamu <[EMAIL PROTECTED]> wrote: > > Hi Everyone, > > > > Already posted this question, posting it again with different subject > line.. > > > > I have the files on my remote repository and was also able to access the > jar > > files, pom files using the browser but > > i am getting following check sum failed error. I have using maven > > deploy:deploy-file to create my repository. > > Can you please tell us how to resolve this problem ? Is this problem > with > > md5 files or is it a problem with web server. > > > > Directory of R:\test\test\6.0.1 > > > > 03/07/2006 12:40 AM . > > 03/07/2006 12:40 AM .. > > 03/07/2006 12:15 AM 1,157 test-6.0.1.jar > > 03/07/2006 12:15 AM 342 test-6.0.1.pom > > 03/07/2006 12:15 AM32 test-6.0.1.jar.md5 > > 03/07/2006 12:15 AM40 test-6.0.1.jar.sha1 > > 03/07/2006 12:15 AM32 test-6.0.1.pom.md5 > > 03/07/2006 12:15 AM40 test-6.0.1.pom.sha1 > >6 File(s) 1,643 bytes > >2 Dir(s) 1,796,906,942,464 bytes free > > > > > > Directory of R:\test\test > > > > 03/07/2006 12:40 AM . > > 03/07/2006 12:17 AM .. > > 03/07/2006 12:15 AM 292 maven-metadata.xml > > 03/07/2006 12:15 AM32 maven-metadata.xml.md5 > > 03/07/2006 12:15 AM40 maven-metadata.xml.sha1 > > 03/07/2006 12:40 AM 6.0.1 > >3 File(s)364 bytes > >3 Dir(s) 1,796,906,942,464 bytes free > > > > > > [INFO] > > > > > [INFO] Building maven.repositorytools > > [INFO]task-segment: [install] > > [INFO] > > > > > [INFO] [resources:resources] > > [INFO] Using default encoding to copy filtered resources. > > Downloading: > > > http://hostname1/projects/c/buildrepository/maven/repository/test/test/6.0.1/test-6.0.1.po > > m > > [WARNING] *** CHECKSUM FAILED - Invalid checksum file - RETRYING > > Downloading: > > > http://hostname1/projects/c/buildrepository/maven/repository/test/test/6.0.1/test-6.0.1.po > > m > > [WARNING] *** CHECKSUM FAILED - Invalid checksum file - IGNORING > > [WARNING] Unable to get resource from repository repository ( > > http://hostname1/projects/c/buildrepository/ma > > ven/repository) > > Downloading: > http://repo1.maven.org/maven2/test/test/6.0.1/test-6.0.1.pom > > [WARNING] Unable to get resource from repository central ( > > http://repo1.maven.org/maven2) > > Downloading: > > > http://hostname1/projects/c/buildrepository/maven/repository/test/test/6.0.1/test-6.0.1.ja > > r > > [WARNING] *** CHECKSUM FAILED - Invalid checksum file - RETRYING > > Downloading: > > > http://hostname1/projects/c/buildrepository/maven/repository/test/test/6.0.1/test-6.0.1.ja > > r > > [WARNING] *** CHECKSUM FAILED - Invalid checksum file - IGNORING > > [WARNING] Unable to get resource from repository repository ( > > http://hostname1/projects/c/buildrepository/ma > > ven/repository) > > Downloading: > http://repo1.maven.org/maven2/test/test/6.0.1/test-6.0.1.jar > > [WARNING] Unable to get resource from repository central ( > > http://repo1.maven.org/maven2) > > [INFO] > > > > > [ERROR] BUILD ERROR > > [INFO] > > > > > [INFO] Failed to resolve artifact. > > > > required artifacts missing: > > -- > > -Gautham Pamu > > > > > > > -- > I could give you my word as a Spaniard. > No good. I've known too many Spaniards. > -- The Princess Bride > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- -Gautham Pamu
Re: [m2] How to use deploy:deploy-file to manage my private repo ?
On 3/30/06, Nicolas De Loof <[EMAIL PROTECTED]> wrote: > > > Hello, > > I've got to add some private / restricted artifacts in my corporate > repo, but I'd like to avoid creating all the required directories. > > install:intall-file can be used to put an artifact in local repo. Can I > use deploy:deploy-file to do the same in my corporate repo ? Yep. See: http://maven.apache.org/guides/mini/guide-deploying-3rd-party-jars.html You'll also need to add a entry to your settings.xml. See: http://maven.apache.org/maven-settings/settings.html#class_server How to set the remote repository path (I cannot find an entry for this > in setting.xml) ? That's specified in the 'url' value to deploy:deploy-file. -- Martin Cooper Nico. > > > > > > This message contains information that may be privileged or confidential > and is the property of the Capgemini Group. It is intended only for the > person to whom it is addressed. If you are not the intended recipient, you > are not authorized to read, print, retain, copy, disseminate, distribute, > or use this message or any part thereof. If you receive this message in > error, please notify the sender immediately and delete all copies of this > message. > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
Re: [m2] How to use deploy:deploy-file to manage my private repo ?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Nico, > install:intall-file can be used to put an artifact in local repo. Can I > use deploy:deploy-file to do the same in my corporate repo ? Yes. > How to set the remote repository path (I cannot find an entry for this > in setting.xml) ? It depends on how you access your remote repository :-) In our company I've set up a local maven proxy which is used to distribute jars from ibiblio.org as well as our internal ones and to which I have direct file access. To deploy a new jar to the proxy I'm using the following command line: $ mvn deploy:deploy-file -DrepositoryId=bender -Durl=file://H:/maven-proxy/target/repo-local -Dpackaging=jar -DgroupId= -DartifactId= -Dversion= -Dfile= My settings.xml: ... bender HTH Thorsten -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2.2 (MingW32) iD8DBQFEK/kVQvObkgCcDe0RAqGPAKCyav64wUa9pbFyg+b2ES9iOLVM0wCgvt+8 EQqvCqZkxANK9BwCw9Yj+qs= =QO/i -END PGP SIGNATURE- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[m2] How to use deploy:deploy-file to manage my private repo ?
Hello, I've got to add some private / restricted artifacts in my corporate repo, but I'd like to avoid creating all the required directories. install:intall-file can be used to put an artifact in local repo. Can I use deploy:deploy-file to do the same in my corporate repo ? How to set the remote repository path (I cannot find an entry for this in setting.xml) ? Nico. This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Problem with downloading files created with maven deploy:deploy-file CHECKSUM FAILED
Please create an issue at http://jira.codehaus.org/browse/MDEPLOY if it's not already there, with as much information as you can (eg. attach files and checksum) On 3/7/06, Gautham Pamu <[EMAIL PROTECTED]> wrote: > Hi Everyone, > > Already posted this question, posting it again with different subject line.. > > I have the files on my remote repository and was also able to access the jar > files, pom files using the browser but > i am getting following check sum failed error. I have using maven > deploy:deploy-file to create my repository. > Can you please tell us how to resolve this problem ? Is this problem with > md5 files or is it a problem with web server. > > Directory of R:\test\test\6.0.1 > > 03/07/2006 12:40 AM . > 03/07/2006 12:40 AM .. > 03/07/2006 12:15 AM 1,157 test-6.0.1.jar > 03/07/2006 12:15 AM 342 test-6.0.1.pom > 03/07/2006 12:15 AM32 test-6.0.1.jar.md5 > 03/07/2006 12:15 AM40 test-6.0.1.jar.sha1 > 03/07/2006 12:15 AM32 test-6.0.1.pom.md5 > 03/07/2006 12:15 AM40 test-6.0.1.pom.sha1 >6 File(s) 1,643 bytes >2 Dir(s) 1,796,906,942,464 bytes free > > > Directory of R:\test\test > > 03/07/2006 12:40 AM . > 03/07/2006 12:17 AM .. > 03/07/2006 12:15 AM 292 maven-metadata.xml > 03/07/2006 12:15 AM32 maven-metadata.xml.md5 > 03/07/2006 12:15 AM40 maven-metadata.xml.sha1 > 03/07/2006 12:40 AM 6.0.1 >3 File(s)364 bytes >3 Dir(s) 1,796,906,942,464 bytes free > > > [INFO] > > [INFO] Building maven.repositorytools > [INFO]task-segment: [install] > [INFO] > > [INFO] [resources:resources] > [INFO] Using default encoding to copy filtered resources. > Downloading: > http://hostname1/projects/c/buildrepository/maven/repository/test/test/6.0.1/test-6.0.1.po > m > [WARNING] *** CHECKSUM FAILED - Invalid checksum file - RETRYING > Downloading: > http://hostname1/projects/c/buildrepository/maven/repository/test/test/6.0.1/test-6.0.1.po > m > [WARNING] *** CHECKSUM FAILED - Invalid checksum file - IGNORING > [WARNING] Unable to get resource from repository repository ( > http://hostname1/projects/c/buildrepository/ma > ven/repository) > Downloading: http://repo1.maven.org/maven2/test/test/6.0.1/test-6.0.1.pom > [WARNING] Unable to get resource from repository central ( > http://repo1.maven.org/maven2) > Downloading: > http://hostname1/projects/c/buildrepository/maven/repository/test/test/6.0.1/test-6.0.1.ja > r > [WARNING] *** CHECKSUM FAILED - Invalid checksum file - RETRYING > Downloading: > http://hostname1/projects/c/buildrepository/maven/repository/test/test/6.0.1/test-6.0.1.ja > r > [WARNING] *** CHECKSUM FAILED - Invalid checksum file - IGNORING > [WARNING] Unable to get resource from repository repository ( > http://hostname1/projects/c/buildrepository/ma > ven/repository) > Downloading: http://repo1.maven.org/maven2/test/test/6.0.1/test-6.0.1.jar > [WARNING] Unable to get resource from repository central ( > http://repo1.maven.org/maven2) > [INFO] > > [ERROR] BUILD ERROR > [INFO] > > [INFO] Failed to resolve artifact. > > required artifacts missing: > -- > -Gautham Pamu > > -- I could give you my word as a Spaniard. No good. I've known too many Spaniards. -- The Princess Bride - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Problem with downloading files created with maven deploy:deploy-file CHECKSUM FAILED
Hi Everyone, Already posted this question, posting it again with different subject line.. I have the files on my remote repository and was also able to access the jar files, pom files using the browser but i am getting following check sum failed error. I have using maven deploy:deploy-file to create my repository. Can you please tell us how to resolve this problem ? Is this problem with md5 files or is it a problem with web server. Directory of R:\test\test\6.0.1 03/07/2006 12:40 AM . 03/07/2006 12:40 AM .. 03/07/2006 12:15 AM 1,157 test-6.0.1.jar 03/07/2006 12:15 AM 342 test-6.0.1.pom 03/07/2006 12:15 AM32 test-6.0.1.jar.md5 03/07/2006 12:15 AM40 test-6.0.1.jar.sha1 03/07/2006 12:15 AM32 test-6.0.1.pom.md5 03/07/2006 12:15 AM40 test-6.0.1.pom.sha1 6 File(s) 1,643 bytes 2 Dir(s) 1,796,906,942,464 bytes free Directory of R:\test\test 03/07/2006 12:40 AM . 03/07/2006 12:17 AM .. 03/07/2006 12:15 AM 292 maven-metadata.xml 03/07/2006 12:15 AM32 maven-metadata.xml.md5 03/07/2006 12:15 AM40 maven-metadata.xml.sha1 03/07/2006 12:40 AM 6.0.1 3 File(s)364 bytes 3 Dir(s) 1,796,906,942,464 bytes free [INFO] [INFO] Building maven.repositorytools [INFO]task-segment: [install] [INFO] [INFO] [resources:resources] [INFO] Using default encoding to copy filtered resources. Downloading: http://hostname1/projects/c/buildrepository/maven/repository/test/test/6.0.1/test-6.0.1.po m [WARNING] *** CHECKSUM FAILED - Invalid checksum file - RETRYING Downloading: http://hostname1/projects/c/buildrepository/maven/repository/test/test/6.0.1/test-6.0.1.po m [WARNING] *** CHECKSUM FAILED - Invalid checksum file - IGNORING [WARNING] Unable to get resource from repository repository ( http://hostname1/projects/c/buildrepository/ma ven/repository) Downloading: http://repo1.maven.org/maven2/test/test/6.0.1/test-6.0.1.pom [WARNING] Unable to get resource from repository central ( http://repo1.maven.org/maven2) Downloading: http://hostname1/projects/c/buildrepository/maven/repository/test/test/6.0.1/test-6.0.1.ja r [WARNING] *** CHECKSUM FAILED - Invalid checksum file - RETRYING Downloading: http://hostname1/projects/c/buildrepository/maven/repository/test/test/6.0.1/test-6.0.1.ja r [WARNING] *** CHECKSUM FAILED - Invalid checksum file - IGNORING [WARNING] Unable to get resource from repository repository ( http://hostname1/projects/c/buildrepository/ma ven/repository) Downloading: http://repo1.maven.org/maven2/test/test/6.0.1/test-6.0.1.jar [WARNING] Unable to get resource from repository central ( http://repo1.maven.org/maven2) [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Failed to resolve artifact. required artifacts missing: -- -Gautham Pamu
Re: Error in deploy:deploy-file
Is your ftp user same with the username to your repositoryId UnixServ-FTP? Try to check your settings.xml -allan [EMAIL PROTECTED] wrote: Any one had this problem earlier i still have the same issue i can manually login as my ftp user and create ,delete directories there, i also tried use the same command line deploy within that unix box itself, also tried it from my desktop(win) but both the case it throws error C:>mvn -X -P UnixServ deploy:deploy-file -DgroupId=weblogic -DartifactId=ejbgen -Dversion=SNAPSHOT -Dpackaging=jar -Dfile=ejbgen.jar -DrepositoryId=UnixServ-FTP -Durl=ftp://myserver.com i'm still getting the error + Error stacktraces are turned on. [INFO] Scanning for projects... [INFO] Searching repository for plugin with prefix: 'deploy'. [INFO] [INFO] Building Maven Default Project [INFO] task-segment: [deploy:deploy-file] (aggregator-style) [INFO] [INFO] [deploy:deploy-file] [INFO] Retrieving previous build number from UnixServ-FTP Uploading: ftp://myserver.com/weblogic/ejbgen/SNAPSHOT/ejbgen-SNAPSHOT.jar [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Error deploying artifact: Unable to create directory weblogic [INFO] [INFO] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Error deploying artifact: Unable to create directory weblogic at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:556) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:485) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:455) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:303) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:216) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:139) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115) at org.apache.maven.cli.MavenCli.main(MavenCli.java:249) 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:324) 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 deploying artifact: Unable to create directory weblogic at org.apache.maven.plugin.deploy.DeployFileMojo.execute(DeployFileMojo.java:184) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:415) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:531) ... 16 more Caused by: org.apache.maven.artifact.deployer.ArtifactDeploymentException: Error deploying artifact: Unable to create directory weblogic at org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:91) at org.apache.maven.plugin.deploy.DeployFileMojo.execute(DeployFileMojo.java:180) ... 18 more Caused by: org.apache.maven.wagon.TransferFailedException: Unable to create directory weblogic at org.apache.maven.wagon.providers.ftp.FtpWagon.fillOutputData(FtpWagon.java:262) at org.apache.maven.wagon.StreamWagon.put(StreamWagon.java:133) at org.apache.maven.artifact.manager.DefaultWagonManager.putRemoteFile(DefaultWagonManager.java:180) at org.apache.maven.artifact.manager.DefaultWagonManager.putArtifact(DefaultWagonManager.java:109) at org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:77) ... 19 more [INFO] [INFO] Total time: 4 seconds [INFO] Finished at: Mon Feb 27 12:30:34 EST 2006 [INFO] Final M
RE: Error in deploy:deploy-file
Any one had this problem earlier i still have the same issue i can manually login as my ftp user and create ,delete directories there, i also tried use the same command line deploy within that unix box itself, also tried it from my desktop(win) but both the case it throws error C:>mvn -X -P UnixServ deploy:deploy-file -DgroupId=weblogic -DartifactId=ejbgen -Dversion=SNAPSHOT -Dpackaging=jar -Dfile=ejbgen.jar -DrepositoryId=UnixServ-FTP -Durl=ftp://myserver.com i'm still getting the error + Error stacktraces are turned on. [INFO] Scanning for projects... [INFO] Searching repository for plugin with prefix: 'deploy'. [INFO] [INFO] Building Maven Default Project [INFO] task-segment: [deploy:deploy-file] (aggregator-style) [INFO] ---- [INFO] [deploy:deploy-file] [INFO] Retrieving previous build number from UnixServ-FTP Uploading: ftp://myserver.com/weblogic/ejbgen/SNAPSHOT/ejbgen-SNAPSHOT.jar [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Error deploying artifact: Unable to create directory weblogic [INFO] [INFO] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Error deploying artifact: Unable to create directory weblogic at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:556) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:485) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:455) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:303) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:216) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:139) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115) at org.apache.maven.cli.MavenCli.main(MavenCli.java:249) 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:324) 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 deploying artifact: Unable to create directory weblogic at org.apache.maven.plugin.deploy.DeployFileMojo.execute(DeployFileMojo.java:184) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:415) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:531) ... 16 more Caused by: org.apache.maven.artifact.deployer.ArtifactDeploymentException: Error deploying artifact: Unable to create directory weblogic at org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:91) at org.apache.maven.plugin.deploy.DeployFileMojo.execute(DeployFileMojo.java:180) ... 18 more Caused by: org.apache.maven.wagon.TransferFailedException: Unable to create directory weblogic at org.apache.maven.wagon.providers.ftp.FtpWagon.fillOutputData(FtpWagon.java:262) at org.apache.maven.wagon.StreamWagon.put(StreamWagon.java:133) at org.apache.maven.artifact.manager.DefaultWagonManager.putRemoteFile(DefaultWagonManager.java:180) at org.apache.maven.artifact.manager.DefaultWagonManager.putArtifact(DefaultWagonManager.java:109) at org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:77) ... 19 more [INFO] [INFO] Total time: 4 seconds [INFO] Finished at: Mon Feb 27 12:30:34 EST 2006 [INFO] Final Memory: 2M/6M [INFO] Thanks, Raghu "raghu guru" <[EMAIL PROTECTED]> 02/25/2006 08:55 AM Please respond t
RE: Error in deploy:deploy-file
Thanks for your mail, As i said in my post i already logged in as that ftp user and tried making those directories, and i was able to do that without any error i dont' is this something know issue with maven2 or something else i need to include in my command line deploy:deploy-file
RE: Error in deploy:deploy-file
Check if the user has rights/permissions to create a directory in your UNIX machine ... Thanks & Regards, A.S.KRISHNAN, AZTEC, BANGALORE. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Saturday, February 25, 2006 4:27 AM To: users@maven.apache.org Subject: Error in deploy:deploy-file Hi All, I'm trying to deploy some 3rd party jars to my remote repository i'm trying to do this from my desktop(windows) to my server Unix so from my desktop command line i used C:>mvn -X -P UnixServ deploy:deploy-file -DgroupId=weblogic -DartifactId=ejbgen -Dversion=SNAPSHOT -Dpackaging=jar -Dfile=ejbgen.jar -DrepositoryId=UnixServ-FTP -Durl=ftp://myserver.com when i do this i'm getting following error, i was able to manually create a directory when login as the FTP user , anyone has any idea onthis? Please [INFO] [deploy:deploy-file] [INFO] Retrieving previous build number from UnixServ-FTP [DEBUG] repository metadata for: 'snapshot weblogic:ejbgen:SNAPSHOT' could not be found on repository: UnixServ-FTP [DEBUG] not adding permissions to wagon connection Uploading: ftp://myserver.com/weblogic/ejbgen/SNAPSHOT/ejbgen-SNAPSHOT.jar [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Error deploying artifact: Unable to create directory weblogic [INFO] [DEBUG] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Error deploying artifact: Unable to create directory weblogic at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Default LifecycleExecutor.java:556) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoa l(DefaultLifecycleExecutor.java:485) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultL ifecycleExecutor.java:455) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandle Failures(DefaultLifecycleExecutor.jav a:303) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments( DefaultLifecycleExecutor.java:216) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifec ycleExecutor.java:139) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115) at org.apache.maven.cli.MavenCli.main(MavenCli.java:249) 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:324) 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 deploying artifact: Unable to create directory weblogic at org.apache.maven.plugin.deploy.DeployFileMojo.execute(DeployFileMojo.jav a:184) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginMa nager.java:415) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Default LifecycleExecutor.java:531) ... 16 more Caused by: org.apache.maven.artifact.deployer.ArtifactDeploymentException: Error deploying artifact: Unable to create di rectory weblogic at org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(Defaul tArtifactDeployer.java:91) at org.apache.maven.plugin.deploy.DeployFileMojo.execute(DeployFileMojo.jav a:180) ... 18 more Caused by: org.apache.maven.wagon.TransferFailedException: Unable to create directory weblogic at org.apache.maven.wagon.providers.ftp.FtpWagon.fillOutputData(FtpWagon.ja va:262) at org.apache.maven.wagon.StreamWagon.put(StreamWagon.java:133) at org.apache.maven.artifact.manager.DefaultWagonManager.putRemoteFile(Defa ultWagonManager.java:180) at org.apache.maven.artifact.manager.DefaultWagonManager.putArtifact(Defaul tWagonManager.java:109) at org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(Defaul tArtifactDeployer.java:77) ... 19 more [INFO] [INFO] Total time: 2 seconds [INFO] Finished at: Fri Feb 24 16:42:00 CST 2006 [INFO] Final Memory: 2M/4M [INFO] --
Error in deploy:deploy-file
Hi All, I'm trying to deploy some 3rd party jars to my remote repository i'm trying to do this from my desktop(windows) to my server Unix so from my desktop command line i used C:>mvn -X -P UnixServ deploy:deploy-file -DgroupId=weblogic -DartifactId=ejbgen -Dversion=SNAPSHOT -Dpackaging=jar -Dfile=ejbgen.jar -DrepositoryId=UnixServ-FTP -Durl=ftp://myserver.com when i do this i'm getting following error, i was able to manually create a directory when login as the FTP user , anyone has any idea onthis? Please [INFO] [deploy:deploy-file] [INFO] Retrieving previous build number from UnixServ-FTP [DEBUG] repository metadata for: 'snapshot weblogic:ejbgen:SNAPSHOT' could not be found on repository: UnixServ-FTP [DEBUG] not adding permissions to wagon connection Uploading: ftp://myserver.com/weblogic/ejbgen/SNAPSHOT/ejbgen-SNAPSHOT.jar [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Error deploying artifact: Unable to create directory weblogic [INFO] [DEBUG] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Error deploying artifact: Unable to create directory weblogic at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:556) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:485) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:455) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.jav a:303) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:216) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:139) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115) at org.apache.maven.cli.MavenCli.main(MavenCli.java:249) 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:324) 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 deploying artifact: Unable to create directory weblogic at org.apache.maven.plugin.deploy.DeployFileMojo.execute(DeployFileMojo.java:184) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:415) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:531) ... 16 more Caused by: org.apache.maven.artifact.deployer.ArtifactDeploymentException: Error deploying artifact: Unable to create di rectory weblogic at org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:91) at org.apache.maven.plugin.deploy.DeployFileMojo.execute(DeployFileMojo.java:180) ... 18 more Caused by: org.apache.maven.wagon.TransferFailedException: Unable to create directory weblogic at org.apache.maven.wagon.providers.ftp.FtpWagon.fillOutputData(FtpWagon.java:262) at org.apache.maven.wagon.StreamWagon.put(StreamWagon.java:133) at org.apache.maven.artifact.manager.DefaultWagonManager.putRemoteFile(DefaultWagonManager.java:180) at org.apache.maven.artifact.manager.DefaultWagonManager.putArtifact(DefaultWagonManager.java:109) at org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:77) ... 19 more [INFO] [INFO] Total time: 2 seconds [INFO] Finished at: Fri Feb 24 16:42:00 CST 2006 [INFO] Final Memory: 2M/4M [INFO] Thanks, Raghu
[m2] strange behavior for deploy:deploy-file
Can s.o. explain me the following? I'm executing exactly the same deploy:deply-file goal in 2 different subdirectories but giving me a success or failure :( best regards [EMAIL PROTECTED] maven-scripts]$ /home/vandepitte/maven-2.0.2/bin/mvn deploy:deploy-file -Dfile=/usr/local/blackboard/systemlib/bb-cms-admin.jar -DpomFile=/home/vandepitte/maven/pom/cms-admin.xml -DrepositoryId=ftp-repository -Durl=ftp://u0040925.kuleuven.be/public_html/maven -Dversion=6.3.1.574 [INFO] Scanning for projects... [INFO] Searching repository for plugin with prefix: 'deploy'. [INFO] [INFO] Building Maven Default Project [INFO]task-segment: [deploy:deploy-file] (aggregator-style) [INFO] ---- [INFO] [deploy:deploy-file] [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Error deploying artifact: Unsupported Protocol: 'ftp': Cannot find wagon which supports the requested protocol: ftp Component descriptor cannot be found in the component repository: org.apache.maven.wagon.Wagonftp. [INFO] [INFO] For more information, run Maven with the -e switch [INFO] [INFO] Total time: 2 seconds [INFO] Finished at: Thu Feb 23 16:58:38 CET 2006 [INFO] Final Memory: 3M/53M [INFO] [EMAIL PROTECTED] maven-scripts]$ cd .. [EMAIL PROTECTED] vandepitte]$ /home/vandepitte/maven-2.0.2/bin/mvn deploy:deploy-file -Dfile=/usr/local/blackboard/systemlib/bb-cms-admin.jar -DpomFile=/home/vandepitte/maven/pom/cms-admin.xml -DrepositoryId=ftp-repository -Durl=ftp://u0040925.kuleuven.be/public_html/maven -Dversion=6.3.1.574 [INFO] Scanning for projects... [INFO] Searching repository for plugin with prefix: 'deploy'. [INFO] [INFO] Building Unnamed - javax.transaction:jta:jar:1.0.1B [INFO] task-segment: [deploy:deploy-file] (aggregator-style) [INFO] -------- [INFO] [deploy:deploy-file] Uploading: ftp://u0040925.kuleuven.be/public_html/maven/blackboard/cms-admin/6.3.1.574/cms-admin-6.3.1.574.jar 548K uploaded [INFO] Retrieving previous metadata from ftp-repository [INFO] Uploading repository metadata for: 'artifact blackboard:cms-admin' [INFO] Retrieving previous metadata from ftp-repository [INFO] Uploading project information for cms-admin 6.3.1.574 [INFO] [INFO] BUILD SUCCESSFUL [INFO] [INFO] Total time: 4 seconds [INFO] Finished at: Thu Feb 23 16:58:51 CET 2006 [INFO] Final Memory: 3M/53M [INFO] Disclaimer: http://www.kuleuven.be/cwis/email_disclaimer.htm - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: FW: deploy:deploy-file
Thanks Suresh Allan Ramirez <[EMAIL PROTECTED]> wrote: Hi Suresh, mvn install, installs/place the artifact in your local repository(your repo in your own machine), while mvn deploy deploys/place the artifact in a remote repository(repo to a remote machine). -allan Suresh Govindaraj wrote: >what is the difference between doing a mvn install and mvn deploy. Both help >us download to local repositaries right? > > Thanks > > Suresh > >Allan Ramirez wrote: > Hi there, > >You missed the "-Dversion". and one more thing change your groupID to >groupId and artifactID to artifactId. > >Hope this helps. > >-allan > >Rasconi Luca (u.e.) wrote: > > > >>Hi all, >> >>im trying to deploy third party jars to my internal repository >> >>so i use deploy plugin in this way: >> >>mvn deploy:deploy-file -Dfile=classes12.jar -DgroupID=ojdbc >>-DartifactID=classes12 -Dpackaging=jar -Durl=scp://host/path/to/repo >> >>-Dversion=8i-r2 >> >> >> >>but mnv responds in this way: >> >>[ERROR] BUILD ERROR >> >>[INFO] --- >> >>[INFO] Missing group, artifact, version, or packaging information >> >> >> >> >> >>I don't understand! >> >> >> >> >> >>Tnx, >> >>Luca >> >> >> >> >> >> >> >> >> >> >> >> > >- >To unsubscribe, e-mail: [EMAIL PROTECTED] >For additional commands, e-mail: [EMAIL PROTECTED] > > >Thanks > >Suresh Kumar Govindaraj > >- >Brings words and photos together (easily) with > PhotoMail - it's free and works with Yahoo! Mail. > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Thanks Suresh Kumar Govindaraj - Brings words and photos together (easily) with PhotoMail - it's free and works with Yahoo! Mail.
Re: FW: deploy:deploy-file
Hi Suresh, mvn install, installs/place the artifact in your local repository(your repo in your own machine), while mvn deploy deploys/place the artifact in a remote repository(repo to a remote machine). -allan Suresh Govindaraj wrote: what is the difference between doing a mvn install and mvn deploy. Both help us download to local repositaries right? Thanks Suresh Allan Ramirez <[EMAIL PROTECTED]> wrote: Hi there, You missed the "-Dversion". and one more thing change your groupID to groupId and artifactID to artifactId. Hope this helps. -allan Rasconi Luca (u.e.) wrote: Hi all, im trying to deploy third party jars to my internal repository so i use deploy plugin in this way: mvn deploy:deploy-file -Dfile=classes12.jar -DgroupID=ojdbc -DartifactID=classes12 -Dpackaging=jar -Durl=scp://host/path/to/repo -Dversion=8i-r2 but mnv responds in this way: [ERROR] BUILD ERROR [INFO] --- [INFO] Missing group, artifact, version, or packaging information I don't understand! Tnx, Luca - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Thanks Suresh Kumar Govindaraj - Brings words and photos together (easily) with PhotoMail - it's free and works with Yahoo! Mail. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: FW: deploy:deploy-file
what is the difference between doing a mvn install and mvn deploy. Both help us download to local repositaries right? Thanks Suresh Allan Ramirez <[EMAIL PROTECTED]> wrote: Hi there, You missed the "-Dversion". and one more thing change your groupID to groupId and artifactID to artifactId. Hope this helps. -allan Rasconi Luca (u.e.) wrote: >Hi all, > >im trying to deploy third party jars to my internal repository > >so i use deploy plugin in this way: > >mvn deploy:deploy-file -Dfile=classes12.jar -DgroupID=ojdbc >-DartifactID=classes12 -Dpackaging=jar -Durl=scp://host/path/to/repo > > -Dversion=8i-r2 > > > >but mnv responds in this way: > >[ERROR] BUILD ERROR > >[INFO] --- > >[INFO] Missing group, artifact, version, or packaging information > > > > > >I don't understand! > > > > > >Tnx, > >Luca > > > > > > > > > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Thanks Suresh Kumar Govindaraj - Brings words and photos together (easily) with PhotoMail - it's free and works with Yahoo! Mail.
Re: FW: deploy:deploy-file
Hi there, You missed the "-Dversion". and one more thing change your groupID to groupId and artifactID to artifactId. Hope this helps. -allan Rasconi Luca (u.e.) wrote: Hi all, im trying to deploy third party jars to my internal repository so i use deploy plugin in this way: mvn deploy:deploy-file -Dfile=classes12.jar -DgroupID=ojdbc -DartifactID=classes12 -Dpackaging=jar -Durl=scp://host/path/to/repo -Dversion=8i-r2 but mnv responds in this way: [ERROR] BUILD ERROR [INFO] --- [INFO] Missing group, artifact, version, or packaging information I don't understand! Tnx, Luca - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: FW: deploy:deploy-file
Hi, It's 'groupId' not 'groupID' and 'artifactId' not 'artifactID'. Hope this helps -Tim Rasconi Luca (u.e.) schrieb: Hi all, im trying to deploy third party jars to my internal repository so i use deploy plugin in this way: mvn deploy:deploy-file -Dfile=classes12.jar -DgroupID=ojdbc -DartifactID=classes12 -Dpackaging=jar -Durl=scp://host/path/to/repo -Dversion=8i-r2 but mnv responds in this way: [ERROR] BUILD ERROR [INFO] --- [INFO] Missing group, artifact, version, or packaging information I don't understand! Tnx, Luca - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
FW: deploy:deploy-file
Hi all, im trying to deploy third party jars to my internal repository so i use deploy plugin in this way: mvn deploy:deploy-file -Dfile=classes12.jar -DgroupID=ojdbc -DartifactID=classes12 -Dpackaging=jar -Durl=scp://host/path/to/repo -Dversion=8i-r2 but mnv responds in this way: [ERROR] BUILD ERROR [INFO] --- [INFO] Missing group, artifact, version, or packaging information I don't understand! Tnx, Luca
RE: deploy:deploy-file
No comment :-) Tnx, Luca -Original Message- From: Jochen Wiedmann [mailto:[EMAIL PROTECTED] Sent: lunedì 13 febbraio 2006 12.57 To: Maven Users List Subject: Re: deploy:deploy-file On 2/13/06, Rasconi Luca (u.e.) <[EMAIL PROTECTED]> wrote: > mvn deploy:deploy-file -Dfile=classes12.jar -DgroupID=ojdbc > -DartifactID=classes12 -Dpackaging=jar -Durl=scp://host/path/to/repo ID => Id -- If you obey all the rules you miss all the fun. (Katharine Hepburn) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
