[ 
https://issues.apache.org/jira/browse/MINSTALL-126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15439119#comment-15439119
 ] 

Michael Vorburger commented on MINSTALL-126:
--------------------------------------------

Yes Karaf only updates Maven based URLs and Maven SNAPSHOTs, and that's exactly 
what this is for; a proposed new option to be able to install artifacts into an 
additional (!) local Maven repository.  I use this regularly (we have it in 
https://github.com/opendaylight/odlparent/blob/master/odlparent-lite/pom.xml#L273).

Would you like to elaborate in more details on what you mean by "you can use a 
file url or snapshots" - where?  (Using maven-deploy-plugin (with a file:// URL 
parameter) instead of the maven-install-plugin in this context is no good, 
because deploy adds a unique time stamp to JAR file names (and its 
uniqueVersion option appears to be broken; see also issues MDEPLOY-44 and 
MDEPLOY-211).)

BTW: I like my blog! You don't?  Improvement Issues (without Fix Version) are 
perfectly fine for things like this IMHO.  If you are the (sole?) current 
maintainer of maven-install-plugin, you are free to close issues where people 
try to contribute possible enhancements, of course.  (To subscribe to mailing 
lists all over the universe to post an occasional suggestion like this, is too 
much email traffic overhead.)

> localRepositoryPath for install like for install-file
> -----------------------------------------------------
>
>                 Key: MINSTALL-126
>                 URL: https://issues.apache.org/jira/browse/MINSTALL-126
>             Project: Maven Install Plugin
>          Issue Type: Improvement
>            Reporter: Michael Vorburger
>
> I believe there are real world use cases where to have a localRepositoryPath 
> available for maven-install-plugin's install goal like it currently is for 
> the install-file goal would be useful.
> http://blog2.vorburger.ch/2016/06/maven-install-into-additional.html is a 
> Blog post I wrote with some background about why this would be useful.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to