Re: [INFO] Update default etc/org.ops4j.pax.url.mvn.cfg on Karaf 3.0.x

[Matt Sicker]

Maybe some collaboration with Pax URL would help? I don't think many people
work on that (might even be just one or two people). Some help would be
nice I'm sure!


On 3 September 2014 14:55, Christian Schneider 
wrote:

> Sounds good to me. We could use a directory below data as the local
> repository and system as a remote.
>
> The only problem there is that pax url will then copy all jars from the
> system repo into the data dir. If we find a way to avoid this then I think
> this would be great.
>
> Christian
>
>
> Am 03.09.2014 15:13, schrieb Matt Sicker:
>
>  Couldn't you make the system repo read-only (or a "remote") and make an
>> additional user directory or something for extra bundles? It could be like
>> the data/kar/ directory.
>>
>>
>>
> --
>  Christian Schneider
> http://www.liquid-reality.de
>
> Open Source Architect
> Talend Application Integration Division http://www.talend.com
>
>


-- 
Matt Sicker 

Re: [VOTE] Release Apache Karaf 2.3.7

[Heath Kesler]

+1 (non-binding)






+1 (non-binding)
Looks good for me

Best regards
Krzysztof

On 03.09.2014 02:47, Jamie G. wrote:


Hi,

We resolved 15 issues in this release:



http://svn.apache.org/viewvc/karaf/site/trunk/src/main/webapp/index/community/download/karaf-2.3.7-release.page?view=markup


Dependency changes can be reviewed here:



http://svn.apache.org/viewvc/karaf/site/trunk/src/main/webapp/index/documentation/karaf-dependencies/karaf-deps-2.3.x.page?revision=1613719&view=markup


Staging repository:
https://repository.apache.org/content/repositories/orgapachekaraf-1009/

Git tag:
karaf-2.3.7

Please vote to approve this release:

[ ] +1 Approve the release
[ ] -1 Veto the release (please provide specific comments)

This vote will be open for 72 hours.



--
Krzysztof Sobkowiak

JEE& OSS Architect | Senior Solution Architect @ Capgemini | Committer
@ ASF
Capgemini | Software Solutions Center
 | Wroclaw
e-mail: krzys.sobkow...@gmail.com |
Twitter: @KSobkowiak
Calendar: http://goo.gl/yvsebC

Re: [VOTE] Release Apache Karaf 2.3.7

[Andreas Pieber]

builds and tests as it should. Distribution looks good and does what it
should do.

+1 (binding).

Kind regards,
Andreas


On Wed, Sep 3, 2014 at 11:29 PM, Krzysztof Sobkowiak <
krzys.sobkow...@gmail.com> wrote:

> +1 (non-binding)
> Looks good for me
>
> Best regards
> Krzysztof
>
> On 03.09.2014 02:47, Jamie G. wrote:
> > Hi,
> >
> > We resolved 15 issues in this release:
> >
> http://svn.apache.org/viewvc/karaf/site/trunk/src/main/webapp/index/community/download/karaf-2.3.7-release.page?view=markup
> >
> > Dependency changes can be reviewed here:
> >
> http://svn.apache.org/viewvc/karaf/site/trunk/src/main/webapp/index/documentation/karaf-dependencies/karaf-deps-2.3.x.page?revision=1613719&view=markup
> >
> > Staging repository:
> > https://repository.apache.org/content/repositories/orgapachekaraf-1009/
> >
> > Git tag:
> > karaf-2.3.7
> >
> > Please vote to approve this release:
> >
> > [ ] +1 Approve the release
> > [ ] -1 Veto the release (please provide specific comments)
> >
> > This vote will be open for 72 hours.
>
>
> --
> Krzysztof Sobkowiak
>
> JEE & OSS Architect | Senior Solution Architect @ Capgemini | Committer
> @ ASF
> Capgemini  | Software Solutions Center
>  | Wroclaw
> e-mail: krzys.sobkow...@gmail.com  |
> Twitter: @KSobkowiak
> Calendar: http://goo.gl/yvsebC
>

Re: [VOTE] Release Apache Karaf 2.3.7

[Achim Nierbeck]

+1 (binding)

regards, Achim



2014-09-03 23:29 GMT+02:00 Krzysztof Sobkowiak :

