I am using Bundlor 1.1.2.RELEASE and trying to generate manifests for some blueprint projects.
Consider this simple test setup:
A project with only the following blueprint.xml file in resources/META-INF/ and no source or packages.
Note that the namespace links have been removed because unfortunately the forum does not allow to post links outside eclipse.org until I post 5 messages.
<blueprint xmlns="... blueprint namespace ..."
xmlns:xsi="... XMLSchema namespace ..."
xmlns:context="... spring context namespace... "
xsi:schemaLocation="... blueprint and spring context namespaces ..."
default-activation="eager">
<context:component-scan base-package="net.test.impl"/>
<context:annotation-config />
<bean id="entityManagerFactory"
class="org.springframework.orm.jpa.LocalContainerEntityManagerFactoryBean"/>
</blueprint>
Generating the manifest (either inside Eclipse or with a Maven build) creates this MANIFEST.MF:
Manifest-Version: 1.0
Tool: Bundlor 1.1.2.RELEASE
Import-Package: net.test.impl
which is missing the org.springframework.orm.jpa import.
Now changing only the first line of the blueprint.xml to the springframework namespace:
<blueprint xmlns="... springframework namespace ..."
xmlns:xsi="... XMLSchema namespace ..."
xmlns:context="... spring context namespace... "
xsi:schemaLocation="... blueprint and spring context namespaces ..."
default-activation="eager">
<context:component-scan base-package="net.test.impl"/>
<context:annotation-config />
<bean id="entityManagerFactory"
class="org.springframework.orm.jpa.LocalContainerEntityManagerFactoryBean"/>
</blueprint>
creates the correct manifest:
Manifest-Version: 1.0
Tool: Bundlor 1.1.2.RELEASE
Import-Package: net.test.impl,org.springframework.orm.jpa
The same happens with every tag in my blueprint files, only the package from the "context:component-scan" tag is picked up.
Is there any workaround to this?
[Updated on: Tue, 20 November 2012 13:17]
Report message to a moderator
] 
Search
Help
Register
Login
Home
