You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@groovy.apache.org by "Eric Milles (Jira)" <ji...@apache.org> on 2021/10/29 20:51:00 UTC

[jira] [Assigned] (GROOVY-7080) Cycle in Eclipse

     [ https://issues.apache.org/jira/browse/GROOVY-7080?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Eric Milles reassigned GROOVY-7080:
-----------------------------------

    Assignee: Eric Milles

> Cycle in Eclipse
> ----------------
>
>                 Key: GROOVY-7080
>                 URL: https://issues.apache.org/jira/browse/GROOVY-7080
>             Project: Groovy
>          Issue Type: Bug
>         Environment: java version "1.7.0_65"
> OpenJDK Runtime Environment (fedora-2.5.1.3.fc20-x86_64 u65-b17)
> Gradle IDE	3.6.1.201408250705-RELEASE
> java version "1.7.0_65"
> OpenJDK Runtime Environment (fedora-2.5.1.3.fc20-x86_64 u65-b17)
>            Reporter: Erwin Mueller
>            Assignee: Eric Milles
>            Priority: Major
>
> Try to follow guide from https://github.com/groovy/groovy-core#building
> Importing groovy-core and groovy-test gives the error
> A cycle was detected in the build path of project 'groovy'. The cycle consists 
> of projects {groovy, groovy-test}
> Why not just merge groovy-test in groovy-core? The subprojects of Groovy depend on both anyway, and groovy-test is small.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)