> I'm trying to use it differently, not incorrectly. The deploy:deploy-file goal is clearly documented as being run from the command line. No mention is made of using it within a POM. See http://maven.apache.org/plugins/maven-deploy-plugin/usage.html. Unfortunately, there's no "usage" page for the install plugin, but I suspect it would be similar.
> The idea is that I should be able to run "mvn deploy" from my project root (or the > parent project if there are multiple dependencies), and have the jar deployed. This is different than what I'd understood your original question to be. I thought you wanted to run "mvn deploy" and have your third-party jars deployed, each with their own POM, but not deploy the POM of the "current" project. This isn't what the deploy phase is for. From http://maven.apache.org/guides/introduction/introduction-to-the-lifecycl e.html, "copies the final package to the remote repository for sharing with other developers and projects" meaning the package (artifact) of a project, not these 3rd party jars (which are artifacts of other projects). If you're trying to deploy the artifact of a project, then "mvn deploy" is the way to go, but this obviously requires a repository to deploy to. > I don't want to write a DOS .bat script to do this because it won't work on a UN*X system. So then write a shell script :) > Although, actually now I am more keen to get a proper pom in my repo, so deploy looks like the > way to go because I can add a pom with the pomFile parameter. You can specify a pom with either install:install-file or deploy:deploy-file. Check their mojo documentation. The difference is that with install:install-file, generatePom defaults to false whereas with deploy:deploy-file, it defaults to true. -----Original Message----- From: Dave Syer [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 09, 2006 10:26 AM To: [email protected] Subject: RE: Automating install:install-file > It sounds to me like you're using the deploy:deploy-file goal > incorrectly. I'm trying to use it differently, not incorrectly. I don't want to write a DOS .bat script to do this because it won't work on a UN*X system. The idea is that I should be able to run "mvn deploy" from my project root (or the parent project if there are multiple dependencies), and have the jar deployed. I'd be happy with "mvn install" and have the jar installed locally, but that was an even less productive avenue. Although, actually now I am more keen to get a proper pom in my repo, so deploy looks like the way to go because I can add a pom with the pomFile parameter. This is all very frustrating, I must say. I have spent close to three days now trying to build an existing project that was already building fine with ant. I still believe there is some mileage in it, bbut I'm running out of patience. -- View this message in context: http://www.nabble.com/Automating-install%3Ainstall-file-tf2071058.html#a 5726808 Sent from the Maven - Users forum at Nabble.com. --------------------------------------------------------------------- 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]
