[
https://issues.apache.org/jira/browse/KARAF-2011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13534705#comment-13534705
]
Jean-Baptiste Onofré commented on KARAF-2011:
---------------------------------------------
I'm investigating to see if the issue is not in Pax Url or the way that we
create the MavenConfiguration in the BundleWatcher.
I saw that:
- if we define the settings.xml in etc/org.ops4j.pax.url.mvn.cfg, it seems that
the <localRepository/> tag is considered correctly
- if we don't define the settings.xml, MavenConfiguration doesn't fall back to
the default location (home.user/.m2/settings.xml)
I postpone this Jira to 2.2.11 to give me more time to investigate. As a
workaround, I invite you to define localRepository property in the
etc/org.ops4j.pax.url.mvn.cfg.
> 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.11, 2.3.2, 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
