You are viewing a plain text version of this content. The canonical link for it is here.

Posted to derby-dev@db.apache.org by "Rick Hillegas (JIRA)" <ji...@apache.org> on 2018/11/29 01:52:00 UTC

[jira] [Resolved] (DERBY-7020) Fix release targets to account for modularization changes

     [ https://issues.apache.org/jira/browse/DERBY-7020?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rick Hillegas resolved DERBY-7020.
----------------------------------
       Resolution: Fixed
    Fix Version/s: 10.15.0.0

Resolving because I don't know of any more work to do on this issue. Of course, more patches may be applied if we discover other loose ends.

> 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
>             Fix For: 10.15.0.0
>
>         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)