DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=29978>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=29978 ------- Additional Comments From [EMAIL PROTECTED] 2005-04-12 01:05 ------- (In reply to comment #19) > I discovered some problems/bugs that are probably linked to > changes in the brand new JDK 1.5.0_02. I think I manged to fix one > problem but have another problem (see 2 below) that I hope someone can > help with. Apt has a -classpath option which it uses to find user class files AND Annotation Processor Factories. each processor factory must extend that class that is not being found, I suspect the error occurs when loading factories. I suspect your problems is that although tools.jar is on the classpath that apt is executing against, it is NOT on the classpath passed as an option in the simulated command line in the process method(). Change your ant task to put tools.jar on ant's classpath argument and it should work. I got caught out by the programmatic interface change as well. Just a comment, JSR-269 is looking at defining a pluggable annotation processing API, both a mirror, and processing mechanism. So apt is really just a temporary tool, and I suspect mustang (JDK6.0) will have the reference implementation for JSR-269. I am not sure if that reference implementation will be called apt or not. It will be different is some ways. Given this probable change, maybe the official ant task should wait till things have settled down somewhat, that is, till the JSR- 269 reference implementation is at least available in the mustang betas. I am on the 269 EG, but we haven't looked at what the RI might look like yet. I'll endeavour to offer guidance here as best I can given the theoretical secrecy of EG proceedings which in practice don't seem to be all that secret under JCP2.6. How far off is the next ant release that might incorporate this task? I can't say when 269 will have an RI in beta. I am happy to answer questions wrt deploying the ant task. At the moment it might be best to rename the task to something like tiger-apt, to keep the "apt" namespace clear for whatever the RI for JSR-269 is called, given that even if apt is still called apt in mustang, it will be a different beast, and might need to be a different ant task. Bruce -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
