Github user sesuncedu commented on the issue:
https://github.com/apache/commons-compress/pull/26
The packageinfo files are in the source tree because they're source files,
and provide metadata for the package.
You can also use a package annotation on package-info.java, which puts a
Class Retention annotation on the packages package-info.class.
Examples:
https://github.com/apache/felix/blob/trunk/dependencymanager/org.apache.felix.dependencymanager.annotation/src/org/apache/felix/dm/annotation/api/packageinfo
https://github.com/apache/felix/blob/trunk/converter/
converter/src/main/java/org/apache/felix/converter/dto/package-info.java
(Requires provided / compileOnly dependency on the osgi annotation bundle).
On Fri, Jun 2, 2017 at 6:11 PM, Jörg Schaible <[email protected]>
wrote:
> Why are those packageinfo files in src/main/java instead of
> src/main/resources as it is common in Maven builds? Now you have to
> configure explicitly these files as resources. On top of it, I don't like
> the idea of modifying these files for each release manually. I'd look for
a
> solution that generates these files automatically into
> target/generated-resources. Such a plugin should not be difficult.
>
> â
> You are receiving this because you authored the thread.
> Reply to this email directly, view it on GitHub
>
<https://github.com/apache/commons-compress/pull/26#issuecomment-305920965>,
> or mute the thread
>
<https://github.com/notifications/unsubscribe-auth/AAZIGza5aeOCDCCwJhvZ1jufn0jZ7BkWks5sAIitgaJpZM4NukX5>
> .
>
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
