You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@felix.apache.org by CLEMENT Jean-Philippe <je...@fr.thalesgroup.com> on 2013/10/24 08:57:43 UTC
TR: maven-bundle-plugin issue with blueprint and inner-classes
Dear Felix Team,
It seems I found a bug (see below) in the Maven plugin. I'm not too sure which Jira project/component to select.
Is it a bug and in which project/component may I open it?
Regards,
JP
De : Achim Nierbeck [mailto:bcanhome@googlemail.com]
Envoyé : mercredi 23 octobre 2013 21:03
À : user@karaf.apache.org
Objet : Re: maven-bundle-plugin issue with blueprint and inner-classes
Hi JP,
you most likely found a bug :)
You'll need to issue it at the felix project, and most likely will also get a better answer there if
there is a workaround for this already :)
regards, Achim
2013/10/23 CLEMENT Jean-Philippe <je...@fr.thalesgroup.com>>
Dear experts,
I have an issue with the Maven Bundle plugin. It generates an invalid package when an inner class is used to instantiate a bean.
For instance the following blueprint:
<bean class="org.test.MyClass.MyPublicStaticInnerClass"/>
Generates the following entry in the Import-Package section:
Import-Package: org.test.MyClass
As MyClass is part of the bundle, no Import-Package entry should be generated.
Is there a workaround?
Regards,
JP
--
Apache Karaf <http://karaf.apache.org/> Committer & PMC
OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer & Project Lead
OPS4J Pax for Vaadin <http://team.ops4j.org/wiki/display/PAXVAADIN/Home> Commiter & Project Lead
blog <http://notizblog.nierbeck.de/>
Re: TR: maven-bundle-plugin issue with blueprint and inner-classes
Posted by Stuart McCulloch <mc...@gmail.com>.
On 24 Oct 2013, at 14:08, CLEMENT Jean-Philippe wrote:
> ... when I push the "create issue" button the dialog box opens with Felix as project.
seems to be a limitation of JIRA in that it doesn't pre-fill the component based on the current location :/
> No reference to Maven bundle plugin anywhere.
go to the 'Component/s' field and start typing 'Maven Bundle Plugin' and the right component will appear
> If I fill the version field, an error is displayed (Version with id '2.4.0' does not exist).
Felix has versions per-component, so type 'maven-bundle-plugin' and the relevant versions will appear
> How to select the bundle plugin?
>
> JP
>
> -----Message d'origine-----
> De : Stuart McCulloch [mailto:mcculls@gmail.com]
> Envoyé : jeudi 24 octobre 2013 14:26
> À : users@felix.apache.org
> Objet : Re: TR: maven-bundle-plugin issue with blueprint and inner-classes
>
> You can log the issue here: https://issues.apache.org/jira/browse/FELIX/component/12311143
>
> Remember to attach your test project so whoever picks it up can recreate the issue locally.
>
> On 24 Oct 2013, at 07:57, CLEMENT Jean-Philippe wrote:
>
>> Dear Felix Team,
>>
>> It seems I found a bug (see below) in the Maven plugin. I'm not too sure which Jira project/component to select.
>>
>> Is it a bug and in which project/component may I open it?
>>
>> Regards,
>> JP
>>
>>
>> De : Achim Nierbeck [mailto:bcanhome@googlemail.com] Envoyé : mercredi
>> 23 octobre 2013 21:03 À : user@karaf.apache.org Objet : Re:
>> maven-bundle-plugin issue with blueprint and inner-classes
>>
>> Hi JP,
>>
>> you most likely found a bug :)
>> You'll need to issue it at the felix project, and most likely will
>> also get a better answer there if there is a workaround for this
>> already :)
>>
>>
>> regards, Achim
>>
>> 2013/10/23 CLEMENT Jean-Philippe
>> <jean-philippe.clement@fr.thalesgroup.com<mailto:jean-philippe.clement
>> @fr.thalesgroup.com>>
>> Dear experts,
>>
>> I have an issue with the Maven Bundle plugin. It generates an invalid package when an inner class is used to instantiate a bean.
>>
>> For instance the following blueprint:
>> <bean class="org.test.MyClass.MyPublicStaticInnerClass"/>
>>
>> Generates the following entry in the Import-Package section:
>> Import-Package: org.test.MyClass
>>
>> As MyClass is part of the bundle, no Import-Package entry should be generated.
>>
>> Is there a workaround?
>>
>> Regards,
>> JP
>>
>>
>>
>> --
>>
>> Apache Karaf <http://karaf.apache.org/> Committer & PMC OPS4J Pax Web
>> <http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer & Project
>> Lead OPS4J Pax for Vaadin
>> <http://team.ops4j.org/wiki/display/PAXVAADIN/Home> Commiter & Project
>> Lead blog <http://notizblog.nierbeck.de/>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> For additional commands, e-mail: users-help@felix.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> For additional commands, e-mail: users-help@felix.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
For additional commands, e-mail: users-help@felix.apache.org
RE: TR: maven-bundle-plugin issue with blueprint and inner-classes
Posted by CLEMENT Jean-Philippe <je...@fr.thalesgroup.com>.
... when I push the "create issue" button the dialog box opens with Felix as project. No reference to Maven bundle plugin anywhere. If I fill the version field, an error is displayed (Version with id '2.4.0' does not exist).
How to select the bundle plugin?
JP
-----Message d'origine-----
De : Stuart McCulloch [mailto:mcculls@gmail.com]
Envoyé : jeudi 24 octobre 2013 14:26
À : users@felix.apache.org
Objet : Re: TR: maven-bundle-plugin issue with blueprint and inner-classes
You can log the issue here: https://issues.apache.org/jira/browse/FELIX/component/12311143
Remember to attach your test project so whoever picks it up can recreate the issue locally.
On 24 Oct 2013, at 07:57, CLEMENT Jean-Philippe wrote:
> Dear Felix Team,
>
> It seems I found a bug (see below) in the Maven plugin. I'm not too sure which Jira project/component to select.
>
> Is it a bug and in which project/component may I open it?
>
> Regards,
> JP
>
>
> De : Achim Nierbeck [mailto:bcanhome@googlemail.com] Envoyé : mercredi
> 23 octobre 2013 21:03 À : user@karaf.apache.org Objet : Re:
> maven-bundle-plugin issue with blueprint and inner-classes
>
> Hi JP,
>
> you most likely found a bug :)
> You'll need to issue it at the felix project, and most likely will
> also get a better answer there if there is a workaround for this
> already :)
>
>
> regards, Achim
>
> 2013/10/23 CLEMENT Jean-Philippe
> <jean-philippe.clement@fr.thalesgroup.com<mailto:jean-philippe.clement
> @fr.thalesgroup.com>>
> Dear experts,
>
> I have an issue with the Maven Bundle plugin. It generates an invalid package when an inner class is used to instantiate a bean.
>
> For instance the following blueprint:
> <bean class="org.test.MyClass.MyPublicStaticInnerClass"/>
>
> Generates the following entry in the Import-Package section:
> Import-Package: org.test.MyClass
>
> As MyClass is part of the bundle, no Import-Package entry should be generated.
>
> Is there a workaround?
>
> Regards,
> JP
>
>
>
> --
>
> Apache Karaf <http://karaf.apache.org/> Committer & PMC OPS4J Pax Web
> <http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer & Project
> Lead OPS4J Pax for Vaadin
> <http://team.ops4j.org/wiki/display/PAXVAADIN/Home> Commiter & Project
> Lead blog <http://notizblog.nierbeck.de/>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
For additional commands, e-mail: users-help@felix.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
For additional commands, e-mail: users-help@felix.apache.org
Re: TR: maven-bundle-plugin issue with blueprint and inner-classes
Posted by Stuart McCulloch <mc...@gmail.com>.
You can log the issue here: https://issues.apache.org/jira/browse/FELIX/component/12311143
Remember to attach your test project so whoever picks it up can recreate the issue locally.
On 24 Oct 2013, at 07:57, CLEMENT Jean-Philippe wrote:
> Dear Felix Team,
>
> It seems I found a bug (see below) in the Maven plugin. I'm not too sure which Jira project/component to select.
>
> Is it a bug and in which project/component may I open it?
>
> Regards,
> JP
>
>
> De : Achim Nierbeck [mailto:bcanhome@googlemail.com]
> Envoyé : mercredi 23 octobre 2013 21:03
> À : user@karaf.apache.org
> Objet : Re: maven-bundle-plugin issue with blueprint and inner-classes
>
> Hi JP,
>
> you most likely found a bug :)
> You'll need to issue it at the felix project, and most likely will also get a better answer there if
> there is a workaround for this already :)
>
>
> regards, Achim
>
> 2013/10/23 CLEMENT Jean-Philippe <je...@fr.thalesgroup.com>>
> Dear experts,
>
> I have an issue with the Maven Bundle plugin. It generates an invalid package when an inner class is used to instantiate a bean.
>
> For instance the following blueprint:
> <bean class="org.test.MyClass.MyPublicStaticInnerClass"/>
>
> Generates the following entry in the Import-Package section:
> Import-Package: org.test.MyClass
>
> As MyClass is part of the bundle, no Import-Package entry should be generated.
>
> Is there a workaround?
>
> Regards,
> JP
>
>
>
> --
>
> Apache Karaf <http://karaf.apache.org/> Committer & PMC
> OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer & Project Lead
> OPS4J Pax for Vaadin <http://team.ops4j.org/wiki/display/PAXVAADIN/Home> Commiter & Project Lead
> blog <http://notizblog.nierbeck.de/>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
For additional commands, e-mail: users-help@felix.apache.org
Re: maven-bundle-plugin issue with blueprint and inner-classes
Posted by Peter Kriens <pe...@aqute.biz>.
Then your Blueprint is wrong, $ is a valid character so their Tclass is off. It is used by the compiler in certain places but there is no reason no to use it. I have classes with the name $!
I think we should be careful not to add too many options to bnd. I think a rule would be to remove any final package segment that starts with an upper case and is not fully upper case.
However, don't hold your breath ... this is low priority and I am very busy so a patch (with test cases) would be welcome.
https://github.com/bndtools/bnd/issues/423
Kind regards,
Peter Kriens
On 24 okt. 2013, at 16:21, CLEMENT Jean-Philippe <je...@fr.thalesgroup.com> wrote:
> Blueprint XML does not accept $ in the class attribute: "The value 'org.test.MyClass$MyPublicStaticInnerClass' of attribute 'class' on element 'bean' is not valid with respect to its type, 'Tclass'".
>
> Of course the cleanest way is to remove the inner class. In my case the bundle is rather small so I override the Import-Package section.
>
> Package names usually starts with a lowercase character, but this won't be enough to put this as default behavior. Maybe a kind of "strict package" option might be added to consider names beginning with an uppercase character to be a class rather than a package. Does it make sense?
>
> JP
>
> -----Message d'origine-----
> De : Peter Kriens [mailto:peter.kriens@aqute.biz]
> Envoyé : jeudi 24 octobre 2013 16:04
> À : users@felix.apache.org
> Objet : Re: maven-bundle-plugin issue with blueprint and inner-classes
>
> You can try to use a $ instead of a . , org.test.MyClass$MyPublicStaticInnerClass. Class.forName supports this so I guess Spring will be ok. The problem is that the org.test.MyClass.MyPublicStaticInnerClass in this form (as a String since it is in XML) is indistinguishable to be an inner class or a package. This is tricky to detect since it is a known ambiguous construct. In Java class the actual names are separated by $ for exactly this reason. However, Spring XML is just a text file with strings and we use XSLT to find the class names. So don't count on this being fixed any time soon ...
>
> Of course the simplest workaround is of course to not make it an inner class? :-)
>
> Kind regards,
>
> Peter Kriens
>
>
>
> On 24 okt. 2013, at 08:57, CLEMENT Jean-Philippe <je...@fr.thalesgroup.com> wrote:
>
>> Dear Felix Team,
>>
>> It seems I found a bug (see below) in the Maven plugin. I'm not too sure which Jira project/component to select.
>>
>> Is it a bug and in which project/component may I open it?
>>
>> Regards,
>> JP
>>
>>
>> De : Achim Nierbeck [mailto:bcanhome@googlemail.com] Envoyé : mercredi
>> 23 octobre 2013 21:03 À : user@karaf.apache.org Objet : Re:
>> maven-bundle-plugin issue with blueprint and inner-classes
>>
>> Hi JP,
>>
>> you most likely found a bug :)
>> You'll need to issue it at the felix project, and most likely will
>> also get a better answer there if there is a workaround for this
>> already :)
>>
>>
>> regards, Achim
>>
>> 2013/10/23 CLEMENT Jean-Philippe
>> <jean-philippe.clement@fr.thalesgroup.com<mailto:jean-philippe.clement
>> @fr.thalesgroup.com>>
>> Dear experts,
>>
>> I have an issue with the Maven Bundle plugin. It generates an invalid package when an inner class is used to instantiate a bean.
>>
>> For instance the following blueprint:
>> <bean class="org.test.MyClass.MyPublicStaticInnerClass"/>
>>
>> Generates the following entry in the Import-Package section:
>> Import-Package: org.test.MyClass
>>
>> As MyClass is part of the bundle, no Import-Package entry should be generated.
>>
>> Is there a workaround?
>>
>> Regards,
>> JP
>>
>>
>>
>> --
>>
>> Apache Karaf <http://karaf.apache.org/> Committer & PMC OPS4J Pax Web
>> <http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer & Project
>> Lead OPS4J Pax for Vaadin
>> <http://team.ops4j.org/wiki/display/PAXVAADIN/Home> Commiter & Project
>> Lead blog <http://notizblog.nierbeck.de/>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> For additional commands, e-mail: users-help@felix.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> For additional commands, e-mail: users-help@felix.apache.org
>
RE: maven-bundle-plugin issue with blueprint and inner-classes
Posted by CLEMENT Jean-Philippe <je...@fr.thalesgroup.com>.
Added issue https://issues.apache.org/jira/browse/FELIX-4291 along with solution proposals.
JP
-----Message d'origine-----
De : CLEMENT Jean-Philippe [mailto:jean-philippe.clement@fr.thalesgroup.com]
Envoyé : jeudi 24 octobre 2013 16:21
À : users@felix.apache.org
Objet : RE: maven-bundle-plugin issue with blueprint and inner-classes
Blueprint XML does not accept $ in the class attribute: "The value 'org.test.MyClass$MyPublicStaticInnerClass' of attribute 'class' on element 'bean' is not valid with respect to its type, 'Tclass'".
Of course the cleanest way is to remove the inner class. In my case the bundle is rather small so I override the Import-Package section.
Package names usually starts with a lowercase character, but this won't be enough to put this as default behavior. Maybe a kind of "strict package" option might be added to consider names beginning with an uppercase character to be a class rather than a package. Does it make sense?
JP
-----Message d'origine-----
De : Peter Kriens [mailto:peter.kriens@aqute.biz] Envoyé : jeudi 24 octobre 2013 16:04 À : users@felix.apache.org Objet : Re: maven-bundle-plugin issue with blueprint and inner-classes
You can try to use a $ instead of a . , org.test.MyClass$MyPublicStaticInnerClass. Class.forName supports this so I guess Spring will be ok. The problem is that the org.test.MyClass.MyPublicStaticInnerClass in this form (as a String since it is in XML) is indistinguishable to be an inner class or a package. This is tricky to detect since it is a known ambiguous construct. In Java class the actual names are separated by $ for exactly this reason. However, Spring XML is just a text file with strings and we use XSLT to find the class names. So don't count on this being fixed any time soon ...
Of course the simplest workaround is of course to not make it an inner class? :-)
Kind regards,
Peter Kriens
On 24 okt. 2013, at 08:57, CLEMENT Jean-Philippe <je...@fr.thalesgroup.com> wrote:
> Dear Felix Team,
>
> It seems I found a bug (see below) in the Maven plugin. I'm not too sure which Jira project/component to select.
>
> Is it a bug and in which project/component may I open it?
>
> Regards,
> JP
>
>
> De : Achim Nierbeck [mailto:bcanhome@googlemail.com] Envoyé : mercredi
> 23 octobre 2013 21:03 À : user@karaf.apache.org Objet : Re:
> maven-bundle-plugin issue with blueprint and inner-classes
>
> Hi JP,
>
> you most likely found a bug :)
> You'll need to issue it at the felix project, and most likely will
> also get a better answer there if there is a workaround for this
> already :)
>
>
> regards, Achim
>
> 2013/10/23 CLEMENT Jean-Philippe
> <jean-philippe.clement@fr.thalesgroup.com<mailto:jean-philippe.clement
> @fr.thalesgroup.com>>
> Dear experts,
>
> I have an issue with the Maven Bundle plugin. It generates an invalid package when an inner class is used to instantiate a bean.
>
> For instance the following blueprint:
> <bean class="org.test.MyClass.MyPublicStaticInnerClass"/>
>
> Generates the following entry in the Import-Package section:
> Import-Package: org.test.MyClass
>
> As MyClass is part of the bundle, no Import-Package entry should be generated.
>
> Is there a workaround?
>
> Regards,
> JP
>
>
>
> --
>
> Apache Karaf <http://karaf.apache.org/> Committer & PMC OPS4J Pax Web
> <http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer & Project
> Lead OPS4J Pax for Vaadin
> <http://team.ops4j.org/wiki/display/PAXVAADIN/Home> Commiter & Project
> Lead blog <http://notizblog.nierbeck.de/>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
For additional commands, e-mail: users-help@felix.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
For additional commands, e-mail: users-help@felix.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
For additional commands, e-mail: users-help@felix.apache.org
RE: maven-bundle-plugin issue with blueprint and inner-classes
Posted by CLEMENT Jean-Philippe <je...@fr.thalesgroup.com>.
Blueprint XML does not accept $ in the class attribute: "The value 'org.test.MyClass$MyPublicStaticInnerClass' of attribute 'class' on element 'bean' is not valid with respect to its type, 'Tclass'".
Of course the cleanest way is to remove the inner class. In my case the bundle is rather small so I override the Import-Package section.
Package names usually starts with a lowercase character, but this won't be enough to put this as default behavior. Maybe a kind of "strict package" option might be added to consider names beginning with an uppercase character to be a class rather than a package. Does it make sense?
JP
-----Message d'origine-----
De : Peter Kriens [mailto:peter.kriens@aqute.biz]
Envoyé : jeudi 24 octobre 2013 16:04
À : users@felix.apache.org
Objet : Re: maven-bundle-plugin issue with blueprint and inner-classes
You can try to use a $ instead of a . , org.test.MyClass$MyPublicStaticInnerClass. Class.forName supports this so I guess Spring will be ok. The problem is that the org.test.MyClass.MyPublicStaticInnerClass in this form (as a String since it is in XML) is indistinguishable to be an inner class or a package. This is tricky to detect since it is a known ambiguous construct. In Java class the actual names are separated by $ for exactly this reason. However, Spring XML is just a text file with strings and we use XSLT to find the class names. So don't count on this being fixed any time soon ...
Of course the simplest workaround is of course to not make it an inner class? :-)
Kind regards,
Peter Kriens
On 24 okt. 2013, at 08:57, CLEMENT Jean-Philippe <je...@fr.thalesgroup.com> wrote:
> Dear Felix Team,
>
> It seems I found a bug (see below) in the Maven plugin. I'm not too sure which Jira project/component to select.
>
> Is it a bug and in which project/component may I open it?
>
> Regards,
> JP
>
>
> De : Achim Nierbeck [mailto:bcanhome@googlemail.com] Envoyé : mercredi
> 23 octobre 2013 21:03 À : user@karaf.apache.org Objet : Re:
> maven-bundle-plugin issue with blueprint and inner-classes
>
> Hi JP,
>
> you most likely found a bug :)
> You'll need to issue it at the felix project, and most likely will
> also get a better answer there if there is a workaround for this
> already :)
>
>
> regards, Achim
>
> 2013/10/23 CLEMENT Jean-Philippe
> <jean-philippe.clement@fr.thalesgroup.com<mailto:jean-philippe.clement
> @fr.thalesgroup.com>>
> Dear experts,
>
> I have an issue with the Maven Bundle plugin. It generates an invalid package when an inner class is used to instantiate a bean.
>
> For instance the following blueprint:
> <bean class="org.test.MyClass.MyPublicStaticInnerClass"/>
>
> Generates the following entry in the Import-Package section:
> Import-Package: org.test.MyClass
>
> As MyClass is part of the bundle, no Import-Package entry should be generated.
>
> Is there a workaround?
>
> Regards,
> JP
>
>
>
> --
>
> Apache Karaf <http://karaf.apache.org/> Committer & PMC OPS4J Pax Web
> <http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer & Project
> Lead OPS4J Pax for Vaadin
> <http://team.ops4j.org/wiki/display/PAXVAADIN/Home> Commiter & Project
> Lead blog <http://notizblog.nierbeck.de/>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
For additional commands, e-mail: users-help@felix.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
For additional commands, e-mail: users-help@felix.apache.org
Re: maven-bundle-plugin issue with blueprint and inner-classes
Posted by Peter Kriens <pe...@aqute.biz>.
You can try to use a $ instead of a . , org.test.MyClass$MyPublicStaticInnerClass. Class.forName supports this so I guess Spring will be ok. The problem is that the org.test.MyClass.MyPublicStaticInnerClass in this form (as a String since it is in XML) is indistinguishable to be an inner class or a package. This is tricky to detect since it is a known ambiguous construct. In Java class the actual names are separated by $ for exactly this reason. However, Spring XML is just a text file with strings and we use XSLT to find the class names. So don't count on this being fixed any time soon ...
Of course the simplest workaround is of course to not make it an inner class? :-)
Kind regards,
Peter Kriens
On 24 okt. 2013, at 08:57, CLEMENT Jean-Philippe <je...@fr.thalesgroup.com> wrote:
> Dear Felix Team,
>
> It seems I found a bug (see below) in the Maven plugin. I'm not too sure which Jira project/component to select.
>
> Is it a bug and in which project/component may I open it?
>
> Regards,
> JP
>
>
> De : Achim Nierbeck [mailto:bcanhome@googlemail.com]
> Envoyé : mercredi 23 octobre 2013 21:03
> À : user@karaf.apache.org
> Objet : Re: maven-bundle-plugin issue with blueprint and inner-classes
>
> Hi JP,
>
> you most likely found a bug :)
> You'll need to issue it at the felix project, and most likely will also get a better answer there if
> there is a workaround for this already :)
>
>
> regards, Achim
>
> 2013/10/23 CLEMENT Jean-Philippe <je...@fr.thalesgroup.com>>
> Dear experts,
>
> I have an issue with the Maven Bundle plugin. It generates an invalid package when an inner class is used to instantiate a bean.
>
> For instance the following blueprint:
> <bean class="org.test.MyClass.MyPublicStaticInnerClass"/>
>
> Generates the following entry in the Import-Package section:
> Import-Package: org.test.MyClass
>
> As MyClass is part of the bundle, no Import-Package entry should be generated.
>
> Is there a workaround?
>
> Regards,
> JP
>
>
>
> --
>
> Apache Karaf <http://karaf.apache.org/> Committer & PMC
> OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer & Project Lead
> OPS4J Pax for Vaadin <http://team.ops4j.org/wiki/display/PAXVAADIN/Home> Commiter & Project Lead
> blog <http://notizblog.nierbeck.de/>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
For additional commands, e-mail: users-help@felix.apache.org