[ 
http://jira.codehaus.org/browse/MECLIPSE-577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=183224#action_183224
 ] 

Martin Jozef commented on MECLIPSE-577:
---------------------------------------

Anyway i tried the our Ear projects and web project using latest eclipse and 
m2eclipse. Unfortunately i can't get my web app project be recognized as web 
projects.  So i prefer the maven eclipse plugin as it works, and i can publish 
to several servers.  I would prefer if this library grouping be implemented 
into this project itself.  Otherwise the only other alternative that works for 
our project is to use the Netbeans support available in 6.7 release.

> Project Dependencies list too intrusive while navigating projects.
> ------------------------------------------------------------------
>
>                 Key: MECLIPSE-577
>                 URL: http://jira.codehaus.org/browse/MECLIPSE-577
>             Project: Maven 2.x Eclipse Plugin
>          Issue Type: Improvement
>          Components: Core : Multi-projects
>    Affects Versions: 2.6
>         Environment: all
>            Reporter: Martin Jozef
>            Priority: Minor
>         Attachments: eclipse-maven-project.png
>
>
> We have web applications that are growing very quickly having many inner 
> projects etc... The dependency list is becoming very large specially where a 
> lot of frameworks that we use like to split their project into many little 
> jars too.  
> I attached a screen shot to show of how it looks.
> Can we direct the maven-eclipse-plugin to place all these jars under a group 
> like "Maven Dependencies"  or something like that so the entire list is not 
> on the same level with src files.  
> As it stands it's hard to scroll between projects.

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

        

Reply via email to