You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@karaf.apache.org by "Jean-Baptiste Onofré (JIRA)" <ji...@apache.org> on 2015/05/25 22:01:17 UTC
[jira] [Updated] (KARAF-3334) Change Karaf to (from) dev mode
[ https://issues.apache.org/jira/browse/KARAF-3334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jean-Baptiste Onofré updated KARAF-3334:
----------------------------------------
Fix Version/s: (was: 4.0.0.M3)
4.0.0
> Change Karaf to (from) dev mode
> -------------------------------
>
> Key: KARAF-3334
> URL: https://issues.apache.org/jira/browse/KARAF-3334
> Project: Karaf
> Issue Type: Improvement
> Affects Versions: 3.0.2
> Reporter: Jean-Philippe CLEMENT
> Assignee: Jean-Baptiste Onofré
> Fix For: 3.0.4, 4.0.0
>
>
> Karaf assembly plugin creates a configuration which first looks for artifacts from its internal repository.
> A side effect is that assembled bundles would not be updated from user Maven repositories. This is ennoying in dev phase where updating bundles is a daily job :)
> Two solutions can be done. Either change the configuration (3 lines must be modified), or remove bundles from the system sub-directory. At present time we are using the second solution as it is more simple.
> We would suggest to add a Karaf command line to go to dev mode without manually affect the configuration.
> PS: A simple flag inside configuration could also be welcome
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)