Hi
That was the original "goal" of the api module, but it hasn't worked out very
well. Part of it is due to the "common-utilities" module which is really
"other api's that really should have just been part of API". Another part is
the tooling API's are completely separate as well (tools-com
On 1/25/10 17:38, Christian Schneider wrote:
Hi Dan and Richard,
if they can be completely separated then it is ok to give them an
independent release number. On the other hand I don´t think it hurts a
lot if they are built and released with the rest of cxf.
The problem with separate releases
Nicely done team CXF! I've been testing 2.2.6 since yesterday and so far no
problems migrating from 2.2.4.
Gary
> -Original Message-
> From: Daniel Kulp [mailto:dk...@apache.org]
> Sent: Monday, January 25, 2010 11:25
> To: dev@cxf.apache.org; us...@cxf.apache.org
> Subject: [ANN] Apache
Hi Sergey,
thanks for your efforts. The only thing I had to do is to add javax.xml.bind.*
packages to the boot delegation classpath of my OSGi environment. A point I
simply didn't think about as most JRE-classes are usually present by default.
Kind regards,
Daniel
Am 22.01.2010 um 17:46 schrie
