Java Bindings now releasable---what next

John (J5) Palmieri johnp at
Mon Jan 16 10:34:20 PST 2006

I think we are moving away from keeping things in tree.  The advantage
is cross testing which we do with glib and python but the disadvantage
is that in order to dist I run into problems like needing the Qt4
libraries installed.  Also in order to release a new update we need to
release D-Bus as a whole.  We talked about this in the past and it is
something I want to hash out post 1.0.  I think having a good bindings
page and keeping the bindings in once they are
mature enough is the best way to go.

On Thu, 2006-01-12 at 19:39 +0000, Robert McQueen wrote:
> Matthew Johnson wrote:
> > What's the best way to take this forward. I could at this point just put
> > the tarballs on my website, but it would be nice to integrate it
> > somewhat with the main release, even as just a link on the web page.
> I don't know what the other guys think, but I think it's nice having the
> bindings in tree provided we can keep them maintained. However, I'd be
> keen to keep the version in the tree that's buildable with free
> utilities, and update it to the fully featured version when classpath
> and co catch up. Alternatively, we wait for that to happen before we
> commit any java bindings. What do people think?
> > Matt
> Regards,
> Rob
> _______________________________________________
> dbus mailing list
> dbus at

More information about the dbus mailing list