Mailing-List: contact users-help@groovy.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@groovy.apache.org
Subject: Re: GMavenPlus compiles stubs
To: users@groovy.apache.org
References: <5C676E6359909E478C7B811BDB48CA35613416@CWWAPP478.windstream.com>
From: Jochen Theodorou <blackdrag@gmx.org>
Message-ID: <583376C8.7090101@gmx.org>
Date: Mon, 21 Nov 2016 23:35:52 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101
 Thunderbird/38.4.0
MIME-Version: 1.0
In-Reply-To: <5C676E6359909E478C7B811BDB48CA35613416@CWWAPP478.windstream.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
archived-at: Mon, 21 Nov 2016 22:36:06 -0000

On 21.11.2016 23:08, Winnebeck, Jason wrote:
> I recently encountered an error from javac compiling a stub that was
> otherwise valid from Groovy itself when I enabled generate-stubs task. I
> resolved the error properly, but I wonder, should javac be compiling
> stubs when using gmavenplus?

afaik no

> I thought it just referred to them but did
> not compile them. If its compiling the stubs, am I at risk of having
> the stub replace the Groovy-generated code in the final jar?

since groovy compilation happens after the groovy compiler will 
overwrite those classes. So no danger from that front

bye Jochen