[
https://issues.apache.org/jira/browse/DERBY-7020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16702185#comment-16702185
]
ASF subversion and git services commented on DERBY-7020:
--------------------------------------------------------
Commit 1847661 from [email protected] in branch 'code/trunk'
[ https://svn.apache.org/r1847661 ]
DERBY-7020: Make the release machinery pick up the current min.version value so
that the generated user docs will report the correct minimum JDK version;
commit derby-7020-02-aa-fixMinJDKVersionInDocs.diff.
> Fix release targets to account for modularization changes
> ---------------------------------------------------------
>
> Key: DERBY-7020
> URL: https://issues.apache.org/jira/browse/DERBY-7020
> Project: Derby
> Issue Type: Bug
> Components: Build tools
> Affects Versions: 10.15.0.0
> Reporter: Rick Hillegas
> Assignee: Rick Hillegas
> Priority: Major
> Attachments: derby-7020-01-ab-updateReleaseMachinery.diff,
> derby-7020-02-aa-fixMinJDKVersionInDocs.diff
>
>
> Modularization has introduced a new jar file (derbyshared.jar) and some new
> template policies. We should make sure that all of these assets end up in the
> release distributions. The maven publishing logic will need to be adjusted to
> handle derbyshared.jar.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
