Re: Failed to deploy artifacts
Oh, thanks for the pointer... I figured it out... The permissions were wrong. Thank you very much for your help. We are running Nexus 1.8. I am considering upgrading to the latest version. Would our artifacts be migrated safely? -- View this message in context: http://maven.40175.n5.nabble.com/Failed-to-deploy-artifacts-tp5710875p5710923.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
Failed to deploy artifacts
I am getting Failed to deploy artifacts error 500 on trying to deploying an artifact to our releases repository on our nexus server. (I was able to deploy successfully last week!) I even enabled Allow Redeploy on my repository. Any help or guidance would be appreciated. mvn deploy:deploy-file -DpomFile=pecia-1.0.pom -Dfile=pecia-1.0.jar -DrepositoryId=MyID -Durl=http://taus-itpmuprd/nexus/content/repositories/MY-RELEASES [INFO] Scanning for projects... [INFO] [INFO] [INFO] Building Maven Stub Project (No POM) 1 [INFO] [INFO] [INFO] --- maven-deploy-plugin:2.5:deploy-file (default-cli) @ standalone-pom --- Uploading: http://taus-itpmuprd/nexus/content/repositories/MY-RELEASES/nl/flotsam/pecia/pecia/1.0/pecia-1.0.jar 81 KB Uploading: http://taus-itpmuprd/nexus/content/repositories/MY-RELEASES/nl/flotsam/pecia/pecia/1.0/pecia-1.0.pom 7 KB [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 0.743s [INFO] Finished at: Tue Jun 05 18:40:46 PDT 2012 [INFO] Final Memory: 3M/57M [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 nl.flotsam.pecia:pecia:jar:1.0 from/to MY-RELEASES (http://taus-itpmuprd/nexus/content/repositories/MY-RELEASES): Failed to transfer file: http://taus-itpmuprd/nexus/content/repositories/MY-RELEASES/nl/flotsam/pecia/pecia/1.0/pecia-1.0.jar. Return code is: 500 - [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException -- View this message in context: http://maven.40175.n5.nabble.com/Failed-to-deploy-artifacts-tp5710875.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: Checkout and Build all dependencies
Yes, that is very similar to our requirement: We need to lock down the build environment to be able to reproduce the build at anytime in the future. Here are the high level objectives: Checkout all projects from SVN Build projects using Maven and install them to the local Maven repository. We would need to start with the parent projects. Totally agree: we will not check in everything in SVN. On Thu, Apr 7, 2011 at 8:34 AM, Manfred Moser [via Maven] ml-node+4288827-1669842602-196...@n5.nabble.com wrote: We have a compliance/audit requirement that we need to be able to exactly reproduce builds. (Current requirement does not allow the build machine access to our internal nexus repository.) I have had to deal with this sort of requirement in the past in ISO, FDA and code repository context. In my opinion you need to be able to build without anything else apart from the supplied codebase/artifacts. In the Maven world the best way to achieve this is to package up all the source code and your repository server setup (or at least the repository used by your build with all artifacts as well as Maven in the exact version you use. You will have to lock down all plugin and dependency versions and be sure to have them in the repo and then you will be able to do a complete offline build with the repo. If you dont do that you will have some major nightmares in terms of reproducibility of the build and the used artifacts. Do NOT follow down the path of just trying to check everything into svn. If you do that you properly you will end up with the repository server in svn. Might as well allow the repo server to be an artifact... - To unsubscribe, e-mail: [hidden email]http://user/SendEmail.jtp?type=nodenode=4288827i=0by-user=t For additional commands, e-mail: [hidden email]http://user/SendEmail.jtp?type=nodenode=4288827i=1by-user=t -- If you reply to this email, your message will be added to the discussion below: http://maven.40175.n5.nabble.com/Checkout-and-Build-all-dependencies-tp4287477p4288827.html To unsubscribe from Checkout and Build all dependencies, click herehttp://maven.40175.n5.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_codenode=4287477code=YW5hc211Z2hhbEBnbWFpbC5jb218NDI4NzQ3N3wtMzc0Njc1OTEy. -- Anas Mughal -- View this message in context: http://maven.40175.n5.nabble.com/Checkout-and-Build-all-dependencies-tp4287477p4289419.html Sent from the Maven - Users mailing list archive at Nabble.com.
Checkout and Build all dependencies
We have a compliance/audit requirement that we need to be able to exactly reproduce builds. (Current requirement does not allow the build machine access to our internal nexus repository.) We have a few projects with typical maven dependency hierarchy. Is there a way that I could setup a build script that would fetch all dependencies from SVN and then trigger a complete build. Of course, we start the build process by deleting everything from the local maven repository. Then, we build going down the dependency hierarchy. As we build a parent, we install it in the local maven repository on the build machine. This does seem to be something that CruiseControl and Hudson do. Should I consider just setting up CruiseControl or Hudson to perform the builds for us? Or, is there a better way to setup this checkout and build process. Any advice much appreciated. -- Anas Mughal -- View this message in context: http://maven.40175.n5.nabble.com/Checkout-and-Build-all-dependencies-tp4287477p4287477.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
