Summary: | When running <javac> with <compilerarg line="proc:only"/> package-info.class files are still generated | ||
---|---|---|---|
Product: | Ant | Reporter: | jgeorgeson |
Component: | Core tasks | Assignee: | Ant Notifications List <notifications> |
Status: | NEW --- | ||
Severity: | normal | CC: | jglick |
Priority: | P2 | ||
Version: | 1.9.1 | ||
Target Milestone: | --- | ||
Hardware: | PC | ||
OS: | All |
Description
jgeorgeson
2013-02-19 18:57:57 UTC
Doesn't it work if you use createMissngPackageInfoClass="false"? I'm a bit reluctant to adding special handling for the proc flag when there may be other args that would also have an effect and createMissngPackageInfoClass has been introduced just for cases like yours. That option does work for us. When I searched the Ant manual I was looking for processor related options and completely glossed over this one. However I still think it would be nice to not have to specify both. The javac compiler invoked directly with -proc:only doesn't produce class files, so it's counter-intuitive to have to remember this individual case. Agreed with reporter that <javac> should try to follow CLI javac’s behavior unless there is a reason to differ. Well, my reason would be that we'd have to understand several compiler args by several compilers to ensure we do the right thing. That being said, I certainly won't block anybody who'd attempt to implement such logic ;-) |