[
https://issues.apache.org/jira/browse/OPENJPA-951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12678369#action_12678369
]
David Jencks commented on OPENJPA-951:
--------------------------------------
In my experience using the maven-remote-resources-plugin gets the legal files
in both source and javadoc jars as well as the main artifact. I think all the
plugins have to be configured in a profile for this to work (e.g. mvn
source:jar doesn't run the m-r-r-p but mvn -Prelease does)
> 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.
