You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@ant.apache.org by Morten Sabroe Mortensen <mo...@gmail.com> on 2013/04/22 20:05:29 UTC
Anomalous package-info.java
I am very sorry to see all my "package-info.java" files being stamped with
the "anomalous package-info.java" statement from Ant and have javac
generate a lot of "Creating empty .../package-info.class".
While not being in a OSGi environment and not having annotations on
packages, I do not at all find it "anomalous" to have my JavaDoc
documentation written carefully in package-info.java files.
I have read the Ant manual under javac, last section. What is the rationale
behind forcing the generation of "empty" package-info.class files?
When my javac task generates pages of output about
package-info.class-creation and for no apparent reason, I get really
scared. Contrary to most programmers, I actually care to write JavaDoc and
at the vary least state the intended purpose and responsibility of packages.
To me, the current state of package-info.java-handling does not appear to
be sound at all. Is it sound?
Someone care to comment upon the subject?
Re: Anomalous package-info.java
Posted by Antoine Levy Lambert <an...@gmx.de>.
Hello Morten,
I am not aware of this problem.
How do you think that the behavior of ant's javac task should be changed ?
Should it have an option to exclude the package-info.java files ? or exclude them by default ?
Regards,
Antoine
On Apr 22, 2013, at 2:05 PM, Morten Sabroe Mortensen wrote:
> I am very sorry to see all my "package-info.java" files being stamped with
> the "anomalous package-info.java" statement from Ant and have javac
> generate a lot of "Creating empty .../package-info.class".
>
> While not being in a OSGi environment and not having annotations on
> packages, I do not at all find it "anomalous" to have my JavaDoc
> documentation written carefully in package-info.java files.
>
> I have read the Ant manual under javac, last section. What is the rationale
> behind forcing the generation of "empty" package-info.class files?
>
> When my javac task generates pages of output about
> package-info.class-creation and for no apparent reason, I get really
> scared. Contrary to most programmers, I actually care to write JavaDoc and
> at the vary least state the intended purpose and responsibility of packages.
>
> To me, the current state of package-info.java-handling does not appear to
> be sound at all. Is it sound?
>
> Someone care to comment upon the subject?
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@ant.apache.org
For additional commands, e-mail: user-help@ant.apache.org