Hi Juan Pablo,
I appreciate your effort at clarifying the versioning of the public API,
and sympathize with the situation the project is in. And thanks for your
long reply to Jurgen, that was enlightening.
I do think it important to point out that JSPWiki is somewhat different
to a lot of other
Hi,
the recent thread on the public api made me question how do we version
different releases, based on what kind of changes to expect from them.
https://jspwiki-wiki.apache.org/Wiki.jsp?page=VersioningProposal contains
the current proposal for JSPWiki versioning. It states:
"""
As of JSPWiki en
Hi Murray,
I'll look into make the current plugins mantain their signature if
possible. As I wrote else-thread, keep in mind the 6 last
releases contain code changes that could result in custom plugins / filters
not working anymore. That would also
happen on this release, whether the plugin signat
(apologies in advance because this is going to be a large e-mail)
Hi Jürgen,
I agree that retaining backward compatibility should be a top priority.
However, I strongly disagree with this sentence:
"As I understand this public API would bring no advantage in
functionality or user experience, onl
Hi,
part of the appeal of JSPWiki is for me that I can reach deep into the
wiki engine from plugins.
JSPWiki is for hackers, BigCorps use Confluence.
And as hacker I want control, I need to look into the Wiki core and
use what it offers, or work around its limitations.
So I'd rather prefer no API
