Java Bindings now releasable---what next

Daniel P. Berrange dan at
Mon Jan 16 12:19:59 PST 2006

On Mon, Jan 16, 2006 at 01:34:20PM -0500, John (J5) Palmieri wrote:
> I think we are moving away from keeping things in tree.  The advantage
> is cross testing which we do with glib and python

I'm confident that through application of the appropriate tools we can
solve the cross-testing requirement just as well with the bindings in
a separate tree. Indeed potentially even better, because there's the
scope for testing the same release of the python bindings with multiple
undering C DBus releases & vica-verca. 

For my own purposes I already have an automated build & test engine
which builds the latest CVS tip of the Perl bindings against specific
versions of C DBus every night. In turn I build & test a couple of 
high level applications against the Perl bindings, so you get a full
regression test from lowest-to-highest level of code. You can see
example status pages from the 'DBus' group here:

This particular build engine instance runs on a Debian Sarge install,
and its fairly straightforward to setup instances on other platforms

>                                              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?

|=-            GPG key:       -=|
|=-       Perl modules:              -=|
|=-           Projects:               -=|
|=-   berrange at  -  Daniel Berrange  -  dan at    -=|
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url :

More information about the dbus mailing list