One of the Open Source Geospatial Foundation (OSGeo) email lists is reviewing relationship between OS and IP.
I am a big fan of matching license to community. While I recognise that open source and intellectual property can be considered as opposites - I find myself lumping them both together.
ObjectAID is the first UML tool you may actually use; I know I should talk about its features or something - but the real reason you may actually use this application is that it is Fast.
1. Run the wizard to create a new diagram
2. Drag and Drop your classes into the diagram
I am very fond of FindBugz (indeed it has found its way into the QA process of most projects I work on....). When visiting the site to check Eclispe 3.5.2 compatibility I found they were working on a new tool.
Indeed a very interesting tool.
I will be using this blog a little less; it seems the vast majority of my postings are of interest to those involved in open source spatial (and Java is just the canvas I enjoy working with).
An open source mailing list I am on recently took up the interesting debate about the Merits of Maven going on in the blogosphere.
One of the advantages of being a library is that we can really be everywhere. The downside is that even if you attended the conference (wasn't it great!) you could not of managed to catch all that we had going on.
I have written up an article over on the GeoTools wiki: GeoTools at FOSS4G Article.
The Free and Open Source Software for Geospatial conference is ramping up and Java should be everywhere.
JSR-275 is almost ready! And there is much rejoicing to be had - but not quite yet.
In my last blog post I talked about GeoAPI and how we use it to define interfaces for a lot of the spatial goodness happening in the Java world. One of the constructs discussed was the interface for CoordinateReferenceSystem.
Someone pointed me at an interesting new project .... actually an interesting old project in new cloths.
What a silly situation performance (and benchmarks are) have put us in. As developers we really want to know how well things will perform - even if it is just so we can figure out how much hardware we will need at the end of the day.
I first ran into this problem with PostGIS (a set of spatial extensions for the PostgreSQL database).