Tuesday, April 24, 2007
Monday, April 23, 2007
JSR 291 BOF at JavaOne 2007
After reconsideration, a JSR 291 BOF1 has been accepted for JavaOne 2007. The plan is for Richard Hall and I to lead the session.
I hope to include some thoughts on JSR 277 interoperation as well as JSR 294 (superpackages) exploitation.
1. BOF-21240 entitled "JSR 291: Dynamic Component Support For The Java SE Platform", Wednesday 9 May, 9:55pm-10:45pm
I hope to include some thoughts on JSR 277 interoperation as well as JSR 294 (superpackages) exploitation.
1. BOF-21240 entitled "JSR 291: Dynamic Component Support For The Java SE Platform", Wednesday 9 May, 9:55pm-10:45pm
More OSGi assistance for Maven users
A former colleague, Stuart McCulloch, just released some tools for building an OSGi application using Maven.
Apparently it uses bnd under the covers, although the example provided seems to need quite a bit spelling out by hand. Since I'm only a neophite Maven user, it's hard to tell...
Apparently it uses bnd under the covers, although the example provided seems to need quite a bit spelling out by hand. Since I'm only a neophite Maven user, it's hard to tell...
Monday, April 16, 2007
Jeff McAffer's blog
Jeff is a colleague from Eclipse who often has an interesting perspective. You may be interested in his new blog or the first post on provisioning changes in Eclipse.
Welcome to the blogosphere, Jeff!
Welcome to the blogosphere, Jeff!
Wednesday, April 11, 2007
JavaOne, OSGi, and Emacs
According to the advance publicity, there seems to be one session1 at this year's JavaOne conference devoted to OSGi and only a couple of others that refer to OSGi. Not a single mention of JSR 291, although I did try putting in a submission.
I noticed an interesting tidbit in the conference guide: "[James Gosling] has also built a WYSIWYG text editor; a constraint-based drawing editor; and a text editor called Emacs, for UNIX systems."
So did Gosling invent Emacs as well as Java? Well, no, he didn't. The truth is rather more interesting.
Richard Stallman wrote the first version of Emacs and Gosling produced a C version to run on UNIX. A twist is that a legal tussle over the Emacs source code provoked Stallman to write the first precursor of the GPL. Stallman has since endorsed Sun's use of the GPL for their OpenJDK project, so I guess he and Gosling are friends again.
1. TS-1419 "Best OSGi Practices" on Thursday May 10 1:30 PM - 2:30 PM
I noticed an interesting tidbit in the conference guide: "[James Gosling] has also built a WYSIWYG text editor; a constraint-based drawing editor; and a text editor called Emacs, for UNIX systems."
So did Gosling invent Emacs as well as Java? Well, no, he didn't. The truth is rather more interesting.
Richard Stallman wrote the first version of Emacs and Gosling produced a C version to run on UNIX. A twist is that a legal tussle over the Emacs source code provoked Stallman to write the first precursor of the GPL. Stallman has since endorsed Sun's use of the GPL for their OpenJDK project, so I guess he and Gosling are friends again.
1. TS-1419 "Best OSGi Practices" on Thursday May 10 1:30 PM - 2:30 PM
Tuesday, April 10, 2007
Spring-OSGi Milestone 1
Thanks to Hal for the link to Costin's blog on Spring-OSGi which recently shipped the first milestone build.
Now I'm on the look out for the first application to take advantage of Spring-OSGi. Any takers?
Now I'm on the look out for the first application to take advantage of Spring-OSGi. Any takers?
Monday, April 09, 2007
JSR 294 Expert Group
The JSR 294 Expert Group now has a publicly visible mailing list which is good timing as the Expert Group only kicked off a couple of weeks ago, so there'll be a complete archive of its deliberations.
It's a little disappointing that the newly revamped jcp.org site doesn't appear to be capable of hosting openly readable mailing lists as I would like that to be the default for all JSR Expert Groups.
It's a little disappointing that the newly revamped jcp.org site doesn't appear to be capable of hosting openly readable mailing lists as I would like that to be the default for all JSR Expert Groups.