commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From sesuncedu <>
Subject [GitHub] commons-compress issue #26: COMPRESS-399 OSGI package versions are overly pe...
Date Sat, 03 Jun 2017 00:22:24 GMT
Github user sesuncedu commented on the issue:
    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, which puts a
    Class Retention annotation on the packages package-info.class.
    (Requires provided / compileOnly dependency on the osgi annotation bundle).
    On Fri, Jun 2, 2017 at 6:11 PM, Jörg Schaible <>
    > 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
    > <>,
    > or mute the thread
    > <>
    > .

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 or file a JIRA ticket
with INFRA.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message