[jbosstools-issues] [JBoss JIRA] Resolved: (JBIDE-2324) Archives gets corrupted

Rob Stryker (JIRA) jira-events at lists.jboss.org
Thu Jun 12 18:30:47 EDT 2008


     [ http://jira.jboss.com/jira/browse/JBIDE-2324?page=all ]

Rob Stryker resolved JBIDE-2324.
--------------------------------

    Resolution: Cannot Reproduce Bug

Much of the code changed when exploring this issue was about error logging, avoiding NPE's, validating an archive can be built before automatically doing so, etc. Many of these changes will make it easier to share .packages files from one machine to another without it blowing up on you. 

I was unable to force a corruption after making these changes. Since the changes were more general cleanup discovered when using your attached projects, and not related to your actual issue, I'm closing this as cannot duplicate. However, this JIRA definitely precipitated some much-needed cleanup. 

> Archives gets corrupted
> -----------------------
>
>                 Key: JBIDE-2324
>                 URL: http://jira.jboss.com/jira/browse/JBIDE-2324
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: Archives
>    Affects Versions: 2.1.0.GA
>            Reporter: Max Rydahl Andersen
>         Assigned To: Rob Stryker
>             Fix For: 2.1.2
>
>         Attachments: packaging.zip
>
>
> From bbeloff:
> On the corrupted specifications: 
> After an archive is created, it may subsequently be corrupted such that it cannot be viewed in the Project archives window. At this point, it is still visible as deployed under the server, but it is absent.
> The archive disappears from the list of archives in the Project archives view. The archive, if (automatically) updated at this point, appears to be empty. This is difficult to verify, because the problem can be transient.
> I have made available the following: 
> http://www.classcalendar.biz/tech/packaging.zip 
> This contains two Eclipse projects with packaging specifications where this problem has happened several times. (Other projects in my workspace seem to be immune to the problem.) Note that I am not at liberty to include any sources or binaries for these projects.

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

        



More information about the jbosstools-issues mailing list