db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rick Hillegas (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-5462) ant release needs to accommodate for different ant executables on different systems
Date Thu, 13 Oct 2011 19:03:12 GMT

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

Rick Hillegas commented on DERBY-5462:
--------------------------------------

Hi Myrna,

Can you explain what is breaking for you? I see one instance of the ant executable being invoked
(in the master build file in the "builduserdocs" target). I think that ant is invoked as an
executable in order to guarantee the following:

1) enough memory must be given to the JVM to build the docs (the full docs build is a pig)

2) fop.jar needs to be on the classpath in order to build the docs

It may be possible to make the master "release" target fail early if these conditions are
not met. Then we may be able to just use the ordinary <ant> task instead of the <exec>
task for the docs build.

Thanks,
-Rick
                
> ant release needs to accommodate for different ant executables on different systems
> -----------------------------------------------------------------------------------
>
>                 Key: DERBY-5462
>                 URL: https://issues.apache.org/jira/browse/DERBY-5462
>             Project: Derby
>          Issue Type: Improvement
>          Components: Build tools
>    Affects Versions: 10.8.2.3, 10.9.0.0
>            Reporter: Myrna van Lunteren
>            Priority: Trivial
>
> The ant release target will call ant to build the classes, jars, and docs. However, the
ant executable is different when running this on a windows OS vs. Unix. So the target should
either figure out the correct name of the executable, or prompt for it.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message