Github user joehni commented on the issue:
https://github.com/apache/commons-compress/pull/26
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
Github user joehni commented on the issue:
https://github.com/apache/commons-compress/pull/26
This is a Maven project and we follow Maven conventions. Anything that is
processed by a Java compiler belongs into src/main/java (true for
package-info.java files, not true for packageinfo
Github user joehni commented on the issue:
https://github.com/apache/commons-compress/pull/26
... and again we have a bunch of files that we have to modify for every
release.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user joehni commented on the issue:
https://github.com/apache/commons-text/pull/45
In Maven "verify" implies "test", since "verify" is a later step in the
Maven [build
lifecycle](http://maven.apache.org/guides/introduction/intr