> +1 (non-binding)
> Looks good for me
>
> Best regards
> Krzysztof
>
> On 03.09.2014 02:47, Jamie G. wrote:
> > Hi,
> >
> > We resolved 15 issues in this release:
> >
> http://svn.apache.org/viewvc/karaf/site/trunk/src/main/webapp/index/community/download/karaf-2.3.7-release.page?view=markup
> >
> > Dependency changes can be reviewed here:
> >
> http://svn.apache.org/viewvc/karaf/site/trunk/src/main/webapp/index/documentation/karaf-dependencies/karaf-deps-2.3.x.page?revision=1613719&view=markup
> >
> > Staging repository:
> > https://repository.apache.org/content/repositories/orgapachekaraf-1009/
> >
> > Git tag:
> > karaf-2.3.7
> >
> > Please vote to approve this release:
> >
> > [ ] +1 Approve the release
> > [ ] -1 Veto the release (please provide specific comments)
> >
> > This vote will be open for 72 hours.
>
>
> --
> Krzysztof Sobkowiak
>
> JEE & OSS Architect | Senior Solution Architect @ Capgemini | Committer
> @ ASF
> Capgemini  | Software Solutions Center
>  | Wroclaw
> e-mail: krzys.sobkow...@gmail.com  |
> Twitter: @KSobkowiak
> Calendar: http://goo.gl/yvsebC
>



-- 

Apache Member
Apache Karaf  Committer & PMC
OPS4J Pax Web  Committer &
Project Lead
blog 

Software Architect / Project Manager / Scrum Master

Re: [VOTE] Release Apache Karaf 2.3.7

[Krzysztof Sobkowiak]

+1 (non-binding)
Looks good for me

Best regards
Krzysztof

On 03.09.2014 02:47, Jamie G. wrote:
> Hi,
>
> We resolved 15 issues in this release:
> http://svn.apache.org/viewvc/karaf/site/trunk/src/main/webapp/index/community/download/karaf-2.3.7-release.page?view=markup
>
> Dependency changes can be reviewed here:
> http://svn.apache.org/viewvc/karaf/site/trunk/src/main/webapp/index/documentation/karaf-dependencies/karaf-deps-2.3.x.page?revision=1613719&view=markup
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachekaraf-1009/
>
> Git tag:
> karaf-2.3.7
>
> Please vote to approve this release:
>
> [ ] +1 Approve the release
> [ ] -1 Veto the release (please provide specific comments)
>
> This vote will be open for 72 hours.


-- 
Krzysztof Sobkowiak

JEE & OSS Architect | Senior Solution Architect @ Capgemini | Committer
@ ASF
Capgemini  | Software Solutions Center
 | Wroclaw
e-mail: krzys.sobkow...@gmail.com  |
Twitter: @KSobkowiak
Calendar: http://goo.gl/yvsebC

Re: [INFO] Update default etc/org.ops4j.pax.url.mvn.cfg on Karaf 3.0.x

[Christian Schneider]

Sounds good to me. We could use a directory below data as the local 
repository and system as a remote.


The only problem there is that pax url will then copy all jars from the 
system repo into the data dir. If we find a way to avoid this then I 
think this would be great.


Christian


Am 03.09.2014 15:13, schrieb Matt Sicker:

Couldn't you make the system repo read-only (or a "remote") and make an
additional user directory or something for extra bundles? It could be like
the data/kar/ directory.




--
 
Christian Schneider

http://www.liquid-reality.de

Open Source Architect
Talend Application Integration Division http://www.talend.com

Re: [VOTE] Release Apache Karaf 2.3.7

[Jean-Baptiste Onofré]

Unfortunately, no, Karaf 2.3.x is a maintenance release, and we avoid 
such major update.


Regards
JB

On 09/03/2014 03:07 PM, SvS wrote:

Hi,

Is it possible to update org.apache.aries.blueprint.cm to version 1.0.4  in
karaf 2.3.7? It solves many issues with the managed factory services.

Regards,
SvS



--
View this message in context: 
http://karaf.922171.n3.nabble.com/VOTE-Release-Apache-Karaf-2-3-7-tp4035022p4035038.html
Sent from the Karaf - Dev mailing list archive at Nabble.com.



--
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

Re: [VOTE] Release Apache Karaf 2.3.7

[Jamie G.]

SvS,

Can you enter a Jira for updating that package on our next patch roll up?


Cheers,
Jamie

On Wed, Sep 3, 2014 at 1:16 PM, David Bosschaert
 wrote:
> +1
>
> David
>
> On 3 September 2014 01:47, Jamie G.  wrote:
>> Hi,
>>
>> We resolved 15 issues in this release:
>> http://svn.apache.org/viewvc/karaf/site/trunk/src/main/webapp/index/community/download/karaf-2.3.7-release.page?view=markup
>>
>> Dependency changes can be reviewed here:
>> http://svn.apache.org/viewvc/karaf/site/trunk/src/main/webapp/index/documentation/karaf-dependencies/karaf-deps-2.3.x.page?revision=1613719&view=markup
>>
>> Staging repository:
>> https://repository.apache.org/content/repositories/orgapachekaraf-1009/
>>
>> Git tag:
>> karaf-2.3.7
>>
>> Please vote to approve this release:
>>
>> [ ] +1 Approve the release
>> [ ] -1 Veto the release (please provide specific comments)
>>
>> This vote will be open for 72 hours.

Re: [VOTE] Release Apache Karaf 2.3.7

[David Bosschaert]

+1

David

On 3 September 2014 01:47, Jamie G.  wrote:
> Hi,
>
> We resolved 15 issues in this release:
> http://svn.apache.org/viewvc/karaf/site/trunk/src/main/webapp/index/community/download/karaf-2.3.7-release.page?view=markup
>
> Dependency changes can be reviewed here:
> http://svn.apache.org/viewvc/karaf/site/trunk/src/main/webapp/index/documentation/karaf-dependencies/karaf-deps-2.3.x.page?revision=1613719&view=markup
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachekaraf-1009/
>
> Git tag:
> karaf-2.3.7
>
> Please vote to approve this release:
>
> [ ] +1 Approve the release
> [ ] -1 Veto the release (please provide specific comments)
>
> This vote will be open for 72 hours.

Re: [VOTE] Release Apache Karaf 2.3.7

[SvS]

Hi,

Is it possible to update org.apache.aries.blueprint.cm to version 1.0.4  in
karaf 2.3.7? It solves many issues with the managed factory services.

Regards,
SvS



--
View this message in context: 
http://karaf.922171.n3.nabble.com/VOTE-Release-Apache-Karaf-2-3-7-tp4035022p4035038.html
Sent from the Karaf - Dev mailing list archive at Nabble.com.

Re: [VOTE] Release Apache Karaf 2.3.7

[SvS]

Indeed! The console works fine again under Windows.

Regards,
SvS



--
View this message in context: 
http://karaf.922171.n3.nabble.com/VOTE-Release-Apache-Karaf-2-3-7-tp4035022p4035039.html
Sent from the Karaf - Dev mailing list archive at Nabble.com.

Re: [INFO] Update default etc/org.ops4j.pax.url.mvn.cfg on Karaf 3.0.x

[Matt Sicker]

Couldn't you make the system repo read-only (or a "remote") and make an
additional user directory or something for extra bundles? It could be like
the data/kar/ directory.


On 3 September 2014 06:21, Jean-Baptiste Onofré  wrote:

