Rumours of JDeveloper's svelteness have been exaggerated
When I tell my friends in Oracle this they point out that JDeveloper has changed its approach now and it too offers a bloat-free framework with the option to just install what we need. Er, up to a point, Lord Copper.
I was talking to someone today about SQL Developer and how we could build addins for it, when I realised I had a really keen idea for an extension that would make my life a lot easier. It's a rather obvious idea and I'm sure people out there are already working on it. But it seemed like a good excuse for me to reinvigorate my rusting Java skills. So I thought I would download JDeveloper and have a look at building the addin for myself.
I downloaded and installed the base version, fired up the Update Centre to get the Extension SDK, and ... nothing. Turns out the ESDK has a dependency on the J2EE version of JDeveloper, which is not documented in the Feature Matrix. For reference, that version (without JRE) is 181MB compared to the base install which weighs in at a Jodie Kidd-like 52MB. I'm sure there are very good reasons why the ESDK has to use some J2EE components but bloating out JDeveloper by an additional 300% just to look at the feasibility of building a SQL Developer addin seems a bit daft.
If there is a way to install the Extension SDK without downloading all this all stuff I would glad to hear of it. Otherwise I shall just have to wait until somebody else builds the addin for me.
Yes I do realise that the Mark Twain quote I am alluding to is "Rumours of my death have been greatly exaggerated." But I don't think I should change the title as it will break the URL in OraBlogs.
In some late-breaking news it turns out that the dependency on J2EE resides not in the ESDK itself but in some of the examples. Apparently a crack team of JDev ninjas is working on separating the two types of examples even as you are reading this.