[jboss-user] [JBoss Tools (users)] - Re: Bug Highlights in JBoss Tools 2.1.1.GA

bbeloff do-not-reply at jboss.com
Wed Jun 11 05:08:56 EDT 2008


On the corrupted specifications:

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.

On multiple deployments:

This seems to be a problem in the way the Servers view works - the view reports that an EAR file is deployed twice, though it actually isn't.

I have uploaded the following screen grab:

http://www.classcalendar.biz/tech/servers.png

Which shows the incorrect report.

By the way, there are two other problems I didn't mention in my original post:

* Project archive / Edit publish settings - clicking on' Finish' has no effect - the dialogue box remains open.  This problem did not exist in 2.10.1.GA.  Come on guys, didn't you test this?!

* Refresh of archives in Package explorer view - Attempting to export a newly-updated archive frequently results in an error message, because Eclipse was not refreshed following the archive update.  Doing a manual refresh fixes this (until the next update).  This problem did exist in 2.10.1.GA.  I'm not certain about it now.  Is this a JBoss Tools bug, or is something fundamentally non-transactional in the Eclipse APIs?

On installation problems - I'm not an Eclipse plug-in developer, but this looks seriously screwed.  The software update left all the old plug-in and feature elements still sitting there.  This is surely likely to lead to odd behaviour.


With regret, I'm not going to log any of these on Jira, at least not at this stage.  There are simply too many bugs to make a sufficiently reliable report.  If you can deliver something more stable, I'll do what I can then.

Bruno.

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4157261#4157261

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4157261



More information about the jboss-user mailing list