[
https://issues.apache.org/jira/browse/JSPWIKI-38?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12659769#action_12659769
]
Janne Jalkanen commented on JSPWIKI-38:
---------------------------------------
@Murray: everything is an API, both classes and interfaces, if it's public.
However, the question is really about *stable* and *unstable* APIs. The .api
package comes with a promise (and hopefully, a test suite) to make sure that if
you code against them only, your plugins will work in the future. And, if you
do code against anything unstable, you know that it's likely to break from
major version to major version.
Currently, this is not the case. We have even broken interfaces (like the
PageFilter one) between minor versions, which means that it's difficult for
developers to keep up.
The JCR branch has nothing to do with this, really.
The API package does not mean that we lose any sense of the API hierarchy. We
can easily have
org.apache.jspwiki.api.acl
org.apache.jspwiki.api.plugin
org.apache.jspwiki.api.filter
If we choose to have so.
Having the interface in the same package as the concrete implementation has no
advantage with respect to protected members, since interfaces cannot have
members at all...
> Rename packages to "org.apache.jspwiki"
> ---------------------------------------
>
> Key: JSPWIKI-38
> URL: https://issues.apache.org/jira/browse/JSPWIKI-38
> Project: JSPWiki
> Issue Type: Task
> Reporter: Janne Jalkanen
> Assignee: Janne Jalkanen
> Fix For: 3.0
>
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
