[
https://issues.apache.org/jira/browse/WICKET-3976?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13088405#comment-13088405
]
Martin Grigorov commented on WICKET-3976:
-----------------------------------------
Everything works from user perspective.
>From Wicket developer perspective it is a bit cumbersome because the user
>application depends on o.a.w:wicket:jar but when you debug it and you change
>something in -util|-request|-core modules then the change is not visible to
>the IDE because the user app project depends on the "static" o.a.w:wicket.
To be easier for you you need to change the user app's pom.xml and depend on
wicket-core instead. Then both "mvn eclipse:eclipse" and M2E plugin link
Eclipse projects in the "dev friendly way" and all is fine.
What I don't like in unrolling this change is that we will deploy
-util,-request and -core together with wicket.jar and the users will be
confused again ... So it depends on us (the Wicket devs) - is it a big deal to
touch the user's app pom.xml before going to debug it? For me it is not a
problem. M2E deals quite easily with it even after the initial import. It just
something that I have to do once per application.
> 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
