You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@harmony.apache.org by "Alexey Varlamov (JIRA)" <ji...@apache.org> on 2008/01/09 08:12:33 UTC
[jira] Updated: (HARMONY-5359) [drlvm][build] normalized ant build
system
[ https://issues.apache.org/jira/browse/HARMONY-5359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alexey Varlamov updated HARMONY-5359:
-------------------------------------
Attachment: build.zip
Updated the build with latest changes (r609932, r607816).
Please note, the build requires up-to-date working_classlib (not older than r607409).
> [drlvm][build] normalized ant build system
> ------------------------------------------
>
> Key: HARMONY-5359
> URL: https://issues.apache.org/jira/browse/HARMONY-5359
> Project: Harmony
> Issue Type: New Feature
> Components: build - test - ci, DRLVM
> Reporter: Alexey Varlamov
> Attachments: build.zip, build.zip
>
>
> Need to refactor DRLVM build system was stated since early ages of Harmony, due to its awkwardness and bad augmentability (one can find a lot of discussons in dev-list archives).
> Here is this long-expected feature, "normalized" ant build system, featuring:
> - improved portability, as it uses unified set of properties defined by classlib, drops "build.bat/build.sh" wrappers and provides traditional ant interface for users and external scripts;
> - better maintainability and robustness, as it does not rely on XSL build preprocessing, on-fly generated scripts and buggy ant-contrib features (except tests which really need "for" task);
> - much faster rebuild time even with cpptasks: void build takes only 7-8 sec (and can be improved a bit more). Also, it is possible to build standalone component w/o rebuilding dependencies which is also handy.
> - enhanced modularity and plugability: any component or test script can be used independently (modulo 2-3 shared ant files), simplifying component reusing or redeployment.
> For now, the system lacks facilities for managing external dependencies, it just relies on presence and layout of artifacts as retrieved via old build.
> The dependency management is to be refactored cross Harmony components, including classlib, drlvm and jdktools.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.