Ich bin bis 30.08.2009 abwesend

Ich werde Ihre Nachricht nach meiner Rückkehr beantworten.
Bitte wenden Sie Sich in dringenden Fällen an Herrn Eichenhofer.


Hinweis: Dies ist eine automatische Antwort auf Ihre Nachricht  "[ANNOUNCE]
Apache Derby 10.5.3.0 released" gesendet am 26.8.09 21:28:13.

Diese ist die einzige Benachrichtigung, die Sie empfangen werden, während
diese Person abwesend ist.

The Apache Derby project is pleased to announce a new bug-fix release of 
Derby, 10.5.3.0.

Apache Derby is a subproject of the Apache DB project. Derby is a pure 
Java relational database engine which conforms to the ISO/ANSI SQL and 
JDBC standards. Derby aims to be easy for developers and customers to use.

Derby 10.5.3.0 can be obtained from the Apache download site:

  http://db.apache.org/derby/derby_downloads.html


Derby 10.5.3.0 contains many bug fixes plus localizations for messages 
added in the previous feature release, 10.5.1.1. 10.5.3.0 replaces 
10.5.2.0, which introduced a query-ordering regression.

Please try out 10.5.3.0.

Thomas P. Fuller wrote:
>
> Hi Folks,
>
> I'm doing a bit of research on an idea and hope that you might be able 
> to save me some time. In particular, if you're able to point us 
> towards the packages to look at, or point out that this idea is not 
> worth pursuing (for any reason), we would find your information to be 
> very helpful.
>
> Here's the idea:
>
>             We would like to swap out the internal representation of 
> table data and replace it with (very table-like) objects that will be 
> located on a shared memory data grid, such as Oracle Coherence.
>
>             We're in the early stages of exploring this idea so we're 
> not really sure yet if it will work the way we're thinking.
>
> And the question is:
>
>
>             What classes should we look at so that we can virtualise 
> the database onto a grid memory rather than in-memory or to disk - 
> implement a iapi.store.access.ConglomerateController maybe?
>
> Thanks in advance for your feedback.
>

Hi Tom,

I would suggest you re-post to the Apache Derby development list at 
derby-dev@db.apache.org.
You could also have a look at how the in-memory support was added (see 
DERBY-646, path derby-646-2b-vfmem_first_rev.diff), and think about 
whether your idea goes well with that approach or not.
If you want to do something at a higher level, I think you have to 
expect quite a bit of extra work. As an alternative to DERBY-646, you 
could also have a look at DERBY-2798. You're not as tightly bound to a 
file interface here, but the current proposal doesn't integrate as well 
with the existing Derby code.


Regards,
-- 
Kristian
<https://issues.apache.org/jira/secure/attachment/12401841/derby-646-2b-vfmem_first_rev.diff>


>
>
> Tom
>

Hi Folks,

I'm doing a bit of research on an idea and hope that you might be able to save me
some time. In particular, if you're able to point us towards the packages to
look at, or point out that this idea is not worth pursuing (for any reason), we
would find your information to be very helpful.

Here's the idea:

            We would
like to swap out the internal representation of table data and replace it with (very
table-like) objects that will be located on a shared memory data grid, such as
Oracle Coherence.

            We're in the
early stages of exploring this idea so we're not really sure yet if it will
work the way we're thinking.


And the question is:

            What classes
should we look at so that we can virtualise the database onto a grid memory
rather than in-memory or to disk - implement a iapi.store.access.ConglomerateController
maybe?

Thanks in advance for your feedback.

Tom

The vote to release the "early access" version of Apache JDO 2.3 TCK and API 
with the projects that they depend on (enhancer, model, and util) passed with 
4 +1 votes, 4 of them binding, and zero 0 and -1 votes.

+1 votes were from:

Michael Bouschen [pmc member]
Michelle Caisse [pmc member]
Andy Jefferson [pmc member]
Craig Russell [pmc member]



-- 
Andy  (DataNucleus - http://www.datanucleus.org)

The Apache Derby project is pleased to announce a new feature release
of Derby, 10.5.1.1.

Apache Derby is a subproject of the Apache DB project. Derby is a pure
Java relational database engine which conforms to the ISO/ANSI SQL and
JDBC standards. Derby aims to be easy for developers and end-users to
work with.

Derby 10.5.1.1 can be obtained from the Derby download site:
   http://db.apache.org/derby/derby_downloads.html.

Derby 10.5.1.1 contains the following new features:
- SQL Roles - Support for most of SQL feature T331 and parts of T332
- Generated Columns - Support for SQL feature T175
- LOB Improvements - Many performance and usability improvements for
BLOBs and CLOBs
- Replication of encrypted databases - Support for replication of
encrypted databases
- OFFSET/FETCH FIRST - Support for limit result set cardinality (new
SQL 2008 syntax)
- In-memory back end - first revision of a storage engine for Derby
storing all data in-memory.
- Update Statistics Stored Procedure - Make it possible to refresh statistics

In addition, Derby 10.5.1.1 contains many bug and documentation fixes.

Please try 10.5.1.1.

Myrna van Lunteren wrote:
> Hi,
>
> I noticed I wasn't on the list as pmc on http://db.apache.org/whoweare.html.
> So I found instructions on how to update on
> http://svn.apache.org/repos/asf/db/site/README.txt.
> But I don't have time right now to set up the maven or figure out the
> other deploy options...
>
> Is there someone who's got this all set up and can deploy my change
> (revision 769080) to
>  https://svn.apache.org/repos/asf/db/site/project.xml?
>
> Myrna
>   
sure, all done.

It'll take an hour for the web site changes to be visible.

cheers,

 -jean

Hi,

I noticed I wasn't on the list as pmc on http://db.apache.org/whoweare.html.
So I found instructions on how to update on
http://svn.apache.org/repos/asf/db/site/README.txt.
But I don't have time right now to set up the maven or figure out the
other deploy options...

Is there someone who's got this all set up and can deploy my change
(revision 769080) to
 https://svn.apache.org/repos/asf/db/site/project.xml?

Myrna

Author: myrnavl
Date: Mon Apr 27 18:13:52 2009
New Revision: 769080

URL: http://svn.apache.org/viewvc?rev=769080&view=rev
Log:
Adding myself to the list - it was overdue

Modified:
    db/site/project.xml

Modified: db/site/project.xml
URL: http://svn.apache.org/viewvc/db/site/project.xml?rev=769080&r1=769079&r2=769080&view=diff
==============================================================================
--- db/site/project.xml (original)
+++ db/site/project.xml Mon Apr 27 18:13:52 2009
@@ -205,6 +205,14 @@
     </developer>
 
     <developer>
+      <name>Myrna van Lunteren</name>
+      <id>myrnavl</id>
+      <email>myrnavl@apache.org</email>
+      <organization>The Apache Software Foundation</organization>
+      <roles><role>PMC Member, Derby</role></roles>
+    </developer>
+
+    <developer>
       <name>Rick Hillegas</name>
       <id>rhillegas</id>
       <email>rhillegas@apache.org</email>

> Can anyone please provide a few pointers on how to encrypt the pwd of 
the
> database using 
> Apache DBCP(Database Connection Pooling) once the connection is 
initialised.

The solution described in

http://markmail.org/message/p43h4ezqw54cyejb#query:torque%20encrypt%20password+page:1+mid:ab3h5yqyb33gb24w+state:results

should also work for dbcp alone.

   Thomas

Hi there,

Can anyone please provide a few pointers on how to encrypt the pwd of the
database using 
Apache DBCP(Database Connection Pooling) once the connection is initialised.

Thanks and Regards,
Partha.
-- 
View this message in context: http://www.nabble.com/How-to-encrypt-the-db-pwd-using-Apache-dbcp-tp22160305p22160305.html
Sent from the Apache DB - General mailing list archive at Nabble.com.

johnrock wrote:
>
> Thomas Fischer-11 wrote:
>   
>> I am no hibernate expert, but it seems to me that Hibernate can use
>> anything that implements the DataSource interface. So I'd be very
>> astonished if it could not use dbcp. However, there might be some
>> configuration issues.
>> And as dbcp is used successfully in many production environments, it seems
>> like a good choice to me :-)
>>
>> You might also ask at the hibernate mailing lists, they have more
>> knowledge
>> about hibernate internals than we do.
>>
>>           Thomas
>>
>>     
>
>
> Thanks, I have posted to a hibernate forum as well.  It is just amazing to
> me that there seems to be a black hole on this question :-0
>
>   
I have a dim recollection of a short thread sometime around when 
Hibernate became more tight with JBoss that there was an effort to make 
hibernate less friendly to use with dbcp.   The public reasoning was 
that development on dbcp was slow and that the documentation was sorely 
lacking.  Maybe these were good faith criticisms, but I was a little 
skeptical given that they were talking up replacements some of which 
weren't at a 1.0 release yet and whose documentation fairly described 
would have to be said to be worse than dbcp.  But that was all many, 
many moons ago and I haven't followed the developments since.

