You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Jukka Zitting (JIRA)" <ji...@apache.org> on 2009/01/15 14:58:59 UTC
[jira] Created: (JCR-1937) Automatic license header checking
Automatic license header checking
---------------------------------
Key: JCR-1937
URL: https://issues.apache.org/jira/browse/JCR-1937
Project: Jackrabbit Content Repository
Issue Type: Improvement
Components: maven
Reporter: Jukka Zitting
Priority: Minor
To avoid problems with incorrect license headers, we should include some automated header check in the Maven build and have Hudson run the check whenever changes are committed.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (JCR-1937) Automatic license header checking
Posted by "Jukka Zitting (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-1937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jukka Zitting updated JCR-1937:
-------------------------------
Attachment: rat.patch
The attached patch integrates the latest 0.6-SNAPSHOT version of the RAT Maven plugin to the Jackrabbit build.
I'll wait until there's an official 0.6 release of RAT before committing this.
> Automatic license header checking
> ---------------------------------
>
> Key: JCR-1937
> URL: https://issues.apache.org/jira/browse/JCR-1937
> Project: Jackrabbit Content Repository
> Issue Type: Improvement
> Components: maven
> Reporter: Jukka Zitting
> Priority: Minor
> Attachments: rat.patch
>
>
> To avoid problems with incorrect license headers, we should include some automated header check in the Maven build and have Hudson run the check whenever changes are committed.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (JCR-1937) Automatic license header checking
Posted by "Jukka Zitting (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-1937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jukka Zitting resolved JCR-1937.
--------------------------------
Resolution: Fixed
Fix Version/s: 1.6.0
Assignee: Jukka Zitting
Automatic header checks are now enabled both in trunk and the 1.x branch.
> Automatic license header checking
> ---------------------------------
>
> Key: JCR-1937
> URL: https://issues.apache.org/jira/browse/JCR-1937
> Project: Jackrabbit Content Repository
> Issue Type: Improvement
> Components: maven
> Reporter: Jukka Zitting
> Assignee: Jukka Zitting
> Priority: Minor
> Fix For: 1.6.0
>
> Attachments: rat.patch
>
>
> To avoid problems with incorrect license headers, we should include some automated header check in the Maven build and have Hudson run the check whenever changes are committed.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (JCR-1937) Automatic license header checking using
the Apache Rat Plugin
Posted by "Thomas Mueller (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-1937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Thomas Mueller updated JCR-1937:
--------------------------------
Summary: Automatic license header checking using the Apache Rat Plugin (was: Automatic license header checking)
> Automatic license header checking using the Apache Rat Plugin
> -------------------------------------------------------------
>
> Key: JCR-1937
> URL: https://issues.apache.org/jira/browse/JCR-1937
> Project: Jackrabbit Content Repository
> Issue Type: Improvement
> Components: maven
> Reporter: Jukka Zitting
> Assignee: Jukka Zitting
> Priority: Minor
> Fix For: 1.6.0
>
> Attachments: rat.patch
>
>
> To avoid problems with incorrect license headers, we should include some automated header check in the Maven build and have Hudson run the check whenever changes are committed.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.