[CANCEL][VOTE] Apache Karaf 4.0.5 release (take 2)

[Jean-Baptiste Onofré]

Hi,

as discussed on the mailing list, and due to a critical issue in Aries 
Blueprint Core, I cancel this vote.


I will tackle fix and release of Aries Blueprint Core 1.6.1 and update 
in Karaf. I will submit a new 4.0.5 release to vote then.


Thanks
Regards
JB

On 04/04/2016 10:38 PM, Jean-Baptiste Onofré wrote:

Hi all,

I submit Karaf Container 4.0.5 release to your vote.

Release Note:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311140&version=12334629


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

Git tag:
karaf-4.0.5

Please vote to approve this release:

[ ] +1 Approve the release
[ ] -1 Don't approve the release (please provide specific comments)

This vote will be open for at least 72 hours.

Thanks,
Regards
JB


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

Re: [VOTE] Apache Karaf 4.0.5 release (take 2)

[Grzegorz Grzybek]

Thanks for patience!

regards
Grzegorz

2016-04-06 14:57 GMT+02:00 Jean-Baptiste Onofré :

> Thanks man (as discussed on IRC ;)).
>
> I will review the PR and deal with the Aries releases.
>
> Regards
> JB
>
>
> On 04/06/2016 02:45 PM, Grzegorz Grzybek wrote:
>
>> Hello
>>
>> OK, I have a fix and here's an explanation.
>> First (ARIES-1290), following Java relationship of
>> org.apache.aries.blueprint.compendium.cm.CmPropertyPlaceholder and
>> org.apache.aries.blueprint.ext.PropertyPlaceholder I wanted to reflect
>> this
>> fact at XSD level, so we could mix cm and ext namespace elements.
>> Then (ARIES-1503) there was a fix for situations, where XSDs were read for
>> CmNamespaceHandler before ExtNamespaceHandler managed to register itself
>> in
>> NamespaceRegistryImpl.
>>
>> And finally (now) the fix (after adding
>> org.apache.aries.blueprint.NamespaceHandler2#mayResolve() method) is more
>> conservative - we can resolve not registered namespaces using those
>> handlers that return true in their implementation of
>> org.apache.aries.blueprint.NamespaceHandler2#mayResolve() - and there'll
>> be
>> (now) only one such handler - for cm namespace.
>>
>> I'm preparing PR.
>>
>> best regards and I'm very sorry for delay of the release!
>> Grzegorz Grzybek
>>
>> 2016-04-06 11:50 GMT+02:00 Kevin Carr :
>>
>> I agree option 2.  Best to delay and fix.
>>>
>>> On Wed, Apr 6, 2016, 4:49 AM Achim Nierbeck 
>>> wrote:
>>>
>>> yeah option 2 sounds best, so here's my -1 on this release ... a major

>>> bug
>>>
 shouldn't go into any production, especially if we know of it.

 regards, Achim


 2016-04-06 9:47 GMT+02:00 Markus Rathgeb :

 +1 for option 2
>
> 2016-04-06 8:48 GMT+02:00 Sobkowiak Krzysztof <
>
 krzys.sobkow...@gmail.com
>>>
 :
>
>> I prefer the option 2 as well
>>
>> Regards
>> Krzysztof
>>
>> On 06.04.2016 08:39, Jean-Baptiste Onofré wrote:
>>
>>> Hi Cristiano,
>>>
>>> I don't think it's related, as the issue in about blueprint-ext
>>>
>> namespace (not even define). The problem is located in Aries
> Blueprint.
>
>>
>>> I gonna deal with Guillaume.
>>>
>>> We can:
>>> 0. leave Karaf 4.0.5 as it is, but I think it's not acceptable:
>>>
>> blueprint is used by lot of users, and we can't allow a release
>
 without a
>>>
 working blueprint layer.
>
>> 1. downgrade Karaf to Aries Blueprint 1.5.x: unfortunately, we won't
>>>
>> benefit about some improvements implemented in blueprint
>
>> 2. revert or fix the change in Aries: it means we would need a new
>>>
>> Aries Blueprint core release, so 3 days vote, meaning that we won't be
>
 able

> to release Karaf before roughly 6 days.
>
>>
>>> My preference is on 2 even if it delays Karaf 4.0.5 release.
>>>
>>> Thoughts ?
>>>
>>> I will add an Integration Test on blueprint to avoid such problem in
>>>
>> the future.
>
>>
>>> Regards
>>> JB
>>>
>>> On 04/06/2016 08:14 AM, Cristiano Costantini wrote:
>>>
 Hi JB and Krzysztof,

 I don't know if this can be have any impact on the problem you have
 reported, but about 1 month ago I got into an issue with camel XSD

>>> schemas
>
>> for Camel namespaces, and the issue is that the URL of the latest

>>> XSD,

> http://camel.apache.org/schema/blueprint/camel-blueprint.xsd
 is not from latest version 2.16.2, but it is from version 2.15.0

 While upgrading to ServiceMix 7, I had to change manually the XML

>>> to
>>>
 xsi:schemaLocation="http://camel.apache.org/schema/spring

>>> http://camel

> .apache.org/schema/spring/camel-spring-2.16.1.xsd" in order to

>>> make
>>>
 it work
>
>> (note also that SMX 7 is based on camel 2.16.2, but this XSD is not
 available)

 But in fact the only problem I had was that Eclipse validation and
 autocompletion of the XML files was not working properly.

 if this is not relevant, please ignore this message ;-)

 Cristiano




 Il giorno mar 5 apr 2016 alle ore 22:19 Jean-Baptiste Onofré <
 j...@nanthrax.net> ha scritto:

 I tried with Camel 2.16.2, camel-blueprint, and simple route in
> blueprint: it works fine.
>
> I tried with your XML, and actually I have the same problem.
>
> It sounds like a Aries Blueprint bug. Let me try if I downgrade to
> blueprint 1.5.x and check the change in aries blueprint (I know
> Guillaume did some enhancements & changes).
>
> Honestly, I would consider as a blocker for the release, so, I
>
 will
>>>
 probably revert my vote t

Re: [VOTE] Apache Karaf 4.0.5 release (take 2)

[Jean-Baptiste Onofré]

Thanks man (as discussed on IRC ;)).

I will review the PR and deal with the Aries releases.

Regards
JB

On 04/06/2016 02:45 PM, Grzegorz Grzybek wrote:

Hello

OK, I have a fix and here's an explanation.
First (ARIES-1290), following Java relationship of
org.apache.aries.blueprint.compendium.cm.CmPropertyPlaceholder and
org.apache.aries.blueprint.ext.PropertyPlaceholder I wanted to reflect this
fact at XSD level, so we could mix cm and ext namespace elements.
Then (ARIES-1503) there was a fix for situations, where XSDs were read for
CmNamespaceHandler before ExtNamespaceHandler managed to register itself in
NamespaceRegistryImpl.

And finally (now) the fix (after adding
org.apache.aries.blueprint.NamespaceHandler2#mayResolve() method) is more
conservative - we can resolve not registered namespaces using those
handlers that return true in their implementation of
org.apache.aries.blueprint.NamespaceHandler2#mayResolve() - and there'll be
(now) only one such handler - for cm namespace.

I'm preparing PR.

best regards and I'm very sorry for delay of the release!
Grzegorz Grzybek

2016-04-06 11:50 GMT+02:00 Kevin Carr :


I agree option 2.  Best to delay and fix.

On Wed, Apr 6, 2016, 4:49 AM Achim Nierbeck 
wrote:


yeah option 2 sounds best, so here's my -1 on this release ... a major

bug

shouldn't go into any production, especially if we know of it.

regards, Achim


2016-04-06 9:47 GMT+02:00 Markus Rathgeb :


+1 for option 2

2016-04-06 8:48 GMT+02:00 Sobkowiak Krzysztof <

krzys.sobkow...@gmail.com

:

I prefer the option 2 as well

Regards
Krzysztof

On 06.04.2016 08:39, Jean-Baptiste Onofré wrote:

Hi Cristiano,

I don't think it's related, as the issue in about blueprint-ext

namespace (not even define). The problem is located in Aries Blueprint.


I gonna deal with Guillaume.

We can:
0. leave Karaf 4.0.5 as it is, but I think it's not acceptable:

blueprint is used by lot of users, and we can't allow a release

without a

working blueprint layer.

1. downgrade Karaf to Aries Blueprint 1.5.x: unfortunately, we won't

benefit about some improvements implemented in blueprint

2. revert or fix the change in Aries: it means we would need a new

Aries Blueprint core release, so 3 days vote, meaning that we won't be

able

to release Karaf before roughly 6 days.


My preference is on 2 even if it delays Karaf 4.0.5 release.

Thoughts ?

I will add an Integration Test on blueprint to avoid such problem in

the future.


Regards
JB

On 04/06/2016 08:14 AM, Cristiano Costantini wrote:

Hi JB and Krzysztof,

I don't know if this can be have any impact on the problem you have
reported, but about 1 month ago I got into an issue with camel XSD

schemas

for Camel namespaces, and the issue is that the URL of the latest

XSD,

http://camel.apache.org/schema/blueprint/camel-blueprint.xsd
is not from latest version 2.16.2, but it is from version 2.15.0

While upgrading to ServiceMix 7, I had to change manually the XML

to

xsi:schemaLocation="http://camel.apache.org/schema/spring

http://camel

.apache.org/schema/spring/camel-spring-2.16.1.xsd" in order to

make

it work

(note also that SMX 7 is based on camel 2.16.2, but this XSD is not
available)

But in fact the only problem I had was that Eclipse validation and
autocompletion of the XML files was not working properly.

if this is not relevant, please ignore this message ;-)

Cristiano




Il giorno mar 5 apr 2016 alle ore 22:19 Jean-Baptiste Onofré <
j...@nanthrax.net> ha scritto:


I tried with Camel 2.16.2, camel-blueprint, and simple route in
blueprint: it works fine.

I tried with your XML, and actually I have the same problem.

It sounds like a Aries Blueprint bug. Let me try if I downgrade to
blueprint 1.5.x and check the change in aries blueprint (I know
Guillaume did some enhancements & changes).

Honestly, I would consider as a blocker for the release, so, I

will

probably revert my vote to -1. I just want to make more tests.

Regards
JB

On 04/05/2016 09:46 PM, Krzysztof Sobkowiak wrote:

Hi

I tried to upgrade ServiceMix to the new version and have several

problems with blueprint.


2016-04-05 21:42:05,485 | INFO  | pool-46-thread-1 |

FeaturesServiceImpl  | 9 -

org.apache.karaf.features.core

-

4.0.5 |   cxf-wsn-receive/7.0.0.SNAPSHOT

2016-04-05 21:42:05,567 | ERROR | pool-46-thread-1 |

BlueprintContainerImpl   | 28 -

org.apache.aries.blueprint.core -

1.6.0 | Unable to start blueprint container for bundle
cxf-wsn-receive/7.0.0.SNAPSHOT

org.xml.sax.SAXParseException: src-import.3.1: The namespace

attribute, '

http://aries.apache.org/blueprint/xmlns/blueprint-ext/v1.0.0', of

an

 element information item must be identical to the

targetNamespace

attribute, 'http://camel.apache.org/schema/blueprint', of the

imported

document.

   at







org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(Unknown

Source)[:]

   at org.apache.xerces.util.ErrorHandlerWrapper.error(Unknown

Source)[:]

 

Re: [VOTE] Apache Karaf 4.0.5 release (take 2)

[Grzegorz Grzybek]

Hello

OK, I have a fix and here's an explanation.
First (ARIES-1290), following Java relationship of
org.apache.aries.blueprint.compendium.cm.CmPropertyPlaceholder and
org.apache.aries.blueprint.ext.PropertyPlaceholder I wanted to reflect this
fact at XSD level, so we could mix cm and ext namespace elements.
Then (ARIES-1503) there was a fix for situations, where XSDs were read for
CmNamespaceHandler before ExtNamespaceHandler managed to register itself in
NamespaceRegistryImpl.

