
Who says being an PITA doesn’t get results? Well after getting an earful from the java community, Apple has finally released a new version of Java 1.6 for the mac. Now all naysayers that said java is dead on the mac can STFU. Oh wait, was I one of those people?
Anyway, you must be an ADC member to get it from here. This is great news but I really hope this does not stop the development of SoyLatte , the BSD port of Java 6 to Tiger and Leopard (now in it’s 1.0 release). From the SoyLatte webpage they state their admiral goals as :
- Support for Java 6 Development on Mac OS X 10.4 and 10.5
- OpenJDK support for Java 7 on Mac OS X
- On-time release of Java 7 for Mac OS X
This whole java/apple debacle really shows why we need the OpenJDK to succeed.
Well, not exactly but we are moving to a new server. Hopefully some of ya’ll that been syndicatin’ my blog will step up and gimme some of my archives.
Peace
Am I the only one that is excited about the launch of Netbeans.tv? I love the concept and I hope the idea catches on in the development community. Parleys.com has been putting out some excellent videos an podcasts for a while now, even with their non-catchy domain name.. Looks like the “video” web is finally coming to fruition. Both sites make nice targets to point newer developers at to learn popular java concepts at their own pace. I don’t know about you but I’m tired of buying java books that no one reads. I’m currently looking at this one myself. If anyone knows of any other video dev sites, please let me know.
Laterz,
GJ
Remember the days when Wikis were the next great open collaboration tool? They were supposed to shepherd in the long promised era of open collaborative knowledge sharing. Wikis around the Net loudly proclaimed “You can edit this page!” A wikis’ commumity would “police themselves”and the karmic goodness of the Open Collaboration would keep evil spammers at bay. Of course they had previously made a mess of smtp, forums and bulletin boards. In 2007, it’s really hard to find an open Wiki. Wikipedia had learned the lessons of the open wiki love fest. Want to edit an Apache Software Foundation Confluence wiki? You better have a SLA on file with ASF, Mofo. Into this enviroment, I make a half-@ssed attempt to set up a JSPWiki webapp. It was supposed to be a tutorial wiki for GhettoJava.I installed and promptly forgot about it over a year ago. Don’t know what inspired me to check on it a few weeks back but when I did: Whoa Nelly! Girls Girls Girls! It was incredible. I had images, movies and lots of flashy text from all the various pr0n sub-genres. Apparently there must be a worm or something going around seeking out the standard wiki urls and attempting to overwrite them with … pr0n. I’ll admit that when I first saw it I wasn’t in a big hurry to delete it the thing, it was as if someone had giving a big free online stash. I quickly snapped out of my daze when I realized that all the images and links must be going somewhere. Anything I clicked on would be an alert to the spammer mothership that another sucker Wiki had been activated on The Node. I don’t have a lot of time for bs so I ended up doing rm -rf /pathto/JSPWiki. Anywayz, I managed to turn the tables somewhat and have since been making a little loot off it. What about you fellahs and ladies? Anyone else’s Wiki got hit like mine?
Laterz,
GJ
InfoQ has been putting out some cool articles lately and this one slipped under my radar: Using Java to Crack Office 2007
"Without anything more complicated than the native
JDK itself-in other words, no third-party libraries are
necessary-a Java application can now read and write any Office 2007
document, because Office 2007 documents are now nothing more than
ZIP files of XML documents."
I love Maven, I like the way that it tries to define an infrastructure for building modularized applications. I love how it assumes testing is a standard part of the build process. My projects went from needing arial maps to finding config files to a nice standard layout that any many developers can understand. As a bonus, Maven also does semi-automatic dependency management for you. It’s a gift and a curse. The Ant build environment is very good for the “Constant Gardener” type of programmer that love to customize their build process to death. There an ant task for pretty much everything you want to compile, package and deploy in Ant. Maven, a newcomer, is still catching up. When I got my wsdl from Salesforce the other day, all the JAX-WS examples came with ant scripts. Somewhat broken ant scripts, but hackable enough to get working. I kinda wanted to still conform to the maven directory structure of my other projects, so I began fishing for wsimport in the maven2 world. Lo and behold, there was one. The Street was happy, I could keep it real and still “stay maven”. First time I ran the example from here, it simply failed.
Note to CodeHaus:
I often find xml errors in your pom.xml examples.
It's <build> </build> not <build><build>
The build failed because it could not find the jaxws-maven-plugin. This kind of error still surprises me. I can understand if a mainline < dependency/> fails but a plugin? I was kind of assuming that plugins were kept to a higher standard, at least in terms of availability. Who’s running this circus? Now that Web Services in Java is actually getting easy enough for the average blue collar programmer to work with, it’s sad that one still has to fish around for a JAX-WS based maven plugin. Did I already mention that the Ant plugin imported and generated my client classes? In other words, s*** just worked. Hours later, after pouring over mail lists, checking mvnrepository.com, going to java.net where the plugin was last seen, I finally had the plugin. It still didn’t work. Didn’t work on my wsdl or the Amazon WS example on their own site. So I’m ending up doing what I should have done in the first place, stop trying to use a screwdriver on a job where a hammer is a better option.
Refreshing my memory on the jar task as we speak.
Peace
GJ