Hello,
The 1.0.b3 Java API was produced from the same data model as 1.0.15
Analysis. It probably has (perhaps bad) bugs in it, because it hasn't
really been tested. The jar file shouldn't include the *.java or CVS crap
(I guess there must be a way to exclude these in the jar command but
obviously I didn't do that). It should have included compiled metamodel
code, that was an oversight. (But the metamodel is not referenced from
the API so it's not going to break anything.)
In related news, the new Java API (to go along with the new Python API) is
coming along. The in-memory version is just checked into our repository
and will start to be tested (it's probably within a few weeks of being
less buggy than the old Java API). The XML save is a quarter or a third
written, with the (much worse) XML load still to come. It does not have a
metamodel yet.
Not sure about the executive committee. (Others will know more what is
happening on this front.)
Wayne
On Fri, 12 Oct 2007, Gary Thompson wrote:
> Dear All (developers)
>
> I have just started playing with the ccpn datamodel in java and had
> a couple of notes / questions
>
> 1. is it upto date with the latest python api?
> 2. looking at the jar file in ccpnmr1.0.b3/java/lib it appears to
> contain both classes and java files which will unecessarily bloat its
> size. Furthermore the jar file contains CVS repository arifacts and also
> has some java files which haven't been compiled to class files e.g.
> memops/metamodel/MetaDataType.java is this expected?
>
>
> regards
> gary
>
> nb just out of interest what were the result of the ccpn executive
> committee elections?
>
>
>
> --
> -------------------------------------------------------------------
> Dr Gary Thompson
> Astbury Centre for Structural Molecular Biology,
> University of Leeds, Astbury Building,
> Leeds, LS2 9JT, West-Yorkshire, UK Tel. +44-113-3433024
> email: [log in to unmask] Fax +44-113-2331407
> -------------------------------------------------------------------
>
|