{"id":1522,"date":"2008-01-29T16:23:00","date_gmt":"2008-01-29T16:23:00","guid":{"rendered":"http:\/\/gleamynode.net\/articles\/1522\/ant2eclipse-converts-ant-buildxml-into-eclipse-classpath"},"modified":"2022-12-28T01:46:22","modified_gmt":"2022-12-27T16:46:22","slug":"ant2eclipse-converts-ant-build-xml-into-eclipse-classpath","status":"publish","type":"post","link":"https:\/\/vault.motd.kr\/wordpress\/posts\/1522\/ant2eclipse-converts-ant-build-xml-into-eclipse-classpath\/","title":{"rendered":"ant2eclipse – Converts Ant build.xml into Eclipse .classpath"},"content":{"rendered":"
Update: ant2eclipse has been deprecated by Ant2IDE<\/a>. Please use Ant2IDE instead. Update: ant2eclipse has been deprecated by Ant2IDE. Please use Ant2IDE instead. I wrote a simple shell script called ‘ant2eclipse‘. It runs your ant build file with -v switch, gathers essential information such as source path, its output patch and the JAR path that the project depends on, and generates or updates Eclipse .classpath file. More… Continue reading
\nI wrote a simple shell script called ‘ant2eclipse<\/tt>‘. It runs your ant build file with -v<\/tt> switch, gathers essential information such as source path, its output patch and the JAR<\/span> path that the project depends on, and generates or updates Eclipse .classpath<\/tt> file.
\nMore graceful solution would be to inject some byte code to key Ant tasks such as javac<\/tt> to gather various path information. It shouldn\u2019t be that difficult, but I\u2019m just OK with this simple script. Please feel free to download and modify to meet your need.
\nThis script was tested against the JBoss Remoting<\/a>, version 3, so there\u2019s no guarantee that it will work for other projects. Use at your own risk. \ud83d\ude09<\/p>\n","protected":false},"excerpt":{"rendered":"