And finally (now) the fix (after adding
org.apache.aries.blueprint.NamespaceHandler2#mayResolve() method) is more
conservative - we can resolve not registered namespaces using those
handlers that return true in their implementation of
org.apache.aries.blueprint.NamespaceHandler2#mayResolve() - and there'll be
(now) only one such handler - for cm namespace.

I'm preparing PR.

best regards and I'm very sorry for delay of the release!
Grzegorz Grzybek

2016-04-06 11:50 GMT+02:00 Kevin Carr :

> I agree option 2.  Best to delay and fix.
>
> On Wed, Apr 6, 2016, 4:49 AM Achim Nierbeck 
> wrote:
>
> > yeah option 2 sounds best, so here's my -1 on this release ... a major
> bug
> > shouldn't go into any production, especially if we know of it.
> >
> > regards, Achim
> >
> >
> > 2016-04-06 9:47 GMT+02:00 Markus Rathgeb :
> >
> > > +1 for option 2
> > >
> > > 2016-04-06 8:48 GMT+02:00 Sobkowiak Krzysztof <
> krzys.sobkow...@gmail.com
> > >:
> > > > I prefer the option 2 as well
> > > >
> > > > Regards
> > > > Krzysztof
> > > >
> > > > On 06.04.2016 08:39, Jean-Baptiste Onofré wrote:
> > > >> Hi Cristiano,
> > > >>
> > > >> I don't think it's related, as the issue in about blueprint-ext
> > > namespace (not even define). The problem is located in Aries Blueprint.
> > > >>
> > > >> I gonna deal with Guillaume.
> > > >>
> > > >> We can:
> > > >> 0. leave Karaf 4.0.5 as it is, but I think it's not acceptable:
> > > blueprint is used by lot of users, and we can't allow a release
> without a
> > > working blueprint layer.
> > > >> 1. downgrade Karaf to Aries Blueprint 1.5.x: unfortunately, we won't
> > > benefit about some improvements implemented in blueprint
> > > >> 2. revert or fix the change in Aries: it means we would need a new
> > > Aries Blueprint core release, so 3 days vote, meaning that we won't be
> > able
> > > to release Karaf before roughly 6 days.
> > > >>
> > > >> My preference is on 2 even if it delays Karaf 4.0.5 release.
> > > >>
> > > >> Thoughts ?
> > > >>
> > > >> I will add an Integration Test on blueprint to avoid such problem in
> > > the future.
> > > >>
> > > >> Regards
> > > >> JB
> > > >>
> > > >> On 04/06/2016 08:14 AM, Cristiano Costantini wrote:
> > > >>> Hi JB and Krzysztof,
> > > >>>
> > > >>> I don't know if this can be have any impact on the problem you have
> > > >>> reported, but about 1 month ago I got into an issue with camel XSD
> > > schemas
> > > >>> for Camel namespaces, and the issue is that the URL of the latest
> > XSD,
> > > >>> http://camel.apache.org/schema/blueprint/camel-blueprint.xsd
> > > >>> is not from latest version 2.16.2, but it is from version 2.15.0
> > > >>>
> > > >>> While upgrading to ServiceMix 7, I had to change manually the XML
> to
> > > >>> xsi:schemaLocation="http://camel.apache.org/schema/spring
> > http://camel
> > > >>> .apache.org/schema/spring/camel-spring-2.16.1.xsd" in order to
> make
> > > it work
> > > >>> (note also that SMX 7 is based on camel 2.16.2, but this XSD is not
> > > >>> available)
> > > >>>
> > > >>> But in fact the only problem I had was that Eclipse validation and
> > > >>> autocompletion of the XML files was not working properly.
> > > >>>
> > > >>> if this is not relevant, please ignore this message ;-)
> > > >>>
> > > >>> Cristiano
> > > >>>
> > > >>>
> > > >>>
> > > >>>
> > > >>> Il giorno mar 5 apr 2016 alle ore 22:19 Jean-Baptiste Onofré <
> > > >>> j...@nanthrax.net> ha scritto:
> > > >>>
> > >  I tried with Camel 2.16.2, camel-blueprint, and simple route in
> > >  blueprint: it works fine.
> > > 
> > >  I tried with your XML, and actually I have the same problem.
> > > 
> > >  It sounds like a Aries Blueprint bug. Let me try if I downgrade to
> > >  blueprint 1.5.x and check the change in aries blueprint (I know
> > >  Guillaume did some enhancements & changes).
> > > 
> > >  Honestly, I would consider as a blocker for the release, so, I
> will
> > >  probably revert my vote to -1. I just want to make more tests.
> > > 
> > >  Regards
> > >  JB
> > > 
> > >  On 04/05/2016 09:46 PM, Krzysztof Sobkowiak wrote:
> > > > Hi
> > > >
> > > > I tried to upgrade ServiceMix to the new version and have several
> > >  problems with blueprint.
> > > >
> > > > 2016-04-05 21:42:05,485 | INFO  | pool-46-thread-1 |
> > >  FeaturesServiceImpl  | 9 -
> > org.apache.karaf.features.core
> > > -
> > >  4.0.5 |   cxf-wsn-receive/7.0.0.SNAPSHOT
> > > > 20

Re: [VOTE] Apache Karaf 4.0.5 release (take 2)

[Kevin Carr]

I agree option 2.  Best to delay and fix.

On Wed, Apr 6, 2016, 4:49 AM Achim Nierbeck  wrote:

> yeah option 2 sounds best, so here's my -1 on this release ... a major bug
> shouldn't go into any production, especially if we know of it.
>
> regards, Achim
>
>
> 2016-04-06 9:47 GMT+02:00 Markus Rathgeb :
>
> > +1 for option 2
> >
> > 2016-04-06 8:48 GMT+02:00 Sobkowiak Krzysztof  >:
> > > I prefer the option 2 as well
> > >
> > > Regards
> > > Krzysztof
> > >
> > > On 06.04.2016 08:39, Jean-Baptiste Onofré wrote:
> > >> Hi Cristiano,
> > >>
> > >> I don't think it's related, as the issue in about blueprint-ext
> > namespace (not even define). The problem is located in Aries Blueprint.
> > >>
> > >> I gonna deal with Guillaume.
> > >>
> > >> We can:
> > >> 0. leave Karaf 4.0.5 as it is, but I think it's not acceptable:
> > blueprint is used by lot of users, and we can't allow a release without a
> > working blueprint layer.
> > >> 1. downgrade Karaf to Aries Blueprint 1.5.x: unfortunately, we won't
> > benefit about some improvements implemented in blueprint
> > >> 2. revert or fix the change in Aries: it means we would need a new
> > Aries Blueprint core release, so 3 days vote, meaning that we won't be
> able
> > to release Karaf before roughly 6 days.
> > >>
> > >> My preference is on 2 even if it delays Karaf 4.0.5 release.
> > >>
> > >> Thoughts ?
> > >>
> > >> I will add an Integration Test on blueprint to avoid such problem in
> > the future.
> > >>
> > >> Regards
> > >> JB
> > >>
> > >> On 04/06/2016 08:14 AM, Cristiano Costantini wrote:
> > >>> Hi JB and Krzysztof,
> > >>>
> > >>> I don't know if this can be have any impact on the problem you have
> > >>> reported, but about 1 month ago I got into an issue with camel XSD
> > schemas
> > >>> for Camel namespaces, and the issue is that the URL of the latest
> XSD,
> > >>> http://camel.apache.org/schema/blueprint/camel-blueprint.xsd
> > >>> is not from latest version 2.16.2, but it is from version 2.15.0
> > >>>
> > >>> While upgrading to ServiceMix 7, I had to change manually the XML to
> > >>> xsi:schemaLocation="http://camel.apache.org/schema/spring
> http://camel
> > >>> .apache.org/schema/spring/camel-spring-2.16.1.xsd" in order to make
> > it work
> > >>> (note also that SMX 7 is based on camel 2.16.2, but this XSD is not
> > >>> available)
> > >>>
> > >>> But in fact the only problem I had was that Eclipse validation and
> > >>> autocompletion of the XML files was not working properly.
> > >>>
> > >>> if this is not relevant, please ignore this message ;-)
> > >>>
> > >>> Cristiano
> > >>>
> > >>>
> > >>>
> > >>>
> > >>> Il giorno mar 5 apr 2016 alle ore 22:19 Jean-Baptiste Onofré <
> > >>> j...@nanthrax.net> ha scritto:
> > >>>
> >  I tried with Camel 2.16.2, camel-blueprint, and simple route in
> >  blueprint: it works fine.
> > 
> >  I tried with your XML, and actually I have the same problem.
> > 
> >  It sounds like a Aries Blueprint bug. Let me try if I downgrade to
> >  blueprint 1.5.x and check the change in aries blueprint (I know
> >  Guillaume did some enhancements & changes).
> > 
> >  Honestly, I would consider as a blocker for the release, so, I will
> >  probably revert my vote to -1. I just want to make more tests.
> > 
> >  Regards
> >  JB
> > 
> >  On 04/05/2016 09:46 PM, Krzysztof Sobkowiak wrote:
> > > Hi
> > >
> > > I tried to upgrade ServiceMix to the new version and have several
> >  problems with blueprint.
> > >
> > > 2016-04-05 21:42:05,485 | INFO  | pool-46-thread-1 |
> >  FeaturesServiceImpl  | 9 -
> org.apache.karaf.features.core
> > -
> >  4.0.5 |   cxf-wsn-receive/7.0.0.SNAPSHOT
> > > 2016-04-05 21:42:05,567 | ERROR | pool-46-thread-1 |
> >  BlueprintContainerImpl   | 28 -
> > org.apache.aries.blueprint.core -
> >  1.6.0 | Unable to start blueprint container for bundle
> >  cxf-wsn-receive/7.0.0.SNAPSHOT
> > > org.xml.sax.SAXParseException: src-import.3.1: The namespace
> > attribute, '
> >  http://aries.apache.org/blueprint/xmlns/blueprint-ext/v1.0.0', of
> an
> >   element information item must be identical to the
> > targetNamespace
> >  attribute, 'http://camel.apache.org/schema/blueprint', of the
> > imported
> >  document.
> > >   at
> > 
> >
> org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(Unknown
> >  Source)[:]
> > >   at org.apache.xerces.util.ErrorHandlerWrapper.error(Unknown
> >  Source)[:]
> > >   at
> org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown
> >  Source)[:]
> > >   at
> > 
> > org.apache.xerces.impl.xs.traversers.XSDHandler.reportSchemaError(Unknown
> >  Source)[:]
> > >   at
> > 
> > org.apache.xerces.impl.xs.traversers.XSDHandler.reportSchemaError(Unknown
> >  Source)[:]
> > >   at
> > 
> org.apache.xerces.impl.xs.traversers.XSD

Re: [VOTE] Apache Karaf 4.0.5 release (take 2)

[Achim Nierbeck]

yeah option 2 sounds best, so here's my -1 on this release ... a major bug
shouldn't go into any production, especially if we know of it.

regards, Achim


2016-04-06 9:47 GMT+02:00 Markus Rathgeb :

