You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Michael Johns (JIRA)" <ji...@codehaus.org> on 2008/04/25 01:11:52 UTC

[jira] Created: (MECLIPSE-442) Classpath container entries should come last in .classpath

Classpath container entries should come last in .classpath
----------------------------------------------------------

                 Key: MECLIPSE-442
                 URL: http://jira.codehaus.org/browse/MECLIPSE-442
             Project: Maven 2.x Eclipse Plugin
          Issue Type: Improvement
    Affects Versions: 2.5.1
            Reporter: Michael Johns
            Priority: Minor


It would be nice if the classpath container entries (kind="con") came last in the .classpath file.  There are situations where the container I'm using defines configuration that I'd like to override (commons-logging.properties, for example).  If the container comes first, there's no way for me to do this.  If they come last, then my configuration is found first, allowing me to override the container configuration.

-- 
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] Updated: (MECLIPSE-442) Classpath container entries should come last in .classpath

Posted by "Arnaud Heritier (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MECLIPSE-442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Arnaud Heritier updated MECLIPSE-442:
-------------------------------------

         Assignee: Arnaud Heritier
    Fix Version/s: 2.5.2
      Component/s: Core : Dependencies resolution and build path

> Classpath container entries should come last in .classpath
> ----------------------------------------------------------
>
>                 Key: MECLIPSE-442
>                 URL: http://jira.codehaus.org/browse/MECLIPSE-442
>             Project: Maven 2.x Eclipse Plugin
>          Issue Type: Improvement
>          Components: Core : Dependencies resolution and build path
>    Affects Versions: 2.5.1
>            Reporter: Michael Johns
>            Assignee: Arnaud Heritier
>            Priority: Minor
>             Fix For: 2.5.2
>
>         Attachments: MECLIPSE-442.patch
>
>
> It would be nice if the classpath container entries (kind="con") came last in the .classpath file.  There are situations where the container I'm using defines configuration that I'd like to override (commons-logging.properties, for example).  If the container comes first, there's no way for me to do this.  If they come last, then my configuration is found first, allowing me to override the container configuration.

-- 
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: (MECLIPSE-442) Classpath container entries should come last in .classpath

