Posts tagged with 'eclipse'

Want to contribute to JSDT project but do not know how? Think that environment setup is too difficult and comprehensive? Now you can easily setup JSDT using Oomph within a few minutes! Here is a short demo video which explains how to do it:

Node.js support was originally implemented as part of the Eclipse Neon release. In Neon.1 debugger facilities have been significantly improved. Previously in order to change the code during the debug session one should have saved the JavaScript file, right click on it → V8 Debugging → Push Source Changes to VM. Now saving the file is just enough - new changes will be applied automatically:

Also, there are a few important bug fixes that improve the debugging experience:

Now there is a possibility to debug JavaScript using Chrome / Chromium browser. Basically, in order to debug JavaScript one should simply right click on the html file → Debug As.. → Chrome / Chromium Debugger:

There is also a possibility of debugging JavaScript for applications running on servers using Chrome / Chromium Debugger menu item:

Now it is possible to execute tasks via "Quick Access" - just press Cntrl + 3 / ⌘ + 3 and choose Run As Grunt / Gulp task:

All npm scripts defined in the package.json can be now executed via Run As.. → npm Script context menu:

The output of the script command will be reflected in the "Console" view:

In the next release we are going to switch to the Closure compiler which is more tolerant and has better performance in comparison with currently used Esprima parser. Moreover, we are going to return broken JavaScript search facilities back to JSDT. Actually, most of the work in the search direction is already done:

Other plans are coupled with polishing Node.js / JavaScript debuggers and making the whole feature set smooth, stable and complete. If you want to have some particular bug fixed in Neon.2, please, speak up on the wtp-dev mailing list or let us know on twitter, youtube, stackoverflow etc.

Thank you to the contributors who made the Neon.1 release happen:

We would like to express special gratitude to the community for their feedback! We look forward to hearing your comments, remarks and proposals about new Neon.1 release.
Have fun!

Ilya Buziuk
@ilyabuziuk

Description:

The Eclipse JavaScript Development Tools have reached a new level of features and usability with Eclipse Neon. Many things were implemented as part of the JSDT 2.0 release that is now available with Eclipse Neon. This webinar demonstrates the following new features:

The talk also features plans for the future of JavaScript development in Eclipse IDE.

The slides for the presentation are available here.

Description:

Docker is awesome, but how to use it well when doing development? In this talk you will get a quick introduction on how to use Docker effectively, especially for development from within Eclipse. We will show how the release of Eclipse Neon supports Docker to make it even more integrated into your day-to-day work from within your IDE. In particular, you’ll see how you can pull and run an image for a database, build a custom image for an application server, run it and deploy an application using data volume, exposed ports and container links. We will also take a look at some of the newest features, such as support for Docker Machine, TM Terminal integration, run configurations for containers, and a variety of other UI improvements.

The slides for the presentation are available here.

Other webinars have also been recorded and are available on the Eclipse Neon Webinar Series on Youtube.

Enjoy !
Xavier Coulon
@xcoulon

There were mentions of adding static imports for JUnit Assert methods. I recommend also to add some others for these popular frameworks:

Please check out the below screenshot for what to add to your favorites:

There is no more need to type twice Ctrl+space to have the JUnit 4 Template proposals. Even better, when you start typing "test", the JUnit 4 Template is listed first.

Did you ever noticed the little icon on top right corner of JUnit view?

Click on it! You will get a nice dialog comparing the actual and expected results:

MoreUnit is a plugin helping you to create and maintain Unit Tests. Some of its nice features are:

If you have tests in another projects - for instance you are an Eclipse RCP developer and use fragments for your unit tests - you can specify this folder from the MoreUnit Preferences page.

Infinitest is a useful plugin to respect the Fail fast principle. It continuously executes tests in the background each time you save a file.

If there are test failures:

As some tests might be time consuming or requiring some external configuration or UI interactions, you can filter those by providing a infinitest.filters file at the root of the project. The same file will be used in other supported IDEs by Infinitest.

After you wrote your tests, I recommend to launch the Eclemma Coverage tests. You can use Alt+Shift+E,T. It will show you a nice overview of possible missing test coverage in your code.

Note: Don’t focus too much on the percentage but have a deeper look to uncovered or partially covered lines. Make sure that these lines are not critical ones.

If you’re an Eclipse RCP developer, I will be happy to see you assisting to presentation at my talk at EclipseCon France (Toulouse, June 7-9). I will talk about possible architectures and available tooling to have fast Unit tests while developing Eclipse plugins. I’m looking forward sharing my experience and continue discussions later on.

Do you have some other Tips, Tricks and best practice to share?

If you are using a different IDE, do you know about killer features enabling you to efficiently write unit tests but which are missing in Eclipse? Please share them!

RedDeer is a framework for testing Eclipse plugins (or RCP) and can be executed over various operating systems (Linux, Mac, Windows). At the beginning it was developed as an alternative to SWTBot but now it contains many features and tools which can help you with writing automated tests.

Now, when the project has left the incubation phase, the API won’t be significantly changed for a long time and you don’t have to change your existing code together with RedDeer updates. Like the previous version (0.8.0.Final) the RedDeer 1.0.0.Final is also intended for Eclipse Mars.

In addition to making the framework more and more stable we also plan to improve the recorder and our code generation tool. Moreover, the RedDeer framework is becoming a part of JBoss Tools target platform which means it will be available for any developer contributing to JBoss Tools.

Do you have any idea about a new feature? Raise an issue on github! If you want to contribute, please follow steps described at https://github.com/jboss-reddeer/reddeer/wiki/Developer-guide.

You can install the RedDeer framework from http://download.jboss.org/jbosstools/updates/stable/mars/core/reddeer/1.0.0 and learn something about it from the following materials

and don’t forget to follow us on twitter @jbossreddeer ;-)