> IMHO, it had negative impact due to the bug that I saw in Pax URL.
>
> Now, on Karaf 3.0.2-SNAPSHOT, with my latest changes (and update to Pax
> URL 2.1.0), .m2/repository is not populated by default, and only the system
> repo is used.
> It's what I named the "standalone/atomic" production mode.
>
> I agree with your points, but IMHO, it's just different configuration to
> do in etc/org.ops4j.pax.url.mvn.cfg that we can document.
>
> Regards
> JB
>
>
> On 09/03/2014 12:58 PM, Christian Schneider wrote:
>
>> We had this setting  of using the system repo as a local repo at the
>> start of development of karaf 3. It had quite negative effects.
>> The problem is that maven will write into the local repo. The system
>> repo should be read only though.  So I think the system repo as a remote
>> repo is a good choice.
>>
>> The only problem I see is that some people do not like that a local repo
>> is written in .m2 for production machines. So it would be great if we
>> could find a way to optionally
>> avoid writing into the local repo. I think this case is typical if
>> people either have all bundles in the system repo or if they always want
>> to connect to their own nexus or similar server.
>>
>> In some cases on the other hand I think it is good to have a local repo
>> as cache for production machines. In the case where the system repo does
>> not contain all necessary bundles the local repo will
>> cache all necessary bundles after the first install. So the production
>> machine is then independent from the internet.
>>
>> For developer machines as a third case it is good to be able to override
>> the jars in the system repo with the jars in the local repo. So for
>> example if I run a snapshot of karaf and work on a module I can do
>> changes in the module, rebuild it to my local repo and update the bundle
>> in karaf. I hope this case still works after your change.
>>
>> Christian
>>
>> Am 31.08.2014 22:43, schrieb Jean-Baptiste Onofré:
>>
>>> Following this thread, I wonder if it doesn't make sense to add the
>>> system repo as local repo:
>>>
>>> org.ops4j.pax.url.mvn.localRepository=file:${karaf.
>>> home}/${karaf.default.repository}
>>>
>>>
>>> and override the default m2 settings with an empty one in Karaf:
>>>
>>> org.ops4j.pax.url.mvn.settings=${karaf.home}/${
>>> karaf.default.repository}/settings.xml
>>>
>>>
>>> by default, and document how to switch back to Maven "local user
>>> configuration".
>>>
>>> It would avoid to populate the .m2/repository and force to use the
>>> artifacts from the system repo (so very close to what we have in Karaf
>>> 2.x).
>>>
>>> WDYT ?
>>>
>>> Regards
>>> JB
>>>
>>> On 08/31/2014 10:31 PM, Matt Sicker wrote:
>>>
 I quite like that change. In my Karaf usage, I've always reconfigured
 the
 .m2/repository directory to be inside KARAF_HOME instead just to isolate
 the repositories in the first place. Any sort of change that prefers
 usage
 of artifact repositories embedded in Karaf are a step forward IMO.


 On 31 August 2014 14:36, Jean-Baptiste Onofré  wrote:

  Hi all,
>
> FYI, I aligned the etc/org.ops4j.pax.url.mvn.cfg files between master
> (Karaf 4.x) and Karaf 3.0.x.
>
> Basically, the change is to move the system repo and the kar repo as
> default repositories, instead of "regular" repositories.
>
> It allows Karaf to start quicker on a fresh machine, without any
> .m2/repository.
>
> Any objection ?
>
> Regards
> JB
> --
> Jean-Baptiste Onofré
> jbono...@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>
>



>>>
>>
>>
> --
> Jean-Baptiste Onofré
> jbono...@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>



-- 
Matt Sicker 

Re: [INFO] Update default etc/org.ops4j.pax.url.mvn.cfg on Karaf 3.0.x

[Achim Nierbeck]

Hi,

I agree with all of the above.
Don't we have for the dev-mode (Karaf development) already some special
configurations, for example snapshot repos that aren't included in a
released Karaf? I think this can be done for the o.o.p.u.mvn.cfg also.

regards, Achim



2014-09-03 13:21 GMT+02:00 Jean-Baptiste Onofré :

> IMHO, it had negative impact due to the bug that I saw in Pax URL.
>
> Now, on Karaf 3.0.2-SNAPSHOT, with my latest changes (and update to Pax
> URL 2.1.0), .m2/repository is not populated by default, and only the system
> repo is used.
> It's what I named the "standalone/atomic" production mode.
>
> I agree with your points, but IMHO, it's just different configuration to
> do in etc/org.ops4j.pax.url.mvn.cfg that we can document.
>
> Regards
> JB
>
>
> On 09/03/2014 12:58 PM, Christian Schneider wrote:
>
>> We had this setting  of using the system repo as a local repo at the
>> start of development of karaf 3. It had quite negative effects.
>> The problem is that maven will write into the local repo. The system
>> repo should be read only though.  So I think the system repo as a remote
>> repo is a good choice.
>>
>> The only problem I see is that some people do not like that a local repo
>> is written in .m2 for production machines. So it would be great if we
>> could find a way to optionally
>> avoid writing into the local repo. I think this case is typical if
>> people either have all bundles in the system repo or if they always want
>> to connect to their own nexus or similar server.
>>
>> In some cases on the other hand I think it is good to have a local repo
>> as cache for production machines. In the case where the system repo does
>> not contain all necessary bundles the local repo will
>> cache all necessary bundles after the first install. So the production
>> machine is then independent from the internet.
>>
>> For developer machines as a third case it is good to be able to override
>> the jars in the system repo with the jars in the local repo. So for
>> example if I run a snapshot of karaf and work on a module I can do
>> changes in the module, rebuild it to my local repo and update the bundle
>> in karaf. I hope this case still works after your change.
>>
>> Christian
>>
>> Am 31.08.2014 22:43, schrieb Jean-Baptiste Onofré:
>>
>>> Following this thread, I wonder if it doesn't make sense to add the
>>> system repo as local repo:
>>>
>>> org.ops4j.pax.url.mvn.localRepository=file:${karaf.
>>> home}/${karaf.default.repository}
>>>
>>>
>>> and override the default m2 settings with an empty one in Karaf:
>>>
>>> org.ops4j.pax.url.mvn.settings=${karaf.home}/${
>>> karaf.default.repository}/settings.xml
>>>
>>>
>>> by default, and document how to switch back to Maven "local user
>>> configuration".
>>>
>>> It would avoid to populate the .m2/repository and force to use the
>>> artifacts from the system repo (so very close to what we have in Karaf
>>> 2.x).
>>>
>>> WDYT ?
>>>
>>> Regards
>>> JB
>>>
>>> On 08/31/2014 10:31 PM, Matt Sicker wrote:
>>>
 I quite like that change. In my Karaf usage, I've always reconfigured
 the
 .m2/repository directory to be inside KARAF_HOME instead just to isolate
 the repositories in the first place. Any sort of change that prefers
 usage
 of artifact repositories embedded in Karaf are a step forward IMO.


 On 31 August 2014 14:36, Jean-Baptiste Onofré  wrote:

  Hi all,
