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

Rick Hillegas updated DERBY-2573:
---------------------------------

    Attachment: derby-2573-14-aa-useAntExec.diff

Attaching derby-2573-14-aa-useAntExec.diff. It looks as though the 
builduserdocs target in the 10.8 branch was changed to use ant.bat instead of 
ant.exec. That probably makes the target work on Windows, but it breaks the 
build on my Mac. I am reverting the target to use ant.exec again so that I can 
build a release. We need to wrap some portability code around this difference 
so that we can build Derby releases on both platforms.


> Create master ant target for generating all release artifacts, including code 
> and doc artifacts
> -----------------------------------------------------------------------------------------------
>
>                 Key: DERBY-2573
>                 URL: https://issues.apache.org/jira/browse/DERBY-2573
>             Project: Derby
>          Issue Type: Improvement
>          Components: Build tools
>    Affects Versions: 10.3.1.4
>            Reporter: Rick Hillegas
>            Assignee: Rick Hillegas
>              Labels: releasegeneration
>             Fix For: 10.9.1.0
>
>         Attachments: DERBY-2573.diff_1notforcommit, 
> derby-2573-01-aa-masterTarget.diff, 
> derby-2573-02-aa-generateReleaseProperties.diff, 
> derby-2573-03-aa-propertyPrompt.diff, derby-2573-04-aa-emptyClient.diff, 
> derby-2573-05-aa-updateReleaseProperties.diff, 
> derby-2573-06-ab-docsClasspath.diff, derby-2573-07-aa-createBranch.diff, 
> derby-2573-08-aa-useReleaseVariablesInDocsBuild.diff, 
> derby-2573-09-aa-copySQLStateTableEarlier.diff, derby-2573-10-aa-notice.diff, 
> derby-2573-11-aa-signDebugArtifacts.diff, 
> derby-2573-12-aa-eclipse_ui_doc_plugin.diff, 
> derby-2573-13-aa-writePropertiesTarget.diff, derby-2573-14-aa-useAntExec.diff
>
>
> This is one of the tasks tracked by master JIRA DERBY-2571.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Reply via email to