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

[Max Rydahl Andersen (JIRA)]

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

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

Eugene:
> 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)

>Now I am confused. The Maven classpath container can contain any libraries, as long as they are declared in the pom.xml. If your project will use libraries that are not declared in the pom.xml you >have a good chance that command line Maven build is not going to work for such project.

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 ?






> 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