DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14353>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14353 publish ant model to ease IDE integration Summary: publish ant model to ease IDE integration Product: Ant Version: 2.0 spec Platform: All OS/Version: All Status: NEW Severity: Enhancement Priority: Other Component: Core AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] CC: [EMAIL PROTECTED] Hello everybody! I'm currently using ant as a command-line utility and as Eclipse Plugin. The command line version I can use is always the last one, but the integrated IDE version seem to be some version older. :( Clearly the IDE's team must re-code and re-test the news in the IDE-idioms, and this can take time. The same drawback affect netbeans and every one who make an ant wrapper. Thinking in 'meta'... Probably a standard xml ant descriptor file deployed with its ant implementation can help a wrapper to dynamically or statically discovers about ant features and exposes the ant-functionality in a wrapper-defined fashion. If the xml file does not address other problems, ant can make available a public API to discover its feature in a standard mode, so I think always in 'XML mode'. The plug-in capability about ant can be kept unviolated because this API can work together as an enhanchement more like a service. I think that a specific API call can analize the 'ant-environment' and produce the xml descriptor; the wrapper read and analize that file and the game is over. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
