openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Dick (JIRA)" <j...@apache.org>
Subject [jira] Commented: (OPENJPA-951) Javadoc jar file does not contain legal files
Date Tue, 03 Mar 2009 21:00:56 GMT

    [ https://issues.apache.org/jira/browse/OPENJPA-951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12678445#action_12678445
] 

Michael Dick commented on OPENJPA-951:
--------------------------------------

Hi David, I haven't tried the remote-resources-plugin yet.

Since the proper license files are already there in the "main" jar file I just unzipped it
from there into the javadoc location. Seemed to work for me, if it is a bit kludgy. 

If you can point me to an example with the maven-remote-resources-plugin I'm happy to take
look. 

> Javadoc jar file does not contain legal files
> ---------------------------------------------
>
>                 Key: OPENJPA-951
>                 URL: https://issues.apache.org/jira/browse/OPENJPA-951
>             Project: OpenJPA
>          Issue Type: Bug
>          Components: build / infrastructure
>    Affects Versions: 1.0.4, 1.2.1, 1.3.0, 2.0.0
>            Reporter: Michael Dick
>            Assignee: Michael Dick
>            Priority: Minor
>
> Donald's fix to use the ianal plugin revealed a problem in the javadoc plugin. The javadoc
plugin does not include elements from the 
> <resources> tags in pom.xml. The normal jar plugin and source plugin do include
these resources.
> As a result we have no legal files in the javadoc jar and we're failing the ianal check.
Quick browsing of the javadoc plugin mailing lists suggest a few workarounds for this problem
which I'll test during the 1.2.1 release. After the release I'll migrate the changes to the
other affected branches. 

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


Mime
View raw message