[
https://issues.apache.org/jira/browse/SHINDIG-828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12662849#action_12662849
]
Henning Schmiedehausen commented on SHINDIG-828:
------------------------------------------------
To be honest, for me it has mainly cons, which has exactly to do with the
package-info.java convention (where would those go BTW, into "javadoc" or
"java"?). The package-info.java file can contain annotations for the package
itself which needs to be picked up by the compiler so you can't move these
files out (which is also the reason why it was renamed in 1.5 from package.html
to package-info.java; so that it can be treated as a java file, not an HTML
file).
The maven guys sometime went a bit overboard in their quest of imposing
conventions on arbitrary java code bases. :-) This is one of these things. In a
nutshell, my recommendation is: "Don't do it".
> Move all resources in a resources directory
> -------------------------------------------
>
> Key: SHINDIG-828
> URL: https://issues.apache.org/jira/browse/SHINDIG-828
> Project: Shindig
> Issue Type: Improvement
> Components: Gadget Rendering Server (Java), RESTful API (Java)
> Affects Versions: trunk
> Reporter: Vincent Siveton
> Fix For: trunk
>
> Attachments: java.zip, SHINDIG-828.diff
>
>
> Some Javadoc resources are in the src/main/java, should be in src/main/javadoc
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
