https://issues.apache.org/bugzilla/show_bug.cgi?id=50610
--- Comment #17 from Yegor Kozlov <[email protected]> 2011-02-19 01:14:43 EST --- Oops. There was an error in build.xml and antlib.xml was not included in the jar. That was the reason why neither of (2)-(4) did not work. Lines 47-50 should be <copy todir="${build.dir}/src"> <fileset dir="${resource.dir}"/> </copy> instead of <copy todir="${build.dir}"> <fileset dir="${resource.dir}"/> </copy> I created a branch in svn (https://svn.apache.org/repos/asf/poi/branches/excelant/) and ported the code from GitHub into it. Please check out, I would like further work to be done in POI svn, not in GitHub. Actually, we are nearly ready to merge this branch with trunk. ExcelAnt is included in the build cycle. The new build artifact is named poi-excelant. There are compile-excelant and test-excelant targets to compile / test only that module or you can do "ant compile" and "and test" to build everything. The "ant build" target builds distribution packages and poi-excelant is included. Please review, I'm going to include ExcelAnt in 3.8-beta which we plan in early March. Note that I added a new junuit test, see https://svn.apache.org/repos/asf/poi/branches/excelant/src/excelant/testcases/org/apache/poi/ss/excelant/TestBuildFile.java "pure java" junit tests are OK, but they are too low-level. It would be good to test against a real build file to ensure that the code works from Ant perspective. The test extends BuildFileTest.java. Most of Ant's internal tests are based on this class, I just followed the code patterns when I wrote my TestBuildFile.java Unfortunately BuildFileTest.java is in the test area and not included in the ant.jar, I had copy it from Ant's sources. Regards, Yegor -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
