Was there a Jira issue for this yet?
Thanks, Paul.
On Mon, Sep 3, 2018 at 10:33 PM Keegan Witt wrote:
> I'm working on adding Java 9, 10, and 11 bytecodes to the 2.5 branch, and
> 9, 10, and 11 bytecodes when using invokedynamic to master, when I noticed
> we allow the targets to go back quite
Thinking further along that line: A possible Groovy way to solve this might be
through an annotation combined with explicit (G)String literal syntax varieties:
@GStringLiteralToString(true)class Goo { String doGood0(final o) { def s0 =
"o=$o" // s0 is String def gs0 = G"o=$o" // G"..." =>
Those sound like great additions but I don't want to wait too long since
some of the fixes are important to get out soon. We'll no doubt have a
2.5.4 in another month for anything you don't get done.
Cheers, Paul.
On Wed, Sep 12, 2018 at 8:32 PM Remko Popma wrote:
> Thanks for the heads up.
Gotcha! :-)
On Thu, Sep 13, 2018 at 9:57 AM Remko Popma wrote:
> Sorry for being unclear. I didn’t mean to hold up the release. I meant to
> say that for 2.5.3 I may not be able to do more than updating the picocli
> dependency.
>
> I’ll start a separate email thread to discuss potential new
Sorry for being unclear. I didn’t mean to hold up the release. I meant to say
that for 2.5.3 I may not be able to do more than updating the picocli
dependency.
I’ll start a separate email thread to discuss potential new features in
CliBuilder.
Remko
> On Sep 13, 2018, at 6:00, Paul King
But do they expect GString to be immutable, or do they expect a GString literal
to return a String instance (ie for toString() being called implicitely on it) ?
I would expect the latter. At least I was not aware that the Groovy "GString
concept" is actually based on a GString class when I
I've decided to just leave the old bytecode targets alone for now. I
created https://issues.apache.org/jira/browse/GROOVY-8783 for the addition
of the new bytecode targets.
On Wed, Sep 12, 2018 at 5:16 AM Paul King wrote:
> Was there a Jira issue for this yet?
>
> Thanks, Paul.
>
> On Mon, Sep
I do remember experiencing a similar problem at some point while working on the
unit tests.
I don’t remember how it got resolved. Could it be an environmental issue?
Maybe other people on this list have also seen this issue and can shed some
light? (I think it’s a general Groovy question, not
I was thinking of kicking off release voting for a 2.5.3 early next week.
Time to get in any changes you want for that release or let me know of
anything critical we should be waiting for.
Cheers, Paul.
Thanks for the heads up.
Planning to bump picocli to 3.6 (adding internationalization support,
@Command methods, IDefaultValueProvider interface, better error messages
and bash completion script improvements).
The internationalization may be good to bring into the CliBuilder API. (But
not sure I
OK. I was hoping to get some time to add @Generated in many places where it’s
missing but I probably won’t finish by next week. I’ll try to get as much work
done before the weekend.
Sent from my primitive Tricorder
> On 12 Sep 2018, at 11:18, Paul King wrote:
>
>
> I was thinking of
11 matches
Mail list logo
