[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-3874) Maven integration

[Eugene Kuleshov (JIRA)]

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

Eugene Kuleshov commented on JBIDE-3874:
----------------------------------------

>> It is also worth to say that it is a good idea 
>> to generate projects using common maven 
>> conventions. For example, use the src/main/webapp as a web app directory

> Agreed, but Maven is not hardcoded to that dir is it ? 
> (i.e. wtp and seam projects uses different conventions 
> so would be good if we could allow those too for users
> migrating/having other conventions) 

It is not really in "Maven", but in particular plugins. More over, in some cases, when you changing the defaults, you may have to reconfigure multiple plugins to get their settings intact. For example, the war source location is at: http://maven.apache.org/plugins/maven-war-plugin/war-mojo.html#warSourceDirectory

Currently m2eclipse is missing functionality for converting settings from Eclipse projects back to pom.xml, but I hope such feature will be added in the future.

>> Yeah, well that is one of the hard problems we have. 
>> Not all jars might be in a maven repo - some might be 
>> in a specific container (i.e. JBoss AS, Webpshere, etc. ) 
>> and users can't know what versions that is. I'm trying to 
>> make sure JBoss products will provide Maven artifacts 
>> for all its dependencies but that might not be doable for everything.
>> Any ideas on how to support real life situations like this ? 

The most straightforward would be to install all those artifacts to the Maven local repository or into the private Maven repository. There is a half-done wizard in m2eclipse for doing that manually, I think its backend could be used by integrators to bring all required dependencies in.

> Maven integration
> -----------------
>
>                 Key: JBIDE-3874
>                 URL: https://jira.jboss.org/jira/browse/JBIDE-3874
>             Project: Tools (JBoss Tools)
>          Issue Type: Feature Request
>          Components: common
>    Affects Versions: 3.0.0.GA
>            Reporter: Max Rydahl Andersen
>            Assignee: Snjezana Peco
>            Priority: Critical
>             Fix For: 3.1.0.M2
>
>
> It is time to make sure our stuff works well with Maven, at least to the extent that the underline runtimes support it.
> First shot would be to add an adapter that allows m2eclipse controlled projects to activate the seam features.
> That would allow us still to bundle JBoss Tools without any dependencies to m2eclipse which still seem to drag in non-compatible plugins which we need to look into before tying us to m2eclipse.

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