hi
wayne
we include derby in our scout epp distibution
to ease the development of database centric applications.
with each release we try to upgrade to the most recent
stable derby release, that’s why there are several instances
of the fragments.
regarding your question about the cqs.
according to our ip-log [1] we have the following:
4535
|
org.apache.derby Version: 10.5.3
|
6307
|
Apache Derby Version: 10.8.2.2 *Subset*
(PB CQ5813)
|
7090
|
Apache
Derby Version: 10.9.1.0
|
for our derby needs we only include the
binaries in the scout epp, not the sources. it is also not
quite clear to us where you have found those source
fragments (if you let us know we’re happy to remove them).
please let us know if this works for you.
best regards
matthias
[1]
http://www.eclipse.org/projects/ip_log.php?projectid=technology.scout
Hi Matthias.
I think that I recall asking this question before, but...
What are these bundles:
org.apache.derby.jdbc_1053.fragment.source_10.5.3.*.jar (No CQ
found)
org.apache.derby.jdbc_1053.fragment_10.5.3.*.jar (No CQ found)
org.apache.derby.jdbc_1082.fragment.source_10.8.2.*.jar (No CQ
found)
org.apache.derby.jdbc_1082.fragment_10.8.2.*.jar (No CQ found)
org.apache.derby.jdbc_1091.fragment.source_10.9.1.*.jar (No CQ
found)
org.apache.derby.jdbc_1091.fragment_10.9.1.*.jar (No CQ found)
Thanks,
Wayne
Matthias Zimmermann has requested that you review the attached IP Log for a
Release Review. The reason given was:
Scout Release 3.9 (May 24/2013 - Deadline to submit IP Logs for Kepler
releases)
best regards
matthias