[
https://issues.apache.org/jira/browse/KARAF-2011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13534296#comment-13534296
]
Bengt Rodehav commented on KARAF-2011:
--------------------------------------
Interesting. I guess the org.ops4j.pax.url.mvn.localRepository property can
then be used as a workaround. But, of course, it should not be necessary since
other parts of Karaf correctly detects the <localRepository> defined in maven's
settings.xml. Seems like this is code that should be reused in every part of
Karaf that needs to find the local repo.
> dev:watch looks in an incorrect local maven repository
> ------------------------------------------------------
>
> Key: KARAF-2011
> URL: https://issues.apache.org/jira/browse/KARAF-2011
> Project: Karaf
> Issue Type: Bug
> Components: karaf-shell
> Affects Versions: 2.2.9, 2.3.0
> Reporter: Bengt Rodehav
> Assignee: Jean-Baptiste Onofré
> Priority: Minor
> Fix For: 2.2.10, 2.3.1, 3.0.0
>
>
> If a non-default maven repository is used (by setting the "localRepository"
> property in maven's settings.xml), then dev:watch does not work. It seems
> like dev:watch does not consider the "localRepository" setting when looking
> for a bundle in maven.
> Note that other parts of Karaf does take the "localRepository" setting into
> account since installing features and using the "update" command works.
> This has been discussed on the user mailing list:
> http://karaf.922171.n3.nabble.com/dev-watch-problems-td4026725.html#a4026730
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
