Announcement Announcement Module
Collapse
No announcement yet.
Bundlor 'manifest' goal is gone? Page Title Module
Move Remove Collapse
X
Conversation Detail Module
Collapse
  • Filter
  • Time
  • Show
Clear All
new posts

  • Bundlor 'manifest' goal is gone?

    Hi, I tried RC1 today with a maven project, it works just fine.

    The thing is that it only generates the manifest file in the output directory (which seem to be the default according to the documentation). Now my problem is that my project is in eclipse, it has the OSGi bundle nature, and requires a Manifest.mf under META-INF/.

    Now, in the previous versions/milestones, I would have called the 'manifest' goal after bundlor finished doing its thing. Like that:

    Code:
    <plugin>
    	<groupId>com.springsource.bundlor</groupId>
    	<artifactId>com.springsource.bundlor.maven</artifactId>
    	<version>1.0.0.M5</version>
    	<configuration>
    		<failOnWarnings>false</failOnWarnings>
    		<removeNullHeaders>true</removeNullHeaders>
    		<outputManifest>${basedir}/META-INF/MANIFEST.MF</outputManifest>
    	</configuration>
    	<executions>
    		<execution>
    			<id>bundle-manifest</id>
    			<phase>package</phase>
    			<goals>
    				<goal>manifest</goal>
    				<goal>transform</goal>
    			</goals>
    		</execution>
    	</executions>
    </plugin>
    Now bundlor seem to have only one goal, which outputs one Manifest, in ${project.build.outputDirectory}. Is that so? Do I have to copy it with some ant execution commands? How do people deal with this reality?

    Thanks for your answers.

    JS.

  • #2
    New documentation for the 1.0.0.RELEASE version of the plugin is available here:
    http://static.springsource.org/s2-bu...ml#usage.maven
    Last edited by blahb; Jun 11th, 2010, 09:52 PM.

    Comment

    Working...
    X