July 03, 2015
One of the interesting features of NoSQL databases is their schema-less mode of operation. This feature is very useful
during project prototyping and early development since at early the stages of development of projects all data
structures are not clear or have been defined yet. The reason of this post is not to discuss about that subject, but to
show that sometimes you can also use NoSQL with a more traditional database engine like PostgreSQL.
July 02, 2015
Eclipse Mars Release Train
We are happy to announce that Eclipse Scout 5 is out. Taking part for the 5th time in the Eclipse simultaneous release train, the latest release of Eclipse Scout was released last week on 24.06.2015 as part of the train.
Highlights of Scout 5.0.0 are:
- Support for modular Scout Applications
- Improvements Scout Runtime and SDK
Scout Neon – the Outlook
As announced early this year, we have big plans on our roadmap for the Neon release. Most of the team has already been working for months on the develop branch. While the replacement of the Eclipse platform as dependency is already visible, the code of the new HTML5 renderer will be moved over later this year.
We will start to share the result with the coming Neon milestone releases over the coming months. If you have questions or would like to share your thoughts please use this forum post.
Last week at DevNation I had the chance to show some of the cool features that we provide in JBoss Developer Studio, including the Docker tooling that we’ve built for Eclipse Mars and that was released last week.
I also recorded a screencast that highlights some of those Docker tooling features. The video shows how to:
Connect to a local Docker engine (0:32)
Start a PostgreSQL container with a custom username and password (1:52)
Build a custom image for Wildfly to include the PostgreSQL JDBC driver and configure a datasource (3:20)
Start a WildFly container linked to PostgreSQL, with exposed ports and a volume mounted on the host machine (6:44)
Import a Quickstart project using JBoss Central (8:30)
Deploy the project on the WildFly container using a Server Adapter with custom settings (9:55)
Connect to the JVM using the Remote Debugging tools (13:25)
I commented all the tasks as I recorded this screencast to highlight the important steps. Beware that if you run &aposboot2docker&apos, you’ll need to use a specific IP address instead of &aposlocalhost&apos when creating the Server adapter in Eclipse (trust me, I made this mistake before…)..
The dockerfile and its associated resources (module.xml, standalone.xml and JDBC driver) used during the demo is available on GitHub, so feel free to clone the repo and play with it ;-)
Keep in mind that some wizards showed in this screencast may be refactored in the near future, as we target Eclipse Mars SR1 at the end of September for a more complete version of the Docker tooling.
Feel free to discuss features and report bugs with us on the Docker component of Linux Tools at Eclipse.org. As usual, feedback is welcome!
my.openHAB Goes Public!Having offered the cloud companion service for openHAB since more than a year as a closed beta program, it is now time to make it available to everyone! And yes, we are determined to keep it a completely free service for all openHAB users, so that everybody can enjoy the easy and secure remote access as well as the push notifications to the native Android and iOS apps.
Integrate openHAB with Hundreds of Web Services through IFTTTOur new IFTTT integration is the even bigger news and the very best reason to use my.openHAB: From today on, you can use openHAB together with IFTTT (If This Than That)! As a result, you can make use of all existing IFTTT channels within your rules - simply activate the openHAB channel and grant IFTTT access to your my.openHAB account. You can then use openHAB as a trigger for recipes or send any kind of command from an IFTTT recipe to your openHAB instance.
We think that these new services are very useful additions to many openHAB users. Please provide us your feedback on our mailing list. Note that my.openHAB does not yet work with openHAB 2.0 (which is still in alpha and not meant to be used productively by end users) - but the integration with my.openHAB is high on my priority list as this combination will lower the entry barrier for new users to a new minimum - I am looking forward to it!
Let’s say you have a Vert.x 3 application you want to install on a Linux server. But you want the old school way (I meant not the docker way ☺). So, in other words, you need an init.d script. This post proposes an init.d script that you can use to start / stop / restart a Vert.x 3 application.
July 01, 2015
Jonas Helming, Maximilian Koegel develop a simple client-server app using a variety of Eclipse frameworks and producing 10 different versions of the same client running on the multiple platforms.By Jonas Helming, Maximilian Koegel
Holy it’s July already!
Last year I helped organized the first MesosCon community conference and we’re doing the same this year with a slightly larger Program Committee (thankfully, organizing conferences is so under appreciated in the tech industry).
Recently we announced the schedule and some of the keynote speakers for MesosCon 2015. On top of an amazing program, we’re excited to have a bunch of keynote speakers with @benh, @neha, @kenowens12, @adrianco and more.
— Apache Mesos (@ApacheMesos) June 30, 2015
Honestly, it’s been great to watch the Mesos community grow over the years, from its humble beginnings at Twitter to Apple announcing their adoption to seeing a plethora of other companies using it within their infrastructure.
Also, if you’re interested, the lightning talk CFP is open until July 14th.
Hope to see you there! In my opinion, there really is no better set of events if you’re interested in seeing how the future of infrastructure will be run, along with having the opportunity to shape that direction.
June 30, 2015
Eclipse Mars on Linux uses first time GTK3 toolkit by default (all versions before 4.5 were on GTK2), and that is the major driver for new bugs from Linux users. I'm writing this on Linux, and know what I'm talking about. Eclipse SWT team crafted the SWT GTK3 port with tremendous effort, but unfortunately GTK3 exists an a bunch of (partly incompatible) versions with different API behavior, and developing a widget toolkit on top of it is a pain, not a pleasure (IMHO).
The major issue with GTK3 is that if SWT is broken, it affects each and every Eclipse UI plugin, at most unexpected places! Anyway, now this is default toolkit and we must know how to work with it (or workaround it).
So if you are on Linux and see a new UI regression on Eclipse Mars, please be aware that if this a GTK3 issue, there is easy way to fix it - switch to back to the GTK2 version (which is still supported by Eclipse 4.5). But before switching the toolkit - try to help Eclipse and report the issue you observe, so that the next release has a bug fix for it!
1. Search for similar bugsBefore reporting, please search for bugs! All properly reported GTK related bugs contain [GTK], [GTK2] or [GTK3] keywords in the summary. If your bug is already reported, do not report another one, but just add extra details you want to mention.
2. Check if the GTK3 to blame?Try to check if your issue is GTK3 related: switch to GTK2. Either export SWT_GTK3=0 in the shell before starting Eclipse or add this two lines to your eclipse.ini:
--launcher.GTK_versionwhich has exact the same effect. If this helps, we will know that the problem is most likely GTK3 related.
3. Check if the GTK+ theme to blame?Not always the GTK itself is a problem, but the current GTK theme (widget style).
GTK applications can be "styled" - they can look and feel differently on same GTK version due the currently selected "style" or "theme". There are various GTK themes available, and some are better for use with Eclipse as others.
Beware of oxygen-gtk theme on GTK3! This pair is known to be extremely buggy!
Unfortunately, many distributions set the default KDE GTK theme to oxygen-gtk. It worked well in the past with the old GTK2, but on GTK3 this can be a source of multiple issues. If you are using KDE desktop, the first thing you should do is to check if you are using oxygen-gtk. If so, switch to another theme (Adwaita or Clearlooks-Phenix). Later one is my favorite, and I even forked it to make it working on GTK2 in the way I like it :-).
Please note, that after switching GTK theme it is highly recommended to restart Eclipse to avoid unexpected side effects of half-zombied theme artifacts. If the problem do not disappear after restart we know it is independent from the theme.
4. Report the bugIf your bug is not on the list, prepare the information we need to triage it properly! First and foremost we want know exact Eclipse and GTK version used. Eclipse version is shown in the "About" dialog, GTK version is not that easy to retrieve. If you are on Eclipse 4.5, you can see GTK version used by SWT in the "Help -> About -> Installation Details -> Configuration" dialog - search for the "org.eclipse.swt.internal.gtk.version" property, it looks like:
But of course on Linux we want use command line tools :-)
For the rpm - based distributions (Fedora, RHEL, CentOS) it's easy: just call
rpm -q gtk2; rpm -q gtk3and you will see something like:
For the debian based distributions (Ubuntu & Co) I know about two commands:
apt list | grep installed | grep libgtk2.; apt list | grep installed | grep libgtk-3.or
dpkg -l | grep libgtk2.; dpkg -l | grep libgtk-3.but both of them aren't that concise as rpm and print lot of unneeded information. Please also note inconsistent naming schema: libgtk2 but libgtk-3. Nice and makes lot of sense, isn't?
Now we know the installed GTK version we can go and submit bug report against Platform/SWT.
NB: please also add your operating system details, desktop environment (Unity/Gnome/KDE) and GTK+ theme used.
From my personal point of view SWT GTK3 port is still not on par with GTK2 and ideally shouldn't be made default for 4.5 - it wastes lot of space and introduces multiple regressions. But the decision was made and only way to fix it now is to contribute to Eclipse.
Every couple of years, I work with the Eclipse Architecture Council to revise the Eclipse Development Process (EDP). The EDP is the document that describes the structure of projects, relationships between projects and committers, and the sorts of activities that projects are expected to engage in.
After many years and many revisions, it’s past time for a complete (or near complete) rewrite. That’s an exhausting thought, frankly, but it’s my hope that we’ll be able to do just that.
I’ve started gathering ideas for how the EDP can change on Bug 463857; this is an umbrella bug to collect the issues that need to be addressed. I’ve already added a few blocker bugs for some issues that I feel need to be addressed. Feel free to add your comments and other blockers as you see fit. Please do join in the discussion.
The first thing on my list is release reviews. Originally, a release review was an event: a conference call on which the project was required to defend their release to the community (or at least that subset of the community that joined the call). In those days, review materials needed to be prepared and disseminated a week in advance of the call to allow the community to prepare. But as community participation dropped, so to was the conference call and we turned the week of review material availability into the review itself.
I’m not at all convinced that there’s much value in the formal week of waiting to release. The community rarely–if ever–comments on release review documentation and since we set reviews up to succeed, they never fail. Further, I’m of the mind that anybody who is interested in an open source project is either already following the progress of the project or should be. If you’re waiting for the release review to be notified that something new is coming from your favourite open source project, it may be time to consider getting more directly involved with project discussion.
For releases, I’m thinking:
- Get IP Team approval of the IP Log;
- Get Project Management Committee (PMC) Approval of the release; and
- Ship it.
Documentation requirements are the PMC’s call. Personally, I think that it’s totally reasonable to require that projects produce at least a single paragraph that describes the nature of the release in broad terms. And planning needs to happen in some form: either as a formal plan or more informally via target milestones on Bugzilla records.
Add your thoughts on Bug 415620.
With close to 100 participants each, Munich and Zurich are among the largest Eclipse democamps. Last week, participants in the two towns north of the Alps had the opportunity to meet old and new friends and learn about a wide variety of topics in the Eclipse ecosystem.
Democamp Munich, June 23rd
The democamp in Munich was hosted for the second time in the building of Capgemini (many thanks to the friendly staff) and organized by BSI Business Systems Integration, EclipseSource Munich and Angelika Wittek.
The official sessions started with a demo by Tom Schindl presenting his e(fx)clipse Compensator project. Compensator, a set of loosely coupled components, can be used to build light weight IDE. With its Java FX front end the developer may take advantage of the available CSS styling. In the impressive second part of the demo the participants watched Tom assembling a small Dart IDE in less than 10 minutes that included syntax highlighting, error marks and code completion.
In the following session, Jörg Hohwiller demonstrated OASP4J-IDE that helps to quickly share and update complete Eclipse IDE setups for Java projects. As individual project installations do not interfere with each other developers are free to work with as many concurrent project setups as they need.
Next was Jens Reimann and Jürgen Rose with the Package Drone project that was accepted very recently as an Eclipse Foundation Project. With a Package Drone repository Maven Tycho can now also be used to upload software artifacts to a Package Drone repository. Once in this repository Package Drone can provide the artifacts in different forms such as P2 update site or a OSGi R5 repository. For future versions of Package Drone support for additional formats like APT and YUM are planned.
With Profiles for Eclipse (based on Oomph) Frederic Ebelshäuser was addressing the pains of reliably setting up your Eclipse IDE. Profiles for Eclipse is currently available via a proprietary Eclipse HUB portal that also includes some social features. Using this portal it is possible to share profiles between participants, following profiles and getting notified when subscribed profiles are updated.
In the last session before the break, Matthias Zimmermann demonstrated how to build modularized enterprise applications with Eclipse Scout. For modularization, the Scout framework supports both technical layers and business slices. Matthias also announced that with the Neon release train, Scout is removing its dependency on the Eclipse runtime and become a pure Java framework. At the same time, Scout will also get a HTML5 new renderer.
After the break, Alexandra Schladebeck presented the new Jubula Client API in an entertaining talk. With the new Jubula client API that is shipped with the Mars release UI tests can now also be written in the form of JUnit test cases. After the audience had to promise to use these new possibilities only with great responsibility, Tom Zierer performed a hands-on COBOL programming session for mainframe development creating a “Legacy in Action“ feeling. After demonstrating the pain of working with too many character based screens, an Eclipse based IDE was presented that covered syntax highlighting, compiling on the back-end, collecting the result and displaying error markers in the source code.
In his talk about EMF Forms Jonas Helming presented the state of version 1.6 that is shipped with the Eclipse Mars release. The session demonstrated the available tooling to create the view model that maps elements of an entity model to UI controls. After demonstrating the tooling to create a form to manage persons, the created UI was shown in preview mode and in the form of a standalone RCP application. Jonas also mentioned current work on JSONForms a new web renderer that is based on AngularJS.
The democamp in Munich concluded with the Eclipse Smarthome session by Jochen Hiller. This talk concentrated on demonstrating the new features such as the auto-dicovery for attached devices. In the extensive demo, a variety of devices such as light bulbs, smart sockets, audio devices and even a hair dryer were included. For the demo itself Jochen showed the new slick Paper UI of openHAB 2, that is based on the Smarthome project.
The democamp concluded with prolonged networking, buffet and beer that was greatly enjoyed by the participants.
Democamp Zurich, June 24th
Taking place for the 4th time, the democamp Zurich was very well attended and attracted around 90 participants. As in previous years, the Swiss Federal Institute of Technology (ETHZ) was hosting the democamp in one of the centrally located lecture halls and the event was organized by itemis Schweiz and BSI Business Systems Integration and with the Java User Group Switzerland as a partner organisation.
The first session in Zurich by Martin Lippert was all about the Spring and Cloud Foundry Tooling for Eclipse. The demonstration covered various aspects of setting up Spring projects with Spring Boot and included Spring development with advanced code completion, for example when working with YAML configuration files. As an experimental feature Martin also demonstrated the capability to debug a Spring application that is running on a server node in the cloud.
In the following three sessions before the break the audience was listening to contributions that have been presented the day before in Munich. Tom Schindl introduced the e(fx)clipse Compensator, Jonas Helming talked about the latest features of EMF Forms and Matthias Zimmermann demonstrated how to build highly modular enterprise applications with Eclipse Scout.
After a short break, Dierk Koenig presented Grails in a live-coding session to the audience (no slides). In this way Dierk demonstrated how simple data-centric applications can be built with Grails by creating a simple application to manage participants.
In the next talk Axel Terfloth introduced the audience into the Yakindu Statechart Tools, an Eclipse based open source project to specify, validate and implement event-driven systems based on state charts. After creating a first simple state chart, the demo included running simulations, adding parallel execution paths to the example and generating Java sources from the model.
Following the agenda in Munich Jochen Hillers Eclipse Smarthome session also concluded the democamp in Zurich.
In the networking session with food and beer many stimulated discussions took place. As the university was closing down earlier than the more commercial location in Munich, individual groups were simply taking the ongoing discussions to nearby beer places.
Democamps are about the participating People
From repeatedly attending and organizing Eclipse demcoamps it becomes obvious that these events are not only about learning new things and staying up to date with the projects presenting the latest features. Having developers and project leads on-site in an informal setting also allows for interesting discussions about work, personal views and potential collaborations. In addition, the local character of the democamps helps to build and maintain relationships across organisations over many years. It seems that this last point lets attendants come back to these events and makes them look forward to meet their colleagues.
If you have attended one of the democamps and would like to share your thoughts please use this forum post.
Time flies when you’re having fun! EclipseCon France has just finished and it’s already time to plan for EclipseCon Europe 2015 in November. The call for papers is out, and you should not miss the chance to present at the tenth European Eclipse Conference. It’s a great opportunity to meet people and show off your technology.
The first Eclipse Summit Europe was convened in 2006 – a two day event in the charming town of Esslingen am Neckar just south of Stuttgart. Since then the conference has been at the Forum am Schlosspark in Ludwigsburg, also in the Stuttgart region. In 2011, for the tenth anniversary of Eclipse, the name was changed to EclipseCon Europe. The number of attendees, from around 30 different countries, have been growning steadily to about 600 in 2014. It’s now a three day event, well packed with activities and interesting talks. This year we’re even adding a science track for talks about the tools on the scientific workbench.
The deadline for EclipseCon Europe submissions is the 31. of July, so you have a whole month to work on your abstract!
You may also consider submitting a paper for the Trondheim Eclipse Mars DemoCamp in August. We have space for a couple more talks and it’s a good opportunity to try your talk on an Eclipse-savvy audience before the real deal at EclipseCon.
See you there!
Java™ 9 support has not yet landed in our standard download packages. But you can add an early access preview to your existing Eclipse Mars install.
The Eclipse Java™ 9 Support (BETA) contains the following:
- ability to add JRE and JDK 9 as installed JRE;
- support for JavaSE-1.9 execution environment; and
- ability to create Java and Plug-in projects that use a JRE or JDK 9.
At the moment Eclipse must be run with Java™ 9 if you want to use Java™ 9 in your workspace. You can download from http://www.oracle.com/technetwork/articles/java/ea-jsp-142245.html.
This is an implementation of an early-draft specification developed under the Java Community Process (JCP) and is made available for testing and evaluation purposes only. The code is not compatible with any specification of the JCP.
Install the Java 9 Beta via the Eclipse Marketplace:
June 29, 2015
It is now official. A posting from the official Android Developer’s blog has confirmed what many of us already knew, that the days of the original Android Developer Tools based on Eclipse was numbered. Honestly, I think this is not a bad thing. It does free up the resources that Google has to fully concentrate on the Android Studio tooling, and continue to improve and advance their chosen strategy going forward.
However, all is not lost, as the Andmore project is here to continue to provide Android tooling for the Eclipse community. However, progress right now is pretty slow, and that is because my own time has been limited. With this said, we do have integrated support with Maven and the android-maven-plugin through the m2e-android project’s support. The Buildship project can import an existing Android gradle project, and even run some tests, but it still has problems in setting up the project natures and make things work with Andmore. There is a feature request opened to have some sort of project configuration extension so that Andmore can help configure such projects to better work with the tooling.
The state of Android development with Andmore and how well it keeps up with the yearly and quarterly updates coming from the Android Open Source Platform is going to greatly depend on contributions from the community. We need your help, as one person definitely can not maintain the project alone. So please do take a look at the bug/feature backlog, feel free to fork the project on GitHub, roll up your sleeves and get a bit dirty, submit pull requests and file new bugs. Andmore is going to be what the community makes it. We wished for years that ADT had been open more to contributions from the community, now is the time for us to follow through on that wish.
We are happy to announce that together with Mars we have released EMF Forms and EMF Client Platform 1.6.0! We want to thank all committers and all contributors for their work as well as the active ecosystem of users and adopters for the feedback and support!
EMF Forms is a framework focused on the creation of form-based UIs. EMF Client Platform is designed to support the development of applications based on an EMF data model. If you are not yet familiar with EMF Forms, please refer to this tutorial for a introduction of EMF Forms.
Both frameworks are part of Eclipse Modeling Tools Mars (version 1.6.0), however, we have already released a service release (1.6.1) fixing a Bug with the double control, so if you use EMF Forms or want to get started, we recommend to update to 1.6.1, available from our download page.:
Please have a look at our migration guide, e.g. if you have used the service provider interface in a previous version.
Since February 2015 and with the 1.6.x release, we have closed 111 Feature Requests and Bug Reports.
It is amazing to see, that the number of active contributors is still growing and how much effort was spent so far. OpenHub shows some impressive numbers:
We will describe the most notable new features in a small blog post series starting next week. We hope you enjoy the new release and provide us with feedback!
Leave a Comment. Tagged with eclipse, emf, emfforms, mars, eclipse, emf, emfforms, mars
Never ending fight on IDE related meta-files included in code source found an alternative: Eclipse Smart Importer rocks!
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.
When the answer is no, setting up your preferred IDE might become cumbersome. There is missing meta-information, for instance contained in .project files, which can lead a developer to import projects with the wrong nature into the IDE. Hopefully, here comes the Smart Importer! It enables Eclipse to guess the most appropriate nature when importing a project.
For instance, with the Bonita BPM engine project, you just have to specify the git clone repository that you want to import and all the correct natures for every projects are detected automagically.
The project is not integrated in the Eclipse Mars Release train but is available from a dedicated update sites. It will enable you to test and contribute - ideas and code - for Neon, the next version.
June 27, 2015
We at ANCIT are planning to organise a list of Eclipse based Public Training Courses. As part of that we are planning to organise a Public Classroom for Eclipse PDE & RCP. Course Content of the training is attached to the email.
Workshop Title : Eclipse 3x PDE/RCP - 2 Day Workshop
Trainer Profile : Annamalai Chockalingam
[Linked In Profile : https://www.linkedin.com/in/annamalaichockalingam]
Date of Workshop : 9th & 10th July 2015
Time of Workshop : 10.00am to 5.00pm
Venue : ANCIT Consulting Office [Apponix Technologies], Rajaji Nagar, Bangalore
Location on Google Map : https://www.google.co.in/maps/place/Apponix+Technologies
Cost of the Workshop : Rs.7500/participant + ST.
If you have more than 3 nominations you will get a discount of 10%.
If you register before 1st July 2015 you will get 20% discount on the above mentioned price.
For more information write to email@example.com
Max Domeika discusses the relative strengths and weaknesses of the current Eclipse IDE for IoT development, and tooling support for Sensor emulation, Power Analysis, and Cloud.By Max Domeika