[
https://issues.apache.org/jira/browse/JSPWIKI-423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12646488#action_12646488
]
Janne Jalkanen commented on JSPWIKI-423:
----------------------------------------
Yes, we have something similar now:
* First, scan the default packages of "com.ecyrd.jspwiki" and
"org.apache.jspwiki"
* Then, use the contents of "jspwiki.plugin.searchPath" just like in 2.x,
except now we also search subpackages.
* Last, use jspwiki_module.xml to locate the rest. There's a new attribute
now, so you can say
<code>
<modules package="com.mycompany.jspwiki"/>
</code>
To add "com.mycompany.jspwiki" to the search path.
I agree that ModuleData is not very descriptive. However, we've already got
"WikiModule" as a superclass to WikiPlugin ;-). So I don't think those
particular alternatives are better. Open to suggestions though...
> Plugins should use annotations instead of jspwiki_module.xml
> ------------------------------------------------------------
>
> Key: JSPWIKI-423
> URL: https://issues.apache.org/jira/browse/JSPWIKI-423
> Project: JSPWiki
> Issue Type: Improvement
> Components: Plugins
> Reporter: Janne Jalkanen
> Assignee: Janne Jalkanen
> Fix For: 3.0
>
>
> Use of annotations makes it much easier to keep a plugin up to date. Please
> see org.apache.jspwiki.api.ModuleData annotation.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
