[
https://issues.apache.org/jira/browse/WICKET-3976?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13088350#comment-13088350
]
Martin Grigorov commented on WICKET-3976:
-----------------------------------------
For the other devs with Eclipse+M2E plugin: I needed to close/remove the
project for o.a.w:wicket in Eclipse, otherwise M2E tries to resolve the
dependency in the projects and it fails. Closing it makes M2E to look for the
dependency in ~/.m2/repository/** and then it works.
> 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