I also think you should be able to use dbcp with hibernate. But don't be 
surprised if your question is ignored or you get responses like:  Why 
use dbcp?  Use X, it is extremely superior.

John McNally

Thomas Fischer-11 wrote:
> 
> 
> I am no hibernate expert, but it seems to me that Hibernate can use
> anything that implements the DataSource interface. So I'd be very
> astonished if it could not use dbcp. However, there might be some
> configuration issues.
> And as dbcp is used successfully in many production environments, it seems
> like a good choice to me :-)
> 
> You might also ask at the hibernate mailing lists, they have more
> knowledge
> about hibernate internals than we do.
> 
>           Thomas
> 


Thanks, I have posted to a hibernate forum as well.  It is just amazing to
me that there seems to be a black hole on this question :-0

John
-- 
View this message in context: http://www.nabble.com/Can-dbcp-be-used-in-Hibernate-3.3--tp21885163p21892430.html
Sent from the Apache DB - General mailing list archive at Nabble.com.

Why don't you place your question on a Hibernate support forum?

> I am a newbie to Hibernate and very confused about how to Not use the default
> Hibernate connection pool. Hibernate assures you that this pool should not
> be used for Production. Great..I get it..its dinky. However, if I am using
> Spring and Hibernate on simple old Tomcat 6 what is the best PRODUCTION
> QUALITY way to implement my Hibernate connection pool?  I thought Apache
> DBCP would suffice but it looks like Hibernate 3.3 no longer supports DBCP. 
> Is this true? There is no documentation about how to do this and the only
> posts I found seem to be using
> "org.hibernate.connection.DBCPConnectionProvider" which does not exist in
> Hibernate 3.3 apparently. What should I be doing?
>
> Any help would be much appreciated!
>
> Thanks
> John 
>   
> ------------------------------------------------------------------------
>
>
> Eingehende eMail ist virenfrei.
> Von AVG uberpruft - www.avg.de 
> Version: 8.0.233 / Virendatenbank: 270.10.19/1938 - Ausgabedatum: 02/06/09 11:31:00 
>
>   

I am no hibernate expert, but it seems to me that Hibernate can use
anything that implements the DataSource interface. So I'd be very
astonished if it could not use dbcp. However, there might be some
configuration issues.
And as dbcp is used successfully in many production environments, it seems
like a good choice to me :-)

You might also ask at the hibernate mailing lists, they have more knowledge
about hibernate internals than we do.

          Thomas

> I am a newbie to Hibernate and very confused about how to Not use
>the default Hibernate connection pool. Hibernate assures you that
>this pool should not be used for Production. Great..I get it..its
>dinky. However, if I am using Spring and Hibernate on simple old
>Tomcat 6 what is the best PRODUCTION QUALITY way to implement my
>Hibernate connection pool?  I thought Apache DBCP would suffice but
>it looks like Hibernate 3.3 no longer supports DBCP.  Is this true?
>There is no documentation about how to do this and the only posts I
>found seem to be using
>"org.hibernate.connection.DBCPConnectionProvider" which does not
>exist in Hibernate 3.3 apparently. What should I be doing?  Any help
>would be much appreciated!  Thanks John

I am a newbie to Hibernate and very confused about how to Not use the default
Hibernate connection pool. Hibernate assures you that this pool should not
be used for Production. Great..I get it..its dinky. However, if I am using
Spring and Hibernate on simple old Tomcat 6 what is the best PRODUCTION
QUALITY way to implement my Hibernate connection pool?  I thought Apache
DBCP would suffice but it looks like Hibernate 3.3 no longer supports DBCP. 
Is this true? There is no documentation about how to do this and the only
posts I found seem to be using
"org.hibernate.connection.DBCPConnectionProvider" which does not exist in
Hibernate 3.3 apparently. What should I be doing?

Any help would be much appreciated!

Thanks
John 
-- 
View this message in context: http://www.nabble.com/Can-dbcp-be-used-in-Hibernate-3.3--tp21885163p21885163.html
Sent from the Apache DB - General mailing list archive at Nabble.com.

The vote to release the Apache JDO 2.2 specification, TCK, and API (both 
legacy and current versions) with the projects that they depend on 
(enhancer, model, and util ) passed with 7 +1 votes, 4 of them binding, 
and zero 0 and -1 votes.

+1 votes were from:

Awais Bajwa
Michael Bouschen [pmc member]
Michelle Caisse [pmc member]
Christian Ernst
Andy Jefferson [pmc member]
Craig Russell [pmc member]
Richard Schilling

-- Michelle

An error occured while fetching this message, sorry !

Author: jta
Date: Sun Oct 19 11:04:47 2008
New Revision: 706048

URL: http://svn.apache.org/viewvc?rev=706048&view=rev
Log:
Switch pmc chair from Jean to Rick

Modified:
    db/site/project.xml

Modified: db/site/project.xml
URL: http://svn.apache.org/viewvc/db/site/project.xml?rev=706048&r1=706047&r2=706048&view=diff
==============================================================================
--- db/site/project.xml (original)
+++ db/site/project.xml Sun Oct 19 11:04:47 2008
@@ -136,7 +136,7 @@
       <id>jta</id>
       <email>jta@apache.org</email>
       <organization>The Apache Software Foundation</organization>
-      <roles><role>PMC Chair</role></roles>
+      <roles><role>PMC Member, Derby</role></roles>
     </developer>
 
     <developer>
@@ -209,7 +209,7 @@
       <id>rhillegas</id>
       <email>rhillegas@apache.org</email>
       <organization>The Apache Software Foundation</organization>
-      <roles><role>PMC Member, Derby</role></roles>
+      <roles><role>PMC Chair, Derby</role></roles>
     </developer>
 
     <developer>

Author: kristwaa
Date: Wed Oct  8 06:54:04 2008
New Revision: 702878

URL: http://svn.apache.org/viewvc?rev=702878&view=rev
Log:
Sorted list of PMC members according to instructions in README.txt.
Fixed some indentation.

Modified:
    db/site/project.xml

Modified: db/site/project.xml
URL: http://svn.apache.org/viewvc/db/site/project.xml?rev=702878&r1=702877&r2=702878&view=diff
==============================================================================
--- db/site/project.xml (original)
+++ db/site/project.xml Wed Oct  8 06:54:04 2008
@@ -52,9 +52,9 @@
     </developer>
 
     <developer>
-       <name>Bryan Pendleton</name>
-       <id>bpendleton</id>
-       <email>bpendleton@apache.org</email>
+      <name>Bryan Pendleton</name>
+      <id>bpendleton</id>
+      <email>bpendleton@apache.org</email>
       <organization>The Apache Software Foundation</organization>
       <roles><role>PMC Member, Derby</role></roles>
     </developer>
@@ -68,19 +68,19 @@
     </developer>
 
     <developer>
-      <name>Dan Debrunner</name>
-      <id>djd</id>
-      <email>djd@apache.org</email>
+      <name>Craig Russell</name>
+      <id>clr</id>
+      <email>clr@apache.org</email>
       <organization>The Apache Software Foundation</organization>
-      <roles><role>PMC Member, Derby</role></roles>
+      <roles><role>PMC Member, JDO</role></roles>
     </developer>
 
     <developer>
-      <name>Daniel Rall</name>
-      <id>dlr</id>
-      <email>dlr@apache.org</email>
+      <name>Dag H. Wanvik</name>
+      <id>dag</id>
+      <email>dag@apache.org</email>
       <organization>The Apache Software Foundation</organization>
