This check and more is easily automatable with Apache RAT. The
relevant configuration from Shiro's parent pom:
<plugin>
<groupId>org.apache.rat</groupId>
<artifactId>apache-rat-plugin</artifactId>
<version>0.7</version>
<configuration>
<!-- note that this configuration needs to be
maintain both in pluginManagement and reporting sections -->
<excludes>
<exclude>README-runtime-requirements.txt</exclude>
<exclude>**/.externalToolBuilders/*</exclude>
<!-- Apparently some test in
samples/spring-client generates velocity log - would be better to
reconfigure to output to target/ -->
<exclude>velocity.log</exclude>
</excludes>
</configuration>
</plugin>
Kalle
On Sat, Oct 2, 2010 at 8:37 AM, Ulrich Stärk <[email protected]> wrote:
> Ulrich Stärk: +1 (binding)
>
> Tapestry-beanvalidator, tapestry-func, tapestry-jmx and tapestry-json are
> all missing the NOTICE and LICENSE files. They were probably also not there
> in previous releases, I just didn't notice. I don't think we have to cancel
> the vote, just rebuild the artifacts with the proper files in place.
> Everything else looks OK to me.
>
> Cheers,
>
> Uli
>
> On 29.09.2010 19:15, Howard Lewis Ship wrote:
>>
>> I've created and uploaded a release of Tapestry 5.2.1, ready to be
>> voted upon.
>>
>> The binary and source downloads are uploaded to:
>>
>> http://people.apache.org/~XXX/tapestry-releases/
>>
>> and the Maven artifacts staged to:
>>
>>
>> https://repository.apache.org/content/repositories/orgapachetapestry-024/org/apache/tapestry/
>>
>> Please examine these files to determine if the new release, 5.2.1, is
>> ready and of BETA quality.
>>
>> I've also created a 5.2.1. tag in Subversion:
>>
>> http://svn.apache.org/viewvc/tapestry/tapestry5/tags/releases/5.2.1/
>>
>> On a successful vote, I'll move the files from these directories to
>> the proper distribution directories and update the Tapestry site
>> documentation to indicate
>> the availability of the release, and its beta status.
>>
>> Vote will run for three days; on success I'll move the voted artifacts
>> into place and send out appropriate notifications.
>>
>>
>> Howard M. Lewis Ship: +1 (binding)
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
