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 "ASF subversion and git services (Jira)" <ji...@apache.org> on 2020/01/12 19:25:00 UTC
[jira] [Commented] (DERBY-7050) In build.xml of derby root there's
a vestigial target (+ patch)
[ https://issues.apache.org/jira/browse/DERBY-7050?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17013861#comment-17013861 ]
ASF subversion and git services commented on DERBY-7050:
--------------------------------------------------------
Commit 1872686 from Richard N. Hillegas in branch 'code/branches/10.15'
[ https://svn.apache.org/r1872686 ]
DERBY-7050: Port 1863766 from trunk to 10.15 branch.
> 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
(v8.3.4#803005)