You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Barrie Treloar (JIRA)" <ji...@codehaus.org> on 2011/11/18 03:59:51 UTC

[jira] Created: (MECLIPSE-705) Use Aether (or the shared exposed interface) to ensure orrect .classpath ordering of dependencies.

Use Aether (or the shared exposed interface) to ensure orrect .classpath ordering of dependencies.
--------------------------------------------------------------------------------------------------

                 Key: MECLIPSE-705
                 URL: https://jira.codehaus.org/browse/MECLIPSE-705
             Project: Maven 2.x Eclipse Plugin
          Issue Type: Bug
          Components: Core : Dependencies resolution and build path (.classpath)
    Affects Versions: 2.9
            Reporter: Barrie Treloar
            Priority: Critical


The eclipse plugin works out the classpath ordering itself.

It should be re-using whatever is done internally by Maven.


--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] Updated: (MECLIPSE-705) Use Aether (or the shared exposed interface) to ensure correct .classpath ordering of dependencies.

Posted by "Barrie Treloar (JIRA)" <ji...@codehaus.org>.
     [ https://jira.codehaus.org/browse/MECLIPSE-705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Barrie Treloar updated MECLIPSE-705:
------------------------------------

    Fix Version/s: 2.10

> Use Aether (or the shared exposed interface) to ensure correct .classpath ordering of dependencies.
> ---------------------------------------------------------------------------------------------------
>
>                 Key: MECLIPSE-705
>                 URL: https://jira.codehaus.org/browse/MECLIPSE-705
>             Project: Maven 2.x Eclipse Plugin
>          Issue Type: Bug
>          Components: Core : Dependencies resolution and build path (.classpath)
>    Affects Versions: 2.9
>            Reporter: Barrie Treloar
>            Priority: Critical
>             Fix For: 2.10
>
>
> The eclipse plugin works out the classpath ordering itself.
> It should be re-using whatever is done internally by Maven.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] Updated: (MECLIPSE-705) Use Aether (or the shared exposed interface) to ensure correct .classpath ordering of dependencies.

Posted by "Barrie Treloar (JIRA)" <ji...@codehaus.org>.
     [ https://jira.codehaus.org/browse/MECLIPSE-705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Barrie Treloar updated MECLIPSE-705:
------------------------------------

    Summary: Use Aether (or the shared exposed interface) to ensure correct .classpath ordering of dependencies.  (was: Use Aether (or the shared exposed interface) to ensure orrect .classpath ordering of dependencies.)

> Use Aether (or the shared exposed interface) to ensure correct .classpath ordering of dependencies.
> ---------------------------------------------------------------------------------------------------
>
>                 Key: MECLIPSE-705
>                 URL: https://jira.codehaus.org/browse/MECLIPSE-705
>             Project: Maven 2.x Eclipse Plugin
>          Issue Type: Bug
>          Components: Core : Dependencies resolution and build path (.classpath)
>    Affects Versions: 2.9
>            Reporter: Barrie Treloar
>            Priority: Critical
>
> The eclipse plugin works out the classpath ordering itself.
> It should be re-using whatever is done internally by Maven.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira