You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Frank Bille Jensen (JIRA)" <ji...@apache.org> on 2007/03/31 08:50:25 UTC
[jira] Closed: (WICKET-182) Run RAT on all project releases
[ https://issues.apache.org/jira/browse/WICKET-182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Frank Bille Jensen closed WICKET-182.
-------------------------------------
Resolution: Fixed
> Run RAT on all project releases
> -------------------------------
>
> Key: WICKET-182
> URL: https://issues.apache.org/jira/browse/WICKET-182
> Project: Wicket
> Issue Type: Sub-task
> Components: wicket, wicket-auth-roles, wicket-examples, wicket-extensions, wicket-quickstart, wicket-spring
> Affects Versions: 1.3
> Reporter: Frank Bille Jensen
> Assigned To: Frank Bille Jensen
> Priority: Minor
> Fix For: 1.3
>
> Attachments: arat-1.3.log, wicket-auth-roles.rat.log, wicket-datetime.rat.log, wicket-examples.rat.log, wicket-extensions.rat.log, wicket-jmx.rat.log, wicket-parent.rat.log, wicket-quickstart.rat.log, wicket-spring.rat.log, wicket.rat.log
>
>
> The only RAT tool I know of is aRat (http://code.google.com/p/arat/).
> RAT should be run against a release and *not* the checked out sources from SVN. The procedure for building a release is:
> cd wicket-*
> mvn clean site assembly:assembly
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.