Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[m2e-users] m2e EAR deploy to Wildfly

Hi all,

I think this is the right place to start from to find what's the source of my problems. I 'm using Eclipse Luna 4.4.1 with the bundled m2e 1.5.0.20140606-0033, and I 'm trying to deploy an .ear which contains 3 ejb jars and a war to Wildfly using the connector from Jboss tools (3.0.1.Final-v20141209-0156-B106). If run from outside eclipse, the produced .ear gets deployed successfully.

Resources in the .ear are filtered as follows :

        <resources>
            <resource>
                <directory>src/main/resources/APP-INF</directory>
                <targetPath>${project.build.directory}/${project.build.finalName}/APP-INF</targetPath>
            </resource>
            <resource>
                <directory>src/main/resources/META-INF</directory>
                <targetPath>${project.build.directory}/${project.build.finalName}/META-INF</targetPath>
                <includes>
                    <include>jboss-deployment-structure.xml</include>
                    <include>jboss-ejb-client.xml</include>
                    <include>log4j.properties</include>
                </includes>
                <filtering>true</filtering>
            </resource>
        </resources>

...and the relevant configuration on the .ear generation is :

            <plugin>
                <artifactId>maven-ear-plugin</artifactId>
                <configuration>
                <generateApplicationXml>true</generateApplicationXml>
                    <version>7</version>
                    <defaultLibBundleDir>APP-INF/lib</defaultLibBundleDir>
                    <displayName>ApplicationName</displayName>
                    <modules>
                        <ejbModule>
                            <groupId>net.example.foo</groupId>
                            <artifactId>foo-ejb</artifactId>
                        </ejbModule>
                        <webModule>
                            <groupId>net.example.foo</groupId>
                            <artifactId>foo-web</artifactId>                            
                            <contextRoot>foo</contextRoot>
                        </webModule>

foo-web and foo-ejb archive generation should add a manifest as follows : (added in maven-jar and maven-war plugins' configuration)

                    <archive>
                        <manifestEntries>
                            <Dependencies>org.apache.xerces services</Dependencies>
                        </manifestEntries>
                    </archive>

foo-ejb, foo-ear and foo-war are open in eclipse at the time I 'm trying to deploy. My problem so far are :

- foo-ear filtered resources are not end up in wildfly deployment directory
-- they don't even exist in m2e-wtp/ear-resources
- foo-ejb and foo-web MANIFEST.MF doesn't include the xerces dependency

Can you give a hand? 

Dimitris

Back to the top