>
> FYI, I aligned the etc/org.ops4j.pax.url.mvn.cfg files between master
> (Karaf 4.x) and Karaf 3.0.x.
>
> Basically, the change is to move the system repo and the kar repo as
> default repositories, instead of "regular" repositories.
>
> It allows Karaf to start quicker on a fresh machine, without any
> .m2/repository.
>
> Any objection ?
>
> Regards
> JB
> --
> Jean-Baptiste Onofré
> jbono...@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>
>



>>>
>>
>>
> --
> Jean-Baptiste Onofré
> jbono...@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>



-- 

Apache Member
Apache Karaf  Committer & PMC
OPS4J Pax Web  Committer &
Project Lead
blog 

Software Architect / Project Manager / Scrum Master

Re: [VOTE] Release Apache Karaf 2.3.7

[Jean-Baptiste Onofré]

Thanks for the update Jamie.

Regards
JB

On 09/03/2014 01:23 PM, Jamie G. wrote:

The Karaf 2.3.7 column is already checked in:
http://svn.apache.org/viewvc/karaf/site/trunk/src/main/webapp/index/documentation/karaf-dependencies/karaf-deps-2.3.x.page?view=markup

I accidentally picked up the wrong rev for the link above :S

Cheers,
jamie

On Wed, Sep 3, 2014 at 5:50 AM, Christian Schneider
 wrote:

+1 (non binding)

Works fine on windows.

Christian

Am 03.09.2014 02:47, schrieb Jamie G.:


Hi,

We resolved 15 issues in this release:

http://svn.apache.org/viewvc/karaf/site/trunk/src/main/webapp/index/community/download/karaf-2.3.7-release.page?view=markup

Dependency changes can be reviewed here:

http://svn.apache.org/viewvc/karaf/site/trunk/src/main/webapp/index/documentation/karaf-dependencies/karaf-deps-2.3.x.page?revision=1613719&view=markup

Staging repository:
https://repository.apache.org/content/repositories/orgapachekaraf-1009/

Git tag:
karaf-2.3.7

Please vote to approve this release:

[ ] +1 Approve the release
[ ] -1 Veto the release (please provide specific comments)

This vote will be open for 72 hours.




--
  Christian Schneider
http://www.liquid-reality.de

Open Source Architect
Talend Application Integration Division http://www.talend.com



--
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

Re: [VOTE] Release Apache Karaf 2.3.7

[Jamie G.]

The Karaf 2.3.7 column is already checked in:
http://svn.apache.org/viewvc/karaf/site/trunk/src/main/webapp/index/documentation/karaf-dependencies/karaf-deps-2.3.x.page?view=markup

I accidentally picked up the wrong rev for the link above :S

Cheers,
jamie

On Wed, Sep 3, 2014 at 5:50 AM, Christian Schneider
 wrote:
