David Jencks wrote:
I'm seeing a lot of warnings like this:
[WARNING] Warning building bundle
org.apache.geronimo.modules:geronimo-naming-builder:bundle:3.0-SNAPSHOT
: Split package
schemaorg_apache_xmlbeans/javaname/org/apache/xmlbeans/impl/xb/xsdschema/Attribute
Use directive -split-package:=(merge-first|merge-last|error|first) on
Export/Private Package instruction to get rid of this warning
Package found in [Jar:geronimo-j2ee-builder,
Jar:org.apache.servicemix.bundles.xmlbeans, Jar:geronimo-service-builder]
Reference from
/Users/david/.m2/repository/org/apache/geronimo/framework/geronimo-service-builder/3.0-SNAPSHOT/geronimo-service-builder-3.0-SNAPSHOT.jar
Classpath [Jar:., Jar:geronimo-j2ee-builder,
Jar:geronimo-j2ee-schema, Jar:geronimo-deployment,
Jar:geronimo-system, Jar:geronimo-cli, Jar:geronimo-main,
Jar:commons-cli, Jar:geronimo-common, Jar:geronimo-kernel,
Jar:org.osgi.core, Jar:pax-logging-api, Jar:asm, Jar:asm-commons,
Jar:org.apache.servicemix.bundles.cglib, Jar:xbean-reflect,
Jar:org.apache.servicemix.bundles.xstream,
Jar:org.apache.servicemix.bundles.xpp3, Jar:geronimo-crypto,
Jar:org.apache.servicemix.bundles.commons-jexl,
Jar:org.apache.servicemix.bundles.commons-lang,
Jar:org.apache.servicemix.specs.jaxb-api-2.1,
Jar:org.apache.servicemix.specs.stax-api-1.0,
Jar:org.apache.servicemix.bundles.jaxb-impl,
Jar:org.apache.servicemix.specs.activation-api-1.1,
Jar:org.apache.servicemix.bundles.woodstox,
Jar:org.apache.servicemix.bundles.xmlbeans,
Jar:org.apache.servicemix.bundles.xmlresolver,
Jar:geronimo-schema-jee_5, Jar:geronimo-schema-j2ee_1.4,
Jar:geronimo-service-builder,
Jar:geronimo-javaee-deployment_1.1MR3_spec, Jar:geronimo-j2ee,
Jar:geronimo-management, Jar:geronimo-j2ee-management_1.1_spec,
Jar:geronimo-deploy-config, Jar:geronimo-annotation_1.0_spec,
Jar:geronimo-ejb_3.1_spec, Jar:geronimo-jpa_2.0_spec,
Jar:geronimo-servlet_3.0_spec, Jar:xbean-finder, Jar:geronimo-naming,
Jar:xbean-naming, Jar:geronimo-jta_1.1_spec, Jar:geronimo-el_1.0_spec,
Jar:geronimo-interceptor_3.0_spec,
Jar:geronimo-j2ee-connector_1.6_spec, Jar:geronimo-jacc_1.1_spec,
Jar:geronimo-jaspic_1.0_spec, Jar:geronimo-javamail_1.4_mail,
Jar:geronimo-jaxrpc_1.1_spec, Jar:geronimo-jaxr_1.0_spec,
Jar:geronimo-jms_1.1_spec, Jar:geronimo-jsp_2.1_spec,
Jar:geronimo-concurrent_1.0_spec, Jar:geronimo-ws-metadata_2.0_spec,
Jar:geronimo-jaxws_2.1_spec, Jar:geronimo-activation_1.1_spec,
Jar:geronimo-saaj_1.3_spec, Jar:jstl, Jar:myfaces-api,
Jar:geronimo-jdbc, Jar:geronimo-config-groovy-transformer,
Jar:groovy-all-minimal, Jar:geronimo-transformer, Jar:sxc-jaxb,
Jar:sxc-runtime, Jar:org.apache.servicemix.bundles.jline,
Jar:org.apache.felix.configadmin, Jar:slf4j-api]
Looking in geronimo-service-builder jar I see that the core xmlbeans
files in e.g.
schemaorg_apache_xmlbeans/javaname/org/apache/xmlbeans/impl/xb/xsdschema
have been copied into our jar by the felix bundle plugin.
Is anyone else seeing this?
I'm getting fed up with the bizarre behavior of the bundle plugin and
wonder if we should try forking it and preventing our copy from
dragging in the kitchen sink from dependencies. Maybe we could make
it handle scope so the pom of bundleizing projects are usable too.
Maybe we could make it fail on split packages too.
I'm getting a bit fed up also. A lot of the time I've been spending in
getting the plugins to build has been in getting the bundle plugin in
create the bundle in the form that we need. I'm constantly running into
issues like this one where it produces what I think needs to be
produced, but then discover after the fact that it's doing something
extraneous that breaks something else. Then it's back on the roller
coaster to find the combination that gives the correct result.
Rick
david jencks
