From issues-return-169290-archive-asf-public=cust-asf.ponee.io@maven.apache.org Thu Jul 2 09:34:24 2020 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [207.244.88.153]) by mx-eu-01.ponee.io (Postfix) with SMTP id C065918037A for ; Thu, 2 Jul 2020 11:34:23 +0200 (CEST) Received: (qmail 20284 invoked by uid 500); 2 Jul 2020 09:34:23 -0000 Mailing-List: contact issues-help@maven.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@maven.apache.org Delivered-To: mailing list issues@maven.apache.org Received: (qmail 20272 invoked by uid 99); 2 Jul 2020 09:34:23 -0000 Received: from ec2-52-202-80-70.compute-1.amazonaws.com (HELO gitbox.apache.org) (52.202.80.70) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 02 Jul 2020 09:34:23 +0000 From: =?utf-8?q?GitBox?= To: issues@maven.apache.org Subject: =?utf-8?q?=5BGitHub=5D_=5Bmaven-dependency-analyzer=5D_adangel_opened_a_new_?= =?utf-8?q?pull_request_=2311=3A_=5BMSHARED-870=5D_-_Upgrade_asm_to_8=2E0=2E?= =?utf-8?q?1?= Message-ID: Date: Thu, 02 Jul 2020 09:34:22 -0000 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit adangel opened a new pull request #11: URL: https://github.com/apache/maven-dependency-analyzer/pull/11 Upgrades again from 8.0.0 -> 8.0.1 Also uses the new Opcodes constant, so that the new features can actually be used. Note: we could go to ASM9_EXPERIMENTAL to support class files with preview features as well. Note2: I'm reusing MSHARED-870, since maven-dependency-analyzer 1.1.2 is not released yet. I'll reopen that issue. Following this checklist to help us incorporate your contribution quickly and easily: - [x] Make sure there is a [JIRA issue](https://issues.apache.org/jira/browse/MSHARED) filed for the change (usually before you start working on it). Trivial changes like typos do not require a JIRA issue. Your pull request should address just this issue, without pulling in other changes. Also be sure having selected the correct component. - [x] Each commit in the pull request should have a meaningful subject line and body. - [x] Format the pull request title like `[MSHARED-XXX] - Fixes bug in ApproximateQuantiles`, where you replace `MSHARED-XXX` with the appropriate JIRA issue. Best practice is to use the JIRA issue title in the pull request title and in the first line of the commit message. - [x] Write a pull request description that is detailed enough to understand what the pull request does, how, and why. - [x] Run `mvn clean verify` to make sure basic checks pass. A more thorough check will be performed on your pull request automatically. - [x] You have run the integration tests successfully (`mvn -Prun-its clean verify`). If your pull request is about ~20 lines of code you don't need to sign an [Individual Contributor License Agreement](https://www.apache.org/licenses/icla.pdf) if you are unsure please ask on the developers list. To make clear that you license your contribution under the [Apache License Version 2.0, January 2004](http://www.apache.org/licenses/LICENSE-2.0) you have to acknowledge this by using the following check-box. - [ ] I hereby declare this contribution to be licenced under the [Apache License Version 2.0, January 2004](http://www.apache.org/licenses/LICENSE-2.0) - [x] In any other case, please file an [Apache Individual Contributor License Agreement](https://www.apache.org/licenses/icla.pdf). ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: users@infra.apache.org