[
https://issues.apache.org/jira/browse/KARAF-1333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tuomas Kiviaho updated KARAF-1333:
----------------------------------
Description:
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 as
directory pointing to project's output directory.
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.
Without intermediate round-trip via OSGi framework's bundle cache the
'workspace resolution' mode now offers also hot code replacement.
{code:xml}
<features xmlns="http://karaf.apache.org/xmlns/features/v1.0.0"; name="example">
<feature name="example" description="example">
...
<bundle>reference:file:/~/workspace/example/classes/</bundle>
...
</feature>
</features>
{code}
was:
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 as
directory pointing to project's output directory.
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.
Without intermediate round-trip via OSGi framework's bundle cache the
'workspace resolution' mode now offers also hot code replacement.
Summary: Support for M2E workspace resolution via reference: protocol
(was: Support for M2E workspace reresolution via reference: protocol)
> 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 as
> directory pointing to project's output directory.
> 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.
> Without intermediate round-trip via OSGi framework's bundle cache the
> 'workspace resolution' mode now offers also hot code replacement.
> {code:xml}
> <features xmlns="http://karaf.apache.org/xmlns/features/v1.0.0";
> name="example">
> <feature name="example" description="example">
> ...
> <bundle>reference:file:/~/workspace/example/classes/</bundle>
> ...
> </feature>
> </features>
> {code}
--
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
