You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@aries.apache.org by Tom Aerden <to...@aca-it.be> on 2015/07/27 18:16:11 UTC

Subsystem bundle's manifest headers not read correctly

Hi,

we're trying to deploy a subsystem generated by maven esa plugin, but when
parsing the bundle manifests, some attributes are not recognized. I.e while
we're adding com.springsource.org.aspectj.weaver as a bundle to our
subsystem, all headers after "Name: org/aspectj/weaver/" are not
recognized, among them Bundle-SymbolicName.

We could downtrace the error to the ManifestProcessor in
org.apache.aries.util-1.1.0, and while doing so, we discovered there was
already a bug logged describing almost exactly the same situation:
https://issues.apache.org/jira/browse/ARIES-958.

Although this bug has already been resolved for quite some time, it hasn't
been released yet. Is there a chance util-1.1.1 will be available soon?

kind regards,

Tom

Re: Subsystem bundle's manifest headers not read correctly

Posted by David Bosschaert <da...@gmail.com>.
Hi Tom,

The release is currently under vote which is why its not yet in Maven
Central. You can get the artifacts from the staging area:
https://repository.apache.org/content/repositories/orgapachearies-1035

I think it makes sense to do a Subsystem release once that (and maybe
other) bugs are fixed, and yes that dependency should be updated. In the
mean time you should be able to just replace the util 1.1.0 bundle with the
1.1.1 bundle in your subsystems deployment.

Best regards,

David

On 7 August 2015 at 13:13, Tom De Wolf <to...@aca-it.be> wrote:

> David,
>
> I've seen aries util 1.1.1 was released, thanks for that. However, is it
> also already available in the central maven repository? I cannot find it at
> http://mvnrepository.com/artifact/org.apache.aries/org.apache.aries.util
>
> Also, is it planned to update the dependency of the subsystem artefacts on
> this aries util bundle? Maybe combine it with the fix and release of
> https://issues.apache.org/jira/browse/ARIES-1368
>
> That would be great to deblock our adoption of the aries subsystems
> approach.
>
> Met vriendelijke groeten,
> Kind regards,
>
> Tom De Wolf
>
>  Let's Develop Your Future Together: www.aca-it.be/jobs
> <http://www.aca-it.be/jobs?utm_source=handtekening&utm_medium=email&utm_campaign=handtekening_jobs_12_03_2015>
>
> [image: Foto van Tom De Wolf][image: email]tom.dewolf@aca-it.be[image:
> Phone]+32 (0) 11 26 50 10[image: Logo ACA IT-Solutions]
> <http://t.signaleuna.com/e1t/c/5/f18dQhb0S7lC8dDMPbW2n0x6l2B9nMJW7t5XYg4WJ23-W5v0sYv4WYzvFW8rByXx56dSv_f6M7J0H02?t=http%3A%2F%2Fwww.aca-it.be%2F&si=6140990011211776&pi=d02f8a41-96f6-4941-8e2d-eebf8e47a674>
>
> *ACA IT-Solutions NV*
> *HQ:* Ilgatlaan 5C | 3500 Hasselt
> T +32(0)11 26 50 10 | F +32(0)11 26 50 11
> www.aca-it.be | Twitter
> <http://t.signaleuna.com/e1t/c/5/f18dQhb0S7lC8dDMPbW2n0x6l2B9nMJW7t5XYg4WJ23-W5v0sYv4WYzvFW8rByXx56dSv_f6M7J0H02?t=https%3A%2F%2Ftwitter.com%2Fdorien_jorissen&si=6140990011211776&pi=d02f8a41-96f6-4941-8e2d-eebf8e47a674>
>  | Facebook
> <http://t.signaleuna.com/e1t/c/5/f18dQhb0S7lC8dDMPbW2n0x6l2B9nMJW7t5XYg4WJ23-W5v0sYv4WYzvFW8rByXx56dSv_f6M7J0H02?t=http%3A%2F%2Fwww.facebook.com%2Fpages%2FACA-IT-Solutions%2F278520212202909&si=6140990011211776&pi=d02f8a41-96f6-4941-8e2d-eebf8e47a674>
>  | Linkedin
> <http://t.signaleuna.com/e1t/c/5/f18dQhb0S7lC8dDMPbW2n0x6l2B9nMJW7t5XYg4WJ23-W5v0sYv4WYzvFW8rByXx56dSv_f6M7J0H02?t=http%3A%2F%2Fwww.linkedin.com%2Fcompany%2F6524&si=6140990011211776&pi=d02f8a41-96f6-4941-8e2d-eebf8e47a674>
>
>
> 2015-07-28 9:16 GMT+02:00 David Bosschaert <da...@gmail.com>:
>
>> I'm planning to do a release of Aries Async services sometime next
>> week. I can do Aries Util 1.1.1 then as well if nobody beats me to
>> it...
>>
>> David
>>
>> On 27 July 2015 at 17:16, Tom Aerden <to...@aca-it.be> wrote:
>> > Hi,
>> >
>> > we're trying to deploy a subsystem generated by maven esa plugin, but
>> when
>> > parsing the bundle manifests, some attributes are not recognized. I.e
>> while
>> > we're adding com.springsource.org.aspectj.weaver as a bundle to our
>> > subsystem, all headers after "Name: org/aspectj/weaver/" are not
>> recognized,
>> > among them Bundle-SymbolicName.
>> >
>> > We could downtrace the error to the ManifestProcessor in
>> > org.apache.aries.util-1.1.0, and while doing so, we discovered there was
>> > already a bug logged describing almost exactly the same situation:
>> > https://issues.apache.org/jira/browse/ARIES-958.
>> >
>> > Although this bug has already been resolved for quite some time, it
>> hasn't
>> > been released yet. Is there a chance util-1.1.1 will be available soon?
>> >
>> > kind regards,
>> >
>> > Tom
>>
>
>

Re: Subsystem bundle's manifest headers not read correctly

Posted by Tom De Wolf <to...@aca-it.be>.
David,

I've seen aries util 1.1.1 was released, thanks for that. However, is it
also already available in the central maven repository? I cannot find it at
http://mvnrepository.com/artifact/org.apache.aries/org.apache.aries.util

Also, is it planned to update the dependency of the subsystem artefacts on
this aries util bundle? Maybe combine it with the fix and release of
https://issues.apache.org/jira/browse/ARIES-1368

That would be great to deblock our adoption of the aries subsystems
approach.

Met vriendelijke groeten,
Kind regards,

Tom De Wolf

 Let's Develop Your Future Together: www.aca-it.be/jobs
<http://www.aca-it.be/jobs?utm_source=handtekening&utm_medium=email&utm_campaign=handtekening_jobs_12_03_2015>

[image: Foto van Tom De Wolf][image: email]tom.dewolf@aca-it.be[image:
Phone]+32 (0) 11 26 50 10[image: Logo ACA IT-Solutions]
<http://t.signaleuna.com/e1t/c/5/f18dQhb0S7lC8dDMPbW2n0x6l2B9nMJW7t5XYg4WJ23-W5v0sYv4WYzvFW8rByXx56dSv_f6M7J0H02?t=http%3A%2F%2Fwww.aca-it.be%2F&si=6140990011211776&pi=d02f8a41-96f6-4941-8e2d-eebf8e47a674>

*ACA IT-Solutions NV*
*HQ:* Ilgatlaan 5C | 3500 Hasselt
T +32(0)11 26 50 10 | F +32(0)11 26 50 11
www.aca-it.be | Twitter
<http://t.signaleuna.com/e1t/c/5/f18dQhb0S7lC8dDMPbW2n0x6l2B9nMJW7t5XYg4WJ23-W5v0sYv4WYzvFW8rByXx56dSv_f6M7J0H02?t=https%3A%2F%2Ftwitter.com%2Fdorien_jorissen&si=6140990011211776&pi=d02f8a41-96f6-4941-8e2d-eebf8e47a674>
 | Facebook
<http://t.signaleuna.com/e1t/c/5/f18dQhb0S7lC8dDMPbW2n0x6l2B9nMJW7t5XYg4WJ23-W5v0sYv4WYzvFW8rByXx56dSv_f6M7J0H02?t=http%3A%2F%2Fwww.facebook.com%2Fpages%2FACA-IT-Solutions%2F278520212202909&si=6140990011211776&pi=d02f8a41-96f6-4941-8e2d-eebf8e47a674>
 | Linkedin
<http://t.signaleuna.com/e1t/c/5/f18dQhb0S7lC8dDMPbW2n0x6l2B9nMJW7t5XYg4WJ23-W5v0sYv4WYzvFW8rByXx56dSv_f6M7J0H02?t=http%3A%2F%2Fwww.linkedin.com%2Fcompany%2F6524&si=6140990011211776&pi=d02f8a41-96f6-4941-8e2d-eebf8e47a674>


