You are viewing a plain text version of this content. The canonical link for it is here.

Posted to notifications@ant.apache.org by "Adam Karl (JIRA)" <ji...@apache.org> on 2009/01/06 19:00:44 UTC

[jira] Commented: (IVYDE-149) Changing any setting for the classpath container loses the "exported" setting of the classpath container

    [ https://issues.apache.org/jira/browse/IVYDE-149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12661229#action_12661229 ] 

Adam Karl commented on IVYDE-149:
---------------------------------

Thank you for putting work into IvyDE.  It was needed and is very much appreciated.  

> Changing any setting for the classpath container loses the "exported" setting of the classpath container
> --------------------------------------------------------------------------------------------------------
>
>                 Key: IVYDE-149
>                 URL: https://issues.apache.org/jira/browse/IVYDE-149
>             Project: IvyDE
>          Issue Type: Bug
>    Affects Versions: 2.0.0.alpha1, 2.0.0.beta1
>            Reporter: Adam Karl
>            Assignee: Nicolas Lalevée
>            Priority: Minor
>             Fix For: 2.0.0.final
>
>
> If I change any setting for the classpath container the "exported" setting for the classpath container resets to false.  If another project depends on this project, the dependencies will no longer be exported to it.  In my case, my higher level projects are not yet using ivy so they need IvyDEs classpath container to be pushed up to them. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.