[
https://issues.apache.org/jira/browse/GROOVY-8934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17109037#comment-17109037
]
Remko Popma commented on GROOVY-8934:
-------------------------------------
I believe [~paulk] is correct and this should no longer be an issue.
Prior to picocli 4.0, the picocli jar did indeed contain some classes that
depend on Groovy. In the 4.0 release, these classes were split off from the
picocli artifact into a separate artifact {{picocli-groovy}}.
Groovy itself does not use the {{picocli-groovy}} artifact, only {{picocli}}.
[~roptat] can you try again with a recent version of Groovy?
> Groovy 2.5 introduced a bootstrap loop
> --------------------------------------
>
> Key: GROOVY-8934
> URL: https://issues.apache.org/jira/browse/GROOVY-8934
> Project: Groovy
> Issue Type: Bug
> Reporter: julien lepiller
> Priority: Major
>
> Hi,
> I'm a packager in Guix and I'm interested in getting the java stack packaged
> in Guix. We already have a package for Groovy 2.4.15
> ([https://git.savannah.gnu.org/cgit/guix.git/tree/gnu/packages/groovy.scm])
> that I'm trying to update to the latest version. This old version was
> perfectly bootstrappable, meaning that I was able to build Groovy without a
> pre-existing Groovy compiler. I only had to ignore Gradle (because it depends
> on Groovy) and somewhat emulate its behavior with simpler tools. This works
> well and I'm able to build most of Gradle with it!
> During the update process, I realised that Groovy now requires picocli. When
> I tried to package it, I discovered that it depends on Groovy. This
> introduces a bootstrap loop that I need to break, as I can no longer build
> Groovy without itself. Would you consider removing picocli to make Groovy
> bootstrappable (in the sense of
> [https://bootstrappable.org|https://bootstrappable.org)/]) again in future
> releases?
> Another solution for us is to update to the latest version in the 2.4 series,
> build picocli with it, and then use that to build the latest Groovy. This is
> less nice, because future versions of picocli might require intermediate
> versions of Groovy, which will eventually create a long chain of compilers,
> but could work as well.
> Thanks in advance!
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
