karaf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jean-Baptiste Onofré (JIRA) <j...@apache.org>
Subject [jira] [Updated] (KARAF-1333) Support for M2E workspace resolution via reference: protocol
Date Wed, 09 Apr 2014 03:53:15 GMT

     [ https://issues.apache.org/jira/browse/KARAF-1333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jean-Baptiste Onofré updated KARAF-1333:
----------------------------------------

    Fix Version/s:     (was: 3.0.1)
                   3.0.2

> 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
>            Assignee: Jean-Baptiste Onofré
>              Labels: m2e, reference, workspace
>             Fix For: 4.0.0, 3.0.2
>
>         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 was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message