Marcel Bruch's blog
Eclipse has a vibrant community. This is particularly evident when attending EclipseCon France.
What I especially like about the French (but English speaking) branch is its great mix of talks. EclipseCon France did not start out with the intention of being just another home for great technology talks. With its Unconference day, Ignite talks and special technology tracks it also offers plenty of room for additional emerging topics and technologies which are especially relevant for industries. It also aims to provide a great environment for the numerous Eclipse Industry Working Groups such as Automotive, Polarsys, and Eclipse Science in order to foster the collaboration, presentation and discussion of novel ideas and to help find new partners in industry.
As such the EclipseCon France 2015 program committee is looking for a great mix of talks on well-known technologies, emerging (industry-related science) topics, and also those showcasing the benefits of, for instance, using code quality tools, code review tools, and testing frameworks in your company. For example, which obstacles you had to overcome in order to get your team using such tools. In other words, talks from which developers can learn about how to improve themselves and their team. Personally, I’d also like to see a couple more talks reporting experiences of how to get en vogue software development processes right in your company.
So, if you introduced new tools or changed your team’s development process and would like to talk about it, submit a talk to EclipseCon France. I’ll be glad to see your submission.
If you work on an amazing research project that has the potential to change our daily developer life, submit a talk. I’ll happily attend your session.
If you breath code and want to talk about other cool stuff that does not fit existing categories, let us know.
But remember: the deadline is fast approaching, April 14! Your proposal should clearly state your target audience and what will be learned by attending your session.
See you at EclipseCon France in June,
Automated Error Reporting and UI Freeze Detection for Eclipse Mars Milestones
Christmas is just around the corner. Besides being a contemplative time, this is also an unmistakable sign that the Eclipse community is already halfway there on its journey towards the next annual simultaneous release. As in the years before, there will (likely) be more than 70 participating projects, with more than 700 people contributing more than 60 million lines of code. And somewhere, hidden within these 60 million lines, there will be bugs. Unavoidably.
Perspective switch: Imagine it’s June and you’ve just downloaded the latest annual Eclipse release. You are curious about all the new features that have been implemented in the last year and maybe it even feels a bit like unwrapping a Christmas present in June. But as you start working with it, you notice that some things do not always work as expected. Nothing severe yet, but it starts getting annoying. Then you open the error log and see that slowly, but steadily, it starts to fill up...
Big Data Makes Life Easier for Software Developers
Software systems not only pervade more and more industries, but they are also growing more and more complex. But regardless of whether software developers have to understand yesterday’s legacy systems or tomorrow’s hot technologies, one question is always the same: How do I tell the machine what to do? Using Big Data, the young company Codetrails GmbH answers this question for Java developers. High-Tech Gründerfonds funds the spin-off of TU Darmstadt to further Codetrails’ capabilities of automated knowledge transfer and bug detection.
Codetrails continuously strives to improve your performance by building tools that let you develop code faster with Eclipse. If you know Eclipse Code Recommenders then you probably know that (among other things) we spent quite some time on improving Eclipse’s content assist.
In case you wonder why, the answer is pretty simple: We improve content assist because it is the fifth-most frequently used command in the IDE. Right after
Save, (Jump to)
Next Word and Paste:
It’s been a while since the Eclipse Foundation decided to stop the Usage Data Collector. The main reason for stopping this service was that, although thousands of users shared data, neither plug-in providers nor researchers took significant advantage of the data collected at that time. Since its shutdown, however, a new demand for collecting usage data evolved. But compared to the data collected by the UDC, today’s demands are different and vary quite a lot from project to project.
We are happy to announce the availability of the first service release for Eclipse Code Recommenders 2.1. While most changes in a service release are usually bug fixes only, there are four features I’d like to highlight:
As a frequent reader of this blog, you already know that Code Recommenders is all about helping developers to use existing APIs correctly. It does so by analyzing thousands of sample applications and extracts patterns how other developers used that API before and enhances your code completion with neat percentage values that give you pointers which methods you are likely to use next.
You probably also know that Mylyn Tasks is about clean UIs. To keep your UI clean, Mylyn for example removes elements from the package explorer which are irrelevant for the current task you are working on and thus removes the clutter that may distract you from your goal. It also boosts code completion proposals to the top that are more interesting than others. All purely based on the knowledge which methods or types developers (who worked on that very same task before) used or looked at.
You may have noticed that Pascal Rapicault started a Kickstarter project called EasyEclipse recently. It aims to improve the Eclipse Java IDE in various ways and tries to find its niche between complete open-source and a closed-source licensing model by offering a commercial license for some features only available in EasyEclipse and giving back to the open-source version of Eclipse making Eclipse a better IDE over the time.
When we released 1.0 in June 2012, we actually had no idea how developers would respond to a completion engine that “messes up” with your code completion window just because it “thinks” it would know better than JDT which proposals you are more interested in. But it turned out that the idea wasn’t wrong at all and you guys actually liked the idea of Code Recommenders quite a lot.