[
https://issues.apache.org/jira/browse/WICKET-3976?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13088751#comment-13088751
]
Martin Grigorov commented on WICKET-3976:
-----------------------------------------
Another approach could be to revert o.a.w:wicket to be with type 'pom' and
depend on -core, -util, and -request. and the new (to be introduced)
o.a.w:wicket-osgi to shade -util, -request and -core into it. This way OSGi
users will have to deploy just wicket-osgi.jar bundle and be happy with it.
Currently using shaded o.a.w:wicket:jar makes debugging of -examples,
-extensions, ... also problematic because all they depend on wicket.jar and
making changes in -core in the IDE are not immediately reloaded (I need to
either tweak -examples' pom.xml to use -core temporarily or to repack
wicket.jar).
> Hide internal sub-modules from users by not deploying them in Maven
> repositories
> --------------------------------------------------------------------------------
>
> Key: WICKET-3976
> URL: https://issues.apache.org/jira/browse/WICKET-3976
> Project: Wicket
> Issue Type: Task
> Components: wicket
> Affects Versions: 1.5-RC5.1
> Reporter: Martin Grigorov
> Assignee: Martin Grigorov
> Priority: Minor
> Attachments: WICKET-3976.patch
>
>
> Creating this ticket in relation to the vote thread about OSGi integration
> http://markmail.org/thread/2iw5wjpn44m4grlx and
> http://markmail.org/thread/wdasrq4caft2spqj.
> The goal is to hide modules wicket-util, wicket-request and wicket-core from
> Wicket's users by not deploying them in Maven central repository.
> org.apache.wicket:wicket:jar module which will contain the classes from all
> these will be deployed instead.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