> +1 for option 2
>
> 2016-04-06 8:48 GMT+02:00 Sobkowiak Krzysztof :
> > I prefer the option 2 as well
> >
> > Regards
> > Krzysztof
> >
> > On 06.04.2016 08:39, Jean-Baptiste Onofré wrote:
> >> Hi Cristiano,
> >>
> >> I don't think it's related, as the issue in about blueprint-ext
> namespace (not even define). The problem is located in Aries Blueprint.
> >>
> >> I gonna deal with Guillaume.
> >>
> >> We can:
> >> 0. leave Karaf 4.0.5 as it is, but I think it's not acceptable:
> blueprint is used by lot of users, and we can't allow a release without a
> working blueprint layer.
> >> 1. downgrade Karaf to Aries Blueprint 1.5.x: unfortunately, we won't
> benefit about some improvements implemented in blueprint
> >> 2. revert or fix the change in Aries: it means we would need a new
> Aries Blueprint core release, so 3 days vote, meaning that we won't be able
> to release Karaf before roughly 6 days.
> >>
> >> My preference is on 2 even if it delays Karaf 4.0.5 release.
> >>
> >> Thoughts ?
> >>
> >> I will add an Integration Test on blueprint to avoid such problem in
> the future.
> >>
> >> Regards
> >> JB
> >>
> >> On 04/06/2016 08:14 AM, Cristiano Costantini wrote:
> >>> Hi JB and Krzysztof,
> >>>
> >>> I don't know if this can be have any impact on the problem you have
> >>> reported, but about 1 month ago I got into an issue with camel XSD
> schemas
> >>> for Camel namespaces, and the issue is that the URL of the latest XSD,
> >>> http://camel.apache.org/schema/blueprint/camel-blueprint.xsd
> >>> is not from latest version 2.16.2, but it is from version 2.15.0
> >>>
> >>> While upgrading to ServiceMix 7, I had to change manually the XML to
> >>> xsi:schemaLocation="http://camel.apache.org/schema/spring http://camel
> >>> .apache.org/schema/spring/camel-spring-2.16.1.xsd" in order to make
> it work
> >>> (note also that SMX 7 is based on camel 2.16.2, but this XSD is not
> >>> available)
> >>>
> >>> But in fact the only problem I had was that Eclipse validation and
> >>> autocompletion of the XML files was not working properly.
> >>>
> >>> if this is not relevant, please ignore this message ;-)
> >>>
> >>> Cristiano
> >>>
> >>>
> >>>
> >>>
> >>> Il giorno mar 5 apr 2016 alle ore 22:19 Jean-Baptiste Onofré <
> >>> j...@nanthrax.net> ha scritto:
> >>>
>  I tried with Camel 2.16.2, camel-blueprint, and simple route in
>  blueprint: it works fine.
> 
>  I tried with your XML, and actually I have the same problem.
> 
>  It sounds like a Aries Blueprint bug. Let me try if I downgrade to
>  blueprint 1.5.x and check the change in aries blueprint (I know
>  Guillaume did some enhancements & changes).
> 
>  Honestly, I would consider as a blocker for the release, so, I will
>  probably revert my vote to -1. I just want to make more tests.
> 
>  Regards
>  JB
> 
>  On 04/05/2016 09:46 PM, Krzysztof Sobkowiak wrote:
> > Hi
> >
> > I tried to upgrade ServiceMix to the new version and have several
>  problems with blueprint.
> >
> > 2016-04-05 21:42:05,485 | INFO  | pool-46-thread-1 |
>  FeaturesServiceImpl  | 9 - org.apache.karaf.features.core
> -
>  4.0.5 |   cxf-wsn-receive/7.0.0.SNAPSHOT
> > 2016-04-05 21:42:05,567 | ERROR | pool-46-thread-1 |
>  BlueprintContainerImpl   | 28 -
> org.apache.aries.blueprint.core -
>  1.6.0 | Unable to start blueprint container for bundle
>  cxf-wsn-receive/7.0.0.SNAPSHOT
> > org.xml.sax.SAXParseException: src-import.3.1: The namespace
> attribute, '
>  http://aries.apache.org/blueprint/xmlns/blueprint-ext/v1.0.0', of an
>   element information item must be identical to the
> targetNamespace
>  attribute, 'http://camel.apache.org/schema/blueprint', of the
> imported
>  document.
> >   at
> 
> org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(Unknown
>  Source)[:]
> >   at org.apache.xerces.util.ErrorHandlerWrapper.error(Unknown
>  Source)[:]
> >   at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown
>  Source)[:]
> >   at
> 
> org.apache.xerces.impl.xs.traversers.XSDHandler.reportSchemaError(Unknown
>  Source)[:]
> >   at
> 
> org.apache.xerces.impl.xs.traversers.XSDHandler.reportSchemaError(Unknown
>  Source)[:]
> >   at
>  org.apache.xerces.impl.xs.traversers.XSDHandler.constructTrees(Unknown
>  Source)[:]
> >   at
>  org.apache.xerces.impl.xs.traversers.XSDHandler.constructTrees(Unknown
>  Source)[:]
> >   at
>  org.apache.xerces.impl.xs.traversers.XSDHandler.parseSchema(Unknown
>  Source)[:]
> >
> > or
> >
> >
> > 2016-04-05 21:31:36,969 | ERROR | pool-42-thread-1 |
> 

Re: [VOTE] Apache Karaf 4.0.5 release (take 2)

[Markus Rathgeb]

+1 for option 2

2016-04-06 8:48 GMT+02:00 Sobkowiak Krzysztof :
> I prefer the option 2 as well
>
> Regards
> Krzysztof
>
> On 06.04.2016 08:39, Jean-Baptiste Onofré wrote:
>> Hi Cristiano,
>>
>> I don't think it's related, as the issue in about blueprint-ext namespace 
>> (not even define). The problem is located in Aries Blueprint.
>>
>> I gonna deal with Guillaume.
>>
>> We can:
>> 0. leave Karaf 4.0.5 as it is, but I think it's not acceptable: blueprint is 
>> used by lot of users, and we can't allow a release without a working 
>> blueprint layer.
>> 1. downgrade Karaf to Aries Blueprint 1.5.x: unfortunately, we won't benefit 
>> about some improvements implemented in blueprint
>> 2. revert or fix the change in Aries: it means we would need a new Aries 
>> Blueprint core release, so 3 days vote, meaning that we won't be able to 
>> release Karaf before roughly 6 days.
>>
>> My preference is on 2 even if it delays Karaf 4.0.5 release.
>>
>> Thoughts ?
>>
>> I will add an Integration Test on blueprint to avoid such problem in the 
>> future.
>>
>> Regards
>> JB
>>
>> On 04/06/2016 08:14 AM, Cristiano Costantini wrote:
>>> Hi JB and Krzysztof,
>>>
>>> I don't know if this can be have any impact on the problem you have
>>> reported, but about 1 month ago I got into an issue with camel XSD schemas
>>> for Camel namespaces, and the issue is that the URL of the latest XSD,
>>> http://camel.apache.org/schema/blueprint/camel-blueprint.xsd
>>> is not from latest version 2.16.2, but it is from version 2.15.0
>>>
>>> While upgrading to ServiceMix 7, I had to change manually the XML to
>>> xsi:schemaLocation="http://camel.apache.org/schema/spring http://camel
>>> .apache.org/schema/spring/camel-spring-2.16.1.xsd" in order to make it work
>>> (note also that SMX 7 is based on camel 2.16.2, but this XSD is not
>>> available)
>>>
>>> But in fact the only problem I had was that Eclipse validation and
>>> autocompletion of the XML files was not working properly.
>>>
>>> if this is not relevant, please ignore this message ;-)
>>>
>>> Cristiano
>>>
>>>
>>>
>>>
>>> Il giorno mar 5 apr 2016 alle ore 22:19 Jean-Baptiste Onofré <
>>> j...@nanthrax.net> ha scritto:
>>>
 I tried with Camel 2.16.2, camel-blueprint, and simple route in
 blueprint: it works fine.

 I tried with your XML, and actually I have the same problem.

 It sounds like a Aries Blueprint bug. Let me try if I downgrade to
 blueprint 1.5.x and check the change in aries blueprint (I know
 Guillaume did some enhancements & changes).

 Honestly, I would consider as a blocker for the release, so, I will
 probably revert my vote to -1. I just want to make more tests.

 Regards
 JB

 On 04/05/2016 09:46 PM, Krzysztof Sobkowiak wrote:
> Hi
>
> I tried to upgrade ServiceMix to the new version and have several
 problems with blueprint.
>
> 2016-04-05 21:42:05,485 | INFO  | pool-46-thread-1 |
 FeaturesServiceImpl  | 9 - org.apache.karaf.features.core -
 4.0.5 |   cxf-wsn-receive/7.0.0.SNAPSHOT
> 2016-04-05 21:42:05,567 | ERROR | pool-46-thread-1 |
 BlueprintContainerImpl   | 28 - org.apache.aries.blueprint.core -
 1.6.0 | Unable to start blueprint container for bundle
 cxf-wsn-receive/7.0.0.SNAPSHOT
> org.xml.sax.SAXParseException: src-import.3.1: The namespace attribute, '
 http://aries.apache.org/blueprint/xmlns/blueprint-ext/v1.0.0', of an
  element information item must be identical to the targetNamespace
 attribute, 'http://camel.apache.org/schema/blueprint', of the imported
 document.
>   at
 org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(Unknown
 Source)[:]
>   at org.apache.xerces.util.ErrorHandlerWrapper.error(Unknown
 Source)[:]
>   at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown
 Source)[:]
>   at
 org.apache.xerces.impl.xs.traversers.XSDHandler.reportSchemaError(Unknown
 Source)[:]
>   at
 org.apache.xerces.impl.xs.traversers.XSDHandler.reportSchemaError(Unknown
 Source)[:]
>   at
 org.apache.xerces.impl.xs.traversers.XSDHandler.constructTrees(Unknown
 Source)[:]
>   at
 org.apache.xerces.impl.xs.traversers.XSDHandler.constructTrees(Unknown
 Source)[:]
>   at
 org.apache.xerces.impl.xs.traversers.XSDHandler.parseSchema(Unknown
 Source)[:]
>
> or
>
>
> 2016-04-05 21:31:36,969 | ERROR | pool-42-thread-1 |
 BlueprintContainerImpl   | 28 - org.apache.aries.blueprint.core -
 1.6.0 | Unable to start blueprint container for bundle
 drools-camel-cxf-server/7.0.0.SNAPSHOT
> org.xml.sax.SAXParseException: src-import.3.1: The namespace attribute, '
 http://cxf.apache.org/configuration/beans', of an  element
 information item must be identical to the targetNamespace attribute, '
 http://camel.apache.org/schema/bl

Re: [VOTE] Apache Karaf 4.0.5 release (take 2)

[Sobkowiak Krzysztof]

I prefer the option 2 as well

Regards
Krzysztof

On 06.04.2016 08:39, Jean-Baptiste Onofré wrote:
> Hi Cristiano,
>
> I don't think it's related, as the issue in about blueprint-ext namespace 
> (not even define). The problem is located in Aries Blueprint.
>
> I gonna deal with Guillaume.
>
> We can:
> 0. leave Karaf 4.0.5 as it is, but I think it's not acceptable: blueprint is 
> used by lot of users, and we can't allow a release without a working 
> blueprint layer.
> 1. downgrade Karaf to Aries Blueprint 1.5.x: unfortunately, we won't benefit 
> about some improvements implemented in blueprint
> 2. revert or fix the change in Aries: it means we would need a new Aries 
> Blueprint core release, so 3 days vote, meaning that we won't be able to 
> release Karaf before roughly 6 days.
>
> My preference is on 2 even if it delays Karaf 4.0.5 release.
>
> Thoughts ?
>
> I will add an Integration Test on blueprint to avoid such problem in the 
> future.
>
> Regards
> JB
>
> On 04/06/2016 08:14 AM, Cristiano Costantini wrote:
>> Hi JB and Krzysztof,
>>
>> I don't know if this can be have any impact on the problem you have
>> reported, but about 1 month ago I got into an issue with camel XSD schemas
>> for Camel namespaces, and the issue is that the URL of the latest XSD,
>> http://camel.apache.org/schema/blueprint/camel-blueprint.xsd
>> is not from latest version 2.16.2, but it is from version 2.15.0
>>
>> While upgrading to ServiceMix 7, I had to change manually the XML to
>> xsi:schemaLocation="http://camel.apache.org/schema/spring http://camel
>> .apache.org/schema/spring/camel-spring-2.16.1.xsd" in order to make it work
>> (note also that SMX 7 is based on camel 2.16.2, but this XSD is not
>> available)
>>
>> But in fact the only problem I had was that Eclipse validation and
>> autocompletion of the XML files was not working properly.
>>
>> if this is not relevant, please ignore this message ;-)
>>
>> Cristiano
>>
>>
>>
>>
>> Il giorno mar 5 apr 2016 alle ore 22:19 Jean-Baptiste Onofré <
>> j...@nanthrax.net> ha scritto:
>>
>>> I tried with Camel 2.16.2, camel-blueprint, and simple route in
>>> blueprint: it works fine.
>>>
>>> I tried with your XML, and actually I have the same problem.
>>>
>>> It sounds like a Aries Blueprint bug. Let me try if I downgrade to
>>> blueprint 1.5.x and check the change in aries blueprint (I know
>>> Guillaume did some enhancements & changes).
>>>
>>> Honestly, I would consider as a blocker for the release, so, I will
>>> probably revert my vote to -1. I just want to make more tests.
>>>
>>> Regards
>>> JB
>>>
>>> On 04/05/2016 09:46 PM, Krzysztof Sobkowiak wrote:
 Hi

 I tried to upgrade ServiceMix to the new version and have several
