[
https://issues.apache.org/jira/browse/JSPWIKI-38?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12658738#action_12658738
]
Andrew Jaquith commented on JSPWIKI-38:
---------------------------------------
Craig: good to know what our constraints are with respect to naming. Sounds
like you agree 2 jars is the right solution: 1 for the API and one for the
private implementation.
If both public APIs and "private" implementation code *must* be under the
org.apache namespace, then I am not sure that it makes a lot of sense to have
both a .jspwiki package and a .wiki package (for example).
However, what I do *not* want is to have the package that the general public
uses to be four levels deep. Having developers needing to use
org.apache.jspwiki.api just sounds wrong to me. This is *my* non-starter.
If anything, I'd prefer to invert things, so that the public API namespace is
org.apache.jspwiki, and the private namespace is off of that:
org.apache.jspwiki.private. We could put 'em in different source folders too,
so that IDE developers (basically, just about everyone) have clearly delineated
working areas.
Perfect? No. But if all top-level options other than org.apache are closed off
to us, then this may be the best we can do, while still accomplishing the
desired separation between public APIs and private implementations.
Janne, what do you think?
> 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.