-      <roles><role>PMC Member</role></roles>
+      <roles><role>PMC Member, Derby</role></roles>
     </developer>
 
     <developer>
@@ -92,6 +92,22 @@
     </developer>
 
     <developer>
+      <name>Dan Debrunner</name>
+      <id>djd</id>
+      <email>djd@apache.org</email>
+      <organization>The Apache Software Foundation</organization>
+      <roles><role>PMC Member, Derby</role></roles>
+    </developer>
+
+    <developer>
+      <name>Daniel Rall</name>
+      <id>dlr</id>
+      <email>dlr@apache.org</email>
+      <organization>The Apache Software Foundation</organization>
+      <roles><role>PMC Member</role></roles>
+    </developer>
+
+    <developer>
       <name>Andrew McIntyre</name>
       <id>fuzzylogic</id>
       <email>fuzzylogic@apache.org</email>
@@ -108,9 +124,9 @@
     </developer>
 
     <developer>
-      <name>Jason van Zyl</name>
-      <id>jvanzyl</id>
-      <email>jvanzyl@apache.org</email>
+      <name>John McNally</name>
+      <id>jmcnally</id>
+      <email>jmcnally@apache.org</email>
       <organization>The Apache Software Foundation</organization>
       <roles><role>PMC Member</role></roles>
     </developer>
@@ -124,9 +140,9 @@
     </developer>
 
     <developer>
-      <name>John McNally</name>
-      <id>jmcnally</id>
-      <email>jmcnally@apache.org</email>
+      <name>Jason van Zyl</name>
+      <id>jvanzyl</id>
+      <email>jvanzyl@apache.org</email>
       <organization>The Apache Software Foundation</organization>
       <roles><role>PMC Member</role></roles>
     </developer>
@@ -165,6 +181,22 @@
     </developer>
 
     <developer>
+      <name>Michael Bouschen</name>
+      <id>mbo</id>
+      <email>mbo@apache.org</email>
+      <organization>The Apache Software Foundation</organization>
+      <roles><role>PMC Member, JDO</role></roles>
+    </developer>
+
+    <developer>
+      <name>Michelle Caisse</name>
+      <id>mcaisse</id>
+      <email>mcaisse@apache.org</email>
+      <organization>The Apache Software Foundation</organization>
+      <roles><role>PMC Member, JDO</role></roles>
+    </developer>
+
+    <developer>
       <name>Mike Matrigali</name>
       <id>mikem</id>
       <email>mikem@apache.org</email>
@@ -181,6 +213,14 @@
     </developer>
 
     <developer>
+      <name>Rodney Waldhoff</name>
+      <id>rwaldhoff</id>
+      <email>rwaldhoff@apache.org</email>
+      <organization>The Apache Software Foundation</organization>
+      <roles><role>PMC Member</role></roles>
+    </developer>
+
+    <developer>
       <name>Scott Eade</name>
       <id>seade</id>
       <email>seade@apache.org</email>
@@ -206,14 +246,6 @@
     </developer>
 
     <developer>
-      <name>Thomas Vandahl</name>
-      <id>tv</id>
-      <email>tv@apache.org</email>
-      <organization>The Apache Software Foundation</organization>
-      <roles><role>PMC Member, Torque</role></roles>
-    </developer>
-
-    <developer>
       <name>Tomohito Nakayama</name>
       <id>tmnk</id>
       <email>tmnk@apache.org</email>
@@ -231,43 +263,11 @@
     </developer>
 
     <developer>
-      <name>Rodney Waldhoff</name>
-      <id>rwaldhoff</id>
-      <email>rwaldhoff@apache.org</email>
-      <organization>The Apache Software Foundation</organization>
-      <roles><role>PMC Member</role></roles>
-    </developer>
-
-    <developer>
-      <name>Michelle Caisse</name>
-      <id>mcaisse</id>
-      <email>mcaisse@apache.org</email>
-      <organization>The Apache Software Foundation</organization>
-      <roles><role>PMC Member, JDO</role></roles>
-    </developer>
-
-    <developer>
-      <name>Michael Bouschen</name>
-      <id>mbo</id>
-      <email>mbo@apache.org</email>
-      <organization>The Apache Software Foundation</organization>
-      <roles><role>PMC Member, JDO</role></roles>
-    </developer>
-
-    <developer>
-      <name>Craig Russell</name>
-      <id>clr</id>
-      <email>clr@apache.org</email>
-      <organization>The Apache Software Foundation</organization>
-      <roles><role>PMC Member, JDO</role></roles>
-    </developer>
-
-    <developer>
-      <name>Dag H. Wanvik</name>
-      <id>dag</id>
-      <email>dag@apache.org</email>
+      <name>Thomas Vandahl</name>
+      <id>tv</id>
+      <email>tv@apache.org</email>
       <organization>The Apache Software Foundation</organization>
-      <roles><role>PMC Member, Derby</role></roles>
+      <roles><role>PMC Member, Torque</role></roles>
     </developer>
 
   </developers>

Author: kristwaa
Date: Wed Oct  8 06:21:43 2008
New Revision: 702863

URL: http://svn.apache.org/viewvc?rev=702863&view=rev
Log:
Removed Henning P. Schmiedehausen from the PMC member list (request posted to private@db.apache.org).

Modified:
    db/site/project.xml

Modified: db/site/project.xml
URL: http://svn.apache.org/viewvc/db/site/project.xml?rev=702863&r1=702862&r2=702863&view=diff
==============================================================================
--- db/site/project.xml (original)
+++ db/site/project.xml Wed Oct  8 06:21:43 2008
@@ -108,15 +108,6 @@
     </developer>
 
     <developer>
-      <name>Henning P. Schmiedehausen</name>
-      <id>henning</id>
-      <email>henning@apache.org</email>
-      <organization>The Apache Software Foundation</organization>
-      <roles><role>PMC Member, Torque</role></roles>
-      <timezone>+2</timezone>
-    </developer>
-
-    <developer>
       <name>Jason van Zyl</name>
       <id>jvanzyl</id>
       <email>jvanzyl@apache.org</email>

The Apache Derby project is pleased to announce a new bug-fix release of 
Derby, 10.4.2.0.

Apache Derby is a subproject of the Apache DB project. Derby is a pure 
Java relational database engine which conforms to the ISO/ANSI SQL and 
JDBC standards. Derby aims to be easy for developers and end-users to 
work with.

Derby 10.4.2.0 can be obtained from the Derby download site:

http://db.apache.org/derby/derby_downloads.html.


Derby 10.4.2.0 contains localizations for messages added in the previous 
feature release, 10.4.1.3. In addition, Derby 10.4.2.0 contains many bug 
and documentation fixes, including improvements to large object access, 
UNION queries, pooled connections, function arguments, metadata access, 
and statement caching.

Please try 10.4.2.0.

Content-type: text/plain; format=flowed; charset=ISO-8859-1
Content-transfer-encoding: 7BIT

The vote to release Apache JDO 2.1.1 passed with six +1 votes and zero 0 
and -1 votes.

Andy Jefferson
Craig Russell (binding)
Michelle Caisse (binding)
Christian Ernst
Awais Bajwa
Michael Bouschen (binding)

-- Michelle

-------- Original Message --------
Subject: 	[VOTE] Release Apache JDO 2.1.1
Date: 	Sat, 02 Aug 2008 09:41:56 -0700
From: 	Michelle Caisse <Michelle.Caisse@Sun.COM>
To: 	jdo-dev@db.apache.org, jdo-experts-ext@sun.com

	



This vote is to release the Apache JDO 2.1.1 TCK and API (both legacy 
and current versions) with the projects that they depend on: enhancer, 
model, and util.

[+1] Release JDO 2.1.1 api, tck, enhancer, model, and util
[0] Don't care
[-1] Don't release JDO 2.1.1 api, tck, enhancer, model, and util because:


The TCK can be tested from the staging area, 
http://people.apache.org/~mcaisse/jdo2.1.1/dist. Please follow the 
directions at http://wiki.apache.org/jdo/ReleaseTesting2dot1dot1 for 
downloading and testing.

