Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 40848200CC2 for ; Wed, 21 Jun 2017 04:26:04 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 3F3D7160BF5; Wed, 21 Jun 2017 02:26:04 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 8CF83160BE1 for ; Wed, 21 Jun 2017 04:26:03 +0200 (CEST) Received: (qmail 82508 invoked by uid 500); 21 Jun 2017 02:26:02 -0000 Mailing-List: contact notifications-help@groovy.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@groovy.apache.org Delivered-To: mailing list notifications@groovy.apache.org Received: (qmail 82488 invoked by uid 99); 21 Jun 2017 02:26:02 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 21 Jun 2017 02:26:02 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id A18F7C9D61 for ; Wed, 21 Jun 2017 02:26:01 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -100.002 X-Spam-Level: X-Spam-Status: No, score=-100.002 tagged_above=-999 required=6.31 tests=[RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id 4BDw8ou2gU38 for ; Wed, 21 Jun 2017 02:26:01 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id BC9C45F2F1 for ; Wed, 21 Jun 2017 02:26:00 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 5EA90E0BB3 for ; Wed, 21 Jun 2017 02:26:00 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 17E00240BB for ; Wed, 21 Jun 2017 02:26:00 +0000 (UTC) Date: Wed, 21 Jun 2017 02:26:00 +0000 (UTC) From: "Paul King (JIRA)" To: notifications@groovy.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Resolved] (GROOVY-8095) Provide logging for bytecode generation MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Wed, 21 Jun 2017 02:26:04 -0000 [ https://issues.apache.org/jira/browse/GROOVY-8095?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul King resolved GROOVY-8095. ------------------------------- Resolution: Fixed > Provide logging for bytecode generation > --------------------------------------- > > Key: GROOVY-8095 > URL: https://issues.apache.org/jira/browse/GROOVY-8095 > Project: Groovy > Issue Type: New Feature > Reporter: Daniel Sun > Assignee: Daniel Sun > Priority: Minor > Fix For: 2.5.0-beta-2 > > > Debugging bytecode issues is a hard work, one of reason is lack of logging. > LoggableClassVisitor and LoggableTextifier can make debugging easy. We can debug step by step and investigate bytecode generation line by line. Logging bytecode generation can be enabled by -Dgroovy.log.classgen=true -- This message was sent by Atlassian JIRA (v6.4.14#64029)