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:
exec executable=${maven.bin} dir=../lib
arg value=deploy:deploy-file /
arg value=-DgroupId=com.my.package /arg value=-DartifactId=${
ant.project.name} /
arg value=-Dversion=${manifest.implementation.version}-SNAPSHOT /
arg value=-Dpackaging=jar /
arg
value=-Dfile=../lib/${ant.project.name}-${manifest.implementation.version}-SNAPSHOT.jar
/
arg value=-Durl=
http://archiva.patsystems.com/archiva/repository/snapshots; /
arg value=-DrepositoryId=snapshots /
/exec
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: 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 james.clin...@avexa.co.uk 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:
exec executable=${maven.bin} dir=../lib
arg value=deploy:deploy-file /
arg value=-DgroupId=com.my.package /arg value=-DartifactId=${
ant.project.name} /
arg value=-Dversion=${manifest.implementation.version}-SNAPSHOT /
arg value=-Dpackaging=jar /
arg
value=-Dfile=../lib/${ant.project.name}-${manifest.implementation.version}-SNAPSHOT.jar
/
arg value=-Durl=
http://archiva.patsystems.com/archiva/repository/snapshots; /
arg value=-DrepositoryId=snapshots /
/exec
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
Archiva Deployment Problem...
Why can I deploy to the pre-configured internal repository OK, but not my identical custom repository? INTERNAL mvn deploy:deploy-file -Dfile=commons-logging-1.1.1.jar -DgroupId=commons-logging -DartifactId=commons-logging -Dversion=1.1.1 -DrepositoryId=internal -Durl=dav:http://localhost:8080/archiva/repository/internal/ -Dpackaging=jar [INFO] [deploy:deploy-file] Uploading: http://localhost:8080/archiva/repository/internal//commons-logging/commo ns-logging/1.1.1/commons-logging-1.1.1.jar [INFO] Retrieving previous metadata from internal [INFO] Uploading project information for commons-logging 1.1.1 [INFO] Retrieving previous metadata from internal [INFO] Uploading repository metadata for: 'artifact commons-logging:commons-logging' [INFO] [INFO] BUILD SUCCESSFUL CUSTOM mvn deploy:deploy-file -Dfile=commons-logging-1.1.1.jar -DgroupId=commons-logging -DartifactId=commons-logging -Dversion=1.1.1 -DrepositoryId=custom-repos -Durl=dav:http://localhost:8080/archiva/repository/custom/ -Dpackaging=jar [INFO] [deploy:deploy-file] Uploading: http://localhost:8080/archiva/repository/custom//commons-logging/commons -logging/1.1.1/commons-logging-1.1.1.jar [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Error deploying artifact: Resource to deploy not found: File: http://localhost:8080/archiva/repository/custom/commons-logging/com mons-logging/1.1.1/commons-logging-1.1.1.jar does not exist The settings.xml includes the server settings. Advice appreciated? DISCLAIMER: This e-mail is confidential and may also be legally privileged. If you are not the intended recipient, use of the information contained in this e-mail (including disclosure, copying or distribution) is prohibited and may be unlawful. Please inform the sender and delete the message immediately from your system. This e-mail is attributed to the sender and may not necessarily reflect the views of the Patsystems Group and no member of the Patsystems Group accepts any liability for any action taken in reliance on the contents of this e-mail (other than where it has a legal or regulatory obligation to do so) or for the consequences of any computer viruses which may have been transmitted by this e-mail. The Patsystems Group comprises Patsystems plc and its subsidiary group of companies. Thank you for your Co-Operation.
Deploying Libs to Archiva
Is there a way where I can upload my entire local repository into Archiva as a Managed Repository in one hit, or do I need to use the mvn deploy:deploy-file command for each file? Regards.
RE: Deploying Libs to Archiva
I did try that (without attempting to run the build) pressed scan but couldn't see the libs when browsing. Only libs displayed were ones via deploy command... -Original Message- From: David Delbecq [mailto:[EMAIL PROTECTED] Sent: Tuesday, April 15, 2008 12:34 PM To: Maven Users List Subject: Re: Deploying Libs to Archiva En l'instant précis du 15/04/08 13:26, James Clinton s'exprimait en ces termes: Is there a way where I can upload my entire local repository into Archiva as a Managed Repository in one hit, or do I need to use the mvn deploy:deploy-file command for each file? Regards. Just copy the files to the archiva folder on the server filesystem (using scp for example) -- David Delbecq Institut Royal Météorologique Ext:557 - 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]
Packaging of test-jar
A module (B) isn't compiling because maven is skipping the packaging of test-jar in a dependant module (A). goaltest-jar/goal The goal above if declared as part of the profile in the module (A) but Skipping packaging of the test-jar is always outputted. Advice appreciated. J
eclipse classpath
I'd like to change the output directory of the eclipse classpath. mvn eclipse:eclipse defaults to project/target/classes Is this possible? DISCLAIMER: This e-mail is confidential and may also be legally privileged. If you are not the intended recipient, use of the information contained in this e-mail (including disclosure, copying or distribution) is prohibited and may be unlawful. Please inform the sender and delete the message immediately from your system. This e-mail is attributed to the sender and may not necessarily reflect the views of the Patsystems Group and no member of the Patsystems Group accepts any liability for any action taken in reliance on the contents of this e-mail (other than where it has a legalor regulatory obligation to do so) or for the consequences of any computer viruses which may have been transmitted by this e-mail. The Patsystems Group comprises Patsystems plc and its subsidiary group of companies. Thank You For your Co Opeation
assembly beta 2.2
Having problems with sub-modules being included. Followed this example but my child modules are simply ignored? http://maven.apache.org/plugins/maven-assembly-plugin/examples/multimodu le/module-binary-inclusion-simple.html Has anyone had this working successful? (descriptor snippet below) moduleSets moduleSet includes includemygroupid:myartid/include /includes /moduleSet /moduleSets Regards, James
Suppress Warnings
Is it possible to suppress warnings like the following? [WARNING] Entry: Project-1.3- SomeFile.java longer than 100 characters. AFAIK these are produced by the assembler plug-in right?
RE: Strange - Success icon shown and no emails sent in case of bu ild-failure
This is a KI. Use this script to fix. The fixed script for maven 2.0.7 is : https://svn.apache.org/repos/asf/maven/components/branches/maven-2.0.x/maven -core/src/bin/mvn.bat -Original Message- From: mfs [mailto:[EMAIL PROTECTED] Sent: 31 August 2007 00:02 To: continuum-users@maven.apache.org Subject: Re: Strange - Success icon shown and no emails sent in case of build-failure Finally got it fixed...after alot of research...it was due to a maven (2.0.7) issue on windows...issue - MNG-3084...had to modify the mvn.bat file to get it working. Thanks nyways Farhan. mfs wrote: Dear All, I am getting this strange behavior where even on a build-failure (as below) as shown in the Result, the success icon is shown against the project on show-project screen and same is the case with history screen against a project...and even no emails are sent as its intrepreting that the build is a success (dont know why) and no state change since last build.. [INFO] Scanning for projects... [INFO] -- -- [INFO] Building Share : PDFP [INFO]task-segment: [clean, install] [INFO] -- -- [INFO] [clean:clean] [INFO] Deleting directory C:\continuum\continuum_wd\8\target [INFO] Deleting directory C:\continuum\continuum_wd\8\target\classes [INFO] Deleting directory C:\continuum\continuum_wd\8\target\test-classes [INFO] Deleting directory C:\continuum\continuum_wd\8\target\site [INFO] [resources:resources] [INFO] Using default encoding to copy filtered resources. [INFO] [compiler:compile] [INFO] Compiling 18 source files to C:\continuum\continuum_wd\8\target\classes [INFO] -- -- [ERROR] BUILD FAILURE [INFO] -- -- [INFO] Compilation failure C:\continuum\continuum_wd\8\src\main\java\vaudit\pdfp\PdfField.java:[1 ,0] 'class' or 'interface' expected C:\continuum\continuum_wd\8\src\main\java\vaudit\pdfp\PdfField.java:[1 ,0] 'class' or 'interface' expected [INFO] -- -- [INFO] For more information, run Maven with the -e switch [INFO] -- -- [INFO] Total time: 1 second [INFO] Finished at: Thu Aug 30 11:01:50 PDT 2007 [INFO] Final Memory: 4M/8M [INFO] -- -- -- View this message in context: http://www.nabble.com/Strange---Success-icon-shown-and-no-emails-sent-in-cas e-of-build-failure-tf4355976.html#a12417831 Sent from the Continuum - Users mailing list archive at Nabble.com. DISCLAIMER: This e-mail is confidential and may also be legally privileged. If you are not the intended recipient, use of the information contained in this e-mail (including disclosure, copying or distribution) is prohibited and may be unlawful. Please inform the sender and delete the message immediately from your system. This e-mail is attributed to the sender and may not necessarily reflect the views of the Patsystems Group and no member of the Patsystems Group accepts any liability for any action taken in reliance on the contents of this e-mail (other than where it has a legal or regulatory obligation to do so) or for the consequences of any computer viruses which may have been transmitted by this e-mail. The Patsystems Group comprises Patsystems plc and its subsidiary group of companies.
RE: Continuum version 103 (maven2)
See http://maven.apache.org/continuum/faqs.html##how-does-continuum-detect-a-suc cessful-build Sounds like the same issue? Apologies if I'm wrong. James -Original Message- From: Emmanuel Venisse [mailto:[EMAIL PROTECTED] Sent: 28 August 2007 16:59 To: continuum-users@maven.apache.org Subject: Re: Continuum version 103 (maven2) We don't have an entry in the faq about the bug in mvn.bat from maven 2.0.7 (http://jira.codehaus.org/browse/MNG-3084 ) James Clinton a écrit : Opps - should of read my original post!. Anwser is for Windows the mvn.bat file needs to be altered...I didn't read the faq's properly. -Original Message- From: Emmanuel Venisse [mailto:[EMAIL PROTECTED] Sent: 28 August 2007 16:48 To: continuum-users@maven.apache.org Subject: Re: Continuum version 103 (maven2) Do you use maven 2.0.7? James Clinton a écrit : Hello, I have a project structure like so: - parent - child - child Parent pom is them loaded into CI and the projects are detected. It builds fine, but if there is a compilation error, the status of the build is still 'success'. Is this a known issue? James DISCLAIMER: This e-mail is confidential and may also be legally privileged. If you are not the intended recipient, use of the information contained in this e-mail (including disclosure, copying or distribution) is prohibited and may be unlawful. Please inform the sender and delete the message immediately from your system. This e-mail is attributed to the sender and may not necessarily reflect the views of the Patsystems Group and no member of the Patsystems Group accepts any liability for any action taken in reliance on the contents of this e-mail (other than where it has a legal or regulatory obligation to do so) or for the consequences of any computer viruses which may have been transmitted by this e-mail. The Patsystems Group comprises Patsystems plc and its subsidiary group of companies. DISCLAIMER: This e-mail is confidential and may also be legally privileged. If you are not the intended recipient, use of the information contained in this e-mail (including disclosure, copying or distribution) is prohibited and may be unlawful. Please inform the sender and delete the message immediately from your system. This e-mail is attributed to the sender and may not necessarily reflect the views of the Patsystems Group and no member of the Patsystems Group accepts any liability for any action taken in reliance on the contents of this e-mail (other than where it has a legal or regulatory obligation to do so) or for the consequences of any computer viruses which may have been transmitted by this e-mail. The Patsystems Group comprises Patsystems plc and its subsidiary group of companies. DISCLAIMER: This e-mail is confidential and may also be legally privileged. If you are not the intended recipient, use of the information contained in this e-mail (including disclosure, copying or distribution) is prohibited and may be unlawful. Please inform the sender and delete the message immediately from your system. This e-mail is attributed to the sender and may not necessarily reflect the views of the Patsystems Group and no member of the Patsystems Group accepts any liability for any action taken in reliance on the contents of this e-mail (other than where it has a legal or regulatory obligation to do so) or for the consequences of any computer viruses which may have been transmitted by this e-mail. The Patsystems Group comprises Patsystems plc and its subsidiary group of companies.
RE: Continuum version 103 (maven2)
Ok - many thanks. -Original Message- From: Emmanuel Venisse [mailto:[EMAIL PROTECTED] Sent: 28 August 2007 17:07 To: continuum-users@maven.apache.org Subject: Re: Continuum version 103 (maven2) yes and no. The problem is the same but not the patch to do, This entry is for an old maven version The fixed script for maven 2.0.7 is : https://svn.apache.org/repos/asf/maven/components/branches/maven-2.0.x/maven -core/src/bin/mvn.bat Emmanuel James Clinton a écrit : See http://maven.apache.org/continuum/faqs.html##how-does-continuum-detect -a-suc cessful-build Sounds like the same issue? Apologies if I'm wrong. James -Original Message- From: Emmanuel Venisse [mailto:[EMAIL PROTECTED] Sent: 28 August 2007 16:59 To: continuum-users@maven.apache.org Subject: Re: Continuum version 103 (maven2) We don't have an entry in the faq about the bug in mvn.bat from maven 2.0.7 (http://jira.codehaus.org/browse/MNG-3084 ) James Clinton a écrit : Opps - should of read my original post!. Anwser is for Windows the mvn.bat file needs to be altered...I didn't read the faq's properly. -Original Message- From: Emmanuel Venisse [mailto:[EMAIL PROTECTED] Sent: 28 August 2007 16:48 To: continuum-users@maven.apache.org Subject: Re: Continuum version 103 (maven2) Do you use maven 2.0.7? James Clinton a écrit : Hello, I have a project structure like so: - parent - child - child Parent pom is them loaded into CI and the projects are detected. It builds fine, but if there is a compilation error, the status of the build is still 'success'. Is this a known issue? James DISCLAIMER: This e-mail is confidential and may also be legally privileged. If you are not the intended recipient, use of the information contained in this e-mail (including disclosure, copying or distribution) is prohibited and may be unlawful. Please inform the sender and delete the message immediately from your system. This e-mail is attributed to the sender and may not necessarily reflect the views of the Patsystems Group and no member of the Patsystems Group accepts any liability for any action taken in reliance on the contents of this e-mail (other than where it has a legal or regulatory obligation to do so) or for the consequences of any computer viruses which may have been transmitted by this e-mail. The Patsystems Group comprises Patsystems plc and its subsidiary group of companies. DISCLAIMER: This e-mail is confidential and may also be legally privileged. If you are not the intended recipient, use of the information contained in this e-mail (including disclosure, copying or distribution) is prohibited and may be unlawful. Please inform the sender and delete the message immediately from your system. This e-mail is attributed to the sender and may not necessarily reflect the views of the Patsystems Group and no member of the Patsystems Group accepts any liability for any action taken in reliance on the contents of this e-mail (other than where it has a legal or regulatory obligation to do so) or for the consequences of any computer viruses which may have been transmitted by this e-mail. The Patsystems Group comprises Patsystems plc and its subsidiary group of companies. DISCLAIMER: This e-mail is confidential and may also be legally privileged. If you are not the intended recipient, use of the information contained in this e-mail (including disclosure, copying or distribution) is prohibited and may be unlawful. Please inform the sender and delete the message immediately from your system. This e-mail is attributed to the sender and may not necessarily reflect the views of the Patsystems Group and no member of the Patsystems Group accepts any liability for any action taken in reliance on the contents of this e-mail (other than where it has a legal or regulatory obligation to do so) or for the consequences of any computer viruses which may have been transmitted by this e-mail. The Patsystems Group comprises Patsystems plc and its subsidiary group of companies. DISCLAIMER: This e-mail is confidential and may also be legally privileged. If you are not the intended recipient, use of the information contained in this e-mail (including disclosure, copying or distribution) is prohibited and may be unlawful. Please inform the sender and delete the message immediately from your system. This e-mail is attributed to the sender and may not necessarily reflect the views of the Patsystems Group and no member of the Patsystems Group accepts any liability for any action taken in reliance on the contents of this e-mail (other than where it has a legal or regulatory obligation to do so) or for the consequences of any computer viruses which may have been transmitted by this e-mail. The Patsystems Group comprises Patsystems plc and its subsidiary group of companies.
RE: Continuum version 103 (maven2)
Found the problem. Basically CI doesn't work if you have your parent pom at the same level as its child modules because CI creates a temporary directory which breaks the path from the parent to the child. This is true for the stable and 1.1 build. -Original Message- From: Emmanuel Venisse [mailto:[EMAIL PROTECTED] Sent: 28 August 2007 16:48 To: [EMAIL PROTECTED] Subject: Re: Continuum version 103 (maven2) Do you use maven 2.0.7? James Clinton a écrit : Hello, I have a project structure like so: - parent - child - child Parent pom is them loaded into CI and the projects are detected. It builds fine, but if there is a compilation error, the status of the build is still 'success'. Is this a known issue? James DISCLAIMER: This e-mail is confidential and may also be legally privileged. If you are not the intended recipient, use of the information contained in this e-mail (including disclosure, copying or distribution) is prohibited and may be unlawful. Please inform the sender and delete the message immediately from your system. This e-mail is attributed to the sender and may not necessarily reflect the views of the Patsystems Group and no member of the Patsystems Group accepts any liability for any action taken in reliance on the contents of this e-mail (other than where it has a legal or regulatory obligation to do so) or for the consequences of any computer viruses which may have been transmitted by this e-mail. The Patsystems Group comprises Patsystems plc and its subsidiary group of companies. DISCLAIMER: This e-mail is confidential and may also be legally privileged. If you are not the intended recipient, use of the information contained in this e-mail (including disclosure, copying or distribution) is prohibited and may be unlawful. Please inform the sender and delete the message immediately from your system. This e-mail is attributed to the sender and may not necessarily reflect the views of the Patsystems Group and no member of the Patsystems Group accepts any liability for any action taken in reliance on the contents of this e-mail (other than where it has a legal or regulatory obligation to do so) or for the consequences of any computer viruses which may have been transmitted by this e-mail. The Patsystems Group comprises Patsystems plc and its subsidiary group of companies.
Continuum version 103 (maven2)
Hello, I have a project structure like so: - parent - child - child Parent pom is them loaded into CI and the projects are detected. It builds fine, but if there is a compilation error, the status of the build is still 'success'. Is this a known issue? James DISCLAIMER: This e-mail is confidential and may also be legally privileged. If you are not the intended recipient, use of the information contained in this e-mail (including disclosure, copying or distribution) is prohibited and may be unlawful. Please inform the sender and delete the message immediately from your system. This e-mail is attributed to the sender and may not necessarily reflect the views of the Patsystems Group and no member of the Patsystems Group accepts any liability for any action taken in reliance on the contents of this e-mail (other than where it has a legal or regulatory obligation to do so) or for the consequences of any computer viruses which may have been transmitted by this e-mail. The Patsystems Group comprises Patsystems plc and its subsidiary group of companies.
FW: Maven Multi-Project - Modules are Numbers when checked out
( apoligies if you received this twice ) Hello, Setting up Continuum for the first time using Maven2 for our builds. (which is a Multi-Project). Pointed Continuum to the parent POM and this loaded in the projects. When running the parent the build fails because it cannot find the child POM in the working directory. Looking in the directory, the reason is because the checked out folder isnt the name of the module, but a number: -1 (parent) -2 (child) -n If this number was the project name the child POM would of been found. Is there some configuration I am missing or is this to do with my setup. My Parent module is at the same level as it children if that matters. Parent POM extract: modules module../ProjectAPI/module module../ProjectCore/module /modules Any help appreciated. Regards, James. DISCLAIMER: This e-mail is confidential and may also be legally privileged. If you are not the intended recipient, use of the information contained in this e-mail (including disclosure, copying or distribution) is prohibited and may be unlawful. Please inform the sender and delete the message immediately from your system. This e-mail is attributed to the sender and may not necessarily reflect the views of the Patsystems Group and no member of the Patsystems Group accepts any liability for any action taken in reliance on the contents of this e-mail (other than where it has a legal or regulatory obligation to do so) or for the consequences of any computer viruses which may have been transmitted by this e-mail. The Patsystems Group comprises Patsystems plc and its subsidiary group of companies.