JDO 2.1.1 provides fixes for the following issues:

    *

        http://issues.apache.org/jira/browse/JDO-584

    *

        http://issues.apache.org/jira/browse/JDO-585

    *

        http://issues.apache.org/jira/browse/JDO-586

    *

        http://issues.apache.org/jira/browse/JDO-593

    *

        http://issues.apache.org/jira/browse/JDO-600

    *

        http://issues.apache.org/jira/browse/JDO-601


Please test and vote. Voting will close at noon PDT Tuesday, August 5.

-- Michelle

-- 
Michelle Caisse               Sun Microsystems
California, U.S.     http://sun.com/postgresql

:Hi Jean,

Thanks for your comments and suggestions. I'll put the proposal on the
wiki as soon as I have some time - I'm off to The Server Side in
Prague tomorrow, so whether it will be this week I don't know :)

Regards,

Cees



On 6/14/08, Jean T. Anderson <jta@bristowhill.com> wrote:
> Hi, Cees,
>
> JDBM certainly looks interesting!
>
> One clarification about process is the project would still enter
> incubation, but sponsored by Apache DB.  On graduation, it would then
> join Apache DB as a subproject -- or possibly even as its own top level
> project. (For example, Apache Derby and JDO were sponsored by Apache DB,
> and graduated as DB subprojects. Apache Cayenne was sponsored by Apache
> DB, but graduated as a TLP. ) Exact destination gets determined at
> graduation time -- but talk of graduation is leaping way too far ahead
> for this discussion.  :-)
>
> The Incubator proposal template will help guide discussion on this list:
>
>    http://incubator.apache.org/guides/proposal.html#proposal-template
>
> You can add a JDBM proposal to the Incubator wiki:
>
>    http://wiki.apache.org/incubator/
>
> I'd especially like to hear more about your thoughts regarding this comment:
>
>> There have been some concerns about the continuity of the package,
>> although the original contributors are still active.
>
> Apache is about community -- and no project graduates from the Incubator
> without demonstrating that it has a community diverse and strong enough
> to manage that code base moving forward. You stated a commitment to keep
> JDBM alive -- how about the other contributors? --I'm keying in on this
> risk mentioned in the template:
>
>
> http://incubator.apache.org/guides/proposal.html#template-orphaned-products
>
>> I sincerely hope the Apache DB project will consider adoption of the code
>> base.
>>
>
> Again, Apache is about communities. We just need to make sure that
> everyone understands that.
>
> Since I pulled out a couple comments, possibly without adequate context,
> I'm including your entire original post down below.
>
> I look forward to hearing more about JDBM.
>
> regards,
>
>  -jean
>
> Cees de Groot wrote:
>> (Currently: http://jdbm.sourceforge.net/)
>>
>> JDBM is an 8-year old open source library currently under a custom
>> (original-BSD-style) license created by me in 2000 as the result of
>> some chat with folks from Intalio and extended by a number of persons
>> since then, most notably Alex Boisvert. It mainly aims to give similar
>> functionality as GDBM but it adds transactions and btrees/htrees. As
>> its goals were (and are) simplicity and robustness, after an initial
>> flurry of development the package has been mostly stable and is in
>> use/has been used by a number of high profile projects
>> (http://jdbm.sourceforge.net/JDBM-Powered.html).
>>
>> There have been some concerns about the continuity of the package,
>> although the original contributors are still active. ApacheDS already
>> includes a (temprary) fork in the code base, and the main question the
>> mailing list receives is along the line "does it still work?" (answer:
>> yes, it does - that fact that the stable release is 3 years old means
>> that we haven't received any serious bug reports since then, I figure
>> ;-)).
>>
>> While we were discussing the future of JDBM on SourceForge (people
>> want to move to Codehaus because of the better tools), Emmanuel
>> Lecharny (ApacheDS) suggested that we'd consider Apache DB as a new
>> home, and I think it is an extremely good idea for obvious reasons
>> (continuity, exposure, peace of mind for Apache DS and other users).
>>
>> JDBM still fills a good niche, IMO, and would be a worthwhile addition
>> to the Apache DB project. At the moment, I'm busy modernizing JDBM:
>> - Move from Ant to Maven (mostly done);
>> - Move from Junit3 to Junit4;
>> - Move to JDK1.5+, most notably by adding generics.
>> - Move from jdbm.* to a package name that is in accordance with the
>> rules of ibiblio et al. for release.
>> - Re-license under ASL/MIT/BSD ("something in that particular corner
>> of the open source licensing jungle").
>> The first three points are underway, the package rename depends
>> partially on its new home, and re-licensing requires some discussion
>> and a vote but the contributors so far are quite relaxed on licensing
>> (how refreshing!).
>>
>> Personally, as OC, I am very much committed to keeping JDBM alive. I
>> have a bit over 2 decades of experience with working in Free
>> Software/Open Source Software environments (starting with an fast
>> ANSI.SYS replacement, distributed over Fidonet, in the '80s :)), among
>> others I contributed to early Linux kernels, helped with the port of
>> Java to Linux as a member of the Blackdown team, ran the
>> Linuxdoc/SGMLtools projects and I have been active in various
>> Smalltak-related communities, most notably the Squeak community
>> (squeak.org). So I hope I qualify the "open source experience"
>> requirement. As to the other main contributors, I leave it to them to
>> chime in.
>>
>> I sincerely hope the Apache DB project will consider adoption of the code
>> base.
>>
>> Regards,
>>
>> Cees
>>
>
>

-- 
Sent from Gmail for mobile | mobile.google.com

"Any sufficiently advanced form of music is indistinguishable from
metal" -- free after A.C.Clarke

Jean,

In response to your post, I think that jdbm has satisified its goals and
core community base relatively well as a small persistence package -- this
is the primary reason why there is not a lot of developer activity at this
time.  There is a broad, if mostly silent, user base out there and questions
posted to the various lists get answered relatively quickly.  You do not
always have to grow to succeed.

That said, if the reason for sponsorship by Apache DB is to develop new
features in support of Apache DB, then perhaps it makes sense to discuss
exactly what features are desired and see who wants to step up for that
goal.

About myself, I worked extensively with jdbm about one year ago fixing
several issues relating to the weak reference cache, optimizing the object
cache model, and in general tuning performance.  I also did an integration
for compact, extensible, and transparently serialized object graphs for jdbm
records.  While I am no longer actively working on the project, I still
monitor the lists and would continue to provide support and might contribute
again if the project goals changed.

My open source activities go back into the late 80's with work on induction
systems, generic algorithms and neural networks.  Most recently, I started
http://www.bigdata.com.  This project is a scale-out database architecture
ala bigtable or HBase, but more general in its handling of key-range
partitioned B+Trees and supports a high performance RDFS+ database in
addition to a bigtable/hbase style store, a distributed file system, and an
object database data model.  It is currently in pre-release while we work
through some issues with load balancing across a cluster.

-bryan

> -----Original Message-----
> From: jdbm-general-bounces@lists.sourceforge.net 
> [mailto:jdbm-general-bounces@lists.sourceforge.net] On Behalf 
> Of Jean T. Anderson
> Sent: Saturday, June 14, 2008 5:00 PM
> To: general@db.apache.org
> Cc: JDBM General listserv
> Subject: Re: [Jdbm-general] Apache DB subproject proposal: JDBM
> 
> [resending to general@db ... I didn't spot 
> jdbm-general@lists.sourceforge.net cc'd on the original. 
> Also, I'm seeing Alex's post now, expressing his interest to 
> make a commitment, which is excellent.]
> 
> Hi, Cees,
> 
> JDBM certainly looks interesting!
> 
> One clarification about process is the project would still 
> enter incubation, but sponsored by Apache DB.  On graduation, 
> it would then join Apache DB as a subproject -- or possibly 
> even as its own top level project. (For example, Apache Derby 
> and JDO were sponsored by Apache DB, and graduated as DB 
> subprojects. Apache Cayenne was sponsored by Apache DB, but 
> graduated as a TLP. ) Exact destination gets determined at 
> graduation time -- but talk of graduation is leaping way too 
> far ahead for this discussion.  :-)
> 
> The Incubator proposal template will help guide discussion on 
> this list:
> 
>   http://incubator.apache.org/guides/proposal.html#proposal-template
> 
> You can add a JDBM proposal to the Incubator wiki:
> 
>   http://wiki.apache.org/incubator/
> 
> I'd especially like to hear more about your thoughts regarding this
> comment:
> 
> > There have been some concerns about the continuity of the package, 
> > although the original contributors are still active.
> 
> Apache is about community -- and no project graduates from 
> the Incubator without demonstrating that it has a community 
> diverse and strong enough to manage that code base moving 
> forward. You stated a commitment to keep JDBM alive -- how 
> about the other contributors? --I'm keying in on this risk 
> mentioned in the template:
> 
>   
> http://incubator.apache.org/guides/proposal.html#template-orph
aned-products
> 
> > I sincerely hope the Apache DB project will consider 
> adoption of the 
> > code base.
> >   
> 
> Again, Apache is about communities. We just need to make sure 
> that everyone understands that.
> 
> Since I pulled out a couple comments, possibly without 
> adequate context, I'm including your entire original post down below.
> 
> I look forward to hearing more about JDBM.
> 
> regards,
> 
> -jean
> 
> 
> Cees de Groot wrote:
> > (Currently: http://jdbm.sourceforge.net/)
> >
> > JDBM is an 8-year old open source library currently under a custom
> > (original-BSD-style) license created by me in 2000 as the result of 
> > some chat with folks from Intalio and extended by a number 
> of persons 
> > since then, most notably Alex Boisvert. It mainly aims to 
> give similar 
> > functionality as GDBM but it adds transactions and 
> btrees/htrees. As 
> > its goals were (and are) simplicity and robustness, after 
> an initial 
> > flurry of development the package has been mostly stable and is in 
> > use/has been used by a number of high profile projects 
> > (http://jdbm.sourceforge.net/JDBM-Powered.html).
> >
> > There have been some concerns about the continuity of the package, 
> > although the original contributors are still active. 
> ApacheDS already 
> > includes a (temprary) fork in the code base, and the main 
> question the 
> > mailing list receives is along the line "does it still 
> work?" (answer:
> > yes, it does - that fact that the stable release is 3 years 
> old means 
> > that we haven't received any serious bug reports since 
> then, I figure 
> > ;-)).
> >
> > While we were discussing the future of JDBM on SourceForge (people 
> > want to move to Codehaus because of the better tools), Emmanuel 
> > Lecharny (ApacheDS) suggested that we'd consider Apache DB as a new 
> > home, and I think it is an extremely good idea for obvious reasons 
> > (continuity, exposure, peace of mind for Apache DS and other users).
> >
> > JDBM still fills a good niche, IMO, and would be a 
> worthwhile addition 
> > to the Apache DB project. At the moment, I'm busy modernizing JDBM:
> > - Move from Ant to Maven (mostly done);
> > - Move from Junit3 to Junit4;
> > - Move to JDK1.5+, most notably by adding generics.
> > - Move from jdbm.* to a package name that is in accordance with the 
> > rules of ibiblio et al. for release.
> > - Re-license under ASL/MIT/BSD ("something in that 
> particular corner 
> > of the open source licensing jungle").
> > The first three points are underway, the package rename depends 
> > partially on its new home, and re-licensing requires some 
> discussion 
> > and a vote but the contributors so far are quite relaxed on 
> licensing 
> > (how refreshing!).
> >
> > Personally, as OC, I am very much committed to keeping JDBM 
> alive. I 
> > have a bit over 2 decades of experience with working in Free 
> > Software/Open Source Software environments (starting with an fast 
> > ANSI.SYS replacement, distributed over Fidonet, in the '80s 
> :)), among 
> > others I contributed to early Linux kernels, helped with 
> the port of 
> > Java to Linux as a member of the Blackdown team, ran the 
> > Linuxdoc/SGMLtools projects and I have been active in various 
> > Smalltak-related communities, most notably the Squeak community 
> > (squeak.org). So I hope I qualify the "open source experience"
> > requirement. As to the other main contributors, I leave it 
> to them to 
> > chime in.
> >
> > I sincerely hope the Apache DB project will consider 
> adoption of the code base.
> >
> > Regards,
> >
> > Cees
> >   
> 
> 
> --------------------------------------------------------------
> -----------
> Check out the new SourceForge.net Marketplace.
> It's the best place to buy or sell services for just about 
> anything Open Source.
> http://sourceforge.net/services/buy/index.php
> _______________________________________________
> Jdbm-general mailing list
> Jdbm-general@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/jdbm-general
> 

[resending to general@db ... I didn't spot 
jdbm-general@lists.sourceforge.net cc'd on the original. Also, I'm 
seeing Alex's post now, expressing his interest to make a commitment, 
which is excellent.]

Hi, Cees,

JDBM certainly looks interesting!

One clarification about process is the project would still enter 
incubation, but sponsored by Apache DB.  On graduation, it would then 
join Apache DB as a subproject -- or possibly even as its own top level 
project. (For example, Apache Derby and JDO were sponsored by Apache DB, 
and graduated as DB subprojects. Apache Cayenne was sponsored by Apache 
DB, but graduated as a TLP. ) Exact destination gets determined at 
graduation time -- but talk of graduation is leaping way too far ahead 
for this discussion.  :-)

The Incubator proposal template will help guide discussion on this list:

  http://incubator.apache.org/guides/proposal.html#proposal-template

You can add a JDBM proposal to the Incubator wiki:

  http://wiki.apache.org/incubator/

I'd especially like to hear more about your thoughts regarding this 
comment:

> There have been some concerns about the continuity of the package,
> although the original contributors are still active.

Apache is about community -- and no project graduates from the Incubator 
without demonstrating that it has a community diverse and strong enough 
to manage that code base moving forward. You stated a commitment to keep 
JDBM alive -- how about the other contributors? --I'm keying in on this 
risk mentioned in the template:

  
http://incubator.apache.org/guides/proposal.html#template-orphaned-products

> I sincerely hope the Apache DB project will consider adoption of the 
> code base.
>   

Again, Apache is about communities. We just need to make sure that 
everyone understands that.

Since I pulled out a couple comments, possibly without adequate context, 
I'm including your entire original post down below.

I look forward to hearing more about JDBM.

regards,

-jean


Cees de Groot wrote:
> (Currently: http://jdbm.sourceforge.net/)
>
> JDBM is an 8-year old open source library currently under a custom
> (original-BSD-style) license created by me in 2000 as the result of
> some chat with folks from Intalio and extended by a number of persons
> since then, most notably Alex Boisvert. It mainly aims to give similar
> functionality as GDBM but it adds transactions and btrees/htrees. As
> its goals were (and are) simplicity and robustness, after an initial
> flurry of development the package has been mostly stable and is in
> use/has been used by a number of high profile projects
> (http://jdbm.sourceforge.net/JDBM-Powered.html).
>
> There have been some concerns about the continuity of the package,
> although the original contributors are still active. ApacheDS already
> includes a (temprary) fork in the code base, and the main question the
> mailing list receives is along the line "does it still work?" (answer:
> yes, it does - that fact that the stable release is 3 years old means
> that we haven't received any serious bug reports since then, I figure
> ;-)).
>
> While we were discussing the future of JDBM on SourceForge (people
> want to move to Codehaus because of the better tools), Emmanuel
> Lecharny (ApacheDS) suggested that we'd consider Apache DB as a new
> home, and I think it is an extremely good idea for obvious reasons
> (continuity, exposure, peace of mind for Apache DS and other users).
>
> JDBM still fills a good niche, IMO, and would be a worthwhile addition
> to the Apache DB project. At the moment, I'm busy modernizing JDBM:
> - Move from Ant to Maven (mostly done);
> - Move from Junit3 to Junit4;
> - Move to JDK1.5+, most notably by adding generics.
> - Move from jdbm.* to a package name that is in accordance with the
> rules of ibiblio et al. for release.
> - Re-license under ASL/MIT/BSD ("something in that particular corner
> of the open source licensing jungle").
> The first three points are underway, the package rename depends
> partially on its new home, and re-licensing requires some discussion
> and a vote but the contributors so far are quite relaxed on licensing
> (how refreshing!).
>
> Personally, as OC, I am very much committed to keeping JDBM alive. I
> have a bit over 2 decades of experience with working in Free
> Software/Open Source Software environments (starting with an fast
> ANSI.SYS replacement, distributed over Fidonet, in the '80s :)), among
> others I contributed to early Linux kernels, helped with the port of
> Java to Linux as a member of the Blackdown team, ran the
> Linuxdoc/SGMLtools projects and I have been active in various
> Smalltak-related communities, most notably the Squeak community
> (squeak.org). So I hope I qualify the "open source experience"
> requirement. As to the other main contributors, I leave it to them to
> chime in.
>
> I sincerely hope the Apache DB project will consider adoption of the code base.
>
> Regards,
>
> Cees
>   

Hi, Cees,

JDBM certainly looks interesting!

One clarification about process is the project would still enter 
incubation, but sponsored by Apache DB.  On graduation, it would then 
join Apache DB as a subproject -- or possibly even as its own top level 
project. (For example, Apache Derby and JDO were sponsored by Apache DB, 
and graduated as DB subprojects. Apache Cayenne was sponsored by Apache 
DB, but graduated as a TLP. ) Exact destination gets determined at 
graduation time -- but talk of graduation is leaping way too far ahead 
for this discussion.  :-)

The Incubator proposal template will help guide discussion on this list:

   http://incubator.apache.org/guides/proposal.html#proposal-template

You can add a JDBM proposal to the Incubator wiki:

   http://wiki.apache.org/incubator/

I'd especially like to hear more about your thoughts regarding this comment:

> There have been some concerns about the continuity of the package,
> although the original contributors are still active.

Apache is about community -- and no project graduates from the Incubator 
without demonstrating that it has a community diverse and strong enough 
to manage that code base moving forward. You stated a commitment to keep 
JDBM alive -- how about the other contributors? --I'm keying in on this 
risk mentioned in the template:

   
http://incubator.apache.org/guides/proposal.html#template-orphaned-products

> I sincerely hope the Apache DB project will consider adoption of the code base.
>   

Again, Apache is about communities. We just need to make sure that 
everyone understands that.

Since I pulled out a couple comments, possibly without adequate context, 
I'm including your entire original post down below.

I look forward to hearing more about JDBM.

regards,

 -jean

Cees de Groot wrote:
> (Currently: http://jdbm.sourceforge.net/)
>
> JDBM is an 8-year old open source library currently under a custom
> (original-BSD-style) license created by me in 2000 as the result of
> some chat with folks from Intalio and extended by a number of persons
> since then, most notably Alex Boisvert. It mainly aims to give similar
> functionality as GDBM but it adds transactions and btrees/htrees. As
> its goals were (and are) simplicity and robustness, after an initial
> flurry of development the package has been mostly stable and is in
> use/has been used by a number of high profile projects
> (http://jdbm.sourceforge.net/JDBM-Powered.html).
>
> There have been some concerns about the continuity of the package,
> although the original contributors are still active. ApacheDS already
> includes a (temprary) fork in the code base, and the main question the
> mailing list receives is along the line "does it still work?" (answer:
> yes, it does - that fact that the stable release is 3 years old means
> that we haven't received any serious bug reports since then, I figure
> ;-)).
>
> While we were discussing the future of JDBM on SourceForge (people
> want to move to Codehaus because of the better tools), Emmanuel
> Lecharny (ApacheDS) suggested that we'd consider Apache DB as a new
> home, and I think it is an extremely good idea for obvious reasons
> (continuity, exposure, peace of mind for Apache DS and other users).
>
> JDBM still fills a good niche, IMO, and would be a worthwhile addition
> to the Apache DB project. At the moment, I'm busy modernizing JDBM:
> - Move from Ant to Maven (mostly done);
> - Move from Junit3 to Junit4;
> - Move to JDK1.5+, most notably by adding generics.
> - Move from jdbm.* to a package name that is in accordance with the
> rules of ibiblio et al. for release.
> - Re-license under ASL/MIT/BSD ("something in that particular corner
> of the open source licensing jungle").
> The first three points are underway, the package rename depends
> partially on its new home, and re-licensing requires some discussion
> and a vote but the contributors so far are quite relaxed on licensing
> (how refreshing!).
>
> Personally, as OC, I am very much committed to keeping JDBM alive. I
> have a bit over 2 decades of experience with working in Free
> Software/Open Source Software environments (starting with an fast
> ANSI.SYS replacement, distributed over Fidonet, in the '80s :)), among
> others I contributed to early Linux kernels, helped with the port of
> Java to Linux as a member of the Blackdown team, ran the
> Linuxdoc/SGMLtools projects and I have been active in various
> Smalltak-related communities, most notably the Squeak community
> (squeak.org). So I hope I qualify the "open source experience"
> requirement. As to the other main contributors, I leave it to them to
> chime in.
>
> I sincerely hope the Apache DB project will consider adoption of the code base.
>
> Regards,
>
> Cees
>   

Looks good to me.   I think the proposal should mention a potential list of
committers/contributors who are interested in maintaining and keeping JDBM
alive, and I think these people should step up to be included in the
proposal.    And please add me to this list :)   I also have extensive
open-source experience, starting down Memory Lane with FidoNet and writing
my own BBS software based off a fork from Tony Hsieh's EBBS, continuing at
Intalio with the genesis of OpenEJB, OpenJMS, Slide, and a few others.  I'm
currently PMC member for Apache Ode, PPMC member for Apache Buildr and
committer for Apache ServiceMix.   I'm also involved in the open-source
Tempo project (http://tempo.intalio.org) which isn't ready for a transition
to a large open-source community/foundation yet ;)

alex

On Thu, Jun 12, 2008 at 11:12 PM, Cees de Groot <cdegroot@gmail.com> wrote:

> (Currently: http://jdbm.sourceforge.net/)
>
> JDBM is an 8-year old open source library currently under a custom
> (original-BSD-style) license created by me in 2000 as the result of
> some chat with folks from Intalio and extended by a number of persons
> since then, most notably Alex Boisvert. It mainly aims to give similar
> functionality as GDBM but it adds transactions and btrees/htrees. As
> its goals were (and are) simplicity and robustness, after an initial
> flurry of development the package has been mostly stable and is in
> use/has been used by a number of high profile projects
> (http://jdbm.sourceforge.net/JDBM-Powered.html).
>
> There have been some concerns about the continuity of the package,
> although the original contributors are still active. ApacheDS already
> includes a (temprary) fork in the code base, and the main question the
> mailing list receives is along the line "does it still work?" (answer:
> yes, it does - that fact that the stable release is 3 years old means
> that we haven't received any serious bug reports since then, I figure
> ;-)).
>
> While we were discussing the future of JDBM on SourceForge (people
> want to move to Codehaus because of the better tools), Emmanuel
> Lecharny (ApacheDS) suggested that we'd consider Apache DB as a new
> home, and I think it is an extremely good idea for obvious reasons
> (continuity, exposure, peace of mind for Apache DS and other users).
>
> JDBM still fills a good niche, IMO, and would be a worthwhile addition
> to the Apache DB project. At the moment, I'm busy modernizing JDBM:
> - Move from Ant to Maven (mostly done);
> - Move from Junit3 to Junit4;
> - Move to JDK1.5+, most notably by adding generics.
> - Move from jdbm.* to a package name that is in accordance with the
> rules of ibiblio et al. for release.
> - Re-license under ASL/MIT/BSD ("something in that particular corner
> of the open source licensing jungle").
> The first three points are underway, the package rename depends
> partially on its new home, and re-licensing requires some discussion
> and a vote but the contributors so far are quite relaxed on licensing
> (how refreshing!).
>
> Personally, as OC, I am very much committed to keeping JDBM alive. I
> have a bit over 2 decades of experience with working in Free
> Software/Open Source Software environments (starting with an fast
> ANSI.SYS replacement, distributed over Fidonet, in the '80s :)), among
> others I contributed to early Linux kernels, helped with the port of
> Java to Linux as a member of the Blackdown team, ran the
> Linuxdoc/SGMLtools projects and I have been active in various
> Smalltak-related communities, most notably the Squeak community
> (squeak.org). So I hope I qualify the "open source experience"
> requirement. As to the other main contributors, I leave it to them to
> chime in.
>
> I sincerely hope the Apache DB project will consider adoption of the code
> base.
>
> Regards,
>
> Cees
>
> -------------------------------------------------------------------------
> Check out the new SourceForge.net Marketplace.
> It's the best place to buy or sell services for
> just about anything Open Source.
> http://sourceforge.net/services/buy/index.php
> _______________________________________________
> Jdbm-general mailing list
> Jdbm-general@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/jdbm-general
>

(Currently: http://jdbm.sourceforge.net/)

JDBM is an 8-year old open source library currently under a custom
(original-BSD-style) license created by me in 2000 as the result of
some chat with folks from Intalio and extended by a number of persons
since then, most notably Alex Boisvert. It mainly aims to give similar
functionality as GDBM but it adds transactions and btrees/htrees. As
its goals were (and are) simplicity and robustness, after an initial
flurry of development the package has been mostly stable and is in
use/has been used by a number of high profile projects
(http://jdbm.sourceforge.net/JDBM-Powered.html).

There have been some concerns about the continuity of the package,
although the original contributors are still active. ApacheDS already
includes a (temprary) fork in the code base, and the main question the
mailing list receives is along the line "does it still work?" (answer:
yes, it does - that fact that the stable release is 3 years old means
that we haven't received any serious bug reports since then, I figure
;-)).

While we were discussing the future of JDBM on SourceForge (people
want to move to Codehaus because of the better tools), Emmanuel
Lecharny (ApacheDS) suggested that we'd consider Apache DB as a new
home, and I think it is an extremely good idea for obvious reasons
(continuity, exposure, peace of mind for Apache DS and other users).

JDBM still fills a good niche, IMO, and would be a worthwhile addition
to the Apache DB project. At the moment, I'm busy modernizing JDBM:
- Move from Ant to Maven (mostly done);
- Move from Junit3 to Junit4;
- Move to JDK1.5+, most notably by adding generics.
- Move from jdbm.* to a package name that is in accordance with the
rules of ibiblio et al. for release.
- Re-license under ASL/MIT/BSD ("something in that particular corner
of the open source licensing jungle").
The first three points are underway, the package rename depends
partially on its new home, and re-licensing requires some discussion
and a vote but the contributors so far are quite relaxed on licensing
(how refreshing!).

Personally, as OC, I am very much committed to keeping JDBM alive. I
have a bit over 2 decades of experience with working in Free
Software/Open Source Software environments (starting with an fast
ANSI.SYS replacement, distributed over Fidonet, in the '80s :)), among
others I contributed to early Linux kernels, helped with the port of
Java to Linux as a member of the Blackdown team, ran the
Linuxdoc/SGMLtools projects and I have been active in various
Smalltak-related communities, most notably the Squeak community
(squeak.org). So I hope I qualify the "open source experience"
requirement. As to the other main contributors, I leave it to them to
chime in.

I sincerely hope the Apache DB project will consider adoption of the code base.

Regards,

Cees

Author: jorgenlo
Date: Fri Jun  6 00:42:38 2008
New Revision: 663848

URL: http://svn.apache.org/viewvc?rev=663848&view=rev
Log:
Added myself to committer list.

Modified:
    db/site/projects/derby/project.xml

Modified: db/site/projects/derby/project.xml
URL: http://svn.apache.org/viewvc/db/site/projects/derby/project.xml?rev=663848&r1=663847&r2=663848&view=diff
==============================================================================
--- db/site/projects/derby/project.xml (original)
+++ db/site/projects/derby/project.xml Fri Jun  6 00:42:38 2008
@@ -170,6 +170,15 @@
        </roles>
     </developer>
     <developer>
+       <name>Jorgen Loland</name>
+       <id>jorgenlo</id>
+       <email>jorgenlo@apache.org</email>
+       <organization>Sun Microsystems</organization>
+       <roles>
+        <role>Derby</role>
+       </roles>
+    </developer>
+    <developer>
        <name>Knut Anders Hatlen</name>
        <id>kahatlen</id>
        <email>kahatlen@apache.org</email>

Author: dag
Date: Thu Jun  5 09:44:06 2008
New Revision: 663656

URL: http://svn.apache.org/viewvc?rev=663656&view=rev
Log:
Added myself as PMC member.

Modified:
    db/site/project.xml

Modified: db/site/project.xml
URL: http://svn.apache.org/viewvc/db/site/project.xml?rev=663656&r1=663655&r2=663656&view=diff
==============================================================================
--- db/site/project.xml (original)
+++ db/site/project.xml Thu Jun  5 09:44:06 2008
@@ -271,6 +271,14 @@
       <roles><role>PMC Member, JDO</role></roles>
     </developer>
 
+    <developer>
+      <name>Dag H. Wanvik</name>
+      <id>dag</id>
+      <email>dag@apache.org</email>
+      <organization>The Apache Software Foundation</organization>
+      <roles><role>PMC Member, Derby</role></roles>
+    </developer>
+
   </developers>
 
   <dependencies>

Bryan Pendleton wrote:
>> Do the other changes look acceptable?
>> What does it take before I, or someone else, can commit the changes?
> 
> Those changes look great, Kristian; I think you should commit them.
> 

I committed the changes with revision 663035 and did a site deploy.

I was unable to follow the instructions on using the proxy to verify, as 
the proxy seems to be down. Maybe the instructions are stale?

Also, I got lots of these error messages when deploying, seemingly 
related to missing permissions:
     [exec] chmod: ./torque/releases/torque-3.3/village/xref-test: 
Operation not permitted



-- 
Kristian

> thanks,
> 
> bryan

Author: kristwaa
Date: Wed Jun  4 01:44:04 2008
New Revision: 663035

URL: http://svn.apache.org/viewvc?rev=663035&view=rev
Log:
Removed a lonely quote and fixed three broken links;
 - removed mention of a non-existing FAQ page.
 - removed links for "JAR" and "Sun JARs" (non-existing page "jars.html").
 - replaced branches link to Turbine with a link to Derby.

Modified:
    db/site/xdocs/source.xml

Modified: db/site/xdocs/source.xml
URL: http://svn.apache.org/viewvc/db/site/xdocs/source.xml?rev=663035&r1=663034&r2=663035&view=diff
==============================================================================
--- db/site/xdocs/source.xml (original)
+++ db/site/xdocs/source.xml Wed Jun  4 01:44:04 2008
@@ -19,14 +19,12 @@
 
       <p>
         All Java Language source code in the repository must be written in
-        conformance to the &quot;
+        conformance to the
         <a
           href="http://java.sun.com/docs/codeconv/html/CodeConvTOC.doc.html">Code
           Conventions for the Java Programming Language</a> as published by
         Sun, or in conformance with another well-defined convention specified
-        by the subproject. See the
-        <a href="faqs.html">FAQ page</a>
-        for links to subproject conventions.
+        by the subproject.
       </p>
 
       <subsection name="License">
@@ -57,12 +55,10 @@
         </p>
 
         <p>
-          Any
-          <a href="jars.html">JAR</a> committed to the Project's repositories
+          Any JAR committed to the Project's repositories
           <strong>must</strong> be licensed for redistribution. BSD and MPL style
           licenses are generally fine, but many
-          <a href="jars.html">Sun JARs</a>
-          do not permit redistribution.
+          Sun JARs do not permit redistribution.
         </p>
       </subsection>
 
@@ -93,8 +89,8 @@
           their release cycle is complete. All branches currently in use should
           be documented by the respective projects. For example,
           <a
-            href="/turbine/branches.html">Turbine</a> has page on the site that
-          details the branches currently in use.
+            href="/derby/dev/derby_source.html#Branches">Derby</a> has a page on
+          the site that details the branches currently in use.
         </p>
       </subsection>
 

> Do the other changes look acceptable?
> What does it take before I, or someone else, can commit the changes?

Those changes look great, Kristian; I think you should commit them.

thanks,

bryan

Content-type: text/plain; format=flowed; charset=ISO-8859-1
Content-transfer-encoding: 7BIT

Bryan Pendleton wrote:
>> When looking into a code convention issue, I discovered that there are 
>> three broken links on the DB project source page at 
>> http://db.apache.org/source.html:
>>
>> 1) http://db.apache.org/turbine/branches.html ("Turbine")
>> 2) http://db.apache.org/faqs.html ("FAQ page")
>> 3) http://db.apache.org/jars.html ("Sun JARs", "JAR")
>>
>> Does anyone know what should be done about these links?
>> Should they be removed or fixed?
> 
> Hi Kristian, thanks for looking at this.
> 
> I think it would be reasonable to:
> 
> 1) Remove the sentence "See the FAQ page  for links to
> subproject conventions." since that page does not exist.
> 
> 2) Change the sentence "Any JAR committed to the Project's
> repositories must be licensed for redistribution. BSD and MPL
> style licenses are generally fine, but many Sun JARs  do
> not permit redistribution." so that it doesn't use hyperlinks,
> but just uses the words "JAR" and "Sun JARs" normally. I think
> the sentence is sensible on its own and doesn't need the
> hyperlinks.
> 
> 3) Change the sentence "For example, Turbine has page on
> the site that details the branches currently in use." to
> replace "Turbine has page" with "Derby has a page", and to
> change the hyperlink to point to
> http://db.apache.org/derby/derby_downloads.html since that
> page seems to be a good example of a page which details
> the branches currently in use.
> 

Hello Bryan,

Thank you for the suggestions.
I have made a patch based on what you wrote (see attached diff and 
html). I also noticed there is a missing quote around the link to the 
code convention document. Instead of adding one on the other side, maybe 
the existing quote could be removed?

Do the other changes look acceptable?
What does it take before I, or someone else, can commit the changes?

FYI, the page being changed is accessible from db.apache.org/index.html 
("DB Apache Project"), selecting "DB Project Guidelines" under "More 
information" and finally "Source Repositories" (*not* from the left side 
meny).


-- 
Kristian

> thanks,
> 
> bryan

> When looking into a code convention issue, I discovered that there are 
> three broken links on the DB project source page at 
> http://db.apache.org/source.html:
> 
> 1) http://db.apache.org/turbine/branches.html ("Turbine")
> 2) http://db.apache.org/faqs.html ("FAQ page")
> 3) http://db.apache.org/jars.html ("Sun JARs", "JAR")
> 
> Does anyone know what should be done about these links?
> Should they be removed or fixed?

Hi Kristian, thanks for looking at this.

I think it would be reasonable to:

1) Remove the sentence "See the FAQ page  for links to
subproject conventions." since that page does not exist.

