Another things is that we plan to open source the product and post the code
on a website.
People that download will need to build the product.  We are not going to
put our repo manager out there for the world to use.

this requirement makes configuring a pom like this a necessity.  Ideally it
would be nice to have some of these jars on a maven repo but with some of
them, it's simply not going to happen.

thanks



Tim O'Brien wrote:
> 
> On Thu, Jul 30, 2009 at 1:23 PM, jvsrvcs<jvsr...@gmail.com> wrote:
>>
>> Thanks, the reason we are doing this is because:
>>
>> 1.  We have a lot of new programmers coming on board (10) that need to
>> quickly setup their local repo
> 
> Use a repository manager.   Distribute a settings.xml file.
> 
>> 2.  Many of these programmers/consultants are bash handicapped and don't
>> have cygwin installed
>> 3.  Doing it locally first is better than getting from a repo (and we can
>> use this init to provision the repo
>> once and will have it should we need to do it again).
>>
>> I appreciate the help and will give it a spin.
>>
>> thanks
>>
>> jv
>>
>> justinedelson wrote:
>>>
>>> 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:jvsr...@gmail.com]
>>> Sent: Thursday, July 30, 2009 10:51 AM
>>> To: users@maven.apache.org
>>> 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
>>> 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
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
>>> For additional commands, e-mail: users-h...@maven.apache.org
>>>
>>>
>>>
>>
>> --
>> View this message in context:
>> http://www.nabble.com/How-to-use-mvn-install-but-have-all-options-in-the-pom.xml--tp24739597p24744063.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
>>
>>
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
> 
> 
> 

-- 
View this message in context: 
http://www.nabble.com/How-to-use-mvn-install-but-have-all-options-in-the-pom.xml--tp24739597p24745709.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

Reply via email to