[
https://issues.apache.org/jira/browse/KARAF-1333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13285512#comment-13285512
]
Tuomas Kiviaho commented on KARAF-1333:
---------------------------------------
http://team.ops4j.org/browse/PAXURL-144 would provide an alternative approach
to deal with the issue provided that Pax URL Reference hander is changed so
that it will throw exception at getInputstream instead of postponing it to
read() method as it currently does. This way features service could remain
totally URL agnostic so that installBundle will only be provided a stream to
use when it can be achieved.
URL carrying multiple alternative locations (perhaps using Content-Location
header http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.14) would
require some sort preference/fallback queue for protocols so that correct url
is chosen.
> Support for M2E workspace resolution via reference: protocol
> ------------------------------------------------------------
>
> Key: KARAF-1333
> URL: https://issues.apache.org/jira/browse/KARAF-1333
> Project: Karaf
> Issue Type: Improvement
> Components: karaf-core, karaf-tooling
> Affects Versions: 3.0.0
> Reporter: Tuomas Kiviaho
> Labels: m2e, reference, workspace
> Attachments: FeaturesServiceImpl.patch, maven-plugin.patch
>
>
> Eclipse M2E plugin provides a 'workspace resolution' mode where Maven
> projects in Eclipse workspace are provided as workspace repository which
> takes precedence over other repositories.
> This leads to situation where artifact file isn't necessarily yet - depending
> on Mavens current lifecycle phase - provided as .jar but instead as directory
> pointing to project's output directory.
> {code:xml}
> <features xmlns="http://karaf.apache.org/xmlns/features/v1.0.0";
> name="example">
> <feature name="example" description="example">
> <bundle>mvn:com/example/dependency/1.0.0</bundle>
> ...
> <bundle>mvn:com/example/project/0.0.1-SNAPSHOT</bundle>
> ...
> </feature>
> </features>
> {code}
> The patches provided in this issue not only takes care of treating
> directories as exploded .jar files (common approach) but also provisions
> them with reference: protocol that most of the OSGi frameworks understand as
> direct filesystem references thus allowing exploded .jars to be installed.
> {code:xml}
> <features xmlns="http://karaf.apache.org/xmlns/features/v1.0.0";
> name="example">
> <feature name="example" description="example">
> <bundle>mvn:com/example/dependency/1.0.0</bundle>
> ...
> <bundle>reference:file:/~/workspace/example-project/classes/</bundle>
> ...
> </feature>
> </features>
> {code}
> Without intermediate round-trip via OSGi framework's bundle cache the
> 'workspace resolution' mode now offers also hot code replacement.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