>>> problems with blueprint.

 2016-04-05 21:42:05,485 | INFO  | pool-46-thread-1 |
>>> FeaturesServiceImpl  | 9 - org.apache.karaf.features.core -
>>> 4.0.5 |   cxf-wsn-receive/7.0.0.SNAPSHOT
 2016-04-05 21:42:05,567 | ERROR | pool-46-thread-1 |
>>> BlueprintContainerImpl   | 28 - org.apache.aries.blueprint.core -
>>> 1.6.0 | Unable to start blueprint container for bundle
>>> cxf-wsn-receive/7.0.0.SNAPSHOT
 org.xml.sax.SAXParseException: src-import.3.1: The namespace attribute, '
>>> http://aries.apache.org/blueprint/xmlns/blueprint-ext/v1.0.0', of an
>>>  element information item must be identical to the targetNamespace
>>> attribute, 'http://camel.apache.org/schema/blueprint', of the imported
>>> document.
   at
>>> org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(Unknown
>>> Source)[:]
   at org.apache.xerces.util.ErrorHandlerWrapper.error(Unknown
>>> Source)[:]
   at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown
>>> Source)[:]
   at
>>> org.apache.xerces.impl.xs.traversers.XSDHandler.reportSchemaError(Unknown
>>> Source)[:]
   at
>>> org.apache.xerces.impl.xs.traversers.XSDHandler.reportSchemaError(Unknown
>>> Source)[:]
   at
>>> org.apache.xerces.impl.xs.traversers.XSDHandler.constructTrees(Unknown
>>> Source)[:]
   at
>>> org.apache.xerces.impl.xs.traversers.XSDHandler.constructTrees(Unknown
>>> Source)[:]
   at
>>> org.apache.xerces.impl.xs.traversers.XSDHandler.parseSchema(Unknown
>>> Source)[:]

 or


 2016-04-05 21:31:36,969 | ERROR | pool-42-thread-1 |
>>> BlueprintContainerImpl   | 28 - org.apache.aries.blueprint.core -
>>> 1.6.0 | Unable to start blueprint container for bundle
>>> drools-camel-cxf-server/7.0.0.SNAPSHOT
 org.xml.sax.SAXParseException: src-import.3.1: The namespace attribute, '
>>> http://cxf.apache.org/configuration/beans', of an  element
>>> information item must be identical to the targetNamespace attribute, '
>>> http://camel.apache.org/schema/blueprint', of the imported document.
   at
>>> org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(Unknown
>>> Source)[:]
   at org.apache.xerces.util.ErrorHandlerWrap

Re: [VOTE] Apache Karaf 4.0.5 release (take 2)

[Sobkowiak Krzysztof]

Hi Cristiano

This problem happens on Karaf 4.0.5 with both 2.16.2 and 2.17.0 (I didn't test 
it with 2.15.x) but doesn't happen on Karaf 4.0.4, so I think it's rather 
caused by changes in Karaf (in this case Aries).
But I have also mentioned the validation problems in IDE last days, so I think, 
the xsd file in Camel should be corrected as well.

Regards
Krzysztof

On 06.04.2016 08:14, Cristiano Costantini wrote:
> Hi JB and Krzysztof,
>
> I don't know if this can be have any impact on the problem you have
> reported, but about 1 month ago I got into an issue with camel XSD schemas
> for Camel namespaces, and the issue is that the URL of the latest XSD,
> http://camel.apache.org/schema/blueprint/camel-blueprint.xsd
> is not from latest version 2.16.2, but it is from version 2.15.0
>
> While upgrading to ServiceMix 7, I had to change manually the XML to
> xsi:schemaLocation="http://camel.apache.org/schema/spring http://camel
> .apache.org/schema/spring/camel-spring-2.16.1.xsd" in order to make it work
> (note also that SMX 7 is based on camel 2.16.2, but this XSD is not
> available)
>
> But in fact the only problem I had was that Eclipse validation and
> autocompletion of the XML files was not working properly.
>
> if this is not relevant, please ignore this message ;-)
>
> Cristiano
>
>
>
>
> Il giorno mar 5 apr 2016 alle ore 22:19 Jean-Baptiste Onofré <
> j...@nanthrax.net> ha scritto:
>
>> I tried with Camel 2.16.2, camel-blueprint, and simple route in
>> blueprint: it works fine.
>>
>> I tried with your XML, and actually I have the same problem.
>>
>> It sounds like a Aries Blueprint bug. Let me try if I downgrade to
>> blueprint 1.5.x and check the change in aries blueprint (I know
>> Guillaume did some enhancements & changes).
>>
>> Honestly, I would consider as a blocker for the release, so, I will
>> probably revert my vote to -1. I just want to make more tests.
>>
>> Regards
>> JB
>>
>> On 04/05/2016 09:46 PM, Krzysztof Sobkowiak wrote:
>>> Hi
>>>
>>> I tried to upgrade ServiceMix to the new version and have several
>> problems with blueprint.
>>> 2016-04-05 21:42:05,485 | INFO  | pool-46-thread-1 |
>> FeaturesServiceImpl  | 9 - org.apache.karaf.features.core -
>> 4.0.5 |   cxf-wsn-receive/7.0.0.SNAPSHOT
>>> 2016-04-05 21:42:05,567 | ERROR | pool-46-thread-1 |
>> BlueprintContainerImpl   | 28 - org.apache.aries.blueprint.core -
>> 1.6.0 | Unable to start blueprint container for bundle
>> cxf-wsn-receive/7.0.0.SNAPSHOT
>>> org.xml.sax.SAXParseException: src-import.3.1: The namespace attribute, '
>> http://aries.apache.org/blueprint/xmlns/blueprint-ext/v1.0.0', of an
>>  element information item must be identical to the targetNamespace
>> attribute, 'http://camel.apache.org/schema/blueprint', of the imported
>> document.
>>>  at
>> org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(Unknown
>> Source)[:]
>>>  at org.apache.xerces.util.ErrorHandlerWrapper.error(Unknown
>> Source)[:]
>>>  at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown
>> Source)[:]
>>>  at
>> org.apache.xerces.impl.xs.traversers.XSDHandler.reportSchemaError(Unknown
>> Source)[:]
>>>  at
>> org.apache.xerces.impl.xs.traversers.XSDHandler.reportSchemaError(Unknown
>> Source)[:]
>>>  at
>> org.apache.xerces.impl.xs.traversers.XSDHandler.constructTrees(Unknown
>> Source)[:]
>>>  at
>> org.apache.xerces.impl.xs.traversers.XSDHandler.constructTrees(Unknown
>> Source)[:]
>>>  at
>> org.apache.xerces.impl.xs.traversers.XSDHandler.parseSchema(Unknown
>> Source)[:]
>>> or
>>>
>>>
>>> 2016-04-05 21:31:36,969 | ERROR | pool-42-thread-1 |
>> BlueprintContainerImpl   | 28 - org.apache.aries.blueprint.core -
>> 1.6.0 | Unable to start blueprint container for bundle
>> drools-camel-cxf-server/7.0.0.SNAPSHOT
>>> org.xml.sax.SAXParseException: src-import.3.1: The namespace attribute, '
>> http://cxf.apache.org/configuration/beans', of an  element
>> information item must be identical to the targetNamespace attribute, '
>> http://camel.apache.org/schema/blueprint', of the imported document.
>>>  at
>> org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(Unknown
>> Source)[:]
>>>  at org.apache.xerces.util.ErrorHandlerWrapper.error(Unknown
>> Source)[:]
>>>  at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown
>> Source)[:]
>>>  at
>> org.apache.xerces.impl.xs.traversers.XSDHandler.reportSchemaError(Unknown
>> Source)[:]
>>>  at
>> org.apache.xerces.impl.xs.traversers.XSDHandler.reportSchemaError(Unknown
>> Source)[:]
>>>  at
>> org.apache.xerces.impl.xs.traversers.XSDHandler.constructTrees(Unknown
>> Source)[:]
>>>  at
>> org.apache.xerces.impl.xs.traversers.XSDHandler.constructTrees(Unknown
>> Source)[:]
>>>
>>>
>>> Here my try to reproduce one of them in K405
>>>
>>> Assume you have following simple blueprint (I have reduced one of the
>> blueprints from the examples)
>>> http://www.osgi.org/xmlns/blueprint/v1

Re: [VOTE] Apache Karaf 4.0.5 release (take 2)

[Morgan Hautman]

Hi,

My preference would also go to option 2.
If we can fix it , it would be beneficial for everyone.

Regards,
Morgan

2016-04-06 8:39 GMT+02:00 Jean-Baptiste Onofré :

> Hi Cristiano,
>
> I don't think it's related, as the issue in about blueprint-ext namespace
> (not even define). The problem is located in Aries Blueprint.
>
> I gonna deal with Guillaume.
>
> We can:
> 0. leave Karaf 4.0.5 as it is, but I think it's not acceptable: blueprint
> is used by lot of users, and we can't allow a release without a working
> blueprint layer.
> 1. downgrade Karaf to Aries Blueprint 1.5.x: unfortunately, we won't
> benefit about some improvements implemented in blueprint
> 2. revert or fix the change in Aries: it means we would need a new Aries
> Blueprint core release, so 3 days vote, meaning that we won't be able to
> release Karaf before roughly 6 days.
>
> My preference is on 2 even if it delays Karaf 4.0.5 release.
>
> Thoughts ?
>
> I will add an Integration Test on blueprint to avoid such problem in the
> future.
>
> Regards
> JB
>
>
> On 04/06/2016 08:14 AM, Cristiano Costantini wrote:
>
>> Hi JB and Krzysztof,
>>
>> I don't know if this can be have any impact on the problem you have
>> reported, but about 1 month ago I got into an issue with camel XSD schemas
>> for Camel namespaces, and the issue is that the URL of the latest XSD,
>> http://camel.apache.org/schema/blueprint/camel-blueprint.xsd
>> is not from latest version 2.16.2, but it is from version 2.15.0
>>
>> While upgrading to ServiceMix 7, I had to change manually the XML to
>> xsi:schemaLocation="http://camel.apache.org/schema/spring http://camel
>> .apache.org/schema/spring/camel-spring-2.16.1.xsd" in order to make it
>> work
>> (note also that SMX 7 is based on camel 2.16.2, but this XSD is not
>> available)
>>
>> But in fact the only problem I had was that Eclipse validation and
>> autocompletion of the XML files was not working properly.
>>
>> if this is not relevant, please ignore this message ;-)
>>
>> Cristiano
>>
>>
>>
>>
>> Il giorno mar 5 apr 2016 alle ore 22:19 Jean-Baptiste Onofré <
>> j...@nanthrax.net> ha scritto:
>>
>> I tried with Camel 2.16.2, camel-blueprint, and simple route in
>>> blueprint: it works fine.
>>>
>>> I tried with your XML, and actually I have the same problem.
>>>
>>> It sounds like a Aries Blueprint bug. Let me try if I downgrade to
>>> blueprint 1.5.x and check the change in aries blueprint (I know
>>> Guillaume did some enhancements & changes).
>>>
>>> Honestly, I would consider as a blocker for the release, so, I will
>>> probably revert my vote to -1. I just want to make more tests.
>>>
>>> Regards
>>> JB
>>>
>>> On 04/05/2016 09:46 PM, Krzysztof Sobkowiak wrote:
>>>
 Hi

 I tried to upgrade ServiceMix to the new version and have several

>>> problems with blueprint.
>>>

 2016-04-05 21:42:05,485 | INFO  | pool-46-thread-1 |

>>> FeaturesServiceImpl  | 9 - org.apache.karaf.features.core -
>>> 4.0.5 |   cxf-wsn-receive/7.0.0.SNAPSHOT
>>>
 2016-04-05 21:42:05,567 | ERROR | pool-46-thread-1 |

>>> BlueprintContainerImpl   | 28 - org.apache.aries.blueprint.core -
>>> 1.6.0 | Unable to start blueprint container for bundle
>>> cxf-wsn-receive/7.0.0.SNAPSHOT
>>>
 org.xml.sax.SAXParseException: src-import.3.1: The namespace attribute,
 '

