Re: Java problem when upgrading pixelmed
On 09-10-15 00:58, Emmanuel Bourg wrote:
> Le 08/10/2015 13:40, Bas Couwenberg a écrit :
>> Due to the difficulties getting JCS  and its dependencies 
>> packaged, I've not been able to update to any of the newer JOSM upstream
>> releases making the josm package increasingly irrelevant. And if I
>> remain unable to get JCS packaged, I'll have josm removed from the
>> archive before the freeze.
> I noticed that JOSM imports directly the sources from the trunk of JCS
> using svn externals. JCS is still in a beta state, the API isn't stable,
> so if we upload the version 2.0-beta-1 there is no guarantee it will
> work with JOSM. In this case I think you should just go ahead and use
> the version of JCS bundled with JOSM.
> Note that JOSM fetches only the jcs-core module, so you don't need the
> jcache stuff and you don't have to wait for geronimo-jcache-1.0-spec to
> enter unstable.
Thanks for these hints too.
I've already raised my concerns about the JCS requirement in JOSM which
in my opinion is premature due to the beta stage of JCS 2.0 and its
alpha stage dependency on jcache. But JOSM upstream doesn't care much
about building from source by downstreams.
I'll see what I can do with the embedded dependency, although we need it
for the current upstream releases for both JOSM and JMapViewer. I'd
rather not duplicate JCS for both.
GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1