You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@harmony.apache.org by "Tim Ellison (JIRA)" <ji...@apache.org> on 2006/05/09 09:53:22 UTC
[jira] Closed: (HARMONY-439) java build improvements - delegation
to modules
[ http://issues.apache.org/jira/browse/HARMONY-439?page=all ]
Tim Ellison closed HARMONY-439:
-------------------------------
Verified by Mark.
> java build improvements - delegation to modules
> -----------------------------------------------
>
> Key: HARMONY-439
> URL: http://issues.apache.org/jira/browse/HARMONY-439
> Project: Harmony
> Type: Improvement
> Components: Classlib
> Reporter: Mark Hindess
> Assignee: Tim Ellison
> Priority: Minor
> Attachments: 01.delegate.build.to.modules.sh, 01.stub.jars.moves.sh, 02.delegate.build.to.modules.diff, 02.stub.jars.changes.diff, logging.properties.copied.twice.diff
>
> There are a couple of issues that could be tidied up:
> 1) Currently we build java code into both 'build' and 'modules/*/bin/main' - we might avoid problems if we always built code to 'build'. This also means we build everything twice ... once into 'build' then again into 'modules/*/bin/main' when the tests are run.
> 2) We build jars in two places 'make/build-java.xml' and 'modules/*/make/common/build.xml' - HARMONY-431 is proof that this is a bad idea.
> 3) To make matters worse 'make/build-java.xml' builds the jars to a location under 'build' where as the module build creates straight into 'deploy'.
> I suggest fixing these issues by delegating the building of the jars to the module ant files and to always build the code to the top-level 'build' directory.
> I will submit a patch shortly.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira