jira-importer commented on issue #302: URL: https://github.com/apache/maven-ear-plugin/issues/302#issuecomment-2955276389
**[Fred Bricon](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=fbricon)** commented Hi, Benjamin's patch is exactly what we need for m2eclipse-wtp (I was about to propose the same kind of stuff). Currently, due to m2eclipse project resolution behavior (explained here : http://jira.codehaus.org/browse/MWAR-192?focusedCommentId=175406&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#action_175406), artifact.getFile() returns <workspace_project_path>/target/classes. That doesn't look good when trying to run **mvn package** from within eclipse. As you may know, or not, application.xml in eclipse WTP is currently generated using WTP's API. Since it's a source of countless issues, I've tried delegating to ear:generate-application-xml instead (more or less), but hit the <workspace_project_path>/target/classes bug. Quick resolution of this issue would help m2eclipse-wtp (at least) to move forward. Let me know if I can do anything to help. regards, Fred Bricon -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