2) Change the sentence "Any JAR committed to the Project's
repositories must be licensed for redistribution. BSD and MPL
style licenses are generally fine, but many Sun JARs  do
not permit redistribution." so that it doesn't use hyperlinks,
but just uses the words "JAR" and "Sun JARs" normally. I think
the sentence is sensible on its own and doesn't need the
hyperlinks.

3) Change the sentence "For example, Turbine has page on
the site that details the branches currently in use." to
replace "Turbine has page" with "Derby has a page", and to
change the hyperlink to point to
http://db.apache.org/derby/derby_downloads.html since that
page seems to be a good example of a page which details
the branches currently in use.

thanks,

bryan

Hello,

When looking into a code convention issue, I discovered that there are 
three broken links on the DB project source page at 
http://db.apache.org/source.html:

1) http://db.apache.org/turbine/branches.html ("Turbine")
2) http://db.apache.org/faqs.html ("FAQ page")
3) http://db.apache.org/jars.html ("Sun JARs", "JAR")

Does anyone know what should be done about these links?
Should they be removed or fixed?



FYI, the W3C link checker also complained about the JDO project url, so 
I added a slash at the end. I haven't re-deployed the site.


thanks,
-- 
Kristian

Author: kristwaa
Date: Fri May 30 04:08:38 2008
New Revision: 661647

