Summary: | You could enhance ant by "AOP" task,very useful in many place!!! | ||
---|---|---|---|
Product: | Ant | Reporter: | dengchaoming <dengchaoming> |
Component: | Core | Assignee: | Ant Notifications List <notifications> |
Status: | NEW --- | ||
Severity: | enhancement | Keywords: | PatchAvailable |
Priority: | P4 | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Hardware: | Other | ||
OS: | other | ||
Attachments: |
Source code for AOP task
Source code for AOP task |
Description
dengchaoming
2005-09-10 03:49:11 UTC
You can attach source to this bugrep if you want, but from your example above I, so far, have no idea what you're talking about. we dont yet use any "aspects" in ant, though there has been some thought in the past to use attributes in different namespaces, eg ant:failonerror="true" to control some parts of Ant's execution. for the particular problem you cite -iterative execution, I would use the Ant-contrib <for> and <foreach> commands, that explicitly do iteration Thank you very much for your answer,I download Ant-contrib and read it just now.I think it's better than my "AOP" task But I think this is another way that ant could become more powerful with "AOP",as this way could extend the function of old ant task but need't modify it's code. Ant is a very useful tool for me,I wish I could do something for it,^_^ I modify IntrospectionHelper.java and UnknownElement.java to support it Such as: IntrospectionHelper.java private NestedCreator getNestedCreator(){ ... //by dcming if(nc == null){ nc = createAopTask(project,parentUri,parent,elementName,child); } .... } I paste source code,you could search "dcming",then could find modified Created attachment 16384 [details]
Source code for AOP task
Created attachment 16385 [details]
Source code for AOP task
We are accustomed to (and much more appreciative of) code submissions made in the form of unified diffs so we can quickly see what modifications have been made. |