Java

Blog Petals planet - Part 3. This is a blog post to sum up some of my thoughts I shared on the Nebula-dev mailing list with Wim Jongmam and later on Twitter with Zoltán Ujhelyi and Dave Carver about naming build types at Eclipse.org and scheduling them.

It is a topic open to debate. My goal with it is to find out practices and names that are relevant and useful for community (contributors and, mainly, consumers) and also to give food for thoughts about how to deal with builds. Background Historically, Eclipse has 4 to 5 classical qualifier for binary artifacts: ReleaseMaintenanceStableIntegrationNightly This wording is specific to Eclipse, only Eclipse people do understand the meaning of it.

This guy has driven a revolution in the way we build and deliver software Now Eclipse.org provides continuous integration, to automate and manage builds executions, and most of them happen whenever a change happen on your VCS. Requalifying binaries to make consumption clearer ReleaseIntegration Name it to know what it provides! Java, Interrupted - Justin Santa Barbara's blog. It can’t have escaped anyone’s notice that I have a contrarian opinion of Java: it might not be the coolest language, but it lets me get things done.

But I know it’s not perfect; in particular InterruptedException is a serious pain-point. tldr: I’m experimenting with wrapping InterruptedException in an unchecked exception: my code is cleaner and it hasn’t yet died horribly. I think I like it. Any time you call a long-running method, like waiting for a lock or sleeping, then that method will likely throw InterruptedException. InterruptedException is a checked exception, which means you either need to throw it from your method or catch it. It’s painful to do this catch/interrupt/rethrow dance, so it’s often better just to let your method throw InterruptedException. So you have this: But… you shouldn’t do that, because then you lose the Thread.interrupted status.

So you do this: And now we have some seriously smelly code. How did this happen? Now, in theory, x + y will always be 0. Java Algorithms and Clients. Realestate.com.au Tech Blog. We’ve started some new work in Scala!

Most of the back-end developers in the Residential team have a Java background though, so we put together this cheatsheet to help get the team started. Scala does almost everything Java does, plus a whole lot of useful functional stuff. There’s a direct analog in Scala for almost everything in Java. Keep in mind though, real idiomatic Scala needs a bit more than just Java semantics — there’s lots of really powerful and useful functional features and idioms that you can learn as you go. Java SE 6 HotSpot[tm] Virtual Machine Garbage Collection Tuning.

Note: For Java SE 8, see Java Platform, Standard Edition HotSpot Virtual Machine Garbage Collection Tuning Guide.

The Java™ Platform, Standard Edition (Java SE™) is used for a wide variety of applications, from small applets on desktops to web services on large servers. In support of this diverse range of deployments, the Java HotSpot™ virtual machine implementation (Java HotSpot™ VM) provides multiple garbage collectors, each designed to satisfy different requirements. This is an important part of meeting the demands of both large and small applications. However, users, developers and administrators that need high performance are burdened with the extra step of selecting the garbage collector that best meets their needs. A significant step toward removing this burden was made in J2SE™ 5.0: the garbage collector is selected based on the class of the machine on which the application is run. When does the choice of a garbage collector matter?

The young generation consists of eden and two.