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

@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

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.

---

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

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

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

I agree with the above statement. Good point!!

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