[
https://issues.apache.org/jira/browse/MAPREDUCE-1038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Douglas updated MAPREDUCE-1038:
-------------------------------------
Attachment: M1038-1.patch
{noformat}
ant test -Dtestcase=TestConfiguration # Observe that weaving does not occur.
touch src/java/org/apache/hadoop/mapred/JobClient.java # "change" a MapReduce
file
ant test -Dtestcase=TestConfiguration # Observe that weaving does not occur.
{noformat}
I don't think Hudson runs a clean before testing the patched build. This means
that the Mumak tests would be run against the trunk version, rather than the
patched version.
The aspects *should* be re-weaved if the core classes are modified.
> Mumak's compile-aspects target weaves aspects even though there are no
> changes to the Mumak's sources
> -----------------------------------------------------------------------------------------------------
>
> Key: MAPREDUCE-1038
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-1038
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: build
> Affects Versions: 0.21.0
> Reporter: Vinod K V
> Assignee: Aaron Kimball
> Fix For: 0.21.0
>
> Attachments: M1038-1.patch, MAPREDUCE-1038.patch
>
>
> This is particularly time consuming and is the bottle neck even for a simple
> ant build. In the case where no files have been updated in Mumak, there is no
> reason to recompile sources along with the aspects. compile-aspects should
> skip this step in these cases.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
