incubator-jspwiki-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Janne Jalkanen (JIRA)" <j...@apache.org>
Subject [jira] Updated: (JSPWIKI-425) Auto-update (Ecplise-like) mechanism for JSPWiki plugins.
Date Sat, 15 Nov 2008 09:18:54 GMT

     [ https://issues.apache.org/jira/browse/JSPWIKI-425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Janne Jalkanen updated JSPWIKI-425:
-----------------------------------

    Fix Version/s:     (was: 3.0)
                   3.1

Good idea but too big to fit in 3.0 scope.  Put it in 3.1.

>  Auto-update (Ecplise-like) mechanism for JSPWiki plugins.
> ----------------------------------------------------------
>
>                 Key: JSPWIKI-425
>                 URL: https://issues.apache.org/jira/browse/JSPWIKI-425
>             Project: JSPWiki
>          Issue Type: New Feature
>          Components: Core & storage, Plugins
>    Affects Versions: 3.0
>         Environment: any
>            Reporter: John Volkar
>            Priority: Minor
>             Fix For: 3.1
>
>
> Provide a means to enable a running JSPWiki installation to periodically update its installed
plugins.
> The following properties illustrate the idea.
> jspwiki.plugins.autoupdate.svn-url = xxx:xxx
> jspwiki.plugins.autoupdate.period = never | hourly | daily | weekly
> jspwiki.plugins.autoupdate.versioning = none | X.X.any | X.any.any  | any.any.any
> jspwiki.plugins.autoupdate.doc-source = none |  from-plugin-help | from-svn-url
> jspwiki.plugins.autoupdate.doc-target = none | %p | %p Help   (where %p is the Plugin
classname) 
> Mandatory plugin behaviors:
> 1) follow a Major.Minor.Patch version numbering scheme (via annotations or simply an
interface or abstract method on WikiPlugin)
> 2) invoke with param=help return plugin help as wikitext , or maintain a standard named
file in svn.
> Item 1 allows a versioning update policy to be followed consistently.
> Item 2 allows generation of a docs/help/usage page for the installed plugin version.
> Of course the attributes in jspwiki_module.xml (which  become annotations in 3.0) should
be respected (specifically min and max jspwiki version that the plugin needs).  *Possibly*
this could be extended to autoinstall dependencies.
> What I *really* want is a more OSGi like bundle scheme, but that may be overkill for
plugins (as well as perhaps being more complex that is really warranted at this time).

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message