You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@wicket.apache.org by "Martin Grigorov (JIRA)" <ji...@apache.org> on 2017/04/27 20:16:04 UTC

[jira] [Resolved] (WICKET-6363) Do not use jetty-all but specific dependencies

     [ https://issues.apache.org/jira/browse/WICKET-6363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Martin Grigorov resolved WICKET-6363.
-------------------------------------
       Resolution: Fixed
    Fix Version/s: 8.0.0-M6

> Do not use jetty-all but specific dependencies
> ----------------------------------------------
>
>                 Key: WICKET-6363
>                 URL: https://issues.apache.org/jira/browse/WICKET-6363
>             Project: Wicket
>          Issue Type: Task
>          Components: wicket
>    Affects Versions: 8.0.0-M5
>            Reporter: Martin Grigorov
>            Assignee: Martin Grigorov
>            Priority: Minor
>             Fix For: 8.0.0-M6
>
>
> According to Jetty team member no one should use the Jetty aggregates jars as dependencies. They are meant to be used for Jetty's own documentation.
> All products/projects should depend on the fine-grained Jetty artifacts.
> See https://github.com/eclipse/jetty.project/issues/1502#issuecomment-297704299



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)