I am running into issues with my artifacts having the Maven pom.* files in a "META-INF" directory and files such as the Manifest.MF, ejb-jar.xml, etc. in a "meta-inf" directory.
I have created an EJB jar that when I look at it in WinZip has the following: ... class files ... meta-inf/Manifest.mf meta-inf/ejb-jar.xml meta-inf/jboss.xml META-INF/maven/.../pom.properties META-INF/maven/.../pom.xml When the files are extracted with Winzip only the META-INF directory gets created with all the meta-inf files in it. However, when deploying in JBoss the "meta-inf" files are ignored and thus the EJBs are not deployed. I posted this on the user list and received this as an answer: http://jira.codehaus.org/browse/MOJO-377 http://jira.codehaus.org/browse/MOJO-377 The different case meta-inf directories are also happening with everything that I build. So far it has only affected my EJB deployments. I have tried <addMavenDescriptor>false</addMavenDescriptor> but this does not work. I did see a post in regards to this same issue with EARs and was noted as can't reproduce. -- View this message in context: http://www.nabble.com/META-INF-and-meta-inf-tf2017373.html#a5546417 Sent from the Apache Maven Developers List forum at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
