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

Max Rydahl Andersen (JIRA) jira-events at lists.jboss.org
Mon Aug 17 07:01:26 EDT 2009


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

Max Rydahl Andersen commented on JBIDE-4736:
--------------------------------------------

This looks great!

"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 ?

"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. 

> 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

        


More information about the jbosstools-issues mailing list