Bug submitted https://bugs.eclipse.org/bugs/show_bug.cgi?id=460895

Hope it's descriptive, let me know if you need sth more.

Cheers

On Wed, Feb 25, 2015 at 1:32 PM, Dimitris Mandalidis <[email protected]>
wrote:

> Workaround and maven archiver plugin update did the work! Thanks! I ll
> create the bug in the next couple of days.
>
> Thanks again
> Στις 25 Φεβ 2015 1:27 π.μ., ο χρήστης "Fred Bricon" <[email protected]>
> έγραψε:
>
> Ok, so missing (filtered) resources is a bug in m2e-wtp, can you please
>> open a ticket in BugZilla[1]?
>>
>> As a workaround, you can move your src/main/resources/APP-INF folder
>> to  src/main/application/APP-INF/ and enable filtering  in
>>                 <artifactId>maven-ear-plugin</artifactId>
>>                 <configuration>
>>                   <filtering>true</true>
>>
>> <generateApplicationXml>true</generateApplicationXml>
>>                         <version>7</version>
>>
>> As for the missing MANIFEST entries, I suggest you install
>> m2eclipse-mavenarchiver 0.17.0 from [2]
>>
>>
>> [1] https://bugs.eclipse.org/bugs/enter_bug.cgi?product=M2E-WTP
>> [2]
>> http://repo1.maven.org/maven2/.m2e/connectors/m2eclipse-mavenarchiver/0.17.0/N/LATEST/
>>
>> Fred
>>
>> On Tue, Feb 24, 2015 at 8:31 AM, Dimitris Mandalidis <[email protected]>
>> wrote:
>>
>>> 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
>>>
>>> _______________________________________________
>>> m2e-users mailing list
>>> [email protected]
>>> To change your delivery options, retrieve your password, or unsubscribe
>>> from this list, visit
>>> https://dev.eclipse.org/mailman/listinfo/m2e-users
>>>
>>
>>
>>
>> --
>> "Have you tried turning it off and on again" - The IT Crowd
>>
>> _______________________________________________
>> m2e-users mailing list
>> [email protected]
>> To change your delivery options, retrieve your password, or unsubscribe
>> from this list, visit
>> https://dev.eclipse.org/mailman/listinfo/m2e-users
>>
>
_______________________________________________
m2e-users mailing list
[email protected]
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/m2e-users

Reply via email to