[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-3050) Project Archives freezes with large includes

Max Rydahl Andersen (JIRA) jira-events at lists.jboss.org
Fri Mar 6 04:40:22 EST 2009


    [ https://jira.jboss.org/jira/browse/JBIDE-3050?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12455840#action_12455840 ] 

Max Rydahl Andersen commented on JBIDE-3050:
--------------------------------------------

wow - big changes coming ;) 

A few questions on that:

1) What has actually changed ? ui wise and functionallity wise ?

2) Why is all those excellent comments in DirectoryScanner being removed ?

3) Why is the symbolic link code not relevant ?

4) What is the point of the test that compares two instances of DirectoryScanner with the exact same input ?
(i.e. it does not seem to test that it can be stopped nor continued ?)

5) Why are we using doubles for version comparison ? What is wrong with an enum or long ?

6) will  this iterator approach  be used for the actual building too ? (i.e. to allow stopping a long running build) ?


> Project Archives freezes with large includes
> --------------------------------------------
>
>                 Key: JBIDE-3050
>                 URL: https://jira.jboss.org/jira/browse/JBIDE-3050
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: Archives
>    Affects Versions: 3.0.0.beta1
>            Reporter: Max Rydahl Andersen
>            Assignee: Rob Stryker
>            Priority: Critical
>             Fix For: 3.1.0
>
>
> It looks like everything is copied/calculated in bulk and not incrementally
> Try using fileset with / as the root and do a **/*.pdf or similar many hit pattern.
> The Preview Table does not show it is actually working
> When it returns there is a risk for outof memory since it is fetching *all* matching files instead of just a subset(preview)
> When pressing finish the dialog just freezes waiting for the packaging to finish - why is that not done in a background job ?
> During this i always end up getting an outofmemory exception ... 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        



More information about the jbosstools-issues mailing list