[GitHub] commons-text issue #45: Added IBM Jdk8 build support to travis-ci configurat...
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/introduction-to-the-lifecycle.html#Build_Lifecycle_Basics). --- 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 infrastruct...@apache.org or file a JIRA ticket with INFRA. --- - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
[GitHub] commons-compress issue #26: COMPRESS-399 OSGI package versions are overly pe...
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 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 infrastruct...@apache.org or file a JIRA ticket with INFRA. --- - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
[GitHub] commons-compress issue #26: COMPRESS-399 OSGI package versions are overly pe...
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 files or package.html files). Anything else that should be collected in a jar file is a resource and belongs therefore into src/main/resources. The fact that you have to reconfigure the resources clearly demonstrates this. Nevertheless, these files will make our release process even more cumbersome if they are checked in as sources. The nature and content of the files identifies them clearly as something that can be generated. We might even be able to use the antrun plugin directly. If we put it into a profile and activate it based on file existence, we might even move it into commons-parent. --- 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 infrastruct...@apache.org or file a JIRA ticket with INFRA. --- - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
[GitHub] commons-compress issue #26: COMPRESS-399 OSGI package versions are overly pe...
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 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. --- 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 infrastruct...@apache.org or file a JIRA ticket with INFRA. --- - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
