]
Rob Stryker resolved JBDS-485.
------------------------------
Fix Version/s: 2.0.0.cr1
Resolution: Done
I was unable to replicate the endless loop / flashing.
The error you reported in your comment was different than the one in your screenshot. I
was unable to reproduce the one in your screenshot, but the one in your comment was
reproduceable when right-clicking on a project in the Project Archives view and selecting
"build project (full)". It was not reproducable if clicking on an *archive* and
selecting "build archive (full)".
Commits have been made including new unit tests.
Project Archives from JBDS 1.1 project don't work anymore
---------------------------------------------------------
Key: JBDS-485
URL:
https://jira.jboss.org/jira/browse/JBDS-485
Project: Developer Studio
Issue Type: Bug
Affects Versions: 2.0.0.beta1
Environment: 64-bit Linux (4GB of RAM), OpenJDK 1.6
Reporter: Andrig Miller
Fix For: 2.0.0.cr1
Attachments: EJB3StressTest.tar.gz, ProjectArchiveProblem.png,
ProjectArchiveProblem2.png, Screenshot-Error building project archives .png
After installing JBDS 2.0 Beta 1, I pulled in my Eclipse workspace from JBDS 1.1. When
you use the Project Archives view and click on a project, and then click to expand the
tree, it seems like Eclipse goes into an endless loop. I have captured two screenshots
from my desktop showing the progress view of expanding the archive that shows the two
outputs that it constantly goes back and forth between (very fast by the way).
Also, if you right click and select build full archive, you get the following exception:
An internal error occurred during: "Build Archive Node".
org.jboss.ide.eclipse.archives.ui.providers.ArchivesContentProviderDelegate$WrappedProject
cannot be cast to org.jboss.ide.eclipse.archives.core.model.IArchiveNode
I cannot find how I can get a full stack trace, so if you could point me in the right
direction, I can capture that, but couldn't find how to get more information on the
error.
The endless loop seems very strange as well.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: