You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by "fabrizio giustina (JIRA)" <ji...@codehaus.org> on 2005/11/27 23:40:06 UTC

[jira] Closed: (MPECLIPSE-59) Skipped dependency with eclipse.dependency false

     [ http://jira.codehaus.org/browse/MPECLIPSE-59?page=all ]
     
fabrizio giustina closed MPECLIPSE-59:
--------------------------------------

      Assign To: fabrizio giustina
     Resolution: Won't Fix
    Fix Version: 1.10

I can't see any valid use case why the eclipse project should not contain dependencies needed when building using maven.
Closing as a won't fix, please reopen the bug if you think this could be needed and post a valid use case.

> Skipped dependency with eclipse.dependency  false
> -------------------------------------------------
>
>          Key: MPECLIPSE-59
>          URL: http://jira.codehaus.org/browse/MPECLIPSE-59
>      Project: maven-eclipse-plugin
>         Type: Bug
>  Environment: Java 1.4.2_04, win2k
>     Reporter: Henri Bonnehuit
>     Assignee: fabrizio giustina
>     Priority: Minor
>      Fix For: 1.10

>
>
> A dependency element like:
> <eclipse.dependency>true</eclipse.dependency>
> in project.xml causes maven eclipse to skip the dependency completely,
> rather than reverting to simple .classpath entry.
> I have maven-eclipse-plugin-1.9.jar and maven v. 1.0.1

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


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org