[jira] Commented: (MAPREDUCE-1038) Mumak's compile-aspects target weaves aspects even though there are no changes to the Mumak's sources

["Hudson (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/MAPREDUCE-1038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12772939#action_12772939 ] 

Hudson commented on MAPREDUCE-1038:
-----------------------------------

Integrated in Hadoop-Mapreduce-trunk-Commit #105 (See [http://hudson.zones.apache.org/hudson/job/Hadoop-Mapreduce-trunk-Commit/105/])
    . Weave Mumak aspects only if related files have changed.
Contributed by Aaron Kimball


> 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.