You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Igor Vaynberg (JIRA)" <ji...@apache.org> on 2009/02/09 08:42:59 UTC

[jira] Resolved: (WICKET-2088) ApacheLicenceHeaderTests fail after projects' metadata created by Eclipse

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

Igor Vaynberg resolved WICKET-2088.
-----------------------------------

    Resolution: Fixed
      Assignee: Igor Vaynberg

> ApacheLicenceHeaderTests fail after projects' metadata created by Eclipse
> -------------------------------------------------------------------------
>
>                 Key: WICKET-2088
>                 URL: https://issues.apache.org/jira/browse/WICKET-2088
>             Project: Wicket
>          Issue Type: Bug
>    Affects Versions: 1.4-RC2
>            Reporter: Dominik Drzewiecki
>            Assignee: Igor Vaynberg
>            Priority: Minor
>             Fix For: 1.4-RC3
>
>         Attachments: wicket-parent.patch
>
>
> Wicket and all it's accompanying projects when being worked on in Eclipse tend to fail several ApacheLicenceHeaderTest as it is an IDE that creates .settings directory containing several  xml projects' metadata files. There are 6 solutions:
> 1. don't use eclipse
> 2. skip tests entirely (-Dmaven.test.skip=true passed on the CLI when invoking maven)
> 3. skip running the tests (-DskipTests)
> 4. compile & run but ignore tests failures (-Dmaven.test.failure.ignore=true)
> 5. Modify the ApacheLicenceHeaderTests so that the xml files in the .settings directories are ignored
> IMHO, having considered all pros and cons, only 5. is a an option. As there already is an Eclipse originating .xml file that gets ignored I hope that you don't mind going this way. The patch to follow shortly.

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