The next release of NetBeans (8.2) has a cool new build-in support for Docker.
Get latest NetBeans development build here.
But since I switched to native Docker integration on my Mac the connection broke as now Docker communicates via socket instead of docker-machine URL:
NetBeans would like to get a valid http or https URL, thus this URI scheme is currently not supported:
But with help of socat (e.g. via
brew install socat) you can create a TCP port (e.g. 9090) listening on localhost attached to the Docker socket to establish a bidirectional connection:
socat tcp-listen:9090,fork UNIX:///var/run/docker.sock
Now we are talking
The recently released NetBeans 8 holds a great gift for all Java Embedded Developers:
Build-in support for Remote Java Standard Edition platform.
To introduce this great and handy feature I created some screencasts:
Part2: JavaFX on Pi
Part 3 – Remote Platform Debugging
José Pereda has also blogged about this feature in action: He and Mark Heckler used it in a distributed environment for their talk G-Force! Self-Powering Global Sensor Nets for IoT (JFokus 2014).
In addition to the support for a full JRE Environment its also worth to mention there is a nice editor as a fronted to the “recreate”-command provided by the all new EJDK 8:
To launch Raspberry PI Java applications from within Eclipse a project called LaunchPI has been started.
For Intellij/IDEA there is a plugin called “sourcesync” that might be helpful for even remote deployment.
But by now I can’t find other approaches that are such seamless and well integrated as NetBeans Remote Platform support.
I always missed a way to format Fluent API code blocks in Netbeans properly.
In Netbeans 7.1 at last there was an option to set the wrapping for chained method calls via:
Preferences: Editor -> Language: Java -> Category: Wrapping
Netbeans 7.2 now offers an additional option to choose whether the wrapping should take place: