You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Claudio Di Vita (JIRA)" <ji...@codehaus.org> on 2007/11/02 16:07:11 UTC

[jira] Created: (MDEP-118) Resolving dependencies with the same JDK specified by the Compiler plugin

Resolving dependencies with the same JDK specified by the Compiler plugin
-------------------------------------------------------------------------

                 Key: MDEP-118
                 URL: http://jira.codehaus.org/browse/MDEP-118
             Project: Maven 2.x Dependency Plugin
          Issue Type: Bug
          Components: resolve
    Affects Versions: 2.0-alpha-4
            Reporter: Claudio Di Vita
            Assignee: Brian Fox


The dependencies have to be resolved with the same JDK specified by the Compiler plugin, not with the version used by Maven scripts.

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

        

[jira] Commented: (MDEP-118) Resolving dependencies with the same JDK specified by the Compiler plugin

Posted by "Brian Fox (JIRA)" <ji...@codehaus.org>.
    [ http://jira.codehaus.org/browse/MDEP-118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_112605 ] 

Brian Fox commented on MDEP-118:
--------------------------------

I don't understand the issue. The plugins have no control over the JDK, Maven is doing the resolution.

> Resolving dependencies with the same JDK specified by the Compiler plugin
> -------------------------------------------------------------------------
>
>                 Key: MDEP-118
>                 URL: http://jira.codehaus.org/browse/MDEP-118
>             Project: Maven 2.x Dependency Plugin
>          Issue Type: Bug
>          Components: resolve
>    Affects Versions: 2.0-alpha-4
>            Reporter: Claudio Di Vita
>            Assignee: Brian Fox
>
> The dependencies have to be resolved with the same JDK specified by the Compiler plugin, not with the version used by Maven scripts.

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

        

[jira] Commented: (MDEP-118) Resolving dependencies with the same JDK specified by the Compiler plugin

Posted by "Brian Fox (JIRA)" <ji...@codehaus.org>.
    [ http://jira.codehaus.org/browse/MDEP-118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_114174 ] 

Brian Fox commented on MDEP-118:
--------------------------------

Can you provide a working test project? I still am not really sure what exactly the problem is supposed to be.

> Resolving dependencies with the same JDK specified by the Compiler plugin
> -------------------------------------------------------------------------
>
>                 Key: MDEP-118
>                 URL: http://jira.codehaus.org/browse/MDEP-118
>             Project: Maven 2.x Dependency Plugin
>          Issue Type: Bug
>          Components: resolve
>    Affects Versions: 2.0-alpha-4
>            Reporter: Claudio Di Vita
>            Assignee: Brian Fox
>
> The dependencies have to be resolved with the same JDK specified by the Compiler plugin, not with the version used by Maven scripts.

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

        

[jira] Commented: (MDEP-118) Resolving dependencies with the same JDK specified by the Compiler plugin

Posted by "Claudio Di Vita (JIRA)" <ji...@codehaus.org>.
    [ http://jira.codehaus.org/browse/MDEP-118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_114173 ] 

Claudio Di Vita commented on MDEP-118:
--------------------------------------

Sorry for my late reply.

In my project the activation of some dependencies relies on the Java version. Unfortunately the JVM recognized by the Dependency Plugin is the same used for running Maven, but because I compiled my sources with an anoter JDK my dependencies aren't resolved.

So I use:

 - The JDK 1.6 for running Maven
 - The JDK 1.4.2 for compile my sources

> Resolving dependencies with the same JDK specified by the Compiler plugin
> -------------------------------------------------------------------------
>
>                 Key: MDEP-118
>                 URL: http://jira.codehaus.org/browse/MDEP-118
>             Project: Maven 2.x Dependency Plugin
>          Issue Type: Bug
>          Components: resolve
>    Affects Versions: 2.0-alpha-4
>            Reporter: Claudio Di Vita
>            Assignee: Brian Fox
>
> The dependencies have to be resolved with the same JDK specified by the Compiler plugin, not with the version used by Maven scripts.

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

        

[jira] Commented: (MDEP-118) Resolving dependencies with the same JDK specified by the Compiler plugin

Posted by "Claudio Di Vita (JIRA)" <ji...@codehaus.org>.
    [ http://jira.codehaus.org/browse/MDEP-118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_112613 ] 

Claudio Di Vita commented on MDEP-118:
--------------------------------------

You know that you can specify the JDK version used for compiling the source files (like the example available on Maven site: http://maven.apache.org/plugins/maven-compiler-plugin/examples/compile-using-different-jdk.html).

If I enable this behaviour I want that dependecies will be resolved against the JDK version used for compiling my source, not the JDK version used for running Maven.

> Resolving dependencies with the same JDK specified by the Compiler plugin
> -------------------------------------------------------------------------
>
>                 Key: MDEP-118
>                 URL: http://jira.codehaus.org/browse/MDEP-118
>             Project: Maven 2.x Dependency Plugin
>          Issue Type: Bug
>          Components: resolve
>    Affects Versions: 2.0-alpha-4
>            Reporter: Claudio Di Vita
>            Assignee: Brian Fox
>
> The dependencies have to be resolved with the same JDK specified by the Compiler plugin, not with the version used by Maven scripts.

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

        

[jira] Commented: (MDEP-118) Resolving dependencies with the same JDK specified by the Compiler plugin

Posted by "Brian Fox (JIRA)" <ji...@codehaus.org>.
    [ http://jira.codehaus.org/browse/MDEP-118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_112734 ] 

Brian Fox commented on MDEP-118:
--------------------------------

I still don't understand, sorry. Resolving the dependencies has nothing to do with the JDK, unless of course you mean things that have JDK classifiers like TestNG. If that's the case, you can already do that by specifying the classifier. Can you provide an example?

> Resolving dependencies with the same JDK specified by the Compiler plugin
> -------------------------------------------------------------------------
>
>                 Key: MDEP-118
>                 URL: http://jira.codehaus.org/browse/MDEP-118
>             Project: Maven 2.x Dependency Plugin
>          Issue Type: Bug
>          Components: resolve
>    Affects Versions: 2.0-alpha-4
>            Reporter: Claudio Di Vita
>            Assignee: Brian Fox
>
> The dependencies have to be resolved with the same JDK specified by the Compiler plugin, not with the version used by Maven scripts.

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

        

[jira] Closed: (MDEP-118) Resolving dependencies with the same JDK specified by the Compiler plugin

Posted by "Brian Fox (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MDEP-118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Fox closed MDEP-118.
--------------------------

    Resolution: Cannot Reproduce

Need a sample project to figure out what is being asked.

> Resolving dependencies with the same JDK specified by the Compiler plugin
> -------------------------------------------------------------------------
>
>                 Key: MDEP-118
>                 URL: http://jira.codehaus.org/browse/MDEP-118
>             Project: Maven 2.x Dependency Plugin
>          Issue Type: Bug
>          Components: resolve
>    Affects Versions: 2.0-alpha-4
>            Reporter: Claudio Di Vita
>            Assignee: Brian Fox
>
> The dependencies have to be resolved with the same JDK specified by the Compiler plugin, not with the version used by Maven scripts.

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