URL: http://svn.apache.org/viewvc?rev=661647&view=rev
Log:
Made JDO url exact by adding a slash at the end.

Modified:
    db/site/projects/jdo/project.xml

Modified: db/site/projects/jdo/project.xml
URL: http://svn.apache.org/viewvc/db/site/projects/jdo/project.xml?rev=661647&r1=661646&r2=661647&view=diff
==============================================================================
--- db/site/projects/jdo/project.xml (original)
+++ db/site/projects/jdo/project.xml Fri May 30 04:08:38 2008
@@ -33,7 +33,7 @@
 Java model abstraction of persistence, developed as Java Specification 
 Requests (JSR 12 and 243) under the auspices of the Java Community Process.
     </description>
-    <url>http://db.apache.org/jdo</url>
+    <url>http://db.apache.org/jdo/</url>
     <repository>
         <connection>scm:svn:http://svn.apache.org/repos/asf/db/jdo/trunk</connection>
         <developerConnection>scm:svn:https://svn.apache.org/repos/asf/db/jdo/trunk</developerConnection>

The Apache Derby project is pleased to announce an important
maintenance release of Derby, 10.3.3.0.

Apache Derby is a subproject of the Apache DB project.
Derby is a pure Java relational database engine which conforms to the
ISO/ANSI SQL and JDBC standards. Derby aims to be easy for developers
and end-users to work with.

