Am 03.01.2008 um 17:41 schrieb Stuart McCulloch:

On 04/01/2008, Stuart McCulloch <[EMAIL PROTECTED]> wrote:
On 04/01/2008, Ingo Meyer <[EMAIL PROTECTED]> wrote:
Hi,

since today afternoon all my pax-projects are not build anymore
without any changes from myself.

The bundle goal is claiming about missing  references:

[ERROR] Error building bundle xxx:yyy:bundle: 1.0 : Unresolved
references to [org.apache.activemq, org.apache.activemq.command,
org.apache.activemq.pool, org.springframework.jms.listener,
org.springframework.jms.listener.adapter] by class(es) on the Bundle-
Classpath[Jar:dot]: []
[ERROR] Error(s) found in bundle configuration

I ran some tests locally and if Import-Package ends with a * clause then afaik you shouldn't see this error - could you send the BND instructions
that cause this problem? (ie. the osgi.bnd file)

yes, here it is. It is generated by my generator (MDD, oAW), that's why I always have everything there:

#-----------------------------------------------------------------
# Use this file to add customized Bnd instructions for the bundle
#-----------------------------------------------------------------
Bundle-SymbolicName: ${bundle.symbolicName};singleton:=true
Import-Package: org.xxx.kunde.dtos;version=1.0, \
                                org.eclipse.swt.widgets, \
                                org.xxx.kunde.vo;version=1.0, \
                                org.eclipse.ui, \
                                org.eclipse.ui.part, \
                                
org.xxx.ui.tree.kundentree.abstr.provider;version=1.0, \
                                org.xxx.ui.view.kundentree.abstr;version=1.0, \
                                org.eclipse.core.runtime, \
                                org.xxx.kunde.beans.impl;version=1.0, \
                                org.eclipse.swt.graphics, \
                                org.xxx.kunde.dataservice;version=1.0, \
                                org.xxx.kunde.dtos.abstr;version=1.0, \
                                org.springframework.beans.factory, \
                                org.eclipse.jface.viewers, \
                                org.eclipse.jface.dialogs, \
                                org.xxx.kunde.beans;version=1.0, \
                                
org.springframework.core;version=${spring.version}, \
                                org.eclipse.core.commands.common, \
                                org.eclipse.jface.action, \
                                org.xxx.kunde.dtos.impl;version=1.0, \
                                org.xxx.kunde.beans.abstr;version=1.0, \
                                
org.springframework.beans;version=${spring.version}, \
                                org.eclipse.jface.resource, \
                                
org.springframework.context;version=${spring.version}, \
                                javax.jms;version=1.1, \
                                org.xxx.kunde.dtos.converter;version=0.1, \
                                org.eclipse.swt, \
                                org.springframework.jms.support.converter
Export-Package: org.xxx.ui.view.kundentree;version=1.0


this has nothing to do with Pax-Construct per se, but is due to the new version of BND (0.0.226) used in the current 1.0.0-SNAPSHOT of the maven- bundle-plugin which has additional code to scan your Spring-OSGi configuration for classes you
need to import/bundle (I believe this was contributed by Andy Piper?)

Ok, I understand that.

But I never needed the imports for the spring configuration since the spring-dm extender bundle always handles that correctly by itself.


have you tried adding these packages to your current Import-Package directive? (btw, do you set Import-Package to an explicit value or leave it as the default: *)

note that you can also turn off this new BND feature by adding:

    -plugin:

to the bundle's " osgi.bnd" file, or alternatively:

        <groupId>org.apache.felix</groupId>
        <artifactId>maven-bundle-plugin</artifactId>
        <configuration>
          <instructions>
            <_plugin/>
            <!--
              ....etc...
            -->
          </instructions>
        </configuration>

to your poms/compiled/pom.xml file to set this for all bundles

I will test that.

Thanks very much for that fast answer

HTH

The strange thing is that these classes are ony mentioned in my META-
INF/spring/bundle-context.xml

So I guess that something changed in pax so that not only .java
classes are evaluated, but also .xml.
Is this a wanted behaviour???

Please, please give me a tip how to avoid that, it stops my hole work!
If you need more informations please ask.


Thanks in advance,
Ingo

_______________________________________________
general mailing list
general@lists.ops4j.org
http://lists.ops4j.org/mailman/listinfo/general



--
Cheers, Stuart



--
Cheers, Stuart
_______________________________________________
general mailing list
general@lists.ops4j.org
http://lists.ops4j.org/mailman/listinfo/general

_______________________________________________
general mailing list
general@lists.ops4j.org
http://lists.ops4j.org/mailman/listinfo/general

Reply via email to