[
https://issues.apache.org/jira/browse/JDKIM-1?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefano Bagnara resolved JDKIM-1.
---------------------------------
Resolution: Fixed
Just added the test data to svn.
> Check with legal team if we can include Artistic License 1.0 licensed corpus
> from the Mail-DKIM perl project.
> -------------------------------------------------------------------------------------------------------------
>
> Key: JDKIM-1
> URL: https://issues.apache.org/jira/browse/JDKIM-1
> Project: JAMES jDKIM
> Issue Type: Task
> Components: library
> Affects Versions: 0.2
> Reporter: Stefano Bagnara
> Assignee: Stefano Bagnara
> Priority: Minor
> Fix For: 0.2
>
>
> I just wrote to legal-discuss:
> ------------
> I wrote a DKIM library (email authentication) in Java for the James
> project. Now I was expanding the test cases and found that the perl
> library named "Mail-DKIM" includes a good corpus of signed messages
> (http://search.cpan.org/dist/Mail-DKIM/). I'd like to add them "as is"
> in our test/resources folder so that they can be processed by a java
> tester class as part of the default tests.
> The library itself claims the license is the same of Perl 5.8.6, so it
> is the Artistic License 1.0:
> http://www.opensource.org/licenses/artistic-license-1.0.php
> From my understanding there should be no harm in redistributing this
> kind of "data" (they are email messages, mime messages, and not some
> language code) in apache packages, but I didn't find a clear answer on
> the website.
> So:
> 1) Are we allowed to include them in our src/test/resources folder
> (and in derivate distributed packages)?
> 2) If "yes": where am I supposed to write their "origin"/"license"?
> (NOTICE/LICENSE/README? In the root of cvs or the src/test/resources
> folder where I'll copy them?).
> ----------
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
