Deploying snapshots of same artifactId but different types
Hi, Using Maven 2.2.1, I deployed (with deploy:deploy-file through command-line) several artifacts with same version (SNAPSHOT), same artifactId and groupId, but different types. Here is the list I get in my nexus storage: myArtifact-1.0-20120106.101541-1.ear myArtifact-1.0-20120106.101541-1.ear.md5 myArtifact-1.0-20120106.101541-1.ear.sha1 myArtifact-1.0-20120106.101541-1.pom myArtifact-1.0-20120106.101541-1.pom.md5 myArtifact-1.0-20120106.101541-1.pom.sha1 myArtifact-1.0-20120106.101603-2.jar myArtifact-1.0-20120106.101603-2.jar.md5 myArtifact-1.0-20120106.101603-2.jar.sha1 myArtifact-1.0-20120106.101603-2.pom myArtifact-1.0-20120106.101603-2.pom.md5 myArtifact-1.0-20120106.101603-2.pom.sha1 myArtifact-1.0-20120106.101622-3.pom myArtifact-1.0-20120106.101622-3.pom.md5 myArtifact-1.0-20120106.101622-3.pom.sha1 myArtifact-1.0-20120106.101622-3.war myArtifact-1.0-20120106.101622-3.war.md5 myArtifact-1.0-20120106.101622-3.war.sha1 maven-metadata.xml maven-metadata.xml.md5 maven-metadata.xml.sha1 The problem now is that if I add the following dependency to a module pom : dependency groupIdmyGroup/groupId artifactIdmyArtifact/artifactId version1.0-SNAPSHOT/version typeear/type /dependency ... build fails with following error : [INFO] snapshot myGroup:myArtifact:1.0-SNAPSHOT: checking for updates from MYREPO Downloading: http://host/nexus/content/repositories/MYREPO//myGroup/myArtifact/1.0-SNAPSHOT/myArtifact-1.0-20120106.101622-3.pom 471b downloaded (myArtifact-1.0-20120106.101622-3.pom) Downloading: http://host/nexus/content/repositories/MYREPO//myGroup/myArtifact/1.0-SNAPSHOT/myArtifact-1.0-20120106.101622-3.ear [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Failed to resolve artifact. What happens is that maven, for this artifact, gets timestamp-3 as last snapshot version (for the pom), and then tries to retrieve the ear with this same version with timestamp-3, and in our case, it does not exist. If I only leave the timestamp-1 pom, and rename the war so it has same version (timestamp-1), then it works and maven is able to download 1.0-SNAPSHOT of both ear or war. I tried generatePom=false for second deploy command but result was the same - except that only 1 pom was generated of course. I should I have deployed the war and ear in first place to avoid this issue ? Thanks, Jeremie -- View this message in context: http://maven.40175.n5.nabble.com/Deploying-snapshots-of-same-artifactId-but-different-types-tp5432928p5432928.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: Deploying snapshots of same artifactId but different types
Try uploading all at once using 'files', 'types' and 'classifiers'. Or if you are on Nexus, deploy them using the UI, you can attach multiple artifacts there. On 26.01.2012 15:08, jerem wrote: Hi, Using Maven 2.2.1, I deployed (with deploy:deploy-file through command-line) several artifacts with same version (SNAPSHOT), same artifactId and groupId, but different types. Here is the list I get in my nexus storage: myArtifact-1.0-20120106.101541-1.ear myArtifact-1.0-20120106.101541-1.ear.md5 myArtifact-1.0-20120106.101541-1.ear.sha1 myArtifact-1.0-20120106.101541-1.pom myArtifact-1.0-20120106.101541-1.pom.md5 myArtifact-1.0-20120106.101541-1.pom.sha1 myArtifact-1.0-20120106.101603-2.jar myArtifact-1.0-20120106.101603-2.jar.md5 myArtifact-1.0-20120106.101603-2.jar.sha1 myArtifact-1.0-20120106.101603-2.pom myArtifact-1.0-20120106.101603-2.pom.md5 myArtifact-1.0-20120106.101603-2.pom.sha1 myArtifact-1.0-20120106.101622-3.pom myArtifact-1.0-20120106.101622-3.pom.md5 myArtifact-1.0-20120106.101622-3.pom.sha1 myArtifact-1.0-20120106.101622-3.war myArtifact-1.0-20120106.101622-3.war.md5 myArtifact-1.0-20120106.101622-3.war.sha1 maven-metadata.xml maven-metadata.xml.md5 maven-metadata.xml.sha1 The problem now is that if I add the following dependency to a module pom : dependency groupIdmyGroup/groupId artifactIdmyArtifact/artifactId version1.0-SNAPSHOT/version typeear/type /dependency ... build fails with following error : [INFO] snapshot myGroup:myArtifact:1.0-SNAPSHOT: checking for updates from MYREPO Downloading: http://host/nexus/content/repositories/MYREPO//myGroup/myArtifact/1.0-SNAPSHOT/myArtifact-1.0-20120106.101622-3.pom 471b downloaded (myArtifact-1.0-20120106.101622-3.pom) Downloading: http://host/nexus/content/repositories/MYREPO//myGroup/myArtifact/1.0-SNAPSHOT/myArtifact-1.0-20120106.101622-3.ear [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Failed to resolve artifact. What happens is that maven, for this artifact, gets timestamp-3 as last snapshot version (for the pom), and then tries to retrieve the ear with this same version with timestamp-3, and in our case, it does not exist. If I only leave the timestamp-1 pom, and rename the war so it has same version (timestamp-1), then it works and maven is able to download 1.0-SNAPSHOT of both ear or war. I tried generatePom=false for second deploy command but result was the same - except that only 1 pom was generated of course. I should I have deployed the war and ear in first place to avoid this issue ? Thanks, Jeremie -- View this message in context: http://maven.40175.n5.nabble.com/Deploying-snapshots-of-same-artifactId-but-different-types-tp5432928p5432928.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 -- Roland Asmann Senior Software Engineer adesso Austria GmbH Floridotower 26. Stock T +43 1 2198790-27 Floridsdorfer Hauptstr. 1 F +43 1 2198790-927 A-1210 Wien M +43 664 88657566 E roland.asm...@adesso.at W www.adesso.at - business. people. technology. - - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Deploying snapshots of same artifactId but different types
Try uploading all at once using 'files', 'types' and 'classifiers'. Or if you are on Nexus, deploy them using the UI, you can attach multiple artifacts there. What Roland said is true and will work. Alternatively you should reconsider deploying so many artifacts with different types under the same G/A/V. Obviously this can be a problem. You should use different coordinates for these artifacts IMO. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
timestamped snapshots in local repo
Are there supposed to be timestamp uniquely named snapshot artifacts in my local repo? I'm investigating the uniqueVersion = false setting to solve a disks space problem, but I read some threads here and there that expressed disagreement on whether there should actually be an accumulation of the these uniquely named artifacts in a local repo under normal operating conditions. I assume they show up there whenever a build has a snapshot dependency. I know that installing a snapshot doesn't create a uniquely named one, in contrast.
How to parse JUnit report xml that causes build to pass/fail
Hi, I have been using Maven 2.2.1 for a while now and have used it successfully for multiple projects so far. I must say it is one the most sophisticated build system that is well thought and comprehensive in nature. I have 'maven'ized a project to a certain extent but we have an outstanding issue that is troubling developers. Take a deep breath as I explain this problem below... I'm trying to follow beautiful principal of maven lifecycle thoroughly and performing unit tests in 'test' phase and integration tests in 'integration-test' phase. Since its a webapp (war), I start/stop server during pre/post integration-phases. During this 'integration-test', I run a series of Java JUnit tests that asserts different features of server. If one of the test fails, the main maven build comes out saying.. [ERROR] BUILD FAILURE [INFO] [INFO] There are test failures. And this is very useful for me and treasure this logic very much. Life is good so far and here comes the problem. Along with these Java based JUnit integration tests, I also have some other non-Java, non-JUnit based tests (actually phantomjs/Jasmine) which validates some other aspects of server. And this external test executable exports its test results in a xml file that is compatible with JUnit, described here http://www.junit.org/node/399. Note that this is NOT a junit test and maven runtime does not know abt how the test are ran, rather external test exec just exports a xml file that is fully JUnit result compatible. And if there is a failure reported in this exported xml file, I need to cause the build to fail like above. That means I want maven to parse this report xml, treat it similar to any other tests and cause build to fail. Currently my build says 'Successful' even if there are test failures in the exported xml file. Note: Similar feature exists in the CI tools like Jenkins/TeamCity but its not something that developer can use locally. I wish simple 'mvn clean install' to work with my exported xml file. Note: Surefire report-only goal does generates the reports with all the test xml files I have and shows the test failure in the HTML report. But this does not cause final build to fail upon test failures. Q. Is there a way to tell maven (via plugin or something) that look for test failures in the test xml file and declare the build pass/fail? Appreciate any help/clues/suggestions. Thanks you. Deep 'Maven'er :) -- View this message in context: http://maven.40175.n5.nabble.com/How-to-parse-JUnit-report-xml-that-causes-build-to-pass-fail-tp5433750p5433750.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: How to parse JUnit report xml that causes build to pass/fail
Please take a look at the maven-failsafe-plugin, it is a version of surefire to cover your exact use case On 26 January 2012 19:36, swapsa...@gmail.com swapsa...@gmail.com wrote: Hi, I have been using Maven 2.2.1 for a while now and have used it successfully for multiple projects so far. I must say it is one the most sophisticated build system that is well thought and comprehensive in nature. I have 'maven'ized a project to a certain extent but we have an outstanding issue that is troubling developers. Take a deep breath as I explain this problem below... I'm trying to follow beautiful principal of maven lifecycle thoroughly and performing unit tests in 'test' phase and integration tests in 'integration-test' phase. Since its a webapp (war), I start/stop server during pre/post integration-phases. During this 'integration-test', I run a series of Java JUnit tests that asserts different features of server. If one of the test fails, the main maven build comes out saying.. [ERROR] BUILD FAILURE [INFO] [INFO] There are test failures. And this is very useful for me and treasure this logic very much. Life is good so far and here comes the problem. Along with these Java based JUnit integration tests, I also have some other non-Java, non-JUnit based tests (actually phantomjs/Jasmine) which validates some other aspects of server. And this external test executable exports its test results in a xml file that is compatible with JUnit, described here http://www.junit.org/node/399. Note that this is NOT a junit test and maven runtime does not know abt how the test are ran, rather external test exec just exports a xml file that is fully JUnit result compatible. And if there is a failure reported in this exported xml file, I need to cause the build to fail like above. That means I want maven to parse this report xml, treat it similar to any other tests and cause build to fail. Currently my build says 'Successful' even if there are test failures in the exported xml file. Note: Similar feature exists in the CI tools like Jenkins/TeamCity but its not something that developer can use locally. I wish simple 'mvn clean install' to work with my exported xml file. Note: Surefire report-only goal does generates the reports with all the test xml files I have and shows the test failure in the HTML report. But this does not cause final build to fail upon test failures. Q. Is there a way to tell maven (via plugin or something) that look for test failures in the test xml file and declare the build pass/fail? Appreciate any help/clues/suggestions. Thanks you. Deep 'Maven'er :) -- View this message in context: http://maven.40175.n5.nabble.com/How-to-parse-JUnit-report-xml-that-causes-build-to-pass-fail-tp5433750p5433750.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: How to parse JUnit report xml that causes build to pass/fail
Sorry, my bad. I mis-understood. You can just write your own plugin, very easy to do On 26 January 2012 22:58, Stephen Connolly stephen.alan.conno...@gmail.comwrote: Please take a look at the maven-failsafe-plugin, it is a version of surefire to cover your exact use case On 26 January 2012 19:36, swapsa...@gmail.com swapsa...@gmail.com wrote: Hi, I have been using Maven 2.2.1 for a while now and have used it successfully for multiple projects so far. I must say it is one the most sophisticated build system that is well thought and comprehensive in nature. I have 'maven'ized a project to a certain extent but we have an outstanding issue that is troubling developers. Take a deep breath as I explain this problem below... I'm trying to follow beautiful principal of maven lifecycle thoroughly and performing unit tests in 'test' phase and integration tests in 'integration-test' phase. Since its a webapp (war), I start/stop server during pre/post integration-phases. During this 'integration-test', I run a series of Java JUnit tests that asserts different features of server. If one of the test fails, the main maven build comes out saying.. [ERROR] BUILD FAILURE [INFO] [INFO] There are test failures. And this is very useful for me and treasure this logic very much. Life is good so far and here comes the problem. Along with these Java based JUnit integration tests, I also have some other non-Java, non-JUnit based tests (actually phantomjs/Jasmine) which validates some other aspects of server. And this external test executable exports its test results in a xml file that is compatible with JUnit, described here http://www.junit.org/node/399. Note that this is NOT a junit test and maven runtime does not know abt how the test are ran, rather external test exec just exports a xml file that is fully JUnit result compatible. And if there is a failure reported in this exported xml file, I need to cause the build to fail like above. That means I want maven to parse this report xml, treat it similar to any other tests and cause build to fail. Currently my build says 'Successful' even if there are test failures in the exported xml file. Note: Similar feature exists in the CI tools like Jenkins/TeamCity but its not something that developer can use locally. I wish simple 'mvn clean install' to work with my exported xml file. Note: Surefire report-only goal does generates the reports with all the test xml files I have and shows the test failure in the HTML report. But this does not cause final build to fail upon test failures. Q. Is there a way to tell maven (via plugin or something) that look for test failures in the test xml file and declare the build pass/fail? Appreciate any help/clues/suggestions. Thanks you. Deep 'Maven'er :) -- View this message in context: http://maven.40175.n5.nabble.com/How-to-parse-JUnit-report-xml-that-causes-build-to-pass-fail-tp5433750p5433750.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: How to parse JUnit report xml that causes build to pass/fail
runtime does not know abt how the test are ran, rather external test exec just exports a xml file that is fully JUnit result compatible. And if there is a failure reported in this exported xml file, I need to cause the build to fail like above. That means I want maven to parse this report xml, treat it similar to any other tests and cause build to fail. Currently my build Write your own plugin to call your external test and report failures, either by parsing the xml or some other approach - or - Adjust your external test tool so it returns false (1) when it has a failure which Maven should pick up and understand to mean failure encountered and it will fail the build Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: gwt-maven-plugin build error
Greetings, On Thu, Jan 5, 2012 at 5:33 PM, David Hoffer dhoff...@gmail.com wrote: I've tracked this down considerably more. Did you make any more progress? Frankly, this doesn't really smell like a gwt-m-p problem... but I am curious if you resolved it. -Jesse -- There are 10 types of people in this world, those that can read binary and those that can not. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
