Mailing-List: contact issues-help@karaf.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@karaf.apache.org
Date: Fri, 24 Oct 2014 13:23:34 +0000 (UTC)
From: "Jean-Philippe CLEMENT (JIRA)" <jira@apache.org>
To: issues@karaf.apache.org
Message-ID: <JIRA.12750344.1414156697000.330680.1414157014013@Atlassian.JIRA>
In-Reply-To: <JIRA.12750344.1414156697000@Atlassian.JIRA>
References: <JIRA.12750344.1414156697000@Atlassian.JIRA>
 <JIRA.12750344.1414156697923@arcas>
Subject: [jira] [Commented] (KARAF-3334) Change Karaf to (from) dev mode
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/KARAF-3334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14182758#comment-14182758 ] 

Jean-Philippe CLEMENT commented on KARAF-3334:
----------------------------------------------

I'm wondering if it could be automatic depending on bundle version, i.e. SNAPSHOT

> 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
>
> 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)