IMPORTANT NOTICE:

If you are currently using Derby 10.3.1.4 or Derby 10.3.2.1, it is strongly
recommended that you upgrade to Derby 10.4.1.3 or 10.3.3.0 to avoid
any chance of database corruption due to an issue with multiple threads
accessing a database that is documented in DERBY-3347.

This bug can cause unrecoverable database corruption during periods of
heavy, multi-thread I/O operations. The error produced in the test case
used to diagnose the problem was:

ERROR XSDB3: Container information cannot change once written: was 0, now 80.

It is felt that other errors might also be generated when this type of
corruption occurs. The corruption message will most likely refer to page 0
of the container. For example:

ERROR XSDG1: Page Page(0 ,Container(0, 5856)) could not be
written...

This bug corrupts the pages on disk and can go unnoticed. If you do not
run database consistency checks regularly it is recommended you begin doing
so as soon as possible after the upgrade. To insure that corruption has not
already occurred in existing databases, after upgrade run the database
consistency check at least once to validate all tables in the database. This
process is documented at:

http://wiki.apache.org/db-derby/DatabaseConsistencyCheck

If the corruption has already occurred there is no guaranteed recovery of data
other than to recover from the last good backup. When doing so one should
also check that the previous backup did not also have the corruption.

In some cases one may recover data from the existing
database, depending on the extent of the corruption, but will require
by hand data recovery. Depending on the type of corruption this may
be successful or not. one should consult the Derby list if attempting
this recovery - no automatic software solution to this recovery exists.

