[
https://issues.apache.org/jira/browse/JSPWIKI-719?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13195855#comment-13195855
]
Juan Pablo Santos RodrÃguez commented on JSPWIKI-719:
-----------------------------------------------------
what about
{code:title=org.apache.wiki.plugin.PluginManager.java|borderStyle=solid}
private Class findPluginClass( String classname ) throws
ClassNotFoundException
{
return ClassUtil.findClass( Arrays.asList( m_searchPath,
"org.apache.wiki" ), classname );
}
{code}
?
Shouldn't affect existing plugins, as their searchpath is used first; if not
found (like in com.ecyrd.jspwiki.plugin.*) then we try on default plugin
namespace.
> provide plugin compatibility with pre 2.9 releases (patch PluginManager)
> ------------------------------------------------------------------------
>
> Key: JSPWIKI-719
> URL: https://issues.apache.org/jira/browse/JSPWIKI-719
> Project: JSPWiki
> Issue Type: Improvement
> Components: Plugins
> Affects Versions: 2.9
> Environment: NA
> Reporter: Harry Metske
> Assignee: Harry Metske
> Priority: Minor
> Fix For: 2.9
>
> Attachments: JSPWiki-719.patch
>
>
> JSPWiki 2.9 uses the new org.apache.wiki package names.
> If you have a bunch of wiki pages with plugin invocations that include the
> old (com.ecyrd.jspwiki) package name, this will now fail.
> So for example :
> {noformat}
> Index Page
> [{com.ecyrd.jspwiki.plugin.IndexPlugin}]
> {noformat}
> The suggestion is to patch the PluginManager to handle this by replacing the
> old package name by the new one.
> See attached patch.
> What do you think ?
--
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