[
https://issues.apache.org/jira/browse/WICKET-6584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16605341#comment-16605341
]
Emond Papegaaij commented on WICKET-6584:
-----------------------------------------
If this works for OSGI, we should merge this. Wrt maven dependency resolution
it makes no difference.
For wicket 9 we should fix the cause of these problems: test classes in core
packages. IMHO we should move these classes to a new maven module and not
pollute our core packages with test related classes. A challenge might be a
circular dependency between wicket-core, wicket-tester and the tests in
wicket-core.
> Import Junit Package as optional
> --------------------------------
>
> Key: WICKET-6584
> URL: https://issues.apache.org/jira/browse/WICKET-6584
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 8.0.0
> Reporter: Subrahmanyam Sistha
> Priority: Critical
> Labels: pull-request-available
>
> Currently the wicket-core and the wicket-util bundle import junit packages,
> we should export packages as resolution:=optional
> Fix provided https://issues.apache.org/jira/browse/WICKET-6509 is not working
> as expected
>
> Refer :
> http://apache-wicket.1842946.n4.nabble.com/wicket-core-and-util-OSGI-wiring-problem-with-junit-framework-with-test-environment-td4680840.html
>
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
