[
https://issues.apache.org/jira/browse/KNOX-3051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17903419#comment-17903419
]
ASF subversion and git services commented on KNOX-3051:
-------------------------------------------------------
Commit 4748771c41a399b72f9cde8c9eea251469053701 in knox's branch
refs/heads/master from hanicz
[ https://gitbox.apache.org/repos/asf?p=knox.git;h=4748771c4 ]
KNOX-3051: Ability to extend classpath with configurable paths (#971)
* KNOX-3051: Ability to extend classpath with configurable paths
* KNOX-3051: Code cleanup
* KNOX-3051: Rename Extender class, modified Extender to not retain reference
to the properties
> Add a classpath location for patches
> ------------------------------------
>
> Key: KNOX-3051
> URL: https://issues.apache.org/jira/browse/KNOX-3051
> Project: Apache Knox
> Issue Type: Improvement
> Components: Server
> Affects Versions: 2.0.0
> Reporter: Philip Zampino
> Priority: Minor
> Time Spent: 2h 10m
> Remaining Estimate: 0h
>
> It would be convenient to have the ability to easily pre-pend classes to the
> Knox classpath for quickly applying/testing patches.
> If this could be configurable, that would be ideal, though I'm not sure it's
> possible.
> If hard-coded, we should consider whether or not this location should be
> within the Knox installation directory or external to it. There are pros and
> cons to both, especially when considering upgrades in managed environments.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
