Eclipse

aurelien.pupier's picture
aurelien.pupier
Blog Categories: 

Everyone is already aware of the Automated Error Reporter Tool - and if you're not I invite you to check one of these articles: reason of this project, InfoQ interwiew. The excellent news is that it is shipped by default in Eclipse Mars. Each time a stacktrace is logged, you can easily report the error with details by clicking View Details in notification popup.

aurelien.pupier's picture
aurelien.pupier
Blog Categories: 

Should the meta files related to an IDE be committed?

There is a never-ending fight over this question. I'm sure that most of the advanced Eclipse users will answer yes but unfortunately in a team you might get some Eclipse haters (and sometimes even IDE haters, who I also call last-century coders). This second and third categories will answer no.

aurelien.pupier's picture
aurelien.pupier
Blog Categories: 

I came across a strange issue with manipulating SWTBotTree, and it took me few hours to find a workaround. I found no exact match with my issue during my research, so let's keep a trace here while waiting for a better understanding of the issue and a fix in SWTBot.

The issue

In a SWTBot Test, calls to SWTBotTreeItem.contextMenu() or SWTBotTreeItem.select() might lead to the following exception:

Caused by: java.lang.IllegalArgumentException: Argument not valid
    at org.eclipse.swt.SWT.error(SWT.java:4422)
    at org.eclipse.swt.SWT.error(SWT.java:4356)
    at org.eclipse.swt.SWT.error(SWT.java:4327)
    at org.eclipse.swt.widgets.Widget.error(Widget.java:476)
    at org.eclipse.swt.widgets.Tree.setSelection(Tree.java:4986)
    at org.eclipse.swt.widgets.Tree.setSelection(Tree.java:4948)
    at org.eclipse.swtbot.swt.finder.widgets.SWTBotTreeItem$10.run(SWTBotTreeItem.java:362)
    at org.eclipse.swtbot.swt.finder.finders.UIThreadRunnable$4.doRun(UIThreadRunnable.java:196)
    at org.eclipse.swtbot.swt.finder.finders.UIThreadRunnable$1.run(UIThreadRunnable.java:89)

Quite an obscure message... what is happening? How can I solve my issue?

The workaround

Easily applicable - but hard to guess - the workaround consists of simply calling SWTBotTree.setFocus() before manipulating the SWTBotTree. For instance:

final SWTBotTree tree = bot.tree();
tree.setFocus();
final SWTBotTreeItem cssNodeFile = tree.expandNode("application", "css", "bonita_form_confirm.css");
cssNodeFile.contextMenu("Open").click();
aurelien.pupier's picture
aurelien.pupier
Blog Categories: 

Do you want to contribute to Bonita BPM Engine? Just follow these steps!

Github Requirements

Bonita BPM source code is hosted on Github.

Consequently, you need to create a Github account if you don't already have one.

aurelien.pupier's picture
aurelien.pupier
Blog Categories: 

I discovered a new issue since my last post about Target Platform migration from Eclipse 4.3 to 4.4.1. It concerns a behavior modification in Datatools API which broke our integration of the Datatools Graphical Designer.

datatools Graphical Designer Integration

The symptom

aurelien.pupier's picture
aurelien.pupier
Blog Categories: 

The Bonitasoft Eclipse RCP development team has migrated Bonita BPM Studio from Eclipse 4.3 to Eclipse 4.4.1 for its Bonita BPM 6.5.0 release. (It is available now / Download / Release note )

It was far more time-consuming than planned and than some previous migrations. Consequently, I would like to share experience in order to help people who didn't migrate yet.

aurelien.pupier's picture
aurelien.pupier
Blog Categories: 

After migrating from Eclipse 4.3 to 4.4.1, we got some Out Of Memory Errors during the startup of our Eclipse RCP application on our CI server. Here's how we spotted and solved the issue!

How to spot the memory issue

aurelien.pupier's picture
aurelien.pupier
Blog Categories: 

After migrating to Eclipse 4.4, and with the support of Java 8 working well, it is time to launch our full test suite on Java 8! Unfortunately, one test for an EMF Validation was failing. It took me quite some time to figure out what went wrong, but the fix is quite easy and it would have never happened if a simple best practice rule was used.

In short:

ALWAYS specify nsURI !

aurelien.pupier's picture
aurelien.pupier
Blog Categories: 

I'd like to offer a few words to say thank you to the folks who worked to make the Eclipse Internal browser work by default on Linux since Eclipse 4.4.

There was a known workaround which required User intervention, such as the one explained on our own community blog.

aurelien.pupier's picture
aurelien.pupier
Blog Categories: 

Oomph is a great tool to automate the setup of an Eclipse development environment. It provides basic default tooling for Mylyn Queries. But:

Notifications