Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 82837 invoked from network); 23 Aug 2007 19:45:55 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 23 Aug 2007 19:45:55 -0000 Received: (qmail 70758 invoked by uid 500); 23 Aug 2007 19:45:51 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 70720 invoked by uid 500); 23 Aug 2007 19:45:51 -0000 Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: Delivered-To: mailing list derby-dev@db.apache.org Received: (qmail 70711 invoked by uid 99); 23 Aug 2007 19:45:51 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 23 Aug 2007 12:45:51 -0700 X-ASF-Spam-Status: No, hits=-100.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.4] (HELO brutus.apache.org) (140.211.11.4) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 23 Aug 2007 19:46:33 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 5193371420C for ; Thu, 23 Aug 2007 12:45:31 -0700 (PDT) Message-ID: <11588931.1187898331331.JavaMail.jira@brutus> Date: Thu, 23 Aug 2007 12:45:31 -0700 (PDT) From: "John H. Embretsen (JIRA)" To: derby-dev@db.apache.org Subject: [jira] Updated: (DERBY-3026) Remove deprecated frameworks directory and scripts In-Reply-To: <8179284.1187884231284.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/DERBY-3026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John H. Embretsen updated DERBY-3026: ------------------------------------- Priority: Major (was: Trivial) Derby Info: [Existing Application Impact, Release Note Needed] (was: [Release Note Needed, Existing Application Impact]) Urgency: Normal Good point, Kim. I'm upgrading the priority to Major to indicate that this has major impact (will remove an entire top-level directory), although an easy work-around exists (using the bin directory). I noticed that the docs were not updated in the 10.2 branch, which is unfortunate if/when more releases are created from that branch. Not sure if we should leave the 'frameworks.DEPRECATED.txt' file or a similar warning in the file tree or not, but I guess we still have some time to think about that. If anyone has opinions, please comment. > Remove deprecated frameworks directory and scripts > -------------------------------------------------- > > Key: DERBY-3026 > URL: https://issues.apache.org/jira/browse/DERBY-3026 > Project: Derby > Issue Type: Task > Components: Demos/Scripts > Affects Versions: 10.4.0.0 > Environment: N/A > Reporter: John H. Embretsen > Fix For: 10.4.0.0 > > > The 10.2.1.6 release notes said: > "New scripts have been added in the bin directory which follow Apache conventions. The scripts in the frameworks directory are deprecated and may be removed in future releases." > DERBY-1709 added a warning message in the scripts in the frameworks/ directory, as well as a textual file (frameworks.DEPRECATED.txt) in the root of the installation tree warning that the frameworks/ directory has been deprecated and that scripts in the bin/ directory should be used instead. This was committed after the 10.2.2.0 release, to both the trunk and the 10.2 branch (before the 10.3 branch was created). > The presence of both a frameworks/ directory and a bin/ directory is annoying to some users, and confusing to others. There is obviously a balance to keep between pleasing such users and other users who want backwards compatibility. > Perhaps the next feature release (10.4?) is the right time to remove the frameworks/ directory once and for all, since deprecation warnings have been issued for the past two feature releases (10.2 and 10.3, though stronger in 10.3 than 10.2), giving users time to adjust. > Marking "Release Note Needed" since it is important to make such changes visible to users. > This change may affect existing applications that are still using the deprecated scripts in the frameworks/ directory. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.