You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Subrahmanyam Sistha (JIRA)" <ji...@apache.org> on 2018/08/31 10:25:01 UTC

[jira] [Commented] (WICKET-6509) Import junit packages as optional

    [ https://issues.apache.org/jira/browse/WICKET-6509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16598549#comment-16598549 ] 

Subrahmanyam Sistha commented on WICKET-6509:
---------------------------------------------

Issue not resolved yet, We are publishing wicket-core as bundle, Still getting issue with the junit.framework and org.junit

observed that, in the manifest file that are not reflected as resolution:=optional expected junit.framework;resolution:=optional

On further investigation observed that 

If we mention in wicket-core, pom.xml

 
<dependency>
   <groupId>junit</groupId>
   <artifactId>junit</artifactId>
   <!-- provided because of WicketTester -->
   <scope>provided</scope>
   <optional>true</optional>
</dependency>
It reflected as resolution:optional in the generated manifest file. 

 

 

 

 

 

> Import junit packages as optional
> ---------------------------------
>
>                 Key: WICKET-6509
>                 URL: https://issues.apache.org/jira/browse/WICKET-6509
>             Project: Wicket
>          Issue Type: Improvement
>          Components: wicket
>    Affects Versions: 8.0.0-M8
>            Reporter: Christoph Läubrich
>            Assignee: Martin Grigorov
>            Priority: Major
>             Fix For: 8.0.0-M9
>
>
> Currently the wicket-core and the wicket-util bundle import junit packages, I think they are not really required to run wicket but imported unintentionally.
> They could be excluded by adding !org.junit* to the maninifest header config section



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)