From: Andrea A. <and...@ge...> - 2012-11-29 16:37:51
|
On Thu, Nov 29, 2012 at 5:31 PM, Carlo Cancellieri <cca...@ho... > wrote: > We only need to configure the maven jar (or war) plugin into the pom as in > the shown into the examples: > > I report it again: > > <plugin> > <groupId>org.apache.maven.plugins</groupId> > <artifactId>maven-jar-plugin</artifactId> > <configuration> > <archive> > <manifest> > <addDefaultImplementationEntries>true</addDefaultImplementationEntries> > <addDefaultSpecificationEntries>true</addDefaultSpecificationEntries> > </manifest> > <manifestEntries> > <!-- custom entries --> > </manifestEntries> > </archive> > </configuration> > </plugin> > Ah ok, I missed it from the first mail. I agree with Justin, we should add an extra element in the manifest to recognize the GeoServer specific manifests, as other GeoServer unrelated jars will have a manifest too. Something like: <manifestEntries> ... <jarType>GeoServerExtensions</jarType> ... </manifestEntries> Instead of adding a custom section in each and every module pom file we should try to just put it in the extensions/community parent poms and check if they are inherited from the child pom: this way we should avoid duplication and maintenance Cheers Andrea -- == Our support, Your Success! Visit http://opensdi.geo-solutions.it for more information. == Ing. Andrea Aime @geowolf Technical Lead GeoSolutions S.A.S. Via Poggio alle Viti 1187 55054 Massarosa (LU) Italy phone: +39 0584 962313 fax: +39 0584 1660272 mob: +39 339 8844549 http://www.geo-solutions.it http://twitter.com/geosolutions_it ------------------------------------------------------- |