You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jdo-dev@db.apache.org by "Matthew T. Adams (Commented) (JIRA)" <ji...@apache.org> on 2011/11/07 14:54:51 UTC
[jira] [Commented] (JDO-699) Archive unmaintained modules
[ https://issues.apache.org/jira/browse/JDO-699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13145508#comment-13145508 ]
Matthew T. Adams commented on JDO-699:
--------------------------------------
> svn ci -m "archiving legacy artifacts"
Adding archive
Adding archive\JDO11.MF
Adding archive\JDO20.MF
Adding archive\api11
Adding archive\api2
Adding archive\api2-legacy
Adding archive\btree
Adding archive\enhancer20
Adding archive\fostore20
Adding archive\model20
Adding archive\query20
Adding archive\ri11
Adding archive\runtime20
Adding archive\tck11
Adding archive\tck2
Adding archive\tck2-legacy
Adding archive\util20
Deleting trunk\JDO11.MF
Deleting trunk\JDO20.MF
Deleting trunk\api11
Deleting trunk\api2
Deleting trunk\api2-legacy
Deleting trunk\btree
Deleting trunk\enhancer20
Deleting trunk\fostore20
Deleting trunk\model20
Deleting trunk\query20
Deleting trunk\ri11
Deleting trunk\runtime20
Deleting trunk\tck11
Deleting trunk\tck2
Deleting trunk\tck2-legacy
Deleting trunk\util20
Committed revision 1198735.
> 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