My team at work was having some issues with IDEA and the Checkstyle plugin. Based on the error message, and without actually looking at the JARs, it seemed pretty clear that the issue was a JDK version issue. While I think this issue has been resolved, when I set up my Mac months ago, I was forced to install Java 6 in order to install IDEA, but, apparently, the new version of the Checkstyle plugin was compiled with a newer JDK (as it should be). Whether or not the Java 6 issue still exists with IDEA, you can make IDEA run on Java 8 pretty easily, and I'll show you how to do it.

Recently, in the #glassfish channel on Freenode, a user was having trouble configuring GlassFish in a Docker environment. He was scripting the configuration of the server, but was having trouble setting the admin user's password, since the change-admin-password command takes input from stdin. Fortunately, there's REST API for that. This curl command will do what the user needs to do without any need for additional input:

Once the password is set, this same command can be used to change the password, but --user admin:$PASSWORD must be added to authenticate the request.

I should note that I don't think this is an officially supported way to execute asadmin commands. It works, but it may change, or it may go away. I would say that Oracle may not support doing this either, but they don't offer any support, so there's no harm there. :) Also note thatAS_ADMIN_PASWORD has a typo in it that may be fixed in future releases of the server. Caveat emptor! :)

As I've noted in a previous post , I recently moved my blog from Awestruct to JBake . This also allowed me to migrate the building and publishing of the blog contents to the toolchain that I know pretty well (Maven). What bothered me, though, was that my POM defined the project as ajar packaging type: the build produces no jar file and, in fact, doesn't process any Java at all. What I wanted, then, was to be able to define the lifecycle in such a way the the compile phase didn't try to compile anything, and the install phase didn't try to put anything in my local repo. Unfortunately, either I'm a bit dense, or the documentation wasn't very clear (it's likely a combination of both :). At any rate, I finally had a eureka moment late last night and figured it out. Here is a distillation of my findings.

For some time now, I have been using awestruct to power my blog, and, for the most part, I've been happy. However, I have found, especially on the Mac, the Ruby-based environment more difficult to setup than I would like. While I have solved this problem before, it presented itself once again when I was issued a Mac upon joining NetSuite. I can, of course, muddle through it, but I'm tired of fighting it, so I started looking around for an alternative and found JBake .