> +1 (non binding)
>
> Works fine on windows.
>
> Christian
>
> Am 03.09.2014 02:47, schrieb Jamie G.:
>
>> Hi,
>>
>> We resolved 15 issues in this release:
>>
>> http://svn.apache.org/viewvc/karaf/site/trunk/src/main/webapp/index/community/download/karaf-2.3.7-release.page?view=markup
>>
>> Dependency changes can be reviewed here:
>>
>> http://svn.apache.org/viewvc/karaf/site/trunk/src/main/webapp/index/documentation/karaf-dependencies/karaf-deps-2.3.x.page?revision=1613719&view=markup
>>
>> Staging repository:
>> https://repository.apache.org/content/repositories/orgapachekaraf-1009/
>>
>> Git tag:
>> karaf-2.3.7
>>
>> Please vote to approve this release:
>>
>> [ ] +1 Approve the release
>> [ ] -1 Veto the release (please provide specific comments)
>>
>> This vote will be open for 72 hours.
>
>
>
> --
>  Christian Schneider
> http://www.liquid-reality.de
>
> Open Source Architect
> Talend Application Integration Division http://www.talend.com
>

Re: [INFO] Update default etc/org.ops4j.pax.url.mvn.cfg on Karaf 3.0.x

[Jean-Baptiste Onofré]

IMHO, it had negative impact due to the bug that I saw in Pax URL.

Now, on Karaf 3.0.2-SNAPSHOT, with my latest changes (and update to Pax 
URL 2.1.0), .m2/repository is not populated by default, and only the 
system repo is used.

It's what I named the "standalone/atomic" production mode.

I agree with your points, but IMHO, it's just different configuration to 
do in etc/org.ops4j.pax.url.mvn.cfg that we can document.


Regards
JB

On 09/03/2014 12:58 PM, Christian Schneider wrote:

We had this setting  of using the system repo as a local repo at the
start of development of karaf 3. It had quite negative effects.
The problem is that maven will write into the local repo. The system
repo should be read only though.  So I think the system repo as a remote
repo is a good choice.

The only problem I see is that some people do not like that a local repo
is written in .m2 for production machines. So it would be great if we
could find a way to optionally
avoid writing into the local repo. I think this case is typical if
people either have all bundles in the system repo or if they always want
to connect to their own nexus or similar server.

In some cases on the other hand I think it is good to have a local repo
as cache for production machines. In the case where the system repo does
not contain all necessary bundles the local repo will
cache all necessary bundles after the first install. So the production
machine is then independent from the internet.

For developer machines as a third case it is good to be able to override
the jars in the system repo with the jars in the local repo. So for
example if I run a snapshot of karaf and work on a module I can do
changes in the module, rebuild it to my local repo and update the bundle
in karaf. I hope this case still works after your change.

Christian

Am 31.08.2014 22:43, schrieb Jean-Baptiste Onofré:

Following this thread, I wonder if it doesn't make sense to add the
system repo as local repo:

org.ops4j.pax.url.mvn.localRepository=file:${karaf.home}/${karaf.default.repository}


and override the default m2 settings with an empty one in Karaf:

org.ops4j.pax.url.mvn.settings=${karaf.home}/${karaf.default.repository}/settings.xml


by default, and document how to switch back to Maven "local user
configuration".

It would avoid to populate the .m2/repository and force to use the
artifacts from the system repo (so very close to what we have in Karaf
2.x).

WDYT ?

Regards
JB

On 08/31/2014 10:31 PM, Matt Sicker wrote:

I quite like that change. In my Karaf usage, I've always reconfigured
the
.m2/repository directory to be inside KARAF_HOME instead just to isolate
the repositories in the first place. Any sort of change that prefers
usage
of artifact repositories embedded in Karaf are a step forward IMO.


On 31 August 2014 14:36, Jean-Baptiste Onofré  wrote:


Hi all,

FYI, I aligned the etc/org.ops4j.pax.url.mvn.cfg files between master
(Karaf 4.x) and Karaf 3.0.x.

Basically, the change is to move the system repo and the kar repo as
default repositories, instead of "regular" repositories.

It allows Karaf to start quicker on a fresh machine, without any
.m2/repository.

Any objection ?

Regards
JB
--
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com












--
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

Re: [INFO] Update default etc/org.ops4j.pax.url.mvn.cfg on Karaf 3.0.x

[Christian Schneider]