Version 10.3.3.0 can be downloaded from:
http://db.apache.org/derby/releases/release-10.3.3.0.cgi

Version 10.4.1.3 can be downloaded from:
http://db.apache.org/derby/releases/release-10.4.1.3.cgi

For help or questions, please post to the Derby User list.
For instructions on how to subcribe and post to the Derby User list,
please see:

http://db.apache.org/derby/derby_mail.html

Hello everyone,

We would like to donate our relational data persistence component called
Empire-db to the ASF. According to the Incubator documentation we need to
find a Champion who can help us with the incubation process.

Even though with iBatis, JDO and Torgue there already are several database
related projects, we think our Empire-db could be a great extension to the
ASF project list as it works considerably different in many ways. Most of
all Empire-db uses a Java Object Model rather than XML-Mappings or
Annotations to describe the database schema. Therefore all Tables, Views,
Columns and so on are Objects which can be referenced from the code to
dynamically build SQL commands or to access Data model metadata – entirely
without the need to provide string literals. This in turn significantly
increases compile-time-safety and simplifies testing and maintenance.
Additionally uses benefit from the IDE’s code completion when building
column transformation expressions or constraints.

Empire-db is a mature project which has been proved its capabilities in many
medium to large scale projects. However we have only recently made it Open
Source under Apache 2.0 License.

There is a lot more information on the Empire-db website on
http://www.empire-db.org

If anyone would like to act as a Champion or knows someone who could be a
suitable Champion we would be happy to get his/her contact details and
further instructions.

Best regards,
Rainer