[jira] [Commented] (DERBY-7050) In build.xml of derby root there's a vestigial target (+ patch)

["ASF subversion and git services (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/DERBY-7050?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16893271#comment-16893271 ] 

ASF subversion and git services commented on DERBY-7050:
--------------------------------------------------------

Commit 1863766 from Richard N. Hillegas in branch 'code/trunk'
[ https://svn.apache.org/r1863766 ]

DERBY-7050: Remove dead engine_169_opt target, a legacy of an old solution for small device support; commit patch submitted by Davide Grandi.

> In build.xml of derby root there's a vestigial target (+ patch)
> ---------------------------------------------------------------
>
>                 Key: DERBY-7050
>                 URL: https://issues.apache.org/jira/browse/DERBY-7050
>             Project: Derby
>          Issue Type: Improvement
>          Components: Build tools
>    Affects Versions: 10.15.1.3
>            Reporter: Davide Grandi
>            Priority: Trivial
>         Attachments: build-20190625.dot, build-20190625.pdf, build-expanded-20190625.dot, build-expanded-20190625.pdf, patch.txt
>
>
> In main build.xml, the one at the project's root, there's a target
>     engine_169_opt
> that executes an
>     <ant dir="${derby.engine.src.dir}" target="engine_169_opt"/>
> task, against
>     java\org.apache.derby.engine\build.xml
> that, in turn, DOESNT contain a engine_169_opt target, so it raises an error.
> No other build file (in fact, no other FILE in derby) contains an "engine_169_opt" string.
> So I think that target engine_169_opt in main build file can be safely removed.
> I'll attach (when possible)
>  # an svn diff file (the engine_169_opt target removal)
>  # and 2 maps (in dot and pdf format) of target relationships of build family files of Derby
> Best regards,
>     Davide Grandi



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)