Generally I agree with the production ready default.

I would like to see the development case covered better though. So I 
propose we have a build profile for karaf to create a karaf with 
development settings. This will allow a karaf developer to work with a 
snapshot karaf without tweaking configs.


Also as I wrote in the other mail I see big problems when using the 
system repo as local repo. Did you find a way to avoid that pax url 
writes into the system dir?


The ideal case for me would be that pax url caches all external bundles 
in the local repository but not the bundles in the system dir. So we 
would need to mark the system dir as read only but "local" to make sure 
the jars are not cached. I am not sure if this is possible though.


Christian


Am 01.09.2014 10:14, schrieb Jean-Baptiste Onofré:

Hi Matt,

I agree.

Let me explain what I have in mind.

Karaf can work in two modes:
- by default, it should be standalone/atomic. I mean here that it 
should not use any "external folders" like the .m2/repository folder.
It means the following configuration in etc/org.ops4j.pax.url.mvn.cfg 
file:

 -- org.ops4j.pax.url.mvn.settings=${karaf.etc}/settings.xml
 where the settings.xml contains an "empty" settings.xml like:


 -- 
org.ops4j.pax.url.mvn.localRepository=${karaf.home}/${karaf.default.repository}

   to use the system repo as local by default (and not .m2/repository)
 -- org.ops4j.pax.url.mvn.defaultRepositories=\
${karaf.home}/${karaf.default.repository}@id=system@snapshots, \
  ${karaf.data}/kar@id=kar@multi@snapshots
 -- org.ops4j.pax.url.mvn.repositories=\
  http://repo1.maven.org/maven2@id=central, \

http://repository.springsource.com/maven/bundle/release@id=spring.ebr.release, 
\


http://repository.springsource.com/maven/bundles/external@id=spring.ebr.external, 
\


http://repository.apache.org/content/groups/snapshots-group@id=apache@snapshots@noreleases, 
\


https://oss.sonatype.org/content/repositories/snapshots@id=sonatype.snapshots.deploy@snapshots@norelease, 
\


https://oss.sonatype.org/content/repositories/ops4j-snapshots@id=ops4j.sonatype.snapshots.deploy@snapshots@noreleases 



- as an alternative, we document (both in the user guide and using 
comments in etc/org.ops4j.pax.url.mnv.cfg) how to switch in 
"development mode", meaning:
  -- comment the org.ops4j.pax.url.mvn.settings property to use the 
user .m2/settings.xml
  -- comment the org.ops4j.pax.url.mvn.localRepository property to use 
the user .m2/repository


WDYT ?

Regards
JB

On 08/31/2014 10:49 PM, Matt Sicker wrote:

Basically, the way I see it, in a developer setting, using your
.m2/repository makes sense as it's likely to have tons of libraries 
there

already. On production/staging/testing servers, however, it's far more
likely to contain things as much as possible. For instance, I may 
wish to

run Karaf as a user that has no home directory.


On 31 August 2014 15:43, Jean-Baptiste Onofré  wrote:

Following this thread, I wonder if it doesn't make sense to add the 
system

repo as local repo:

org.ops4j.pax.url.mvn.localRepository=file:${karaf.home}/${karaf.default. 


repository}

and override the default m2 settings with an empty one in Karaf:

org.ops4j.pax.url.mvn.settings=${karaf.home}/${karaf.default.repository}/ 


settings.xml

by default, and document how to switch back to Maven "local user
configuration".

It would avoid to populate the .m2/repository and force to use the
artifacts from the system repo (so very close to what we have in 
Karaf 2.x).


WDYT ?

Regards
JB


On 08/31/2014 10:31 PM, Matt Sicker wrote:

I quite like that change. In my Karaf usage, I've always 
reconfigured the
.m2/repository directory to be inside KARAF_HOME instead just to 
isolate
the repositories in the first place. Any sort of change that 
prefers usage

of artifact repositories embedded in Karaf are a step forward IMO.


On 31 August 2014 14:36, Jean-Baptiste Onofré  wrote:

  Hi all,


FYI, I aligned the etc/org.ops4j.pax.url.mvn.cfg files between master
(Karaf 4.x) and Karaf 3.0.x.

Basically, the change is to move the system repo and the kar repo as
default repositories, instead of "regular" repositories.

It allows Karaf to start quicker on a fresh machine, without any
.m2/repository.

