Mailing-List: contact jdo-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: jdo-dev@db.apache.org
Date: Fri, 28 Oct 2011 17:21:32 +0000 (UTC)
From: "Matthew T. Adams (Updated) (JIRA)" <jira@apache.org>
To: jdo-dev@db.apache.org
Message-ID: 
 <1234750043.32543.1319822492328.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1676312630.17283.1318688951779.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Updated] (JDO-699) Archive unmaintained modules
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/JDO-699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matthew T. Adams updated JDO-699:
---------------------------------

    Description: There are many modules in the trunk of the JDO source repo that are no longer maintained.  I propose to create a new directory "archive" as a peer to trunk, branches, releases, and site, then svn-move them from trunk to archive.  (was: There are many modules in the trunk of the JDO source repo that are no longer maintained.  I propose to delete them from trunk.)
        Summary: Archive unmaintained modules  (was: Delete unmaintained modules)
    
> Archive unmaintained modules
> ----------------------------
>
>                 Key: JDO-699
>                 URL: https://issues.apache.org/jira/browse/JDO-699
>             Project: JDO
>          Issue Type: Improvement
>          Components: api11, api2-legacy, btree, core2, enhancer2, fostore2, model2, query2, ri11, runtime2, tck11, tck2-legacy, util2
>    Affects Versions: JDO 3 maintenance release 1
>            Reporter: Matthew T. Adams
>            Assignee: Matthew T. Adams
>             Fix For: JDO 3 maintenance release 1
>
>
> There are many modules in the trunk of the JDO source repo that are no longer maintained.  I propose to create a new directory "archive" as a peer to trunk, branches, releases, and site, then svn-move them from trunk to archive.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira