You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Martin Tzvetanov Grigorov (Jira)" <ji...@apache.org> on 2020/12/02 08:35:00 UTC
[jira] [Updated] (WICKET-6855) Request: Provide separate
wicket-api.jar for interfaces
[ https://issues.apache.org/jira/browse/WICKET-6855?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Martin Tzvetanov Grigorov updated WICKET-6855:
----------------------------------------------
Priority: Minor (was: Major)
> 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: Minor
>
> 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)