Return-Path: X-Original-To: apmail-db-general-archive@www.apache.org Delivered-To: apmail-db-general-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 70168DC7B for ; Wed, 19 Dec 2012 18:21:11 +0000 (UTC) Received: (qmail 47463 invoked by uid 500); 19 Dec 2012 18:21:11 -0000 Delivered-To: apmail-db-general-archive@db.apache.org Received: (qmail 47404 invoked by uid 500); 19 Dec 2012 18:21:11 -0000 Mailing-List: contact general-help@db.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: general@db.apache.org List-Id: Delivered-To: mailing list general@db.apache.org Received: (qmail 47397 invoked by uid 99); 19 Dec 2012 18:21:11 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 19 Dec 2012 18:21:11 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.4] (HELO eris.apache.org) (140.211.11.4) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 19 Dec 2012 18:21:06 +0000 Received: from eris.apache.org (localhost [127.0.0.1]) by eris.apache.org (Postfix) with ESMTP id 8144923889DA for ; Wed, 19 Dec 2012 18:20:46 +0000 (UTC) Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: svn commit: r843115 [4/44] - in /websites/production/db/content/derby: ./ binaries/ blogs/ blogs/images/ dev/ docs/ images/ integrate/ integrate/plugin_help/ integrate/plugin_help/images/ logo/ manuals/ papers/ papers/DerbyTut/ releases/ skin/ skin/css... Date: Wed, 19 Dec 2012 18:20:28 -0000 To: general@db.apache.org From: rhillegas@apache.org X-Mailer: svnmailer-1.0.8-patched Message-Id: <20121219182046.8144923889DA@eris.apache.org> X-Virus-Checked: Checked by ClamAV on apache.org Added: websites/production/db/content/derby/binaries/refmanual.tar.gz ============================================================================== Binary file - no diff available. Propchange: websites/production/db/content/derby/binaries/refmanual.tar.gz ------------------------------------------------------------------------------ svn:mime-type = application/octet-stream Added: websites/production/db/content/derby/binaries/refmanual.zip ============================================================================== Binary file - no diff available. Propchange: websites/production/db/content/derby/binaries/refmanual.zip ------------------------------------------------------------------------------ svn:mime-type = application/octet-stream Added: websites/production/db/content/derby/binaries/reuben_derby_perf.pdf ============================================================================== Binary file - no diff available. Propchange: websites/production/db/content/derby/binaries/reuben_derby_perf.pdf ------------------------------------------------------------------------------ svn:mime-type = application/octet-stream Added: websites/production/db/content/derby/binaries/squirrel_derby.zip ============================================================================== Binary file - no diff available. Propchange: websites/production/db/content/derby/binaries/squirrel_derby.zip ------------------------------------------------------------------------------ svn:mime-type = application/octet-stream Added: websites/production/db/content/derby/binaries/tuningderby.zip ============================================================================== Binary file - no diff available. Propchange: websites/production/db/content/derby/binaries/tuningderby.zip ------------------------------------------------------------------------------ svn:mime-type = application/octet-stream Added: websites/production/db/content/derby/binaries/xsljeffmodified.zip ============================================================================== Binary file - no diff available. Propchange: websites/production/db/content/derby/binaries/xsljeffmodified.zip ------------------------------------------------------------------------------ svn:mime-type = application/octet-stream Added: websites/production/db/content/derby/blogs/images/off.jpg ============================================================================== Binary file - no diff available. Propchange: websites/production/db/content/derby/blogs/images/off.jpg ------------------------------------------------------------------------------ svn:mime-type = application/octet-stream Added: websites/production/db/content/derby/blogs/index.html ============================================================================== --- websites/production/db/content/derby/blogs/index.html (added) +++ websites/production/db/content/derby/blogs/index.html Wed Dec 19 18:20:21 2012 @@ -0,0 +1,918 @@ + + + + + + + +Blogs and articles about Derby + + + + + + + + + +
+ +
+apache > db +
+ +
+ + + + +
+Apache DB Project +
+ + + + +
+
+
+
+ +
+ + +
+ +
+ +   +
+ + + + + +
+
Font size: +   +   +   +
+

