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

Jilles van Gurp commented on MECLIPSE-581:
------------------------------------------

Sorry, but this is really annoying behavior. Basically, the order of stuff in 
eclipse classpath has no relevance whatsoever in terms of semantics as far as I 
can see. Basically you should be able to randomize the order and not have any 
functional difference. 

The main argument in MECLIPSE-318 seems to be that maven resolves dependencies 
in some order, which has changed recently. Fine, but the eclipse classpath 
represents the outcome of that process, not the actual process. And if the 
outcome is that main depends on test somehow, that would be pretty messed up. 
Also, from usability point of view, not having the first thing listed being the 
main src package is not the best thing to have.

So, I would like to request this ticket be reopened and fixed. This "it's a 
feature not a bug" kind of reflex is the easy way out here. Fixing the behavior 
to be logical is better than documenting why it is counter intuitive (which it 
is). 

If it is actually required, i.e. there exist eclipse projects that do not work 
unless test is listed before main, which I strongly doubt, it needs to be 
documented why things will break otherwise. Even so, that is probably something 
you would want to fix in your project rather than in maven. 

> Test source directories appear before Main source directories
> -------------------------------------------------------------
>
>                 Key: MECLIPSE-581
>                 URL: http://jira.codehaus.org/browse/MECLIPSE-581
>             Project: Maven 2.x Eclipse Plugin
>          Issue Type: Bug
>          Components: Core : .project
>    Affects Versions: 2.6
>         Environment: Maven 2.0.10
>            Reporter: Paul Benedict
>
> This is either a bug or a questionable feature. When I run eclipse:eclipse on 
> a project that has siblings in its parent POM, two things happen:
> (1) the sibling projects become a dependent project, not jar dependencies
> (2) src/test appears before src/main in the package explorer.
> I can handle #1, but #2 really is a tough adjustment.

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