[
https://issues.apache.org/jira/browse/DERBY-3026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12522208
]
Kim Haase commented on DERBY-3026:
----------------------------------
Thanks for filing this issue. I agree that this is a good thing to do for 10.4.
It's worth pointing out that all references to the frameworks directory have
been removed from the documentation as of 10.3 (DERBY-1662 and DERBY-1709), so
there will be no documentation impact except for the release notes.
I'd suggest marking the priority as at least minor; I don't think it's trivial,
since it affects the file structure and footprint of Derby noticeably.
> 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
> Priority: Trivial
> 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.
