You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cayenne.apache.org by Eshan Sudharaka <es...@gmail.com> on 2011/06/24 02:46:11 UTC
Import-Package header issue
Hi Ksenia ,
I get some help from felix guys and did some changes (remove all
unnecessary third party dependencies , add required bundles header and keep
import package and export package default and change felix version to the
latest one). Once we add all required bundles in to required bundle header
felix is adding all necessary imports to the bundle. In this case it seems
imports is not working.
Actually i have a question regarding import header. As i understood when we
mention a bundle in import header it looks existing manifests files in jar
files is eclipse/plugin folder and the jar files existing in my bundle (
target/dependency folder ) ? And the plugin is compile with out those
import dependencies which are created by felix plugin in import package
header. So is it trying to resolve relative dependencies ?
eg : bundle A require bindle C and when we I use bundle A should i add
bindle C as well ? i think it is not since A has already resolved it's
dependencies.
when i delete that import package header and run the plugin as eclipse
application it is working.
--
*~Thanks & Regards~*
***
*
P.A.Eshan Sudharaka
Dept of Computer Science and Engineering
University of Moratuwa
Sri Lanka
http://esudharaka.blogspot.com/
Re: Import-Package header issue
Posted by Eshan Sudharaka <es...@gmail.com>.
This is solved. According to
http://felix.apache.org/site/apache-felix-maven-bundle-plugin-bnd.html i
added osgi dependencies and then it generates manifest file correctly. Still
wondering how this matters.
<dependency>
<groupId>org.osgi</groupId>
<artifactId>osgi_R4_core</artifactId>
<version>1.0</version>
<scope>provided</scope>
<optional>true</optional>
</dependency>
<dependency>
<groupId>org.osgi</groupId>
<artifactId>osgi_R4_compendium</artifactId>
<version>1.0</version>
<scope>provided</scope>
<optional>true</optional>
</dependency>
On Fri, Jun 24, 2011 at 9:49 AM, Eshan Sudharaka <es...@gmail.com>wrote:
> I trued to remove those import packages by using negation like bellow.
>
> <Import-Package>
> !EDU.oswego.cs.dl.util.concurrent,
> !bsh,
> !org.apache.avalon.framework.logger,
> !org.eclipse.osgi.service.systembundle,
> !org.eclipse.swt.ole.win32,
> !com.sun.java.swing.plaf.windows,
>
> !com.werken.xpath,
> !javax.jms,
> !org.apache.bcel.*,
> !org.jdom.*,
> !org.jivesoftware.smackx.debugger,
> !sun.security.action,
> !org.eclipse.osgi.service.systembundle,
> *
> </Import-Package>
> And still it gives me the error and in manifest file some of packages are
> still exist even i used negation.
>
> On Fri, Jun 24, 2011 at 6:16 AM, Eshan Sudharaka <es...@gmail.com>wrote:
>
>> Hi Ksenia ,
>> I get some help from felix guys and did some changes (remove all
>> unnecessary third party dependencies , add required bundles header and keep
>> import package and export package default and change felix version to the
>> latest one). Once we add all required bundles in to required bundle header
>> felix is adding all necessary imports to the bundle. In this case it seems
>> imports is not working.
>>
>> Actually i have a question regarding import header. As i understood when
>> we mention a bundle in import header it looks existing manifests files in
>> jar files is eclipse/plugin folder and the jar files existing in my bundle (
>> target/dependency folder ) ? And the plugin is compile with out those
>> import dependencies which are created by felix plugin in import package
>> header. So is it trying to resolve relative dependencies ?
>> eg : bundle A require bindle C and when we I use bundle A should i
>> add bindle C as well ? i think it is not since A has already resolved it's
>> dependencies.
>>
>> when i delete that import package header and run the plugin as eclipse
>> application it is working.
>>
>> --
>> *~Thanks & Regards~*
>> ***
>> *
>> P.A.Eshan Sudharaka
>> Dept of Computer Science and Engineering
>> University of Moratuwa
>> Sri Lanka
>> http://esudharaka.blogspot.com/
>>
>>
>
>
> --
> *~Thanks & Regards~*
> ***
> *
> P.A.Eshan Sudharaka
> Dept of Computer Science and Engineering
> University of Moratuwa
> Sri Lanka
> http://esudharaka.blogspot.com/
>
>
--
*~Thanks & Regards~*
***
*
P.A.Eshan Sudharaka
Dept of Computer Science and Engineering
University of Moratuwa
Sri Lanka
http://esudharaka.blogspot.com/
Re: Import-Package header issue
Posted by Eshan Sudharaka <es...@gmail.com>.
I trued to remove those import packages by using negation like bellow.
<Import-Package>
!EDU.oswego.cs.dl.util.concurrent,
!bsh,
!org.apache.avalon.framework.logger,
!org.eclipse.osgi.service.systembundle,
!org.eclipse.swt.ole.win32,
!com.sun.java.swing.plaf.windows,
!com.werken.xpath,
!javax.jms,
!org.apache.bcel.*,
!org.jdom.*,
!org.jivesoftware.smackx.debugger,
!sun.security.action,
!org.eclipse.osgi.service.systembundle,
*
</Import-Package>
And still it gives me the error and in manifest file some of packages are
still exist even i used negation.
On Fri, Jun 24, 2011 at 6:16 AM, Eshan Sudharaka <es...@gmail.com>wrote:
> Hi Ksenia ,
> I get some help from felix guys and did some changes (remove all
> unnecessary third party dependencies , add required bundles header and keep
> import package and export package default and change felix version to the
> latest one). Once we add all required bundles in to required bundle header
> felix is adding all necessary imports to the bundle. In this case it seems
> imports is not working.
>
> Actually i have a question regarding import header. As i understood when
> we mention a bundle in import header it looks existing manifests files in
> jar files is eclipse/plugin folder and the jar files existing in my bundle (
> target/dependency folder ) ? And the plugin is compile with out those
> import dependencies which are created by felix plugin in import package
> header. So is it trying to resolve relative dependencies ?
> eg : bundle A require bindle C and when we I use bundle A should i add
> bindle C as well ? i think it is not since A has already resolved it's
> dependencies.
>
> when i delete that import package header and run the plugin as eclipse
> application it is working.
>
> --
> *~Thanks & Regards~*
> ***
> *
> P.A.Eshan Sudharaka
> Dept of Computer Science and Engineering
> University of Moratuwa
> Sri Lanka
> http://esudharaka.blogspot.com/
>
>
--
*~Thanks & Regards~*
***
*
P.A.Eshan Sudharaka
Dept of Computer Science and Engineering
University of Moratuwa
Sri Lanka
http://esudharaka.blogspot.com/