[xwiki-devs] [IDEA] Distribute javadb based instead of hsqldb based packages
Hi devs, Since we are now depending on java 6 I think we should probably change our default all in one distribution to be based on javadb. I'm not going to do any quality comparison between javadb and hsqldb and this package is not supposed to be used in production anyway, the only thing I'm interested in here is: javadb is embedded in java 6 so using it instead of hdsqldb mean one jar less for the exact same features. WDYT ? -- Thomas Mortagne
On May 20, 2011, at 11:29 AM, Thomas Mortagne wrote:
Hi devs,
Since we are now depending on java 6 I think we should probably change our default all in one distribution to be based on javadb.
I'm not going to do any quality comparison between javadb and hsqldb and this package is not supposed to be used in production anyway, the only thing I'm interested in here is: javadb is embedded in java 6 so using it instead of hdsqldb mean one jar less for the exact same features.
WDYT ?
I'm not 100% sure. Is javadb available in all JDKs? Isn't it only avail in the Oracle JDK? Also is it avail in the JRE? Thanks -Vincent
Also I think I'd prefer using the latest version from derby rather than the repackaged version by Oracle... -Vincent On May 20, 2011, at 11:38 AM, Vincent Massol wrote:
On May 20, 2011, at 11:29 AM, Thomas Mortagne wrote:
Hi devs,
Since we are now depending on java 6 I think we should probably change our default all in one distribution to be based on javadb.
I'm not going to do any quality comparison between javadb and hsqldb and this package is not supposed to be used in production anyway, the only thing I'm interested in here is: javadb is embedded in java 6 so using it instead of hdsqldb mean one jar less for the exact same features.
WDYT ?
I'm not 100% sure. Is javadb available in all JDKs? Isn't it only avail in the Oracle JDK?
Also is it avail in the JRE?
Thanks -Vincent
And I'm not yet 100% convinced of Derby vs H2. H2 is a potential contender I think too. Would need some pros/cons of each. -Vincent On May 20, 2011, at 11:39 AM, Vincent Massol wrote:
Also I think I'd prefer using the latest version from derby rather than the repackaged version by Oracle...
-Vincent
On May 20, 2011, at 11:38 AM, Vincent Massol wrote:
On May 20, 2011, at 11:29 AM, Thomas Mortagne wrote:
Hi devs,
Since we are now depending on java 6 I think we should probably change our default all in one distribution to be based on javadb.
I'm not going to do any quality comparison between javadb and hsqldb and this package is not supposed to be used in production anyway, the only thing I'm interested in here is: javadb is embedded in java 6 so using it instead of hdsqldb mean one jar less for the exact same features.
WDYT ?
I'm not 100% sure. Is javadb available in all JDKs? Isn't it only avail in the Oracle JDK?
Also is it avail in the JRE?
Thanks -Vincent
On Fri, May 20, 2011 at 11:40, Vincent Massol <[email protected]> wrote:
And I'm not yet 100% convinced of Derby vs H2.
H2 is a potential contender I think too.
Would need some pros/cons of each.
IMO all we need to know is if javadb is enough for this distribution which again never targeted heavy performance production.
-Vincent
On May 20, 2011, at 11:39 AM, Vincent Massol wrote:
Also I think I'd prefer using the latest version from derby rather than the repackaged version by Oracle...
-Vincent
On May 20, 2011, at 11:38 AM, Vincent Massol wrote:
On May 20, 2011, at 11:29 AM, Thomas Mortagne wrote:
Hi devs,
Since we are now depending on java 6 I think we should probably change our default all in one distribution to be based on javadb.
I'm not going to do any quality comparison between javadb and hsqldb and this package is not supposed to be used in production anyway, the only thing I'm interested in here is: javadb is embedded in java 6 so using it instead of hdsqldb mean one jar less for the exact same features.
WDYT ?
I'm not 100% sure. Is javadb available in all JDKs? Isn't it only avail in the Oracle JDK?
Also is it avail in the JRE?
Thanks -Vincent
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
-- Thomas Mortagne
Wouldn't it help more incremental debugging to have something that works across restarts fast? paul Le 20 mai 2011 à 11:53, Thomas Mortagne a écrit :
H2 is a potential contender I think too.
Would need some pros/cons of each.
IMO all we need to know is if javadb is enough for this distribution which again never targeted heavy performance production.
On Fri, May 20, 2011 at 11:38, Vincent Massol <[email protected]> wrote:
On May 20, 2011, at 11:29 AM, Thomas Mortagne wrote:
Hi devs,
Since we are now depending on java 6 I think we should probably change our default all in one distribution to be based on javadb.
I'm not going to do any quality comparison between javadb and hsqldb and this package is not supposed to be used in production anyway, the only thing I'm interested in here is: javadb is embedded in java 6 so using it instead of hdsqldb mean one jar less for the exact same features.
WDYT ?
I'm not 100% sure. Is javadb available in all JDKs? Isn't it only avail in the Oracle JDK?
From what I understood when java6 has been released it's part of java 6 standard, At least I never seen anything suggesting that it was only in Sun/Oracle implementation.
Also is it avail in the JRE?
Thanks -Vincent
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
-- Thomas Mortagne
On Fri, May 20, 2011 at 11:50, Thomas Mortagne <[email protected]> wrote:
On Fri, May 20, 2011 at 11:38, Vincent Massol <[email protected]> wrote:
On May 20, 2011, at 11:29 AM, Thomas Mortagne wrote:
Hi devs,
Since we are now depending on java 6 I think we should probably change our default all in one distribution to be based on javadb.
I'm not going to do any quality comparison between javadb and hsqldb and this package is not supposed to be used in production anyway, the only thing I'm interested in here is: javadb is embedded in java 6 so using it instead of hdsqldb mean one jar less for the exact same features.
WDYT ?
I'm not 100% sure. Is javadb available in all JDKs? Isn't it only avail in the Oracle JDK?
From what I understood when java6 has been released it's part of java 6 standard, At least I never seen anything suggesting that it was only in Sun/Oracle implementation.
Just checked on Ubuntu and javadb is not part of sun-java6-jre so I guess that means it's the same pretty much everywhere. So this IDEA become -1 for me :)
Also is it avail in the JRE?
Thanks -Vincent
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
-- Thomas Mortagne
-- Thomas Mortagne
On 05/20/2011 11:29 AM, Thomas Mortagne wrote:
Hi devs,
Since we are now depending on java 6 I think we should probably change our default all in one distribution to be based on javadb.
I'm not going to do any quality comparison between javadb and hsqldb and this package is not supposed to be used in production anyway, the only thing I'm interested in here is: javadb is embedded in java 6 so using it instead of hdsqldb mean one jar less for the exact same features.
I'd rather upgrade to a more recent version of HSQLDB. The authors were kind enough to solve a few bugs that were causing problems for us when upgrading an older database. -- Sergiu Dumitriu http://purl.org/net/sergiu/
participants (4)
-
Paul Libbrecht -
Sergiu Dumitriu -
Thomas Mortagne -
Vincent Massol