Re: Is the mvn url handler really usable?

2011-09-30 Thread Andreas Pieber
Is there a description we can reproduce this problem every time. TBH I've not encountered any of such problems by now. If you've something reproducible please report an issue at team.ops4j.org. The problem will be located in the pax-url modules (maybe an aether update is required). Kind regards, A

Re: Is the mvn url handler really usable?

2011-09-30 Thread Brian Topping
I've seen the same thing, and have a recollection of this happening on 2.2.2 as well. On Sep 30, 2011, at 10:24 PM, David Jencks wrote: > On trunk, I've been having severe problems lately with the mvn url handler > downloading ancient snapshots and overwriting my just-built snapshots. > > Is

Is the mvn url handler really usable?

2011-09-30 Thread David Jencks
On trunk, I've been having severe problems lately with the mvn url handler downloading ancient snapshots and overwriting my just-built snapshots. Is this a configuration problem or something dreadfully wrong with the url handler design (or just a bug)? thanks david jencks

Re: svn commit: r1177574 - in /karaf/trunk/shell: console/src/main/java/org/apache/karaf/shell/console/jline/Activator.java dev/src/main/java/org/apache/karaf/shell/dev/SystemProperty.java dev/src/mai

2011-09-30 Thread Glen Mazza
On 9/30/2011 5:47 AM, gno...@apache.org wrote: Author: gnodet Date: Fri Sep 30 09:47:03 2011 New Revision: 1177574 Added: karaf/trunk/shell/dev/src/main/java/org/apache/karaf/shell/dev/SystemProperty.java URL: http://svn.apache.org/viewvc/karaf/trunk/shell/dev/src/main/java/org/apache/karaf/s

Re: [DISCUSS] Updating karaf core bundles in 3.0

2011-09-30 Thread Guillaume Nodet
osgi:update does work on any version, but for non snapshots, those are not supposed to change. dev:watch is limited to snaphots. I just wonder if we can use a file url *and* specifiy a different update url or something like that. I need to take a closer look. Where is the code using the referenc

Re: [DISCUSS] Updating karaf core bundles in 3.0

2011-09-30 Thread David Jencks
If you use a mvn url then you get two copies of the jar, one in system and a copy in the data area. My first reason for changing to this was to use reference: urls for everything in the system folder to halve the size of the server. Since then I've had enough problems with the mvn url handler

Re: [DISCUSS] Updating karaf core bundles in 3.0

2011-09-30 Thread Jean-Baptiste Onofré
FYI: https://issues.apache.org/jira/browse/KARAF-819 Regards JB On 09/30/2011 03:17 PM, Jean-Baptiste Onofré wrote: Hi Charles, it's not the same of the package, it's a FQFN (Full Qualified Feature Name) :) Regards JB On 09/30/2011 03:15 PM, Charles Moulliard wrote: BTW, the names of the f

Re: [DISCUSS] Updating karaf core bundles in 3.0

2011-09-30 Thread Jean-Baptiste Onofré
Hi Charles, it's not the same of the package, it's a FQFN (Full Qualified Feature Name) :) Regards JB On 09/30/2011 03:15 PM, Charles Moulliard wrote: BTW, the names of the features generated contain the name of the packages in features file of Karaf and not longer war, http, ... On Fri, Se

Re: [DISCUSS] Updating karaf core bundles in 3.0

2011-09-30 Thread Charles Moulliard
BTW, the names of the features generated contain the name of the packages in features file of Karaf and not longer war, http, ... On Fri, Sep 30, 2011 at 1:15 PM, Jean-Baptiste Onofré wrote: > Hi Guillaume, > > this behavior was introduced by the new assemblies generated by the > karaf-maven-plug

Re: [PROPOSAL] Karaf 2.2.4 roadmap

2011-09-30 Thread Jean-Baptiste Onofré
Hi Guillaume, I'm agree by the high usage of Karaf 2.2.x. My proposal is just to really limit the enhancements and new features on the Karaf 2.2.x to focus on Karaf 3.0. Of course, we continue bug fixing on this branch. The purpose is to "force" ourself to use more the trunk, fixing issues

Re: [DISCUSS] Updating karaf core bundles in 3.0

2011-09-30 Thread Jean-Baptiste Onofré
Hi Guillaume, this behavior was introduced by the new assemblies generated by the karaf-maven-plugin made by David. I raised a bug for a complete review and cleanup as I don't consider these assemblies stable and fully correct (see KARAF-772). It's part of the actions to begin just after Ka

Re: [PROPOSAL] Karaf 2.2.4 roadmap

2011-09-30 Thread Jamie G.
Focusing more on Karaf 3.0 would be a good thing after Karaf 2.2.4 is released, that being said I wouldn't fully freeze new development on 2.2.x just encourage more time to be spent on the 3.0.x line. The 2.2.x line will continue for a long time, I think we just want to put a push on getting Karaf

Re: [PROPOSAL] Karaf 2.2.4 roadmap

2011-09-30 Thread Guillaume Nodet
On Fri, Sep 30, 2011 at 09:22, Jean-Baptiste Onofré wrote: > Hi all, > > I prepared the roadmap for Karaf 2.2.4. I selected 13 issues that we should > include: > > KARAF-907 Include 64 bits wrapper library > KARAF-894 Kar deployment failed > KARAF-891 Problem either with documen

[DISCUSS] Updating karaf core bundles in 3.0

2011-09-30 Thread Guillaume Nodet
I have a problem with the way the current trunk installs the default core bundles. Those are installed using an absolute file location such as shown below. I think this lead to multiple problems, such as osgi:update / dev:watch do not work anymore on those bundles, as those were relying on the mvn

[PROPOSAL] Karaf 2.2.4 roadmap

2011-09-30 Thread Jean-Baptiste Onofré
Hi all, I prepared the roadmap for Karaf 2.2.4. I selected 13 issues that we should include: KARAF-907 Include 64 bits wrapper library KARAF-894 Kar deployment failed KARAF-891 Problem either with documentation or shell regarding wrapped wrap:mvn artifacts KA