I'm trying to Maven-ize an EE application. I'm close to having everything deploy without problems, but I've run into an issue I can't figure out. Specifically, I need to add some Dependencies to the web project's MANIFEST.MF, in accordance with AS7 classloading rules. No matter what I do, I cannot get Eclipse/Maven to include the Dependencies in the manifest file. I've tried this:
{code:xml}
<plugin>
<groupId>org.maven.apache.plugins</groupId>
<artifactId>maven-war-plugin</artifactId>
<version>2.2</version>
<configuration>
<archive>
<manifestEntries>
<Dependencies>javax.faces.api, org.joda.time, org.jboss.dmr, org.jboss.as.controller-client</Dependencies>
</manifestEntries>
</archive>
</configuration>
</plugin>
{code}
I've also tried this, with my existing MANIFEST.MF:
{code:xml}
<plugin>
<groupId>org.maven.apache.plugins</groupId>
<artifactId>maven-eclipse-plugin</artifactId>
<version>2.9</version>
<configuration>
<manifest>${basedir}/src/main/resources/META-INF/MANIFEST.MF</manifest>
</configuration>
</plugin>
{code}
Neither works; I get a default MANIFEST.MF in both cases. Any ideas how to fix this?
D'oh! Wrong groupId...
Of course, the real WTF is that m2eclipse didn't complain that I was trying to use a non-existent plugin...