-
1. Re: JBoss WS Dependencies with Maven ending up with truncated MANIFEST.MF
ahw-dev Mar 20, 2012 1:09 PM (in response to ahw-dev)By the way here is my Maven build section:
<build> <finalName>rich-test</finalName> <plugins> <plugin> <artifactId>maven-compiler-plugin</artifactId> <version>2.3.2</version> </plugin> <plugin> <artifactId>maven-war-plugin</artifactId> <version>2.1.1</version> <configuration> <archive> <manifestFile>src/main/resources/META-INF/MANIFEST.MF</manifestFile> <!-- <manifestEntries> <Dependencies>${jboss.dependencies}</Dependencies> </manifestEntries> --> </archive> </configuration> </plugin> </plugins> </build> It doesn't matter whether i try and include a key/value pair as an entry or specify a pre-created MANIFEST.MF file. In either circumstance Maven truncates the Dependencies line.
-
2. Re: JBoss WS Dependencies with Maven ending up with truncated MANIFEST.MF
asoldano Mar 20, 2012 1:16 PM (in response to ahw-dev)This looks like a limitation in the maven war/jar plugin (I assume that's what you're using).
As far as workarounds are concerned, I would suggest having a look at https://docs.jboss.org/author/display/AS71/Class+Loading+in+AS7 , in particular the section on using a custom jboss-deployment-structure.xml for setting the module dependencies.
Modifying the org.jboss.ws.cxf.jbossws-cxf-client module.xml is also going to work (of course it would affect any other deployment you declared that dependency in), but of course you changes are being overwritten if you upgrade jbossws.
-
3. Re: JBoss WS Dependencies with Maven ending up with truncated MANIFEST.MF
ahw-dev Mar 20, 2012 1:30 PM (in response to asoldano)Thanks for the fast response. I will play around wth the jboss-deployment-structure.xml file and see if I can solve my problem that way.
-
4. Re: JBoss WS Dependencies with Maven ending up with truncated MANIFEST.MF
ahw-dev Mar 20, 2012 2:10 PM (in response to asoldano)I was able to solve the Maven MANIFEST (bug?) by adding the dependencies to the jboss-deployment-structure.xml file, and am updating this in case Google brings anyone else here.
<jboss-deployment-structure>
<!-- Make sub deployments isolated by default, so they cannot see each others classes without a Class-Path entry -->
<ear-subdeployments-isolated>true</ear-subdeployments-isolated>
<!-- This corresponds to the top level deployment. For a war this is the war's module, for an ear -->
<!-- This is the top level ear module, which contains all the classes in the EAR's lib folder -->
<deployment>
<!-- Exclusions allow you to prevent the server from automatically adding some dependencies
<exclusions>
<module name="org.javassist" />
</exclusions>
-->
<!-- This allows you to define additional dependencies, it is the same as using the Dependencies: manifest attribute -->
<dependencies>
<module name="org.jboss.ws.cxf.jbossws-cxf-client services export" />
<module name="org.apache.ws.xmlschema services export" />
<module name="org.apache.ws.security services export" />
</dependencies>
<!-- These add additional classes to the module. In this case it is the same as including the jar in the EAR's lib directory
<resources>
<resource-root path="my-library.jar" />
</resources>
-->
</deployment>
</jboss-deployment-structure>