Using DTP with the JDT

The 10/26 build of DTP 1.0M3 adds a new plug-in containing a first step in integration with Java tooling. This plug-in, org.eclipse.datatools.connectivity.jdt was created based on enhancement request 117318. So, what does it do?

If you go to the Java Build Path-->Libraries tab in the JDT (either when creating a new Java project, or on the properties of an existing Java project):

















You then select Add Library:




















And notice that there is a "Connectivity Driver Instance" category available. Selecting that category opens the driver page:




















You then choose from the set of existing connection profiles, and the associated jar is added to your class path:

















There's been interest using DTP with the JDT for a while (for example, bug 113029), and it is good to see a first step in that direction.

We'd be very interested in suggestions about how DTP could be used with the JDT, and of course we wouldn't turn away proposals for contributions :-)

The City Hall and the Forum

I'm back from the Eclipse Summit Europe held last week in Esslingen, Germany. Also attended the Eclipse Council meetings at the same time, though in a different building. The Summit was held in the Neckar Forum, and the Council meetings in the historic city hall. This brought to mind the notion of the Cathedral and the Bazaar. In this case, however, we have the City Hall and the Forum! Is Eclipse the City Hall, a Forum, or something else?

Anyway, the Summit was great -- I really enjoyed the scheduling which gave ample time for informal meetings, without missing the main sessions.

At Eclipse Summit Europe

I'm at the Eclipse Summit Europe this week. Or, rather, I just arrived near the location, and am trying to adjust to the time lag before the Summit and Eclipse Council meetings start. So far everything has been very good -- the hotel that I' staying at (in Stuttgart) is not particularly close to the meeting site, but the staff have been very friendly, even when I roam around the hotel and sit in strange places to get the best wireless connection. :-)

If anyone would like to meet at the Summit to talk about DTP or otherwise, please drop me an email and we'll set something up.

Thanks for sharing

Bjorn recently blogged about the importance of Eclipse projects being “open, transparent and permeable.” I completely agree, but think there are some hard questions around this.

First, there’s the volume of information. For any given Eclipse project, there are a number of communication channels. In no particular order:

1. web site
2. mailing lists
3. wiki pages
4. newsgroups
5. Bugzilla
6. articles
7. source code
8. other mailing lists associated with the project (e.g. Eclipse Councils)
9. meeting minutes
10. conference presentations and discussions

There’s probably more – 10 seems like a reasonable example set. Now, let’s multiple these channels by the number of projects I might be interested in (some projects might not use a particular channel, others might have specific channel… you get the idea…) and that’s a lot of information to absorb. Too much: I’m deeply involved in DTP, and I’m running as fast as I can to keep up with the DTP channels, never mind other projects.

Certainly I pay attention to other projects (example: the platform… who doesn’t?), but my view is a specific slice of their information content. There’s simply not enough time for me to do otherwise.

What I need is information summaries or alerts for topics I care about. I appreciate knowing about technical discussions, and having input into decisions I care about. But how to I isolate this information? I submit that another mailing list, wiki page, or such is not the answer… Telling me “it is there, just read this or that” misses the whole point.

Secondly, there is a back-channel of communication for dealing with individuals or organization/companies who want to have a “private” conversation. There are a lot of reasons why, and maybe I’ll blog about it later if people are interested. Most Eclipse project members I know encourage these conversations to come “into the light” as soon as possible, but that doesn’t mean there isn’t a private component as well. Do you think this is a bad idea, out of the spirit of Eclipse? Maybe. Are all Eclipse project members willing to step into a panopticon with the community? I would, but only if I were convinced that everyone else would too (otherwise, I cut off an important and useful channel without corresponding benefit).