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:13:46 UTC

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

    [ 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