>>> http://aries.apache.org/blueprint/xmlns/blueprint-ext/v1.0.0', of an
>>>  element information item must be identical to the
>>> targetNamespace
>>> attribute, 'http://camel.apache.org/schema/blueprint', of the imported
>>> document.
>>>
   at

>>>
>>> org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(Unknown
>>> Source)[:]
>>>
   at org.apache.xerces.util.ErrorHandlerWrapper.error(Unknown

>>> Source)[:]
>>>
   at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown

>>> Source)[:]
>>>
   at

>>> org.apache.xerces.impl.xs.traversers.XSDHandler.reportSchemaError(Unknown
>>> Source)[:]
>>>
   at

>>> org.apache.xerces.impl.xs.traversers.XSDHandler.reportSchemaError(Unknown
>>> Source)[:]
>>>
   at

>>> org.apache.xerces.impl.xs.traversers.XSDHandler.constructTrees(Unknown
>>> Source)[:]
>>>
   at

>>> org.apache.xerces.impl.xs.traversers.XSDHandler.constructTrees(Unknown
>>> Source)[:]
>>>
   at

>>> org.apache.xerces.impl.xs.traversers.XSDHandler.parseSchema(Unknown
>>> Source)[:]
>>>

 or


 2016-04-05 21:31:36,969 | ERROR | pool-42-thread-1 |

>>> BlueprintContainerImpl   | 28 - org.apache.aries.blueprint.core -
>>> 1.6.0 | Unable to start blueprint container for bundle
>>> drools-camel-cxf-server/7.0.0.SNAPSHOT
>>>
 org.xml.sax.SAXParseException: src-import.3.1: The namespace attribute,
 '

>>> http://cxf.apache.org/configuration/beans', of an  element
>>> information item must be identical to the targetNamespace attribute, '
>>> http://camel.apa

Re: [VOTE] Apache Karaf 4.0.5 release (take 2)

[Cristiano Costantini]

ok, then ignore my message ;-)
yes I prefer too the option 2


Il giorno mer 6 apr 2016 alle ore 08:39 Jean-Baptiste Onofré <
j...@nanthrax.net> ha scritto:

> Hi Cristiano,
>
> I don't think it's related, as the issue in about blueprint-ext
> namespace (not even define). The problem is located in Aries Blueprint.
>
> I gonna deal with Guillaume.
>
> We can:
> 0. leave Karaf 4.0.5 as it is, but I think it's not acceptable:
> blueprint is used by lot of users, and we can't allow a release without
> a working blueprint layer.
> 1. downgrade Karaf to Aries Blueprint 1.5.x: unfortunately, we won't
> benefit about some improvements implemented in blueprint
> 2. revert or fix the change in Aries: it means we would need a new Aries
> Blueprint core release, so 3 days vote, meaning that we won't be able to
> release Karaf before roughly 6 days.
>
> My preference is on 2 even if it delays Karaf 4.0.5 release.
>
> Thoughts ?
>
> I will add an Integration Test on blueprint to avoid such problem in the
> future.
>
> Regards
> JB
>
> On 04/06/2016 08:14 AM, Cristiano Costantini wrote:
> > Hi JB and Krzysztof,
> >
> > I don't know if this can be have any impact on the problem you have
> > reported, but about 1 month ago I got into an issue with camel XSD
> schemas
> > for Camel namespaces, and the issue is that the URL of the latest XSD,
> > http://camel.apache.org/schema/blueprint/camel-blueprint.xsd
> > is not from latest version 2.16.2, but it is from version 2.15.0
> >
> > While upgrading to ServiceMix 7, I had to change manually the XML to
> > xsi:schemaLocation="http://camel.apache.org/schema/spring http://camel
> > .apache.org/schema/spring/camel-spring-2.16.1.xsd" in order to make it
> work
> > (note also that SMX 7 is based on camel 2.16.2, but this XSD is not
> > available)
> >
> > But in fact the only problem I had was that Eclipse validation and
> > autocompletion of the XML files was not working properly.
> >
> > if this is not relevant, please ignore this message ;-)
> >
> > Cristiano
> >
> >
> >
> >
> > Il giorno mar 5 apr 2016 alle ore 22:19 Jean-Baptiste Onofré <
> > j...@nanthrax.net> ha scritto:
> >
> >> I tried with Camel 2.16.2, camel-blueprint, and simple route in
> >> blueprint: it works fine.
> >>
> >> I tried with your XML, and actually I have the same problem.
> >>
> >> It sounds like a Aries Blueprint bug. Let me try if I downgrade to
> >> blueprint 1.5.x and check the change in aries blueprint (I know
> >> Guillaume did some enhancements & changes).
> >>
> >> Honestly, I would consider as a blocker for the release, so, I will
> >> probably revert my vote to -1. I just want to make more tests.
> >>
> >> Regards
> >> JB
> >>
> >> On 04/05/2016 09:46 PM, Krzysztof Sobkowiak wrote:
> >>> Hi
> >>>
> >>> I tried to upgrade ServiceMix to the new version and have several
> >> problems with blueprint.
> >>>
> >>> 2016-04-05 21:42:05,485 | INFO  | pool-46-thread-1 |
> >> FeaturesServiceImpl  | 9 - org.apache.karaf.features.core -
> >> 4.0.5 |   cxf-wsn-receive/7.0.0.SNAPSHOT
> >>> 2016-04-05 21:42:05,567 | ERROR | pool-46-thread-1 |
> >> BlueprintContainerImpl   | 28 - org.apache.aries.blueprint.core
> -
> >> 1.6.0 | Unable to start blueprint container for bundle
> >> cxf-wsn-receive/7.0.0.SNAPSHOT
> >>> org.xml.sax.SAXParseException: src-import.3.1: The namespace
> attribute, '
> >> http://aries.apache.org/blueprint/xmlns/blueprint-ext/v1.0.0', of an
> >>  element information item must be identical to the
> targetNamespace
> >> attribute, 'http://camel.apache.org/schema/blueprint', of the imported
> >> document.
> >>>   at
> >>
> org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(Unknown
> >> Source)[:]
> >>>   at org.apache.xerces.util.ErrorHandlerWrapper.error(Unknown
> >> Source)[:]
> >>>   at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown
> >> Source)[:]
> >>>   at
> >>
> org.apache.xerces.impl.xs.traversers.XSDHandler.reportSchemaError(Unknown
> >> Source)[:]
> >>>   at
> >>
> org.apache.xerces.impl.xs.traversers.XSDHandler.reportSchemaError(Unknown
> >> Source)[:]
> >>>   at
> >> org.apache.xerces.impl.xs.traversers.XSDHandler.constructTrees(Unknown
> >> Source)[:]
> >>>   at
> >> org.apache.xerces.impl.xs.traversers.XSDHandler.constructTrees(Unknown
> >> Source)[:]
> >>>   at
> >> org.apache.xerces.impl.xs.traversers.XSDHandler.parseSchema(Unknown
> >> Source)[:]
> >>>
> >>> or
> >>>
> >>>
> >>> 2016-04-05 21:31:36,969 | ERROR | pool-42-thread-1 |
> >> BlueprintContainerImpl   | 28 - org.apache.aries.blueprint.core
> -
> >> 1.6.0 | Unable to start blueprint container for bundle
> >> drools-camel-cxf-server/7.0.0.SNAPSHOT
> >>> org.xml.sax.SAXParseException: src-import.3.1: The namespace
> attribute, '
> >> http://cxf.apache.org/configuration/beans', of an  element
> >> information item must be identical to the targetNamespace attribute, '
> >> http://camel.apache.org/schema/blueprint', of the imported docum

Re: [VOTE] Apache Karaf 4.0.5 release (take 2)

[Andrea Cosentino]

I guess option 2 is the best solution.

Thanks!
 --
Andrea Cosentino 
--
Apache Camel PMC Member
Apache Karaf Committer
Apache Servicemix Committer
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd



On Wednesday, April 6, 2016 8:39 AM, Jean-Baptiste Onofré  
wrote:
Hi Cristiano,

I don't think it's related, as the issue in about blueprint-ext 
namespace (not even define). The problem is located in Aries Blueprint.

I gonna deal with Guillaume.

We can:
0. leave Karaf 4.0.5 as it is, but I think it's not acceptable: 
blueprint is used by lot of users, and we can't allow a release without 
a working blueprint layer.
1. downgrade Karaf to Aries Blueprint 1.5.x: unfortunately, we won't 
benefit about some improvements implemented in blueprint
2. revert or fix the change in Aries: it means we would need a new Aries 
Blueprint core release, so 3 days vote, meaning that we won't be able to 
release Karaf before roughly 6 days.

My preference is on 2 even if it delays Karaf 4.0.5 release.

Thoughts ?

I will add an Integration Test on blueprint to avoid such problem in the 
future.

Regards
JB

On 04/06/2016 08:14 AM, Cristiano Costantini wrote:
> Hi JB and Krzysztof,
>
> I don't know if this can be have any impact on the problem you have
> reported, but about 1 month ago I got into an issue with camel XSD schemas
> for Camel namespaces, and the issue is that the URL of the latest XSD,
> http://camel.apache.org/schema/blueprint/camel-blueprint.xsd
> is not from latest version 2.16.2, but it is from version 2.15.0
>
> While upgrading to ServiceMix 7, I had to change manually the XML to
> xsi:schemaLocation="http://camel.apache.org/schema/spring http://camel
> .apache.org/schema/spring/camel-spring-2.16.1.xsd" in order to make it work
> (note also that SMX 7 is based on camel 2.16.2, but this XSD is not
> available)
>
> But in fact the only problem I had was that Eclipse validation and
> autocompletion of the XML files was not working properly.
>
> if this is not relevant, please ignore this message ;-)
>
> Cristiano
>
>
>
>
> Il giorno mar 5 apr 2016 alle ore 22:19 Jean-Baptiste Onofré <
> j...@nanthrax.net> ha scritto:
>
>> I tried with Camel 2.16.2, camel-blueprint, and simple route in
>> blueprint: it works fine.
>>
>> I tried with your XML, and actually I have the same problem.
>>
>> It sounds like a Aries Blueprint bug. Let me try if I downgrade to
>> blueprint 1.5.x and check the change in aries blueprint (I know
>> Guillaume did some enhancements & changes).
>>
>> Honestly, I would consider as a blocker for the release, so, I will
>> probably revert my vote to -1. I just want to make more tests.
>>
>> Regards
>> JB
>>
>> On 04/05/2016 09:46 PM, Krzysztof Sobkowiak wrote:
>>> Hi
>>>
>>> I tried to upgrade ServiceMix to the new version and have several
>> problems with blueprint.
>>>
>>> 2016-04-05 21:42:05,485 | INFO  | pool-46-thread-1 |
>> FeaturesServiceImpl  | 9 - org.apache.karaf.features.core -
>> 4.0.5 |   cxf-wsn-receive/7.0.0.SNAPSHOT
>>> 2016-04-05 21:42:05,567 | ERROR | pool-46-thread-1 |
>> BlueprintContainerImpl   | 28 - org.apache.aries.blueprint.core -
>> 1.6.0 | Unable to start blueprint container for bundle
>> cxf-wsn-receive/7.0.0.SNAPSHOT
>>> org.xml.sax.SAXParseException: src-import.3.1: The namespace attribute, '
>> http://aries.apache.org/blueprint/xmlns/blueprint-ext/v1.0.0', of an
>>  element information item must be identical to the targetNamespace
>> attribute, 'http://camel.apache.org/schema/blueprint', of the imported
>> document.
>>>   at
>> org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(Unknown
>> Source)[:]
>>>   at org.apache.xerces.util.ErrorHandlerWrapper.error(Unknown
>> Source)[:]
>>>   at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown
>> Source)[:]
>>>   at
>> org.apache.xerces.impl.xs.traversers.XSDHandler.reportSchemaError(Unknown
>> Source)[:]
>>>   at
>> org.apache.xerces.impl.xs.traversers.XSDHandler.reportSchemaError(Unknown
>> Source)[:]
>>>   at
>> org.apache.xerces.impl.xs.traversers.XSDHandler.constructTrees(Unknown
>> Source)[:]
>>>   at
>> org.apache.xerces.impl.xs.traversers.XSDHandler.constructTrees(Unknown
>> Source)[:]
>>>   at
>> org.apache.xerces.impl.xs.traversers.XSDHandler.parseSchema(Unknown
>> Source)[:]
>>>
>>> or
>>>
>>>
>>> 2016-04-05 21:31:36,969 | ERROR | pool-42-thread-1 |
>> BlueprintContainerImpl   | 28 - org.apache.aries.blueprint.core -
>> 1.6.0 | Unable to start blueprint container for bundle
>> drools-camel-cxf-server/7.0.0.SNAPSHOT
>>> org.xml.sax.SAXParseException: src-import.3.1: The namespace attribute, '
>> http://cxf.apache.org/configuration/beans', of an  element
>> information item must be identical to the targetNamespace attribute, '
>> http://camel.apache.org/schema/blueprint', of the imported document.
>>>   at
>> org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(Unknown

Re: [VOTE] Apache Karaf 4.0.5 release (take 2)

[Jean-Baptiste Onofré]

Hi Cristiano,

I don't think it's related, as the issue in about blueprint-ext 
namespace (not even define). The problem is located in Aries Blueprint.


I gonna deal with Guillaume.

We can:
0. leave Karaf 4.0.5 as it is, but I think it's not acceptable: 
blueprint is used by lot of users, and we can't allow a release without 
a working blueprint layer.
1. downgrade Karaf to Aries Blueprint 1.5.x: unfortunately, we won't 
benefit about some improvements implemented in blueprint
2. revert or fix the change in Aries: it means we would need a new Aries 
Blueprint core release, so 3 days vote, meaning that we won't be able to 
release Karaf before roughly 6 days.


My preference is on 2 even if it delays Karaf 4.0.5 release.

Thoughts ?

I will add an Integration Test on blueprint to avoid such problem in the 
future.


Regards
JB

On 04/06/2016 08:14 AM, Cristiano Costantini wrote:

Hi JB and Krzysztof,

I don't know if this can be have any impact on the problem you have
reported, but about 1 month ago I got into an issue with camel XSD schemas
for Camel namespaces, and the issue is that the URL of the latest XSD,
http://camel.apache.org/schema/blueprint/camel-blueprint.xsd
is not from latest version 2.16.2, but it is from version 2.15.0

While upgrading to ServiceMix 7, I had to change manually the XML to
xsi:schemaLocation="http://camel.apache.org/schema/spring http://camel
.apache.org/schema/spring/camel-spring-2.16.1.xsd" in order to make it work
(note also that SMX 7 is based on camel 2.16.2, but this XSD is not
available)

But in fact the only problem I had was that Eclipse validation and
autocompletion of the XML files was not working properly.

if this is not relevant, please ignore this message ;-)

Cristiano




Il giorno mar 5 apr 2016 alle ore 22:19 Jean-Baptiste Onofré <
j...@nanthrax.net> ha scritto:


I tried with Camel 2.16.2, camel-blueprint, and simple route in
blueprint: it works fine.

I tried with your XML, and actually I have the same problem.

It sounds like a Aries Blueprint bug. Let me try if I downgrade to
blueprint 1.5.x and check the change in aries blueprint (I know
Guillaume did some enhancements & changes).

Honestly, I would consider as a blocker for the release, so, I will
probably revert my vote to -1. I just want to make more tests.

Regards
JB

On 04/05/2016 09:46 PM, Krzysztof Sobkowiak wrote:

Hi

I tried to upgrade ServiceMix to the new version and have several

problems with blueprint.


2016-04-05 21:42:05,485 | INFO  | pool-46-thread-1 |

FeaturesServiceImpl  | 9 - org.apache.karaf.features.core -
4.0.5 |   cxf-wsn-receive/7.0.0.SNAPSHOT

2016-04-05 21:42:05,567 | ERROR | pool-46-thread-1 |

BlueprintContainerImpl   | 28 - org.apache.aries.blueprint.core -
1.6.0 | Unable to start blueprint container for bundle
cxf-wsn-receive/7.0.0.SNAPSHOT

org.xml.sax.SAXParseException: src-import.3.1: The namespace attribute, '

http://aries.apache.org/blueprint/xmlns/blueprint-ext/v1.0.0', of an
 element information item must be identical to the targetNamespace
attribute, 'http://camel.apache.org/schema/blueprint', of the imported
document.

  at

org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(Unknown
Source)[:]

  at org.apache.xerces.util.ErrorHandlerWrapper.error(Unknown

Source)[:]

  at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown

Source)[:]

  at

org.apache.xerces.impl.xs.traversers.XSDHandler.reportSchemaError(Unknown
Source)[:]

  at

org.apache.xerces.impl.xs.traversers.XSDHandler.reportSchemaError(Unknown
Source)[:]

  at

org.apache.xerces.impl.xs.traversers.XSDHandler.constructTrees(Unknown
Source)[:]

  at

org.apache.xerces.impl.xs.traversers.XSDHandler.constructTrees(Unknown
Source)[:]

  at

org.apache.xerces.impl.xs.traversers.XSDHandler.parseSchema(Unknown
Source)[:]


or


2016-04-05 21:31:36,969 | ERROR | pool-42-thread-1 |

BlueprintContainerImpl   | 28 - org.apache.aries.blueprint.core -
1.6.0 | Unable to start blueprint container for bundle
drools-camel-cxf-server/7.0.0.SNAPSHOT

org.xml.sax.SAXParseException: src-import.3.1: The namespace attribute, '

http://cxf.apache.org/configuration/beans', of an  element
information item must be identical to the targetNamespace attribute, '
http://camel.apache.org/schema/blueprint', of the imported document.

  at

org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(Unknown
Source)[:]

  at org.apache.xerces.util.ErrorHandlerWrapper.error(Unknown

Source)[:]

  at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown

Source)[:]

  at

org.apache.xerces.impl.xs.traversers.XSDHandler.reportSchemaError(Unknown
Source)[:]

  at

org.apache.xerces.impl.xs.traversers.XSDHandler.reportSchemaError(Unknown
Source)[:]

  at

org.apache.xerces.impl.xs.traversers.XSDHandler.constructTrees(Unknown
Source)[:]

  at

org.apache.xerces.impl.xs.traversers.XSDHandler.constructTrees(Unknown

Re: [VOTE] Apache Karaf 4.0.5 release (take 2)

[Cristiano Costantini]

Hi JB and Krzysztof,

I don't know if this can be have any impact on the problem you have
reported, but about 1 month ago I got into an issue with camel XSD schemas
for Camel namespaces, and the issue is that the URL of the latest XSD,
http://camel.apache.org/schema/blueprint/camel-blueprint.xsd
is not from latest version 2.16.2, but it is from version 2.15.0

While upgrading to ServiceMix 7, I had to change manually the XML to
xsi:schemaLocation="http://camel.apache.org/schema/spring http://camel
.apache.org/schema/spring/camel-spring-2.16.1.xsd" in order to make it work
(note also that SMX 7 is based on camel 2.16.2, but this XSD is not
available)

But in fact the only problem I had was that Eclipse validation and
autocompletion of the XML files was not working properly.

if this is not relevant, please ignore this message ;-)

Cristiano




Il giorno mar 5 apr 2016 alle ore 22:19 Jean-Baptiste Onofré <
j...@nanthrax.net> ha scritto:

> I tried with Camel 2.16.2, camel-blueprint, and simple route in
> blueprint: it works fine.
>
> I tried with your XML, and actually I have the same problem.
>
> It sounds like a Aries Blueprint bug. Let me try if I downgrade to
> blueprint 1.5.x and check the change in aries blueprint (I know
> Guillaume did some enhancements & changes).
>
> Honestly, I would consider as a blocker for the release, so, I will
> probably revert my vote to -1. I just want to make more tests.
>
> Regards
> JB
>
> On 04/05/2016 09:46 PM, Krzysztof Sobkowiak wrote:
> > Hi
> >
> > I tried to upgrade ServiceMix to the new version and have several
> problems with blueprint.
> >
> > 2016-04-05 21:42:05,485 | INFO  | pool-46-thread-1 |
> FeaturesServiceImpl  | 9 - org.apache.karaf.features.core -
> 4.0.5 |   cxf-wsn-receive/7.0.0.SNAPSHOT
> > 2016-04-05 21:42:05,567 | ERROR | pool-46-thread-1 |
> BlueprintContainerImpl   | 28 - org.apache.aries.blueprint.core -
> 1.6.0 | Unable to start blueprint container for bundle
> cxf-wsn-receive/7.0.0.SNAPSHOT
> > org.xml.sax.SAXParseException: src-import.3.1: The namespace attribute, '
> http://aries.apache.org/blueprint/xmlns/blueprint-ext/v1.0.0', of an
>  element information item must be identical to the targetNamespace
> attribute, 'http://camel.apache.org/schema/blueprint', of the imported
> document.
> >  at
> org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(Unknown
> Source)[:]
> >  at org.apache.xerces.util.ErrorHandlerWrapper.error(Unknown
> Source)[:]
> >  at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown
> Source)[:]
> >  at
> org.apache.xerces.impl.xs.traversers.XSDHandler.reportSchemaError(Unknown
> Source)[:]
> >  at
> org.apache.xerces.impl.xs.traversers.XSDHandler.reportSchemaError(Unknown
> Source)[:]
> >  at
> org.apache.xerces.impl.xs.traversers.XSDHandler.constructTrees(Unknown
> Source)[:]
> >  at
> org.apache.xerces.impl.xs.traversers.XSDHandler.constructTrees(Unknown
> Source)[:]
> >  at
> org.apache.xerces.impl.xs.traversers.XSDHandler.parseSchema(Unknown
> Source)[:]
> >
> > or
> >
> >
> > 2016-04-05 21:31:36,969 | ERROR | pool-42-thread-1 |
> BlueprintContainerImpl   | 28 - org.apache.aries.blueprint.core -
> 1.6.0 | Unable to start blueprint container for bundle
> drools-camel-cxf-server/7.0.0.SNAPSHOT
> > org.xml.sax.SAXParseException: src-import.3.1: The namespace attribute, '
> http://cxf.apache.org/configuration/beans', of an  element
> information item must be identical to the targetNamespace attribute, '
> http://camel.apache.org/schema/blueprint', of the imported document.
> >  at
> org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(Unknown
> Source)[:]
> >  at org.apache.xerces.util.ErrorHandlerWrapper.error(Unknown
> Source)[:]
> >  at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown
> Source)[:]
> >  at
> org.apache.xerces.impl.xs.traversers.XSDHandler.reportSchemaError(Unknown
> Source)[:]
> >  at
> org.apache.xerces.impl.xs.traversers.XSDHandler.reportSchemaError(Unknown
> Source)[:]
> >  at
> org.apache.xerces.impl.xs.traversers.XSDHandler.constructTrees(Unknown
> Source)[:]
> >  at
> org.apache.xerces.impl.xs.traversers.XSDHandler.constructTrees(Unknown
> Source)[:]
> >
> >
> >
> > Here my try to reproduce one of them in K405
> >
> > Assume you have following simple blueprint (I have reduced one of the
> blueprints from the examples)
> >
> > http://www.osgi.org/xmlns/blueprint/v1.0.0";
> > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> > xmlns:cm="
> http://aries.apache.org/blueprint/xmlns/blueprint-cm/v1.1.0";
> > xsi:schemaLocation="
> http://www.osgi.org/xmlns/blueprint/v1.0.0
> http://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd";>
> >
> >  
> >   persistent-id="org.apache.servicemix.examples.cxf.receive"
> update-strategy="reload">
> >  
> >  http://localhost:12345/test/"/>
> >  
>

Re: [VOTE] Apache Karaf 4.0.5 release (take 2)

[Jean-Baptiste Onofré]

Regarding the issue, I suspect it's related to this change in Aries 
Blueprint:


---
commit b685f35c9c9074d26a3d2af63bc4aa41ec5c0b6e
Author: Guillaume Nodet 
Date:   Fri Mar 11 13:47:57 2016 +

[ARIES-1290][ARIES-1503] Better handling of XSD imports between 
namespace handlers (e.g. cm->ext)


git-svn-id: https://svn.apache.org/repos/asf/aries/trunk@1734559 
13f79535-47bb-0310-9956-ffa450edef68

-

and especially this part:

