[
https://issues.apache.org/jira/browse/WICKET-3976?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13088371#comment-13088371
]
Martin Grigorov edited comment on WICKET-3976 at 8/21/11 2:21 PM:
------------------------------------------------------------------
Hm, it is inconvenient for development of Wicket now ...
User applications now depend on o.a.w:wicket.jar and if I change something in
Wicket's code then I need to re-build wicket.jar to make the change visible to
the IDE.
A workaround is to configure the user application project to depend on -util,
-request and -core manually...
was (Author: mgrigorov):
Hm, it is inconvenient for development of Wicket now ...
User applications now depend on o.a.w:wicket.jar and if I change something in
Wicket's code then I need to re-build wicket.jar to make the change to the IDE.
A workaround is to configure the user application project to depend on -util,
-request and -core manually...
> 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-core
> 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