Andrej Podhradsky

We’ve added icon decorators on the containers to show their state. This makes it clearer if a container is running, paused or stopped.

We’ve worked on the workflow to pull and search images from Docker Hub. The updated 'Pull Image' wizard can be launched from the 'Docker Images' view or from the 'Docker Explorer' view (a new context menu entry is available on the connection node and on the 'Images' node)

The wizard detects the tag in the image name and if none is specified, the image tagged latest will be pulled.

If the user needs to search a specific image name, she can click on the 'Search…​' button which will open the 'Search' wizard:

followed by a second page that displays all the tags for the selected image:

Even though this wizard can only search from Docker Hub, users can nonetheless pull images from other third-party registries. In that case, image name needs to be prefixed with the registry host and port, such as 192.168.59.103:5000/centos:7.

Finally, we`ve also added a new launcher to build images from a Dockerfile.

The source path is a directory in the workspace or on the file system and the 'Docker Connection' combo box specifies on which Docker daemon the image will be built.

As always, feedback, feature requests and bug reports are welcome. Since this tooling is developped at Eclipse.org, you can join us on our public mailing-list or use Bugzilla to report any bug or feature request.

Have fun !
Xavier Coulon
@xcoulon

You can find more info at these locations:

There is complete list of RedDeer public resources:

Let us know if you like what you see and feel free to leave a comment on this blog or reach out to the RedDeer project to give them feedback.

Have fun!
Max Rydahl Andersen
@maxandersen

Strategic Members are organizations that view Eclipse as a strategic platform and are investing developer and other resources to further develop Eclipse Foundation technologies. Strategic Developers commit to assign at least eight developers full time to develop Eclipse technology, lead Eclipse projects and contribute annual dues up to 250.000 $.

At Red Hat we already have more than eight developers doing development Eclipse technology, both at and around the base Eclipse distribution.

We are leading multiple Eclipse projects:

This work is used in our JBoss Tools project and two products: JBoss Developer Studio (Middleware) and Red Hat Developer Toolset (Linux Platform).

By upgrading to Strategic Developer we are confirming our continued support and commitement of resources to Eclipse, but also increasing our funding to be $250.000 annually.

Red Hat have an interest in Eclipse Foundation continues to thrive, and that its flagship, the Eclipse IDE and other opensource development tools and runtimes continues to evolve and improve.

This announcement also means I’ll have to step down from the board as solutions member representative, but I’ll be joining again as Red Hat’s representative for their newly aquired Strategic Developer position.

I’m happy to have served and I’m looking forward to see which other solutions member will come join in on the board and bring Eclipse Foundation forward.

We’ve been contributing and continue to help making Eclipse Mars a great release, together with the rest of the community. We are especially working on fixing GTK/SWT on Linux, making Docker support and looking at improving the Java Script Development tools. The latter I did a presentation at EclipseCon which provide some of ideas what we are working on.

By becoming strategic developer we also plan to be involved more in how Eclipse IP and Development process works and evolves. Something that become more important to make more effective for fast moving projects to feel better at home at Eclipse.

On top of that Eclipse have a lot of other areas going on which Red Hat are keeping our eye on - especially in the area of web IDE’s and Internet-of-things.

If you are interested in hearing more about this or have a suggestion please feel free to contact me by mail or leave a comment below!

Let’s Have fun!,
Max Rydahl Andersen
@maxandersen

The Docker Explorer provides a wizard to establish a new connection to a Docker daemon. This wizard can detect default settings if the user’s machine runs Docker natively or in a VM using Boot2Docker. Both Unix sockets on Linux machines and the REST API on other OSes are detected and supported. The wizard also allows remote connections using custom settings.

The Docker Explorer itself is a tree view that handles multiple connections and provides users with quick overview of the existing images and containers.

Built-in filters can show/hide intermediate and 'dangling' images as well as stopped containers.

The Docker Images view lists all images in the Docker host selected in the Docker Explorer view. This view allows user to manage images, including:

A wizard lets the user input all the arguments to create a new container from an image. When the container is started, all the logs can be streamed into the Eclipse Console:

The Docker Containers view lets the user manage her containers. The view toolbar provides commands to start, stop, pause, unpause, display the logs and kill containers.

This view also provides a filter to show/hide stopped containers. Users can also attach an Eclipse console to a running Docker container to follow the logs and use the STDIN to interact with it.

We also integrate with the Eclipse Properties view to provide users with info and 'inspect' data about a selected container or image.

Roland Grunberg and Jeff Johnston from Red Hat started this project and are currently in the process of getting the code accepted to Eclipse.org as part of the Linux Tools project (even if the tooling also runs on other platforms), which explains why the code has not been made public yet.

Taking about code, we rely on the open source Docker client developed by Spotify to handle the low-level communication with the Docker daemons and I should thank the Spotify developers who maintain this library. They’ve been very kind to quickly review and merge the pull requests that we’ve submitted and it’s been a pleasure to contribute to their project. Open source collaboration FTW :-)

There is still some work and the screenshots showed above may still evolve as we add more features, but we hope that this blog entry will give you a taste of what’s coming soon in Eclipse with regards to Docker tooling.

While the code will be hosted in Linux Tools project at Eclipse.org, we intend to also ship it as part of JBoss Developer Studio 9 and JBoss Tools 4.3 later this year.

We also created a JIRA component to track this work-in-progress in the scope of JBoss Tools, including some issues with mockups.

Beyond this basic Docker tooling we are looking at integrating launching servers and even native CDT builds on docker containers, but this will be the subject of future posts on this blog ;-)

As usual, feel free to provide us with feedback on our forum, on JIRA or on IRC. Questions, comments and suggestions are always welcome!

Stay tuned!

/Xavier
@xcoulon