Any objection ?

Regards
JB
--
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com







--
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com










--
 
Christian Schneider

http://www.liquid-reality.de

Open Source Architect
Talend Application Integration Division http://www.talend.com

Re: [INFO] Update default etc/org.ops4j.pax.url.mvn.cfg on Karaf 3.0.x

[Christian Schneider]

We had this setting  of using the system repo as a local repo at the 
start of development of karaf 3. It had quite negative effects.
The problem is that maven will write into the local repo. The system 
repo should be read only though.  So I think the system repo as a remote 
repo is a good choice.


The only problem I see is that some people do not like that a local repo 
is written in .m2 for production machines. So it would be great if we 
could find a way to optionally
avoid writing into the local repo. I think this case is typical if 
people either have all bundles in the system repo or if they always want 
to connect to their own nexus or similar server.


In some cases on the other hand I think it is good to have a local repo 
as cache for production machines. In the case where the system repo does 
not contain all necessary bundles the local repo will
cache all necessary bundles after the first install. So the production 
machine is then independent from the internet.


For developer machines as a third case it is good to be able to override 
the jars in the system repo with the jars in the local repo. So for 
example if I run a snapshot of karaf and work on a module I can do 
changes in the module, rebuild it to my local repo and update the bundle 
in karaf. I hope this case still works after your change.


Christian

Am 31.08.2014 22:43, schrieb Jean-Baptiste Onofré:
Following this thread, I wonder if it doesn't make sense to add the 
system repo as local repo:


org.ops4j.pax.url.mvn.localRepository=file:${karaf.home}/${karaf.default.repository} 



and override the default m2 settings with an empty one in Karaf:

org.ops4j.pax.url.mvn.settings=${karaf.home}/${karaf.default.repository}/settings.xml 



by default, and document how to switch back to Maven "local user 
configuration".


It would avoid to populate the .m2/repository and force to use the 
artifacts from the system repo (so very close to what we have in Karaf 
2.x).


WDYT ?

Regards
JB

On 08/31/2014 10:31 PM, Matt Sicker wrote:
I quite like that change. In my Karaf usage, I've always reconfigured 
the

.m2/repository directory to be inside KARAF_HOME instead just to isolate
the repositories in the first place. Any sort of change that prefers 
usage

of artifact repositories embedded in Karaf are a step forward IMO.


On 31 August 2014 14:36, Jean-Baptiste Onofré  wrote:


Hi all,

FYI, I aligned the etc/org.ops4j.pax.url.mvn.cfg files between master
(Karaf 4.x) and Karaf 3.0.x.

Basically, the change is to move the system repo and the kar repo as
default repositories, instead of "regular" repositories.

It allows Karaf to start quicker on a fresh machine, without any
.m2/repository.

Any objection ?

Regards
JB
--
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com










--
 
Christian Schneider

http://www.liquid-reality.de

Open Source Architect
Talend Application Integration Division http://www.talend.com

Re: [VOTE] Release Apache Karaf 2.3.7

[Christian Schneider]

+1 (non binding)

Works fine on windows.

Christian

Am 03.09.2014 02:47, schrieb Jamie G.:

Hi,

We resolved 15 issues in this release:
http://svn.apache.org/viewvc/karaf/site/trunk/src/main/webapp/index/community/download/karaf-2.3.7-release.page?view=markup

Dependency changes can be reviewed here:
http://svn.apache.org/viewvc/karaf/site/trunk/src/main/webapp/index/documentation/karaf-dependencies/karaf-deps-2.3.x.page?revision=1613719&view=markup

Staging repository:
https://repository.apache.org/content/repositories/orgapachekaraf-1009/

Git tag:
karaf-2.3.7

Please vote to approve this release:

[ ] +1 Approve the release
[ ] -1 Veto the release (please provide specific comments)

This vote will be open for 72 hours.



--
 
Christian Schneider

http://www.liquid-reality.de

Open Source Architect
Talend Application Integration Division http://www.talend.com

Re: [VOTE] Release Apache Karaf 2.3.7

[roedll]

+1 (no binding)

Testet on Windows: Console works again ;-)

regards, Lukas



--
View this message in context: 
http://karaf.922171.n3.nabble.com/VOTE-Release-Apache-Karaf-2-3-7-tp4035022p4035029.html
Sent from the Karaf - Dev mailing list archive at Nabble.com.