2015-07-28 9:16 GMT+02:00 David Bosschaert <da...@gmail.com>:

> I'm planning to do a release of Aries Async services sometime next
> week. I can do Aries Util 1.1.1 then as well if nobody beats me to
> it...
>
> David
>
> On 27 July 2015 at 17:16, Tom Aerden <to...@aca-it.be> wrote:
> > Hi,
> >
> > we're trying to deploy a subsystem generated by maven esa plugin, but
> when
> > parsing the bundle manifests, some attributes are not recognized. I.e
> while
> > we're adding com.springsource.org.aspectj.weaver as a bundle to our
> > subsystem, all headers after "Name: org/aspectj/weaver/" are not
> recognized,
> > among them Bundle-SymbolicName.
> >
> > We could downtrace the error to the ManifestProcessor in
> > org.apache.aries.util-1.1.0, and while doing so, we discovered there was
> > already a bug logged describing almost exactly the same situation:
> > https://issues.apache.org/jira/browse/ARIES-958.
> >
> > Although this bug has already been resolved for quite some time, it
> hasn't
> > been released yet. Is there a chance util-1.1.1 will be available soon?
> >
> > kind regards,
> >
> > Tom
>

Re: Subsystem bundle's manifest headers not read correctly

Posted by Tom Aerden <to...@aca-it.be>.
that would be great!
thanks

[image: Foto van ...][image: email]tom.aerden@aca-it.be[image: Phone]+32
(0) 11 26 50 10[image: GSM]+32 (0) 485 80 78 88[image: twitter]aca_it
<https://twitter.com/#!/aca_it>[image: Logo ACA IT-Solutions]
<http://www.aca-it.be>

*ACA IT-Solutions NV*
*HQ:* Ilgatlaan 5C | 3500 Hasselt
T +32(0)11 26 50 10 | F +32(0)11 26 50 11
www.aca-it.be | Twitter <https://twitter.com/aca_it> | Facebook
<http://www.facebook.com/pages/ACA-IT-Solutions/278520212202909> | Linkedin
<http://www.linkedin.com/company/6524>

2015-07-28 9:16 GMT+02:00 David Bosschaert <da...@gmail.com>:

> I'm planning to do a release of Aries Async services sometime next
> week. I can do Aries Util 1.1.1 then as well if nobody beats me to
> it...
>
> David
>
> On 27 July 2015 at 17:16, Tom Aerden <to...@aca-it.be> wrote:
> > Hi,
> >
> > we're trying to deploy a subsystem generated by maven esa plugin, but
> when
> > parsing the bundle manifests, some attributes are not recognized. I.e
> while
> > we're adding com.springsource.org.aspectj.weaver as a bundle to our
> > subsystem, all headers after "Name: org/aspectj/weaver/" are not
> recognized,
> > among them Bundle-SymbolicName.
> >
> > We could downtrace the error to the ManifestProcessor in
> > org.apache.aries.util-1.1.0, and while doing so, we discovered there was
> > already a bug logged describing almost exactly the same situation:
> > https://issues.apache.org/jira/browse/ARIES-958.
> >
> > Although this bug has already been resolved for quite some time, it
> hasn't
> > been released yet. Is there a chance util-1.1.1 will be available soon?
> >
> > kind regards,
> >
> > Tom
>

Re: Subsystem bundle's manifest headers not read correctly

Posted by David Bosschaert <da...@gmail.com>.
I'm planning to do a release of Aries Async services sometime next
week. I can do Aries Util 1.1.1 then as well if nobody beats me to
it...

David

On 27 July 2015 at 17:16, Tom Aerden <to...@aca-it.be> wrote:
> Hi,
>
> we're trying to deploy a subsystem generated by maven esa plugin, but when
> parsing the bundle manifests, some attributes are not recognized. I.e while
> we're adding com.springsource.org.aspectj.weaver as a bundle to our
> subsystem, all headers after "Name: org/aspectj/weaver/" are not recognized,
> among them Bundle-SymbolicName.
>
> We could downtrace the error to the ManifestProcessor in
> org.apache.aries.util-1.1.0, and while doing so, we discovered there was
> already a bug logged describing almost exactly the same situation:
> https://issues.apache.org/jira/browse/ARIES-958.
>
> Although this bug has already been resolved for quite some time, it hasn't
> been released yet. Is there a chance util-1.1.1 will be available soon?
>
> kind regards,
>
> Tom