Page 2 of 2 FirstFirst 12
Results 11 to 16 of 16

Thread: Bundlor 1.0.0.RC1: MANIFEST.MF is not in the jar

  1. #11
    Join Date
    Dec 2005
    Location
    Philadelphia, PA, USA
    Posts
    228

    Default

    @Ben,

    This would work great. I will try latest snapshot to confirm.

    As for STS - is there a way for STS to pick up a version from some external source vs. template.mf explicit value? Otherwise manifest generated by STS will differ from one generated by the build be that ant or maven.

    Quote Originally Posted by Ben Hale View Post
    If you are using STS which automatically generates your manifests you must specify both a Bundle-SymbolicName and a Bundle-Version or the generated manifest will have errors in it.
    Thanks
    Dmitry

  2. #12
    Join Date
    Nov 2009
    Posts
    12

    Default

    @Ben
    It sounds good for me too. I'll try it.
    Thanks.

  3. #13

    Default

    I just upgraded our parent-pom from bundlor 1.0.0.M6 to 1.0.0.RELEASE using the following config.

    Code:
    			<plugin>
    				<groupId>com.springsource.bundlor</groupId>
    				<artifactId>com.springsource.bundlor.maven</artifactId>
    				<version>1.0.0.RELEASE</version>
    				<configuration>
    					<failOnWarnings>false</failOnWarnings>
    					<removeNullHeaders>true</removeNullHeaders>
    					<manifestTemplatePath>template.mf</manifestTemplatePath>
    					<outputPath>src/main/resources/</outputPath>
    				</configuration>
    				<!-- generate the manifest automatically during packaging -->
    				<executions>
    					<execution>
    						<id>bundlor</id>
    						<goals>
    							<goal>bundlor</goal>
    						</goals>
    					</execution>
    				</executions>
    			</plugin>
    			<plugin>
    				<groupId>org.apache.maven.plugins</groupId>
    				<artifactId>maven-jar-plugin</artifactId>
    				<configuration>
    					<archive>
    						<manifestFile>src/main/resources/META-INF/MANIFEST.MF</manifestFile>
    					</archive>
    				</configuration>
    			</plugin>
    We're using a pom-first approach where properties are defined in the pom.xml and reused in template.mf. This template.mf is then used by maven to generate a MANIFEST.MF which shall be used inside STS (for deployment into dm server) and be put into the jar (for which we now use the maven-jar-plugin)

    cheers
    Alex

  4. #14
    Join Date
    Oct 2010
    Posts
    3

    Default

    if a BSN or BV is specified in the Maven configuration it overrides anything specified in the template.

  5. #15
    Join Date
    Dec 2010
    Posts
    4

    Default

    I agree with the above statement. Good point!!

  6. #16
    Join Date
    Dec 2010
    Posts
    4

    Default

    Different people have different points of view. That’s why we have different opinions.
    You may use Bing or Google to have a try.



    To see more, check here:
    http://www.softpedia.com/get/Office-...peg-Free.shtml

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •