You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "bob robertson jr (JIRA)" <ji...@codehaus.org> on 2008/06/18 10:08:26 UTC

[jira] Commented: (MECLIPSE-262) Maven compilation and eclipse classpath don't match with conflicting versions at same dependency depth

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

bob robertson jr commented on MECLIPSE-262:
-------------------------------------------

Another example. With maven 2.0.9 and version 2.5.1 of the eclipse plugin. 

Our POM is:
{noformat}
<project xmlns="http://maven.apache.org/POM/4.0.0"
        xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
        xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd">

        <modelVersion>4.0.0</modelVersion>
        <groupId>com.org.net</groupId>
        <artifactId>proofOfBrokenness</artifactId>
        <version>1.0-SNAPSHOT</version>
        <packaging>jar</packaging>

        <dependencies>
                <dependency>
                        <groupId>org.acegisecurity</groupId>
                        <artifactId>acegi-security</artifactId>
                        <version>1.0.4</version>
                </dependency>
                <dependency>
                        <groupId>commons-httpclient</groupId>
                        <artifactId>commons-httpclient</artifactId>
                        <version>3.1</version>
                </dependency>
        </dependencies>
</project>
{noformat}

Both artifacts have dependencies on commons-codec. One uses version 1.3, the other version 1.2.

Our eclipse project has a dependency on 1.2 whereas {{mvn dependency:tree}} reports v1.3.

This means that users check out the source code, populate the maven repository by compiling and then start up eclipse to see that not all the required libraries are in the repository.


> Maven compilation and eclipse classpath don't match with conflicting versions at same dependency depth
> ------------------------------------------------------------------------------------------------------
>
>                 Key: MECLIPSE-262
>                 URL: http://jira.codehaus.org/browse/MECLIPSE-262
>             Project: Maven 2.x Eclipse Plugin
>          Issue Type: Bug
>          Components: Core : Dependencies resolution and build path
>    Affects Versions: 2.3
>         Environment: Maven 2.0.6, 2.0.4
>            Reporter: Carlos Sanchez
>         Attachments: compile.txt, eclipse.txt, screenshot-1.jpg, testcase.zip
>
>
> https://svn.apache.org/repos/asf/maven/components/trunk/maven-core rev# 533182
> compile uses plexus-component-api-1.0-alpha-24 (the right one)
> eclipse:eclipse uses plexus-component-api-1.0-alpha-16

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