Re: Proposal for pax url aether config

I think it makes sense to stay with aether. It makes our artifact resolution more standard. So people with maven knowledge understand what happens. Another reason why I would like to stay with aether is that it minimizes the code we have to maintain and that we automatically participate in adva

Re: Proposal for pax url aether config

The maven url handler has been deprecated because there was no foreseen problems with it and aether seemed a good replacement for it. We could easily say we want to maintain it and I think that would un-deprecate it ;-) On Wednesday, March 7, 2012, Andreas Pieber wrote: > I'm strongly in favor o

Re: Proposal for pax url aether config

I'm strongly in favor of option (2) as proposed by JB. option (1) might be an option since dev:watch works anyhow in a dev setting and I think runtime settings have quite different requirements and for option (3) the mvn-url-handler is deprecated in favor of the aether handler; so not sure if I sho

Re: Proposal for pax url aether config

Hi David and Guillaume, David, what you describe was possible with pax-url-mvn, not with pax-url-aether. I don't want to introduce a "system" URL handling as it's a big change for the user and all projects with depending features. I'm strongly against (2) because Maven system repo is a key fe

Re: Proposal for pax url aether config

I agree with this analysis. Just to follow on, I think what you describe is mostly what we had for a long time in the 2.x branch (but the fact that we were needing the mvn url handler but not the aether one).. Should we simply get back to that ? On Tue, Mar 6, 2012 at 23:29, David Jencks wrote:

Re: Proposal for pax url aether config

I introduced the org.ops4j.pax.url.mvn.defaultLocalRepoAsRemote flag and set it to true so that the system repo could work at all. My thinking on mvn urls has changed considerably since then. I think there are two plausible choices: 1. keep the system repo as the local maven repo in karaf and

Re: Proposal for pax url aether config

On Tue, Mar 6, 2012 at 4:33 PM, Jean-Baptiste Onofré wrote: > Hi Christian, > > My only concern was for the people without a local repo (without maven > installation and so no .m2/repository). WHATTT Blasphemy ! ;) But as it concerns only SNAPSHOT, it's clear that only people with Maven >

Re: Proposal for pax url aether config

Hi Christian, My only concern was for the people without a local repo (without maven installation and so no .m2/repository). But as it concerns only SNAPSHOT, it's clear that only people with Maven installed will use SNAPSHOT ;) As Christian proposed, I second him: 1/ to apply what Christia

Proposal for pax url aether config

I just discussed with JB how a correct config for pax url could look like. I think we found a very nice solution (See below). Basically it uses the default local maven repo as a local repo and uses the system dir a a remote repo. - This means the system dir is now read only - The local repo is

Re: Some thoughts about the system dir and artifact resolution on trunk

I think that just adding the system repo (with file: kind of URL) in the org.ops4j.pax.url.mvn.cfg should work. As soon as I have completed sub-shell I will deal with that. Regards JB On 03/06/2012 03:19 PM, Christian Schneider wrote: After I had written my complete mail I also think that we

Re: Update on Karaf 3.0.0

Moving the issues is fine for me. I just would like to delay the branch till we know that most remaining issues are bug fixes and not features. So I think top priority should be to move all issues that can be moved. Christian Am 06.03.2012 13:12, schrieb Jamie G.: @Christian branching 3.0.x

Re: Some thoughts about the system dir and artifact resolution on trunk

After I had written my complete mail I also think that we can achieve it. (It often helps to write thoughts down). So what do you think about making the system dir an external repo for aether and using the default local repo as the aether local repo? I think it might solve most problems. We c

Re: Update on Karaf 3.0.0

Am 06.03.2012 13:10, schrieb Jean-Baptiste Onofré: I'm really concerned about this feedback because: - we discussed about the Karaf 3.0 release in December, including a review during the meeting in January. Now we have different point of view that should have been discussed before - I'm feelin

Re: Some thoughts about the system dir and artifact resolution on trunk

Hi Christian, My comment inline: we recently switched to pax-url-ather on trunk We switched pax-url-aether on trunk quite one year ago: Revision 1090691 Date: Sat Apr 9 21:42:13 2011 + [KARAF-529] - Upgrade to Pax URL 1.3.2 using pax-ur-aether for mvn: urls - When developing eit

Some thoughts about the system dir and artifact resolution on trunk

Hi all, we recently switched to pax-url-ather on trunk and since then artifact resolution does not work like before. JB and others tried to fix the behaviour but I think the problem is more fundamental and can not be fixed in the way we currrently try. As we might have different ideas of how

Re: Update on Karaf 3.0.0

@Christian branching 3.0.x from trunk will allow us more flexibility to move towards a RC. We can push out issues to the 3.1.x line while polishing the 3.0.x line for RC. Cheers, Jamie On Tue, Mar 6, 2012 at 8:22 AM, Christian Schneider wrote: > Hi JB, > > Am 06.03.2012 11:03, schrieb Jean-Bapti

Re: Update on Karaf 3.0.0

On Tue, Mar 6, 2012 at 12:52, Christian Schneider wrote: > Hi JB, > > Am 06.03.2012 11:03, schrieb Jean-Baptiste Onofré: > > Hi all, >> >> I would like to make an update on the status of Karaf 3.0. >> >> 1/ Bootstrap time and artifacts resolution >> I fixed the latest issue around pax-url-aether

Re: Update on Karaf 3.0.0

Hi Christian, my comments inline: 1/ Bootstrap time and artifacts resolution I fixed the latest issue around pax-url-aether and artifacts resolution on Saturday. Now, for SNAPSHOT artifacts, the karaf-maven-plugin (create-kar and install-kar goals) creates or copy the maven-metadata-local.xml.

Re: Update on Karaf 3.0.0

Hi JB, Am 06.03.2012 11:03, schrieb Jean-Baptiste Onofré: Hi all, I would like to make an update on the status of Karaf 3.0. 1/ Bootstrap time and artifacts resolution I fixed the latest issue around pax-url-aether and artifacts resolution on Saturday. Now, for SNAPSHOT artifacts, the karaf-m

Re: Update on Karaf 3.0.0

Sure ;) On 03/06/2012 12:07 PM, Ioannis Canellos wrote: Great news! I'd like to make a really trivial aesthetic comment. Could the sub shell prompt have no parenthesis when no sub shell is active: karaf@root> region karaf@root(region)> exit karaf@root> -- Jean-Baptiste Onofré jbono...@apa

Re: Update on Karaf 3.0.0

Great news! I'd like to make a really trivial aesthetic comment. Could the sub shell prompt have no parenthesis when no sub shell is active: karaf@root> region karaf@root(region)> exit karaf@root> -- *Ioannis Canellos* * FuseSource ** Blog: http://iocanel.blogspot.com *

Update on Karaf 3.0.0

Hi all, I would like to make an update on the status of Karaf 3.0. 1/ Bootstrap time and artifacts resolution I fixed the latest issue around pax-url-aether and artifacts resolution on Saturday. Now, for SNAPSHOT artifacts, the karaf-maven-plugin (create-kar and install-kar goals) creates or c