FlutterCode.com released

I’ve been fairly quiet over the last couple of months as I’ve been working on a few items, working on a new site and working on getting two new Open Source projects final and out the door.

I’ve renamed Spigot to DataValve, and moved it to the new site FlutterCode.com which will also host my other project called Knappsack which is a set of Maven archetypes for Java EE 6.

The new site will be home to most of my tutorials, articles and other writings, as well as possibly some screencasts and even podcasts. It will in essence be a pure java development site. This blog will go a bit quieter and contain less development stuff, although most opinion will get put out here instead of over there. I’ll also be copying some of my tutorials over there from this blog.

I’m aiming to create a fairly cohesive tutorial site, aided in part by the Maven Archetypes which will give me a firm base onto which I can build tutorials without having to start from scratch, but one archetype is a sandbox Java EE 6 app with project configuration, a demo model and some test data. The sandbox app will let developers create a new skeleton java EE 6 application they can play with. Building on that, there is a sandbox-demo application which as an archetype that creates a full working demo CRUD application using Java EE 6 so developers can see how all the different pieces of Java EE 6 go together. It includes features such as conversations, JPA CRUD, page parameters, CDI injection and events.

Again, I have to say it, but Open Source is Hard. In the past couple of months, I have been working on a whole new site, getting 2 projects ready to roll with documentation and site content to boot as well as working a job, and having some kind of life.

Now it’s out, I can start to focus a little more on getting some more Java EE 6 tutorials and articles out.

2 thoughts on “FlutterCode.com released

  1. fluttercode.com seems to redirect to andygibson.net.

    In any event, I’m glad you’re providing tutorials and articles on JSF 2, CDI, EJB 3.1, and JPA because they are very helpful and not much help is out there for this technology stack.

    1. I needed a domain name to use for Java packages. I didn’t want to use net.andygibson and have my name plastered all over it. Since I wanted to use maven and upload to the maven repositories, they require proper package naming so not only did it have to be a top level domain based package, but I had to own it also. Since I was going under the org name, I grabbed the com as well in case I wanted to start advertising for consulting or training.
      Glad you like the material, it can take a while to get the hang of Java EE 6, but once you do it is easy and can offer some great leaps in your development.