+} else if 
(namespace.startsWith("http://aries.apache.org/blueprint/xmlns/blueprint-ext";)) 
{

+try {
+Bundle extBundle = 
FrameworkUtil.getBundle(PlaceholdersUtils.class);
+Class extNsHandlerClazz = 
extBundle.loadClass("org.apache.aries.blueprint.ext.impl.ExtNamespaceHandler");
+return ((NamespaceHandler) 
extNsHandlerClazz.newInstance()).getSchemaLocation(namespace);

+} catch (Throwable t) {
+LOGGER.warn("Could not locate ext namespace schema", t);
+return null;
+}

Let me try to ping Guillaume today, but IMHO, it's a -1 due to this 
change in Aries.


Regards
JB

On 04/05/2016 10:19 PM, Jean-Baptiste Onofré wrote:

I tried with Camel 2.16.2, camel-blueprint, and simple route in
blueprint: it works fine.

I tried with your XML, and actually I have the same problem.

It sounds like a Aries Blueprint bug. Let me try if I downgrade to
blueprint 1.5.x and check the change in aries blueprint (I know
Guillaume did some enhancements & changes).

Honestly, I would consider as a blocker for the release, so, I will
probably revert my vote to -1. I just want to make more tests.

Regards
JB

On 04/05/2016 09:46 PM, Krzysztof Sobkowiak wrote:

Hi

I tried to upgrade ServiceMix to the new version and have several
problems with blueprint.

2016-04-05 21:42:05,485 | INFO  | pool-46-thread-1 |
FeaturesServiceImpl  | 9 - org.apache.karaf.features.core
- 4.0.5 |   cxf-wsn-receive/7.0.0.SNAPSHOT
2016-04-05 21:42:05,567 | ERROR | pool-46-thread-1 |
BlueprintContainerImpl   | 28 -
org.apache.aries.blueprint.core - 1.6.0 | Unable to start blueprint
container for bundle cxf-wsn-receive/7.0.0.SNAPSHOT
org.xml.sax.SAXParseException: src-import.3.1: The namespace
attribute,
'http://aries.apache.org/blueprint/xmlns/blueprint-ext/v1.0.0', of an
 element information item must be identical to the
targetNamespace attribute, 'http://camel.apache.org/schema/blueprint',
of the imported document.
 at
org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(Unknown
Source)[:]
 at org.apache.xerces.util.ErrorHandlerWrapper.error(Unknown
Source)[:]
 at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown
Source)[:]
 at
org.apache.xerces.impl.xs.traversers.XSDHandler.reportSchemaError(Unknown
Source)[:]
 at
org.apache.xerces.impl.xs.traversers.XSDHandler.reportSchemaError(Unknown
Source)[:]
 at
org.apache.xerces.impl.xs.traversers.XSDHandler.constructTrees(Unknown
Source)[:]
 at
org.apache.xerces.impl.xs.traversers.XSDHandler.constructTrees(Unknown
Source)[:]
 at
org.apache.xerces.impl.xs.traversers.XSDHandler.parseSchema(Unknown
Source)[:]

or


2016-04-05 21:31:36,969 | ERROR | pool-42-thread-1 |
BlueprintContainerImpl   | 28 -
org.apache.aries.blueprint.core - 1.6.0 | Unable to start blueprint
container for bundle drools-camel-cxf-server/7.0.0.SNAPSHOT
org.xml.sax.SAXParseException: src-import.3.1: The namespace
attribute, 'http://cxf.apache.org/configuration/beans', of an 
element information item must be identical to the targetNamespace
attribute, 'http://camel.apache.org/schema/blueprint', of the imported
document.
 at
org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(Unknown
Source)[:]
 at org.apache.xerces.util.ErrorHandlerWrapper.error(Unknown
Source)[:]
 at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown
Source)[:]
 at
org.apache.xerces.impl.xs.traversers.XSDHandler.reportSchemaError(Unknown
Source)[:]
 at
org.apache.xerces.impl.xs.traversers.XSDHandler.reportSchemaError(Unknown
Source)[:]
 at
org.apache.xerces.impl.xs.traversers.XSDHandler.constructTrees(Unknown
Source)[:]
 at
org.apache.xerces.impl.xs.traversers.XSDHandler.constructTrees(Unknown
Source)[:]



Here my try to reproduce one of them in K405

Assume you have following simple blueprint (I have reduced one of the
blueprints from the examples)

http://www.osgi.org/xmlns/blueprint/v1.0.0";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";

xmlns:cm="http://aries.apache.org/blueprint/xmlns/blueprint-cm/v1.1.0";

xsi:schemaLocation="http://www.osgi.org/xmlns/blueprint/v1.0.0
http://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd";>

 
 
 
 http://localhost:12345/test/"/>
 
 
 

 http://camel.apache.org/schema/blueprint";>

 



Next

karaf@root()> feature:r

Re: [VOTE] Apache Karaf 4.0.5 release (take 2)

[Jean-Baptiste Onofré]

I tried with Camel 2.16.2, camel-blueprint, and simple route in 
blueprint: it works fine.


I tried with your XML, and actually I have the same problem.

It sounds like a Aries Blueprint bug. Let me try if I downgrade to 
blueprint 1.5.x and check the change in aries blueprint (I know 
Guillaume did some enhancements & changes).


Honestly, I would consider as a blocker for the release, so, I will 
probably revert my vote to -1. I just want to make more tests.


Regards
JB

On 04/05/2016 09:46 PM, Krzysztof Sobkowiak wrote:

Hi

I tried to upgrade ServiceMix to the new version and have several problems with 
blueprint.

2016-04-05 21:42:05,485 | INFO  | pool-46-thread-1 | FeaturesServiceImpl
  | 9 - org.apache.karaf.features.core - 4.0.5 |   
cxf-wsn-receive/7.0.0.SNAPSHOT
2016-04-05 21:42:05,567 | ERROR | pool-46-thread-1 | BlueprintContainerImpl 
  | 28 - org.apache.aries.blueprint.core - 1.6.0 | Unable to start 
blueprint container for bundle cxf-wsn-receive/7.0.0.SNAPSHOT
org.xml.sax.SAXParseException: src-import.3.1: The namespace attribute, 
'http://aries.apache.org/blueprint/xmlns/blueprint-ext/v1.0.0', of an  
element information item must be identical to the targetNamespace attribute, 
'http://camel.apache.org/schema/blueprint', of the imported document.
 at 
org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(Unknown 
Source)[:]
 at org.apache.xerces.util.ErrorHandlerWrapper.error(Unknown Source)[:]
 at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)[:]
 at 
org.apache.xerces.impl.xs.traversers.XSDHandler.reportSchemaError(Unknown 
Source)[:]
 at 
org.apache.xerces.impl.xs.traversers.XSDHandler.reportSchemaError(Unknown 
Source)[:]
 at org.apache.xerces.impl.xs.traversers.XSDHandler.constructTrees(Unknown 
Source)[:]
 at org.apache.xerces.impl.xs.traversers.XSDHandler.constructTrees(Unknown 
Source)[:]
 at org.apache.xerces.impl.xs.traversers.XSDHandler.parseSchema(Unknown 
Source)[:]

or


2016-04-05 21:31:36,969 | ERROR | pool-42-thread-1 | BlueprintContainerImpl 
  | 28 - org.apache.aries.blueprint.core - 1.6.0 | Unable to start 
blueprint container for bundle drools-camel-cxf-server/7.0.0.SNAPSHOT
org.xml.sax.SAXParseException: src-import.3.1: The namespace attribute, 
'http://cxf.apache.org/configuration/beans', of an  element information 
item must be identical to the targetNamespace attribute, 
'http://camel.apache.org/schema/blueprint', of the imported document.
 at 
org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(Unknown 
Source)[:]
 at org.apache.xerces.util.ErrorHandlerWrapper.error(Unknown Source)[:]
 at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)[:]
 at 
org.apache.xerces.impl.xs.traversers.XSDHandler.reportSchemaError(Unknown 
Source)[:]
 at 
org.apache.xerces.impl.xs.traversers.XSDHandler.reportSchemaError(Unknown 
Source)[:]
 at org.apache.xerces.impl.xs.traversers.XSDHandler.constructTrees(Unknown 
Source)[:]
 at org.apache.xerces.impl.xs.traversers.XSDHandler.constructTrees(Unknown 
Source)[:]



Here my try to reproduce one of them in K405

Assume you have following simple blueprint (I have reduced one of the 
blueprints from the examples)

http://www.osgi.org/xmlns/blueprint/v1.0.0";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";

xmlns:cm="http://aries.apache.org/blueprint/xmlns/blueprint-cm/v1.1.0";
xsi:schemaLocation="http://www.osgi.org/xmlns/blueprint/v1.0.0 
http://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd";>

 
 
 
 http://localhost:12345/test/"/>
 
 
 

 http://camel.apache.org/schema/blueprint";>

 



Next

karaf@root()> feature:repo-add camel 2.16.2
Adding feature url mvn:org.apache.camel.karaf/apache-camel/2.16.2/xml/features
karaf@root()> feature:install camel-blueprint


Deploy the blueprint into deploy directory (the same problem occurs when the 
blueprint is part of a bundle). Tho log contains following error


2016-04-05 21:15:47,932 | INFO  | raf-4.0.5/deploy | fileinstall
  | 8 - org.apache.felix.fileinstall - 3.5.4 | Installing bundle x.xml / 
0.0.0
2016-04-05 21:15:48,216 | ERROR | raf-4.0.5/deploy | BlueprintContainerImpl 
  | 13 - org.apache.aries.blueprint.core - 1.6.0 | Unable to start 
blueprint container for bundle x.xml/0.0.0
org.xml.sax.SAXParseException: src-import.3.1: The namespace attribute, 
'http://aries.apache.org/blueprint/xmlns/blueprint-ext/v1.0.0', of an  
element information item must be identical to the targetNamespace attribute, 
'http://camel.apache.org/schema/blueprint', of the imported document.
 at 
org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(Unknown 
Source)[:]
 at org.apache.xerces.util.ErrorHandlerWrapper.error(Unknown Source)[:]
 at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown

Re: [VOTE] Apache Karaf 4.0.5 release (take 2)

[Krzysztof Sobkowiak]

Hi

I tried to upgrade ServiceMix to the new version and have several problems with 
blueprint.

2016-04-05 21:42:05,485 | INFO  | pool-46-thread-1 | FeaturesServiceImpl
  | 9 - org.apache.karaf.features.core - 4.0.5 |   
cxf-wsn-receive/7.0.0.SNAPSHOT
2016-04-05 21:42:05,567 | ERROR | pool-46-thread-1 | BlueprintContainerImpl 
  | 28 - org.apache.aries.blueprint.core - 1.6.0 | Unable to start 
blueprint container for bundle cxf-wsn-receive/7.0.0.SNAPSHOT
org.xml.sax.SAXParseException: src-import.3.1: The namespace attribute, 
'http://aries.apache.org/blueprint/xmlns/blueprint-ext/v1.0.0', of an  
element information item must be identical to the targetNamespace attribute, 
'http://camel.apache.org/schema/blueprint', of the imported document.
at 
org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(Unknown 
Source)[:]
at org.apache.xerces.util.ErrorHandlerWrapper.error(Unknown Source)[:]
at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)[:]
at 
org.apache.xerces.impl.xs.traversers.XSDHandler.reportSchemaError(Unknown 
Source)[:]
at 
org.apache.xerces.impl.xs.traversers.XSDHandler.reportSchemaError(Unknown 
Source)[:]
at org.apache.xerces.impl.xs.traversers.XSDHandler.constructTrees(Unknown 
Source)[:]
at org.apache.xerces.impl.xs.traversers.XSDHandler.constructTrees(Unknown 
Source)[:]
at org.apache.xerces.impl.xs.traversers.XSDHandler.parseSchema(Unknown 
Source)[:]

or


2016-04-05 21:31:36,969 | ERROR | pool-42-thread-1 | BlueprintContainerImpl 
  | 28 - org.apache.aries.blueprint.core - 1.6.0 | Unable to start 
blueprint container for bundle drools-camel-cxf-server/7.0.0.SNAPSHOT
org.xml.sax.SAXParseException: src-import.3.1: The namespace attribute, 
'http://cxf.apache.org/configuration/beans', of an  element information 
item must be identical to the targetNamespace attribute, 
'http://camel.apache.org/schema/blueprint', of the imported document.
at 
org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(Unknown 
Source)[:]
at org.apache.xerces.util.ErrorHandlerWrapper.error(Unknown Source)[:]
at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)[:]
at 
org.apache.xerces.impl.xs.traversers.XSDHandler.reportSchemaError(Unknown 
Source)[:]
at 
org.apache.xerces.impl.xs.traversers.XSDHandler.reportSchemaError(Unknown 
Source)[:]
at org.apache.xerces.impl.xs.traversers.XSDHandler.constructTrees(Unknown 
Source)[:]
at org.apache.xerces.impl.xs.traversers.XSDHandler.constructTrees(Unknown 
Source)[:]



Here my try to reproduce one of them in K405

Assume you have following simple blueprint (I have reduced one of the 
blueprints from the examples)

http://www.osgi.org/xmlns/blueprint/v1.0.0";
   xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
   
xmlns:cm="http://aries.apache.org/blueprint/xmlns/blueprint-cm/v1.1.0";
   xsi:schemaLocation="http://www.osgi.org/xmlns/blueprint/v1.0.0 
http://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd";>




http://localhost:12345/test/"/>




http://camel.apache.org/schema/blueprint";>
   




Next

karaf@root()> feature:repo-add camel 2.16.2
Adding feature url mvn:org.apache.camel.karaf/apache-camel/2.16.2/xml/features
karaf@root()> feature:install camel-blueprint


Deploy the blueprint into deploy directory (the same problem occurs when the 
blueprint is part of a bundle). Tho log contains following error

 
2016-04-05 21:15:47,932 | INFO  | raf-4.0.5/deploy | fileinstall
  | 8 - org.apache.felix.fileinstall - 3.5.4 | Installing bundle x.xml / 
0.0.0
2016-04-05 21:15:48,216 | ERROR | raf-4.0.5/deploy | BlueprintContainerImpl 
  | 13 - org.apache.aries.blueprint.core - 1.6.0 | Unable to start 
blueprint container for bundle x.xml/0.0.0
org.xml.sax.SAXParseException: src-import.3.1: The namespace attribute, 
'http://aries.apache.org/blueprint/xmlns/blueprint-ext/v1.0.0', of an  
element information item must be identical to the targetNamespace attribute, 
'http://camel.apache.org/schema/blueprint', of the imported document.
at 
org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(Unknown 
Source)[:]
at org.apache.xerces.util.ErrorHandlerWrapper.error(Unknown Source)[:]
at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)[:]
at 
org.apache.xerces.impl.xs.traversers.XSDHandler.reportSchemaError(Unknown 
Source)[:]
at 
org.apache.xerces.impl.xs.traversers.XSDHandler.reportSchemaError(Unknown 
Source)[:]
at org.apache.xerces.impl.xs.traversers.XSDHandler.constructTrees(Unknown 
Source)[:]
at org.apache.xerces.impl.xs.traversers.XSDHandler.constructTrees(Unknown 
Source)[:]
at org.apache.xerces.impl.xs.traversers.XSDHandler.parseSchema(Unknown 
Source)[:]
at org.apache.xerces.impl.xs.XMLSchemaLoader.loadSchema(Unknown Source)[:]
at o

Re: [VOTE] Apache Karaf 4.0.5 release (take 2)

[ellirael]

+1 (non-binding)



--
View this message in context: 
http://karaf.922171.n3.nabble.com/VOTE-Apache-Karaf-4-0-5-release-take-2-tp4046157p4046175.html
Sent from the Karaf - Dev mailing list archive at Nabble.com.

Re: [VOTE] Apache Karaf 4.0.5 release (take 2)

[Morgan Hautman]

+1 (non-binding)

2016-04-05 7:54 GMT+02:00 Andrea Cosentino :

> +1 (non-binding).
>
> Thanks JB!
>  --
> Andrea Cosentino
> --
> Apache Camel PMC Member
> Apache Karaf Committer
> Apache Servicemix Committer
> Email: ancosen1...@yahoo.com
> Twitter: @oscerd2
> Github: oscerd
>
>
>
> On Tuesday, April 5, 2016 7:45 AM, Jean-Baptiste Onofré 
> wrote:
> +1 (binding)
>
> Regards
> JB
>
>
> On 04/04/2016 10:38 PM, Jean-Baptiste Onofré wrote:
> > Hi all,
> >
> > I submit Karaf Container 4.0.5 release to your vote.
> >
> > Release Note:
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311140&version=12334629
> >
> >
> > Staging Repository:
> > https://repository.apache.org/content/repositories/orgapachekaraf-1060/
> >
> > Git tag:
> > karaf-4.0.5
> >
> > Please vote to approve this release:
> >
> > [ ] +1 Approve the release
> > [ ] -1 Don't approve the release (please provide specific comments)
> >
> > This vote will be open for at least 72 hours.
> >
> > Thanks,
> > Regards
> > JB
>
> --
> Jean-Baptiste Onofré
> jbono...@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>

Re: [VOTE] Apache Karaf 4.0.5 release (take 2)

[Andrea Cosentino]

+1 (non-binding).

Thanks JB!
 --
Andrea Cosentino 
--
Apache Camel PMC Member
Apache Karaf Committer
Apache Servicemix Committer
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd



On Tuesday, April 5, 2016 7:45 AM, Jean-Baptiste Onofré  
wrote:
+1 (binding)

Regards
JB


On 04/04/2016 10:38 PM, Jean-Baptiste Onofré wrote:
> Hi all,
>
> I submit Karaf Container 4.0.5 release to your vote.
>
> Release Note:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311140&version=12334629
>
>
> Staging Repository:
> https://repository.apache.org/content/repositories/orgapachekaraf-1060/
>
> Git tag:
> karaf-4.0.5
>
> Please vote to approve this release:
>
> [ ] +1 Approve the release
> [ ] -1 Don't approve the release (please provide specific comments)
>
> This vote will be open for at least 72 hours.
>
> Thanks,
> Regards
> JB

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

Re: [VOTE] Apache Karaf 4.0.5 release (take 2)

[Jean-Baptiste Onofré]

+1 (binding)

Regards
JB

On 04/04/2016 10:38 PM, Jean-Baptiste Onofré wrote:

Hi all,

I submit Karaf Container 4.0.5 release to your vote.

Release Note:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311140&version=12334629


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

Git tag:
karaf-4.0.5

Please vote to approve this release:

[ ] +1 Approve the release
[ ] -1 Don't approve the release (please provide specific comments)

This vote will be open for at least 72 hours.

Thanks,
Regards
JB


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

Re: [VOTE] Apache Karaf 4.0.5 release (take 2)

[Markus Rathgeb]

+1 (non-binding)

2016-04-05 5:52 GMT+02:00 Jamie G. :
> +1 (binding)
>
> On Mon, Apr 4, 2016 at 6:40 PM, Fabian Lange
>  wrote:
>> verified, no runtime downloads, everything as I like it, so
>>
>> +1 (non-binding)
>>
>> Fabian
>>
>> On Mon, Apr 4, 2016 at 10:38 PM, Jean-Baptiste Onofré 
>> wrote:
>>
>>> Hi all,
>>>
>>> I submit Karaf Container 4.0.5 release to your vote.
>>>
>>> Release Note:
>>>
>>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311140&version=12334629
>>>
>>> Staging Repository:
>>> https://repository.apache.org/content/repositories/orgapachekaraf-1060/
>>>
>>> Git tag:
>>> karaf-4.0.5
>>>
>>> Please vote to approve this release:
>>>
>>> [ ] +1 Approve the release
>>> [ ] -1 Don't approve the release (please provide specific comments)
>>>
>>> This vote will be open for at least 72 hours.
>>>
>>> Thanks,
>>> Regards
>>> JB
>>> --
>>> Jean-Baptiste Onofré
>>> jbono...@apache.org
>>> http://blog.nanthrax.net
>>> Talend - http://www.talend.com
>>>

Re: [VOTE] Apache Karaf 4.0.5 release (take 2)

[Christian Schneider]

+1 (non binding)
Christian

2016-04-05 5:52 GMT+02:00 Jamie G. :

> +1 (binding)
>
> On Mon, Apr 4, 2016 at 6:40 PM, Fabian Lange
>  wrote:
> > verified, no runtime downloads, everything as I like it, so
> >
> > +1 (non-binding)
> >
> > Fabian
> >
> > On Mon, Apr 4, 2016 at 10:38 PM, Jean-Baptiste Onofré 
> > wrote:
> >
> >> Hi all,
> >>
> >> I submit Karaf Container 4.0.5 release to your vote.
> >>
> >> Release Note:
> >>
> >>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311140&version=12334629
> >>
> >> Staging Repository:
> >> https://repository.apache.org/content/repositories/orgapachekaraf-1060/
> >>
> >> Git tag:
> >> karaf-4.0.5
> >>
> >> Please vote to approve this release:
> >>
> >> [ ] +1 Approve the release
> >> [ ] -1 Don't approve the release (please provide specific comments)
> >>
> >> This vote will be open for at least 72 hours.
> >>
> >> Thanks,
> >> 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
http://www.talend.com

Re: [VOTE] Apache Karaf 4.0.5 release (take 2)

[Jamie G.]

+1 (binding)

On Mon, Apr 4, 2016 at 6:40 PM, Fabian Lange
 wrote:
> verified, no runtime downloads, everything as I like it, so
>
> +1 (non-binding)
>
> Fabian
>
> On Mon, Apr 4, 2016 at 10:38 PM, Jean-Baptiste Onofré 
> wrote:
>
>> Hi all,
>>
>> I submit Karaf Container 4.0.5 release to your vote.
>>
>> Release Note:
>>
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311140&version=12334629
>>
>> Staging Repository:
>> https://repository.apache.org/content/repositories/orgapachekaraf-1060/
>>
>> Git tag:
>> karaf-4.0.5
>>
>> Please vote to approve this release:
>>
>> [ ] +1 Approve the release
>> [ ] -1 Don't approve the release (please provide specific comments)
>>
>> This vote will be open for at least 72 hours.
>>
>> Thanks,
>> Regards
>> JB
>> --
>> Jean-Baptiste Onofré
>> jbono...@apache.org
>> http://blog.nanthrax.net
>> Talend - http://www.talend.com
>>

Re: [VOTE] Apache Karaf 4.0.5 release (take 2)

[Fabian Lange]

verified, no runtime downloads, everything as I like it, so

+1 (non-binding)

Fabian

On Mon, Apr 4, 2016 at 10:38 PM, Jean-Baptiste Onofré 
wrote:

> Hi all,
>
> I submit Karaf Container 4.0.5 release to your vote.
>
> Release Note:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311140&version=12334629
>
> Staging Repository:
> https://repository.apache.org/content/repositories/orgapachekaraf-1060/
>
> Git tag:
> karaf-4.0.5
>
> Please vote to approve this release:
>
> [ ] +1 Approve the release
> [ ] -1 Don't approve the release (please provide specific comments)
>
> This vote will be open for at least 72 hours.
>
> Thanks,
> Regards
> JB
> --
> Jean-Baptiste Onofré
> jbono...@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>

Re: [VOTE] Apache Karaf 4.0.5 release (take 2)

[Achim Nierbeck]

+1 (binding)

regards, Achim


2016-04-04 22:38 GMT+02:00 Jean-Baptiste Onofré :

> Hi all,
>
> I submit Karaf Container 4.0.5 release to your vote.
>
> Release Note:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311140&version=12334629
>
> Staging Repository:
> https://repository.apache.org/content/repositories/orgapachekaraf-1060/
>
> Git tag:
> karaf-4.0.5
>
> Please vote to approve this release:
>
> [ ] +1 Approve the release
> [ ] -1 Don't approve the release (please provide specific comments)
>
> This vote will be open for at least 72 hours.
>
> Thanks,
> Regards
> JB
> --
> 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 
Co-Author of Apache Karaf Cookbook 

Software Architect / Project Manager / Scrum Master

[VOTE] Apache Karaf 4.0.5 release (take 2)

[Jean-Baptiste Onofré]

Hi all,

I submit Karaf Container 4.0.5 release to your vote.

Release Note:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311140&version=12334629

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

Git tag:
karaf-4.0.5

Please vote to approve this release:

[ ] +1 Approve the release
[ ] -1 Don't approve the release (please provide specific comments)

This vote will be open for at least 72 hours.

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