I'm checking out your plugin now. Its looking pretty good, but I've found the following nits:
The install instructions need a lot more detail. I had to import the three plugin .java files to the IDE, and the rest of the VAJ*.java files, then export them to the ide/tools/org-apache-tools-ant directory. The file vajanttool.ini doesn't exist. The default.ini file was in the doc directory and had to be copied over to the org-apache-tools-ant directory. The gui only shows you targets that have descriptions. The logger doesn't trap System.out, so echo messages go to the Console, not the log window. That's the result of my quick $0.10 tour. As to where it should go, I'm not sure. For the moment, I'd say leave them where they are. Glenn McAllister Software Developer. IBM Toronto Lab, (416) 448-3805 "An approximate answer to the right question is better than the right answer to the wrong question." - John W. Tukey Please respond to [EMAIL PROTECTED] To: "'[EMAIL PROTECTED]'" <[EMAIL PROTECTED]> cc: Subject: [submit] Integration of Ant into Visual Age for Java A colleague (Christoph Wilhelms) and me wrote a small PlugIn for Visual Age for Java, which exploits the VAJ Tool API to integrate Ant into this IDE. Our tool contains a small GUI which is not meant to compete with Antidote: - it provides only very restricted functionality (selecting a build file and a target, starting the build) - it is written with AWT to get it running on VAJ 3.02 (JDK1.1 based) and 3.5 (Java2 based) The zip file attached contains the source code, a small documentation, and a configuration file for the VAJ integration. I'm not sure where the files should go: on the one hand they don't really belong to ..taskdefs.optional.ide (where they are at the moment), because it isn't a task. OTOH it doesn't seem worth it to create a new root for them as for Antidote. The tool runs fine here, but the installation instructions aren't tested yet and probably not detailed enough. Feedback is appreciated! Wolf
