I should also say that I personally think using install-file is a bad idea when there are good repository managers available.
Justin -----Original Message----- From: Edelson, Justin Sent: Thursday, July 30, 2009 1:13 PM To: Maven Users List Subject: RE: How to use mvn install but have all options in the pom.xml? It does need to be bound to a phase if you want to do more than one install. Also, the OP said he wanted to use a profile, which implied (to me at least) that this would be part of the lifecycle. generate-sources may or may not be the right phase, that's up to the OP. Justin ________________________________ From: Alexander [mailto:[email protected]] Sent: Thursday, July 30, 2009 11:10 AM To: Maven Users List Subject: Re: How to use mvn install but have all options in the pom.xml? There is no need to bind it to any phase, right? I think it is a pretty Maven-style way of solving problem Needa try.. 2009/7/30 Edelson, Justin <[email protected]> It's no different than any other plugin. Something like this should work: <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-install-plugin</artifactId> <executions> <execution> <id>install-1</id> <phase>generate-sources</phase> <goals> <goal>install-file</goal> </goals> <configuration> <artifactId>blah</artifactId> <groupId>blah</groupId> <version>v</version> <file>lib/somefile.jar</file> </configuration> </execution> ...repeat... </executions> </plugin> I don't think this is particularly common because a) it's very verbose compared with doing it on the command line and b) install-file only needs to be run once, so including it in the build isn't necessary. Justin -----Original Message----- From: jvsrvcs [mailto:[email protected]] Sent: Thursday, July 30, 2009 10:51 AM To: [email protected] Subject: How to use mvn install but have all options in the pom.xml? The docs on the mvn install plugin state: mvn install:install-file -Dfile=your-artifact-1.0.jar \ [-DpomFile=your-pom.xml] \ [-Dsources=src.jar] \ [-Djavadoc=apidocs.jar] \ [-DgroupId=org.some.group] \ [-DartifactId=your-artifact] \ [-Dversion=1.0] \ [-Dpackaging=jar] \ [-Dclassifier=sources] \ [-DgeneratePom=true] \ [-DcreateChecksum=true] So I could build a bash shell script that executes the above $mvn install command for each jar that I want to install into the local repo. What I want to do is to put all the options above into a pom.xml such that the user would only have to run a single maven profile and type only: $mvn -P init and have this profile run the install plugin run on each of about 20 dot jar files in lib/. I have seen this done before on a project but did not write the code nor do I have a copy of the code with me. I know it is possible but can't find any documentation on how to put options to $mvn install inside the pom.xml file (instead of the command line). -- View this message in context: http://www.nabble.com/How-to-use-mvn-install-but-have-all-options-in-the -pom.xml--tp24739597p24739597.html <http://www.nabble.com/How-to-use-mvn-install-but-have-all-options-in-th e-pom.xml--tp24739597p24739597.html> Sent from the Maven - Users mailing list archive 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