Blogs and articles about Derby

+ + + +

+ Here we collect blogs and articles about Derby. Please also check the + Derby Wiki for smaller write-ups. +

+ + +

+ There are many older Derby articles at IBM developer works that may be of interest here + +

+ + +

+ Note: Some articles use the term "Java DB". + + Java DB is essentially the + same as Derby: it is the bits distributed by Oracle as part of the + Java Development Kit (JDK) based on the Derby bits. +

+ + +

+ Note: Some articles use the term "Cloudscape". Cloudscape is the product name used + by IBM before Derby was open sourced. +

+ + +

+ There is also the now somewhat dated book "Apache Derby - Off to the Races"Book frontispiece +
+ +

+ + + + +

Blogs

+
+

+ +Knut Hatlen's blogThis often contains news about the latest releases with examples of the new features. +

+

+ +Lance Andersen's blog Java EE and JDBC related issues. +

+
+ + + + + +

Articles grouped by topic, newest listed first

+
+ +

Tutorials, Tips and Tuning

+ +

Getting Started

+

+ (See also the Derby Tutorial). +

+

+ +Getting Started with Apache Derby (Java DB) (by Stuart Ellis) - including how to use Derby with JRuby on Rails +

+

+ + + Flying out of the gate with Derby (by Sing Li) +
Derby is a 100% + Java open source relational database, and you can't afford to + ignore it. Learn why in this article. +

+

+ +Apache Derby Database - Tutorial + (by Lars Vogel) + + This articles explains how to install the Apache Derby database, + how to start the Derby server, how to connect via Java to Derby + and how to use the Derby command line tool to issue SQL + statements. The installation of Apache Derby as Windows Service is + also explained. +

+

+ +Developing with Apache Derby -- Hitting the Trifecta: Introduction to Apache Derby +
+ +Developing with Apache Derby -- Hitting the Trifecta: Introduction to Apache Derby - Part 1 +
+ +Developing with Apache Derby -- Hitting the Trifecta: Introduction to Apache Derby - Part 2 +
+ +Developing with Apache Derby -- Hitting the Trifecta: Introduction to Apache Derby - Part 3 +
+ +Developing with Apache Derby -- Hitting the Trifecta: Introduction to Apache Derby - Part 4 +
+ +Developing with Apache Derby -- Hitting the Trifecta: Introduction to Apache Derby - Part 5 +
+ +Developing with Apache Derby -- Hitting the Trifecta: Introduction to Apache Derby - Part 6 +
+ +Developing with Apache Derby -- Hitting the Trifecta: Introduction to Apache Derby - Part 7 +
+ "Jump in and try it -- and appreciate the simplicity" +

+

+ + + Getting Started with Derby + (by Stephen + B. Morris) +
This thorough introduction to Derby addresses + installation, environment set up, building and executing an + application with Derby embedded. +

+

+ + + Using Derby as a Network Database Server Engine + (by + Stephen B. Morris +
Need a network database server that can + handle multiple remote clients? There's no longer a need to + spend megabucks. Stephen Morris explains how Derby can serve the + needs of many remote clients via an open-source RDBMS. +

+

+ + + Further Steps with Derby: Defining and Accessing Your Data + (by Stephen + B. Morris)
Do you need a simple database as part of an + application upgrade? Derby is easy to use and program and + combines high performance with a modest footprint. Stephen + Morris tells you why database development is no longer the sole + preserve of DBAs or data center IT people. +

+

+ + + Java databasing with Derby - Java's own open source database(by Pan Pantziarka/the Register ) + +

+ +

Features, Hints and Tips

+

+ +Derby 10.8 is out A feature summary (by Knut Hatlen) +
+ +What's new in Derby 10.7? (by Knut Hatlen) +
+ +Derby 10.6.2 is out (by Knut Hatlen) +
+ + + Introducing Java DB 10.5.1.1 (by Rick Hillegas) + +

+

+ +Java DB Table Functions (Download Code and White Paper) (by Rick Hillegas) + + This white paper explores table functions, a feature introduced in + Derby release 10.4.1.3.
+ Rich and expressive, SQL is the world's most popular database + query language. Table functions let you take SQL outside its + traditional home in the RDBMS, setting SQL loose on data in the + wild. +

+

+ + + LDAP Authentication with Apache Derby (Java DB) + (by John Yeary)
+ A short, simple tutorial on how to use Apache Derby and LDAP. +

+ +

Security

+

+ +Protect Your Apache Derby Database from Superuser Attacks (by Marios Karagiannopoulos) + +

+

+ + + Java DB Security + (by Rick Hillegas) + + Derby provides several ways to protect the correctness and + privacy of your data as well as forestall accidental or + malicious misuse of the database software itself. This white + paper explains how to improve the database security of + applications and machines which use Derby. +

+

+ + + Java DB End-to-End Security + (by Masoud Kalali)
+ Derby, as an open source and pure-Java + relational database, provides several features that make it + suitable for embedded and network server modes, including + Derby mechanisms to make it secure on several levels. If + you are going to build an application using Derby and + security is important, then this article is for you. +

+ +

Performance and Tuning

+

+ + + Tuning Derby + (by Dejan + Bosanac, Software developer, technology consultant and + author, ONJava.net)
+ + There is a big difference in the behavior of a database when + it is populated with a small amount of test inputs and when + it holds a large amount of data. Usually, you would not + address these database performance issues early in the + development process, but when the time comes, you should + take some action to ensure that the application is working + correctly with large amounts of data. +

+ +

Tools and Migration

+ +

Tools

+

+ +MyEclipse Derby Database Server Tutorial + + +

+

+ + + Working with the Java DB (Derby) Database [in NetBeans] (by the Netbeans team) + + This document demonstrates how to quickly set up a connection to + Oracle's Java DB (which is based on the Apache Derby database) in + NetBeans. Once a connection is made, you can easily begin working + with the database in the NetBeans IDE, allowing you to create + tables, populate them with data, run SQL queries, and more. +

+

+ + + Using SQuirreL SQL Client with Derby +
+ + SQuirreL SQL Client is a useful tool for browsing and + manipulating SQL databases via JDBC. This paper discusses + setting up SQuirreL to access Derby databases via the Derby + Embedded Driver and Client Drivers with the 10.1 version of + Derby. +

+

+ + + Using Java DB with Java Studio Creator and Tomcat + (by David + Botterill, Java Tools (Java Studio Creator and NetBeans) + Evangelist, Sun Microsystems)
+ + In this blog David Botterill helps you set up the Travel sample + database of Java Studio Creator 2 on Tomcat using Derby. +

+

+ +Back to basics: Scripting Apache Derby's ij tool + +

+ +

Migration

+

+ + + Using DdlUtils to Migrate Databases to Derby +
+ + +DdlUtils, an + Apache DB subproject, provides utilities for creating and + working with Database Definition (DDL) files and for + exporting and importing data in XML format. Among other + uses, DdlUtils makes it easier to migrate from one database + vendor to another. This paper provides a simple example for + using DdlUtils to migrate a database to Derby using + the DdlUtils + Ant tasks. +

+ +

Applications

+ +

Client

+

+ + + Further Steps with Derby: Derby Embedded in a Browser + + (by + Stephen B. Morris) +

+

+ +Offline Ajax with Apache Derby (by Michael Galpin) + +

+

+ + + Synchronizing a Web Client Database: LocalCalendar and Google Calendar (by David van Couvering) + +

+

+ +Build an Ajax application using Google Web Toolkit, Apache Derby, and Eclipse (by Noel Rappin) + +

+

+ +Real-world Apache Derby: Who needs Ajax, anyway? +
+ +Real-world Apache Derby, Part 1: Apache Derby and OpenOffice.org Calc +
+ +Real-world Apache Derby, Part 3: Portable document storage + +

+

+ + + Cloudscape and Ajax - An example +
+ + This article explains all the steps and requirements to create + an embedded database and Web server application. The source code + and a ready to run application provided as a zip file are + available for download. +

+

+ + + Using Java DB in Desktop Applications (by John O'Connor, Java + Technology evangelist, engineer, and writer at Sun + Microsystems)
+ + Learn how to deploy Derby, based on the Apache Derby database, + within desktop Java applications. The article uses the Address + Book demo to show you how to work with Derby as an embedded + database. +

+ +

Middle Tier

+

+ +Getting Started with the Apache Derby Open Source Database in CF8 (Cold Fusion) (by ColdFusion troubleshooter Charlie Arehart) + +

+

+ +An Experiment In Using An Embedded Apache Derby Database To Power ColdFusion Query-Of-Queries (by Ben Nadel) + +

+

+ +"Using Apache Derby" (with Cold Fusion), watch my Max presentation + +

+

+ +Working with the embedded Derby database for WebSphere Portal (by Cody Burleson) + +

+

+ +Using Apache Derby databases, Part 1: Managed objects in a converged provider environment +
+ +Using Apache Derby databases, Part 2: Manage IT services beyond mere deployment +
+(by Stephen Morris) + Automating IT management with IBM AIDE and Derby +

+

+ +Apache Derby resources from the Web services perspective, Part 1: Derby data as WS-Resources +
+ +Apache Derby resources from the Web services perspective, Part 2: Producing and consuming WS-Notifications with Derby +
+ +Apache Derby resources from the Web services perspective, Part 3: Manage Apache Derby using Web Services Distributed Management +
+ +

+

+ + + Using Apache Derby with iBATIS JPetStore 4 on the WebSphere + Server +
+ + This document demonstrates setting up the JPetStore 4.0 + application to run on a J2EE Application Server using an + embedded Apache Derby database as the persistence layer. Apache + Derby is a small footprint, open source, relational database + engine written in Java. It is ideally suited for use with J2EE + and Web applications where reliability, portability, ease of use + and low maintenance is important. +

+

+ + + Embedding Apache Derby in Tomcat and creating an iBATIS JPetStore + Demo +
+ + Shows the steps required to embed Derby in a Tomcat version + 5.5.12 Server and then deploy a copy of the iBATIS JPetStore + application that utilizes a Derby database. +

+

+ + + Installing Apache Derby Database on ColdFusionMX 7.0.2 +
+ + Instructions for installing and configuring Derby for use on + ColdFusionMX. Conclusion: "All in all, it was very easy to + get Apache Derby to work with ColdFusionMX. ... I'm quite sure + I'll be using much more of Derby in the projects I work + on." +

+

+ + + Implementing Java DB as an Embedded Cache to Support Service + (by Jason Baragry, + Sun Client Solutions Engineer in Oslo, Norway)
+ + Describes how Derby can be used as an embedded database to act + as a cache for services deployed in the Sun Java System + Application Server. +

+

+ + + Apache Derby and Red Hat Application Server: JonAS Integration + (by Ramandeep Kaur)
+ + This document provides details on how to configure and run + Apache Derby with Red Hat Application Server. +

+ +

Persistence

+

+ + + Using JPOX JDO with Derby +
+ + Provides a concrete example of using JPOX JDO to persist and + retrieve data to and from Apache Derby. Java Data Objects (JDO) + is a specification for persisting Java objects. +

+

+ + + Running the Torque Tutorial on Derby +
+ + This page summarizes the changes required to run the Torque 3.2 + tutorial on Derby 10.1 using the Derby embedded JDBC driver. +

+

+ +HibernateHelp +
+ + This wiki page documents various peoples' experience using + Hibernate with Derby. +

+ +

Scalability and Failover

+

+ +Sequoia Database Clustering Middleware with GlassFish and Java DB (Apache Derby) + (by Jagadish + Ramu, Glassful engineer)
+ + This demo and tutorial show how GlassFish and Sequoia can be used + together to provide clustering capability with Apache + Derby. Sequoia is an open source database clustering middleware + that allows any Java application to transparently access a cluster + of databases through + JDBC. +

+

+ + + HOWTO use C-JDBC with Apache Derby (by Emmanuel Cecche)
+ + How to use Derby with C-JDBC,an open source database cluster + middleware that allows any Java application to transparently + access a cluster of databases through JDBC. +

+
+ + +

+Last Updated: August 20, 2011 +

+ +
+ +
 
+
+ + + Added: websites/production/db/content/derby/derby_charter.html ============================================================================== --- websites/production/db/content/derby/derby_charter.html (added) +++ websites/production/db/content/derby/derby_charter.html Wed Dec 19 18:20:21 2012 @@ -0,0 +1,368 @@ + + + + + + + +Apache Derby Project Charter + + + + + + + + + +
+ +
+apache > db +
+ +
+ + + + +
+Apache DB Project +
+ + + + +
+
+
+
+ +
+ + +
+ +
+ +   +
+ + + + + +
+
Font size: +   +   +   +
+

Apache Derby Project Charter

+ + + + +

Derby Project Charter

+
+

+The Derby project develops open source database technology that is: +

+
    + +
  • Pure Java
    • + +
  • Easy to use
    • + +
  • Small footprint
    • + +
  • Standards based
    • + +
  • Secure
    • + +
+ +

Database Technology

+

+ Database technology is defined as software that processes data related + requests from applications. + Data requests include data definition, data modification and data retrieval. + Database GUI tooling and IDEs are not developed by the Derby project. +

+ +

Pure Java

+

+ Derby technology is written in Java to take advantage of Java’s write + once, run anywhere promise. + Java platforms such as OSGi, J2ME, J2SE and J2EE are supported as appropriate. +

+ +

Easy to Use

+

+ Derby technology aims to be easy to use for software developers and zero administration for end users. +

+ +

Small Footprint

+

+ Derby technologies are designed to provide significant useful + functionality in a small code size footprint with efficient runtime + resource usage. +

+ +

Standards based

+

+ Derby technology adheres to database standards such as JDBC + and ANSI SQL standards. + This means Derby provides the functionality expected of a modern relational + database, + including SQL syntax, transaction management, concurrency, triggers, + and online backups. + And it also means developers can later migrate to other databases if they + so choose. +

+ +

Secure

+

+ Derby technology provides secure data management appropriate to environment + the engine is executing in. Traditional enterprise database systems rely on + the machine being physically protected (locked machine room) for security, + Derby databases are often in unprotected environments, such as laptops and + unattended hardware. +

+
+ + + +

Derby Technologies

+
+ +

Derby embedded database engine

+

+ The core of the technology, Derby’s database engine is a full + functioned relational embedded database engine. JDBC and SQL are the + programming APIs. +

+ +

Derby network server

+

+ The Derby network server increases the reach of the Derby database + engine by providing traditional client server functionality. + The network server allows clients to connect over TCP/IP using the standard + DRDA protocol. + The network server allows the Derby engine to support networked JDBC, + ODBC/CLI, Perl and PHP. +

+ +

Database Utilities

+
    + +
  • +ij -- a tool that allows SQL scripts to be executed + against any JDBC database. +
    • + +
  • +dblook -- Schema extraction tool for a Derby database. +
    • + +
  • +sysinfo -- Utility to display version numbers and + class path. +
    • + +
+
+ + + +

Derby History

+
+

+Cloudscape Inc, an Oakland, California start-up, was founded in 1996 to +develop Java database technology. The first release of the database engine, +then called JBMS, was in 1997. +Subsequently the product was renamed Cloudscape and releases were made about +every six months. +In 1999 Informix Software, Inc., acquired Cloudscape, Inc. +In 2001 IBM acquired the database assets of Informix Software, +including Cloudscape. +The database engine was re-branded to IBM Cloudscape and releases continued, +mainly focussing on embedded use with IBM's Java products and middleware. +In August 2004 IBM contributed the code to the Apache Software Foundation +as Derby, an Incubator project sponsored by the Apache DB project +(see the Incubator proposal). +In July 2005 Derby graduated from the Incubator into the Apache DB project. +

+
+ + +

+ +Last updated: 14-February-2006 + +

+ + +
+ +
 
+
+ + + Added: websites/production/db/content/derby/derby_comm.html ============================================================================== --- websites/production/db/content/derby/derby_comm.html (added) +++ websites/production/db/content/derby/derby_comm.html Wed Dec 19 18:20:21 2012 @@ -0,0 +1,622 @@ + + + + + + + +Apache Derby: Get Involved! + + + + + + + + + +
+ +
+apache > db +
+ +
+ + + + +
+Apache DB Project +
+ + + + +
+
+
+
+ +
+ + +
+ +
+ +   +
+ + + + + +
+
Font size: +   +   +   +
+

Apache Derby: Get Involved!

+ + + + +

+Welcome to the Derby community! +We invite you to participate as a user or as a contributor -- or both! +

+ + + +

Provide Feedback

+
+

+The Derby technology will grow and thrive from those who use it, +so send the community your feedback: +

+
    + +
  • + Subscribe to the Derby mail lists. +
    • + +
  • + Add your wisdom to the Derby Wiki. +
    • + + +
  • + Derby uses Apache's Jira + issue tracker + to log bugs and enhancement requests. + Anyone can browse the Jira database. + To log new issues, + see the tips page, + which describes how to create a userid for yourself and how + to log useful bugs. + To update existing issues, email your Jira userid to + derby-dev@db.apache.org and + request that it be added to the derby-developers Jira list. +
    • + +
  • + Pre-built jar files are available on the + Derby Downloads page. +
    • + + +
+
+ + + +

Use the Derby Communication Channels

+
+

+The primary mechanism for Derby communication is +the Derby mail lists. +Anyone can participate, no matter what their time zone. The ASF +maintains a reliable searchable archive of past discussions. Oversight +is enabled. Many eyes ensures that the project evolves in a consistent +direction. +The main channel for development is the "derby-dev" mailing list, and the +main channel for user support is the "derby-user" mailing list. +As is usual with mailing lists, be prepared to wait for an answer. +

+

+The Derby community also maintains an IRC channel on the freenode IRC +network. You are welcome to stop by: +

+

/server irc.freenode.org +/join #derby +

+

+However, keep in mind that all decisions occur on the Derby mail lists +and not on IRC. Please summarize any off-list knowledge gained and post +it for the benefit of all. For example, if a user asks a question and +gets a response, post that exchange to derby-user. If developers work +out a strategy for solving a problem, post a summary to derby-dev, +including alternatives that were considered but ultimately dismissed and +why. If developers figure out how something works, post a summary of the +finding to derby-dev. +

+

+In all cases, additional eyes can catch any errors, point out any +subtleties, and fill in additional information. The more discussions are +on-list, the more the rest of the community will benefit from the +understanding that is developed. +

+
+ + + +

Understand How Development Works at Apache

+
+

+New users and developers who are familiar with how development occurs +on commercial products sometimes get confused by open source development +at Apache. +

+

+The first thing to understand is individuals +volunteer for various tasks. Here are some relevant quotes from the +How the ASF works +page: +

+
    + +
  • +"Projects are normally auto governing and driven by the people who +volunteer for the job. This is sometimes referred to as "do-ocracy" +-- power of those who do. This functions well for most cases." + +
    • + + +
  • +"All of the ASF including the board, the other officers, the + committers, and the members, are participating as individuals. + That is one strength of the ASF, affiliations do not cloud the + personal contributions.
    + Unless they specifically state otherwise, whatever they post on any + mailing list is done *as themselves*. It is the individual + point-of-view, wearing their personal hat and not as a mouthpiece + for whatever company happens to be signing their paychecks right + now, and not even as a director of the ASF."     + +
    • + +
+

+However, lest it look like everybody is working diligently solely as an +individual (and possibly at cross purposes with others), +community coordination and contribution occurs on the Apache mail lists. +The +How the ASF works +page provides helpful context. +

+

+So, Derby depends on the community to work together as a whole +to change the product. +How can new Derby users and developers actively participate in these changes? +

+

+First, +open Jira issues +to report problems you have stumbled upon or to request new features. +However, remember +that volunteers fix issues -- a valuable reminder from the ASF +FAQ +is below: +

+
    + +
  • +What is Apache not about? + +
      + + +
    • +To [...] + demand someone else to fix your bugs. +
      • + +
    + +
    • + +
+

+Second, vote on Jira issues that you feel strongly should be fixed. +

+

+Third, participate even more in the Derby development +process by subscribing to +derby-dev@db.apache.org. That's +where core development discussions occur and decisions get made. +

+

+Fourth, if you want to actually start doing development, the +next section is tailored specifically for you. +

+
+ + + +

Contribute Code or Documentation

+
+

+If you would like to participate directly in Derby development, +here are a few guidelines: +

+
    + +
  • Like all Apache projects, the Derby project + follows the + Apache + Way. +
    • + + +
  • Derby follows the guidelines established by the + Apache DB Project. +
    • + +
+

+Additional information for contributors is on the +Derby Wiki. Below +is just a sampling of the topics covered: +

+ +

+The remainder of this section includes some miscellaneous tips that don't +seem to have made it onto the Wiki (yet). +

+

+ +How to create a patch + +

+
    + + +
  1. + + +

    +Sync up your local svn copy with any changes checked into the server: +

    + + +
    +cd <my_derby_loc>/trunk
+svn update
+
    + + +
    2. + + +
  2. + +

    +Make your change. If you are adding a new file, add it using svn. +The example below shows adding a file named xyz.java: +

    + + +
    +svn add java/engine/impl/yadiyadi/xyz.java 
+svn propset svn:eol-style native java/engine/impl/yadiyadi/xyz.java
+
    + + +
    3. + + +
  3. + +

    +Run the tests (to be safe, run derbyall). +(Be sure to set your CLASSPATH env var to include the trunk/classes dir.) +

    + + +
    +ant all
+cd <a temp/test dir>
+java org.apache.derbyTesting.functionTests.harness.RunSuite derbyall
+
    + + +

    +Resolve any test failures (update relevant ../functionTests/master/*.out files). +

    + + +
    4. + + +
  4. + +

    +Make the patch. +

    + + +
    +svn diff > xyz.diff
+
    + + +
    5. + + +
  5. + + +

    +Attach the patch to the Jira issue. +

    + + +

    +Include the following information with your post: +

    + + +
      + + +
    • Which tests were run. +
      • + + +
    • For a feature, a description of what the detailed functionality that + is being implemented is essential. +
      • + + +
    • A description of the changes, e.g. how a feature is implemented or why + the change fixes a bug. Hopefully this will be in comments in the code + but sometimes an overview in the e-mail is useful, or have the e-mail + point to an overview in the code comments. +
      • + + +
    • If the patch modifies more than one file then the output from + 'svn status' is very useful to have in the e-mail. +
      • + + +
    + +
    6. + + +
+

+ +Submit patches against the trunk + +

+

+New features, code cleanup, performance +fixes and other significant changes need to be submitted against the trunk. +

+

+Bug fixes may be submitted against either the trunk or a branch. +

+

+See the "Contributing with patches" mail list topic. +

+

+ +Enigmail tips for sending and saving patches + +

+

+If you use Enigmail to send a patch to the +derby-dev mail list be aware that, +by default, +Enigmail handles Mozilla's text=flowed formatting +by replacing leading spaces with a tilde ("~") character (see + +http://enigmail.mozdev.org/troubles.html#flowed). +To send a patch in-line using Enigmail, +turn off the Allow flowed text setting: +

+
+     Enigmail -> Preferences -> Sending -> Allow flowed text (RFC 2646)
+
+

+If you use Enigmail to save a patch submitted to the +derby-dev mail list, +you may need to decrypt and save that decrypted email if it was signed using +gnuPG because +lines that begin with a dash get escaped with "- " (see +http://www.stillhq.com/extracted/gnupg-api/doc/faq.html#q4.7). +To extract the text in Enigmail without the escape characters, +first decrypt the email, then save the decrypted message: +

+
+     Enigmail -> Decrypt/verify
+     Enigmail -> Save decrypted message
+
+
+ + +

+ +Last updated: May 4, 2006 + +

+ + +
+ +
 
+
+ + + Added: websites/production/db/content/derby/derby_downloads.html ============================================================================== --- websites/production/db/content/derby/derby_downloads.html (added) +++ websites/production/db/content/derby/derby_downloads.html Wed Dec 19 18:20:21 2012 @@ -0,0 +1,332 @@ + + + + + + + +Apache Derby: Downloads + + + + + + + + + +
+ +
+apache > db +
+ +
+ + + + +
+Apache DB Project +
+ + + + +
+
+
+
+ +
+ + +
+ +
+ +   +
+ + + + + +
+
Font size: +   +   +   +
+

Apache Derby: Downloads

+ + + + + +

Latest Official Releases

+
+
    + +
  • +10.9.1.0 + (June 25, 2012 / SVN 1344872) +
    • + +
  • +10.8.3.0 + (November 16, 2012 / SVN 1405108) +
    • + +
+
+ + +

Archived Official Releases

+
+
    + +
  • +10.8.2.2 + (October 24, 2011 / SVN 1181258) +
    • + +
  • +10.8.1.2 + (April 29, 2011 / SVN 1095077) +
    • + +
  • +10.7.1.1 + (December 14, 2010 / SVN 1040133) +
    • + +
  • +10.6.2.1 + (Oct 5, 2010 / SVN 999685) +
    • + +
  • +10.6.1.0 + (May 19, 2010 / SVN 938214) +
    • + +
  • +10.5.3.0 + (August 21, 2009 / SVN 802917) +
    • + +
  • +10.5.1.1 + (April 28, 2009 / SVN 764942) +
    • + +
  • +10.4.2.0 + (September 5, 2008 / SVN 689064) +
    • + +
  • +10.3.3.0 + (May 12, 2008 / SVN 652961) +
    • + +
  • +10.4.1.3 + (April 24, 2008 / SVN 648739) +
    • + +
  • +10.2.2.0 + (Dec 12, 2006 / SVN 485682) +
    • + +
  • +10.2.1.6 + (Oct 02, 2006 / SVN 452058) +
    • + +
  • +10.1.3.1 + (Jun 30, 2006 / SVN 417277) +
    • + +
  • +10.1.2.1 + (Nov 18, 2005 / SVN 330608) +
    • + +
  • +10.1.1.0 + (Aug 3, 2005 / SVN 208786) +
    • + +
+
+ + + +

Deprecated Releases

+
+

+Derby 10.5.2.0 was removed from the website because of a wrong results regression bug (DERBY-4331). Its replacement release, 10.5.3.0, includes the other fixes listed in the 10.5.2.0 release notes. +

+

+The following releases were removed from the Derby website because they contained a serious, data-corrupting bug. +However, you may still want to review their release notes in order to reconstruct the complete history +of changes to Derby: +

+ +
+ + + +

Change History

+
+

+ +Hey! Where is the information that used to be on this page +on how to check out and build the Derby source code? + +

+

+Information about Derby source code was moved to the +Source Code page. +

+
+ + + +
+ +
 
+
+ + +