[jira] Created: (MNGECLIPSE-429) Classpath resolution

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

[jira] Created: (MNGECLIPSE-429) Classpath resolution

JIRA jira@codehaus.org
Classpath resolution
--------------------

                 Key: MNGECLIPSE-429
                 URL: http://jira.codehaus.org/browse/MNGECLIPSE-429
             Project: Maven Integration for Eclipse
          Issue Type: Bug
          Components: Dependency Resolver
    Affects Versions: 0.0.12
            Reporter: Markus Wolf


The resolved classpath does contain dependencies which are explicitly marked as excluded in the pom.xml.
These should not be added to eclipse path, since this could lead to wrong dependencies being used for compilation/runtime.

--
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 from this list please visit:

    http://xircles.codehaus.org/manage_email

Reply | Threaded
Open this post in threaded view
|

[jira] Commented: (MNGECLIPSE-429) Classpath resolution

JIRA jira@codehaus.org

    [ http://jira.codehaus.org/browse/MNGECLIPSE-429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_112843 ]

Eugene Kuleshov commented on MNGECLIPSE-429:
--------------------------------------------

Please provide test project that would allow to reproduce this issue. See the following document for some hints. http://docs.codehaus.org/display/M2ECLIPSE/How+To+Report+Issues

> Classpath resolution
> --------------------
>
>                 Key: MNGECLIPSE-429
>                 URL: http://jira.codehaus.org/browse/MNGECLIPSE-429
>             Project: Maven Integration for Eclipse
>          Issue Type: Bug
>          Components: Dependency Resolver
>    Affects Versions: 0.0.12
>            Reporter: Markus Wolf
>
> The resolved classpath does contain dependencies which are explicitly marked as excluded in the pom.xml.
> These should not be added to eclipse path, since this could lead to wrong dependencies being used for compilation/runtime.

--
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 from this list please visit:

    http://xircles.codehaus.org/manage_email

Reply | Threaded
Open this post in threaded view
|

[jira] Commented: (MNGECLIPSE-429) Classpath resolution

JIRA jira@codehaus.org
In reply to this post by JIRA jira@codehaus.org

    [ http://jira.codehaus.org/browse/MNGECLIPSE-429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_112919 ]

Markus Wolf commented on MNGECLIPSE-429:
----------------------------------------

After examining the problem a bit more it was not the excluded dependencies, but transitive dependencies on my test classpath.
It would be good (IMHO) to seperate the maven classpath container into the maven classpaths compile, runtime, test and system. This would lead to a better overview.

> Classpath resolution
> --------------------
>
>                 Key: MNGECLIPSE-429
>                 URL: http://jira.codehaus.org/browse/MNGECLIPSE-429
>             Project: Maven Integration for Eclipse
>          Issue Type: Bug
>          Components: Dependency Resolver
>    Affects Versions: 0.0.12
>            Reporter: Markus Wolf
>
> The resolved classpath does contain dependencies which are explicitly marked as excluded in the pom.xml.
> These should not be added to eclipse path, since this could lead to wrong dependencies being used for compilation/runtime.

--
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 from this list please visit:

    http://xircles.codehaus.org/manage_email

Reply | Threaded
Open this post in threaded view
|

[jira] Closed: (MNGECLIPSE-429) Classpath resolution

JIRA jira@codehaus.org
In reply to this post by JIRA jira@codehaus.org

     [ http://jira.codehaus.org/browse/MNGECLIPSE-429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Eugene Kuleshov closed MNGECLIPSE-429.
--------------------------------------

    Resolution: Cannot Reproduce

It doesn't seem like we have issue here. Dependency viewer (not yet available) should address concerns related to dependency origins.

> Classpath resolution
> --------------------
>
>                 Key: MNGECLIPSE-429
>                 URL: http://jira.codehaus.org/browse/MNGECLIPSE-429
>             Project: Maven Integration for Eclipse
>          Issue Type: Bug
>          Components: Dependency Resolver
>    Affects Versions: 0.0.12
>            Reporter: Markus Wolf
>
> The resolved classpath does contain dependencies which are explicitly marked as excluded in the pom.xml.
> These should not be added to eclipse path, since this could lead to wrong dependencies being used for compilation/runtime.

--
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 from this list, please visit:

    http://xircles.codehaus.org/manage_email