Posted by "Michael Johns (JIRA)" <ji...@codehaus.org>.
    [ http://jira.codehaus.org/browse/MECLIPSE-442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=132549#action_132549 ] 

Michael Johns commented on MECLIPSE-442:
----------------------------------------

If it's desirable for some people that the entries come first, perhaps it could be configurable.

> Classpath container entries should come last in .classpath
> ----------------------------------------------------------
>
>                 Key: MECLIPSE-442
>                 URL: http://jira.codehaus.org/browse/MECLIPSE-442
>             Project: Maven 2.x Eclipse Plugin
>          Issue Type: Improvement
>    Affects Versions: 2.5.1
>            Reporter: Michael Johns
>            Priority: Minor
>         Attachments: MECLIPSE-442.patch
>
>
> It would be nice if the classpath container entries (kind="con") came last in the .classpath file.  There are situations where the container I'm using defines configuration that I'd like to override (commons-logging.properties, for example).  If the container comes first, there's no way for me to do this.  If they come last, then my configuration is found first, allowing me to override the container configuration.

-- 
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: (MECLIPSE-442) Classpath container entries should come last in .classpath

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

Barrie Treloar closed MECLIPSE-442.
-----------------------------------

    Resolution: Fixed

Moved container definition to end as per patch.
Fixed IT tests.

> Classpath container entries should come last in .classpath
> ----------------------------------------------------------
>
>                 Key: MECLIPSE-442
>                 URL: http://jira.codehaus.org/browse/MECLIPSE-442
>             Project: Maven 2.x Eclipse Plugin
>          Issue Type: Improvement
>          Components: Core : Dependencies resolution and build path (.classpath)
>    Affects Versions: 2.5.1
>            Reporter: Michael Johns
>            Assignee: Barrie Treloar
>            Priority: Minor
>             Fix For: 2.6
>
>         Attachments: MECLIPSE-442.patch
>
>
> It would be nice if the classpath container entries (kind="con") came last in the .classpath file.  There are situations where the container I'm using defines configuration that I'd like to override (commons-logging.properties, for example).  If the container comes first, there's no way for me to do this.  If they come last, then my configuration is found first, allowing me to override the container configuration.

-- 
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: (MECLIPSE-442) Classpath container entries should come last in .classpath

Posted by "fabrizio giustina (JIRA)" <ji...@codehaus.org>.
    [ http://jira.codehaus.org/browse/MECLIPSE-442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=218053#action_218053 ] 

fabrizio giustina commented on MECLIPSE-442:
--------------------------------------------

Note that this has now been reverted for MECLIPSE-548 in 2.9, swithing back to the old behavior by default. A new property has however been introduced if you need to keep the classpath ordering as describer in this issue.


> Classpath container entries should come last in .classpath
> ----------------------------------------------------------
>
>                 Key: MECLIPSE-442
>                 URL: http://jira.codehaus.org/browse/MECLIPSE-442
>             Project: Maven 2.x Eclipse Plugin
>          Issue Type: Improvement
>          Components: Core : Dependencies resolution and build path (.classpath)
>    Affects Versions: 2.5.1
>            Reporter: Michael Johns
>            Assignee: Barrie Treloar
>            Priority: Minor
>             Fix For: 2.6
>
>         Attachments: MECLIPSE-442.patch
>
>
> It would be nice if the classpath container entries (kind="con") came last in the .classpath file.  There are situations where the container I'm using defines configuration that I'd like to override (commons-logging.properties, for example).  If the container comes first, there's no way for me to do this.  If they come last, then my configuration is found first, allowing me to override the container configuration.

-- 
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] Updated: (MECLIPSE-442) Classpath container entries should come last in .classpath

Posted by "Michael Johns (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MECLIPSE-442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Johns updated MECLIPSE-442:
-----------------------------------

    Attachment: MECLIPSE-442.patch

> Classpath container entries should come last in .classpath
> ----------------------------------------------------------
>
>                 Key: MECLIPSE-442
>                 URL: http://jira.codehaus.org/browse/MECLIPSE-442
>             Project: Maven 2.x Eclipse Plugin
>          Issue Type: Improvement
>    Affects Versions: 2.5.1
>            Reporter: Michael Johns
>            Priority: Minor
>         Attachments: MECLIPSE-442.patch
>
>
> It would be nice if the classpath container entries (kind="con") came last in the .classpath file.  There are situations where the container I'm using defines configuration that I'd like to override (commons-logging.properties, for example).  If the container comes first, there's no way for me to do this.  If they come last, then my configuration is found first, allowing me to override the container configuration.

-- 
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: (MECLIPSE-442) Classpath container entries should come last in .classpath

Posted by "Joe Freeman (JIRA)" <ji...@codehaus.org>.
    [ http://jira.codehaus.org/browse/MECLIPSE-442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=172322#action_172322 ] 

Joe Freeman commented on MECLIPSE-442:
--------------------------------------

This patch should be pulled back out. 

http://jira.codehaus.org/browse/MECLIPSE-548


> Classpath container entries should come last in .classpath
> ----------------------------------------------------------
>
>                 Key: MECLIPSE-442
>                 URL: http://jira.codehaus.org/browse/MECLIPSE-442
>             Project: Maven 2.x Eclipse Plugin
>          Issue Type: Improvement
>          Components: Core : Dependencies resolution and build path (.classpath)
>    Affects Versions: 2.5.1
>            Reporter: Michael Johns
>            Assignee: Barrie Treloar
>            Priority: Minor
>             Fix For: 2.6
>
>         Attachments: MECLIPSE-442.patch
>
>
> It would be nice if the classpath container entries (kind="con") came last in the .classpath file.  There are situations where the container I'm using defines configuration that I'd like to override (commons-logging.properties, for example).  If the container comes first, there's no way for me to do this.  If they come last, then my configuration is found first, allowing me to override the container configuration.

-- 
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] Work started: (MECLIPSE-442) Classpath container entries should come last in .classpath

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

Work on MECLIPSE-442 started by Barrie Treloar.

> Classpath container entries should come last in .classpath
> ----------------------------------------------------------
>
>                 Key: MECLIPSE-442
>                 URL: http://jira.codehaus.org/browse/MECLIPSE-442
>             Project: Maven 2.x Eclipse Plugin
>          Issue Type: Improvement
>          Components: Core : Dependencies resolution and build path (.classpath)
>    Affects Versions: 2.5.1
>            Reporter: Michael Johns
>            Assignee: Barrie Treloar
>            Priority: Minor
>             Fix For: 2.6
>
>         Attachments: MECLIPSE-442.patch
>
>
> It would be nice if the classpath container entries (kind="con") came last in the .classpath file.  There are situations where the container I'm using defines configuration that I'd like to override (commons-logging.properties, for example).  If the container comes first, there's no way for me to do this.  If they come last, then my configuration is found first, allowing me to override the container configuration.

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