You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@ant.apache.org by "Matt Goldspink (JIRA)" <ji...@apache.org> on 2008/09/14 21:59:44 UTC

[jira] Created: (IVYDE-118) Resolve in workspace does not pick up all projects in workspace

Resolve in workspace does not pick up all projects in workspace
---------------------------------------------------------------

                 Key: IVYDE-118
                 URL: https://issues.apache.org/jira/browse/IVYDE-118
             Project: IvyDE
          Issue Type: Bug
          Components: classpath container
    Affects Versions: 2.0.0.alpha1
            Reporter: Matt Goldspink
            Priority: Minor


A member of my team found a bug in the IvyResolveJob.java which is mainly due to a misunderstanding of the api we suspect.

IJavaProject.isOpen() has misleading Javadoc. It only returns true when a project is not in a collapsed state. This leads IvyDE to skip all collapsed projects when resolving in the workspace. 

See the following thread for details: http://dev.eclipse.org/newslists/news.eclipse.tools.jdt/msg22189.html

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


[jira] Resolved: (IVYDE-118) Resolve in workspace does not pick up all projects in workspace

Posted by "Nicolas Lalevée (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/IVYDE-118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Nicolas Lalevée resolved IVYDE-118.
-----------------------------------

       Resolution: Fixed
    Fix Version/s: 2.0
         Assignee: Nicolas Lalevée

Thanks for the patch and the link to the discussion Matt.

> Resolve in workspace does not pick up all projects in workspace
> ---------------------------------------------------------------
>
>                 Key: IVYDE-118
>                 URL: https://issues.apache.org/jira/browse/IVYDE-118
>             Project: IvyDE
>          Issue Type: Bug
>          Components: classpath container
>    Affects Versions: 2.0.0.alpha1
>            Reporter: Matt Goldspink
>            Assignee: Nicolas Lalevée
>            Priority: Minor
>             Fix For: 2.0
>
>         Attachments: ivyde.IVYDE-118.patch
>
>
> A member of my team found a bug in the IvyResolveJob.java which is mainly due to a misunderstanding of the api we suspect.
> IJavaProject.isOpen() has misleading Javadoc. It only returns true when a project is not in a collapsed state. This leads IvyDE to skip all collapsed projects when resolving in the workspace. 
> See the following thread for details: http://dev.eclipse.org/newslists/news.eclipse.tools.jdt/msg22189.html

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


[jira] Updated: (IVYDE-118) Resolve in workspace does not pick up all projects in workspace

Posted by "Matt Goldspink (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/IVYDE-118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matt Goldspink updated IVYDE-118:
---------------------------------

    Attachment: ivyde.IVYDE-118.patch

Adding patch for the issue

> Resolve in workspace does not pick up all projects in workspace
> ---------------------------------------------------------------
>
>                 Key: IVYDE-118
>                 URL: https://issues.apache.org/jira/browse/IVYDE-118
>             Project: IvyDE
>          Issue Type: Bug
>          Components: classpath container
>    Affects Versions: 2.0.0.alpha1
>            Reporter: Matt Goldspink
>            Priority: Minor
>         Attachments: ivyde.IVYDE-118.patch
>
>
> A member of my team found a bug in the IvyResolveJob.java which is mainly due to a misunderstanding of the api we suspect.
> IJavaProject.isOpen() has misleading Javadoc. It only returns true when a project is not in a collapsed state. This leads IvyDE to skip all collapsed projects when resolving in the workspace. 
> See the following thread for details: http://dev.eclipse.org/newslists/news.eclipse.tools.jdt/msg22189.html

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