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

Posted to commits@wicket.apache.org by "Martijn Dashorst (JIRA)" <ji...@apache.org> on 2010/09/22 11:24:32 UTC

[jira] Assigned: (WICKET-3071) Upgrade maven plugins and non-essential dependencies to newest version

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

Martijn Dashorst reassigned WICKET-3071:
----------------------------------------

    Assignee: Martijn Dashorst

> Upgrade maven plugins and non-essential dependencies to newest version
> ----------------------------------------------------------------------
>
>                 Key: WICKET-3071
>                 URL: https://issues.apache.org/jira/browse/WICKET-3071
>             Project: Wicket
>          Issue Type: Improvement
>    Affects Versions: 1.4.12
>            Reporter: Martijn Dashorst
>            Assignee: Martijn Dashorst
>             Fix For: 1.4.13, 1.5-M3
>
>
> Things like jetty and junit can easily be upgraded between x.y.z releases since they don't affect the API, but merely affect our build. Upgrading to the latest doesn't necessarily have benefits, other than not having to do it yourself for each quickstart that is generated.
> The maven plugins should use the newest versions, since a lot of crap can come from not using them. Running the build with maven 3 (due to be released soon) will uncover some issues, for example with multi-threaded builds.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.