[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-4736) Add m2eclipse project-configurator for Seam projects

[Snjezana Peco (JIRA)]

    [ https://jira.jboss.org/jira/browse/JBIDE-4736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12481300#action_12481300 ] 

Snjezana Peco commented on JBIDE-4736:
--------------------------------------

> "EAR projects require more testing especially because there are some m2eclipse bugs that need to be fixed.I have sent the patches that, I hope, will be applied this weekend"
> Do you have a list of those issues so we can keep track ? 

https://issues.sonatype.org/browse/MNGECLIPSE-1564
and
http://archive.cargo.codehaus.org/lists/org.codehaus.m2eclipse.user/msg/4A7C683F.3000008@redhat.com 

Some changes in the m2eclipse's wtp plugin were made yesterday. I will test them as soon as I fix this issue.

> "The m2eclipse EAR configurator doesn't create application.xml, JBoss datasource and jboss-app.xml no mater if they are specified in maven-ear-plugin. I think we need to create these files."
> ...but the project-configurators at the plugin level shouldn't be creating actual project artifacts should they ? I would reckon that to be a common "contract" that the actual maven mojo plugins do the actual 
> artifact creation and the project-configurators just enables as much as possible as they can in the IDE. Otherwise running the maven build in the IDE will have sideeffects that won't happen when just running
> the maven build outside the IDE.

If creating these files is defined in maven-ear-plugin, Maven will create them in the Maven's output directory. They will be deployed correctly to the server. Since Eclipse/WTP/JBoss Tools doesn't see the Maven's output directory, the application deployed by JBoss Tools/WTP won't contain these files and won't work correctly. An example of  this behaviour is the photoalbum application from the RichFaces distribution. If you import this application into Eclipse, you will notice that it doesn't contain application.xml and jboss-app.xml and that deploying to JBoss Server doesn't work. A workaround is to copy these files from the Maven's output directory to src/main/application/META-INF.
If you deploy the application created by Maven, it will work correctly.
I still propose creating these files that would be controlled by a preference (false by default).  



> Add m2eclipse project-configurator for Seam projects
> ----------------------------------------------------
>
>                 Key: JBIDE-4736
>                 URL: https://jira.jboss.org/jira/browse/JBIDE-4736
>             Project: JBoss Tools
>          Issue Type: Feature Request
>          Components: maven
>    Affects Versions: 3.1.0.M2
>            Reporter: Max Rydahl Andersen
>            Assignee: Snjezana Peco
>             Fix For: 3.1.0.M3
>
>
> To get proper Maven integration we should explore the project-configurator of m2eclipse allowing you to import existing maven projects AND allow picking up settings setup in pom.xml after project have been created.
> Created this issue since I couldn't find something similar, let us discuss here what needs to be done/any problems ?

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira