There has been no response to this email from anyone from Code Intelligence.

Unless there are objections from the Apache Commons Community my next step will be to submit a PR to have the following modules removed from oss-fuzz:

apache-commons-bcel
apache-commons-beanutils
apache-commons-cli
apache-commons-codec
apache-commons-collections
apache-commons-configuration
apache-commons-io
apache-commons-jxpath
apache-commons-lang
apache-commons-logging

Code Intelligence (or anyone else) will remain free to add them back in the right place - under apache-commons should they wish to do so.

Mark



On 19/10/2022 10:56, Mark Thomas wrote:
Hi,

You are receiving this email as you are currently configured as the recipients for oss-fuzz reports for Apache Commons JXPath.

As per the discussion on the Apache Commons dev list[1], please make the following configuration changes to the oss-fuzz integrations with immediate effect:

- Move all oss-fuzz integrations added for *ALL* Apache Commons
   components to the oss-fuzz module for Apache-Commons:

   https://github.com/google/oss-fuzz/tree/master/projects/apache-commons

   There should *NOT* be separate oss-fuzz modules for each component


- Add the Google account for "secur...@commons.apache.org" to
   - the notifications for these issues
   - the ACL to enable this account to access the details for each report


Please notify dev@commons.apache.org and secur...@commons.apache.org when these changes have been completed.

Thanks,

Mark



[1]  https://lists.apache.org/thread/53vwy3g8w3f8nydz7jvxm8snrqx7msln

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

Reply via email to