couldn't figure out why I didn't see the new bpel stuff when importing jbosstools/trunk.
Turned out you committed a .project file for it called org.eclipse.bpel-trunk when the bpel merge occurred.
I *assume* that is an error since eclipse won't import it together with the other plugins.
Thus I removed it to make it visible on import of projects.
there doesn't seem to be any other eclipse project metadata in there so looks like an error.
Let me know if there were some magic reason for it being there I missed ?
Shit happens when one do releases ;)
But I've already been asked multiple times today about why JBoss Tools does not work with AS 7.1 so
I've blogged about a known workaround for issue.
For those seeing freezes in test runs (I saw tdiesler mention that on irc) then we also see that if we
use AS 7.1 Beta1 jars against a 7.0.x server. The client library just seem to get stuck - but that isn't
visible in JBoss Tools usage since here we use 7.0.x client libraries.
We've reported what we've found until now in https://issues.jboss.org/browse/AS7-2772
Darran already located the cause of some of the issue(s) and we'll meetup tomorrow morning to discuss options/workarounds
for what JBoss Tools can do to support Beta1.
Once Thanksgiving is over we should look into how we can reduce the chances of similar problems occurring again, i.e.
need to add some basic client regression testing to the AS 7 testsuite before an AS release or something.
Max and I were talking about using the Mylyn AbstractNotificationPopup
dialog instead of the standard Eclipse dialog to notify on startup about
new found runtimes
This would mean adding several mylyn dependencies
(o.e.mylyn.commons.core and o.e.mylyn.commons.ui, probably) to the
I would like to know if anyone sees any problem with having these
JBDS 5.0.0.M4 Early Access installers are now available!
Note that bits may take a while to replicate from our staging server to
publication. Please allow at least an hour before attempting to download
them - if the page above still shows the previous milestone instead of
5.0.0.M4, try again later.
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
I tried JRebel out for doing eclipse development and it just works. super nice.
Just need to install jrebel plugin and enable JRebel on the eclipse launch configuration and
you rarely need to start eclipse while doing development.
Note: be sure to do your final testing without jrebel enabled since you never know what side effects
you've created during many iterations ;)
There is even a free version (require online connection)
I created a new plug-in to provide mylyn connections for
issues.jboss.org and bugzila.redhat.com
See details in jira - https://issues.jboss.org/browse/JBIDE-9351
It's placed in common/plugins/org.jboss.tools.common.mylyn
We set two repositories in this plug-in. Firs one is Bugzilla and second
one is JIRA.
The problem is that Bugzilla connector comes from Eclipse Mylyn plugins
but JIRA connector comes from Atlassian update-site.
So we have to have Atlassian plugins installed to get JBoss JIRA
So there are two questions. What module/feature is better for our mylyn
plug-in? Denis' suggestion is to move this plugin to central.
What do you think?
Also we should update our target platform to include Atlassian plugins.
I'm going to create a sub-task of JBIDE-9351 for Nick to update TP.