[
https://issues.apache.org/jira/browse/WICKET-6855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17242161#comment-17242161
]
Martin Tzvetanov Grigorov commented on WICKET-6855:
---------------------------------------------------
At the moment I don't see value in this.
Do you have any potential users of this ?
What is the problem with the current classes ?
How the new wicket-api.jar will make it better ?
> Request: Provide separate wicket-api.jar for interfaces
> -------------------------------------------------------
>
> Key: WICKET-6855
> URL: https://issues.apache.org/jira/browse/WICKET-6855
> Project: Wicket
> Issue Type: Improvement
> Reporter: Matt Pavlovich
> Priority: Major
>
> Providing a separate wicket-api.jar would provide benefit for web application
> developers and web frameworks that are built on top of wicket by providing a
> clean separation of concerns.
> # All public interfaces into a org.apache.wicket.api.* package (IPage,
> IPanel, etc)
> # All internal interfaces into a org.apache.wicket.spi.* package (page
> stores, serializers, etc)
> This allows for a single-jar dependency for web framework and extension
> layers.
> Similar patterns followed in other open source projects:
> apache log4j2-api
> apache camel-api
> etc..
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
