Armeria: Gradle build failed at buildNeeded task.

Created on 8 Aug 2017  路  7Comments  路  Source: line/armeria

hi @trustin,

I was test a build for buildNeeded task, but failed it.
Could you check it out?

Additionally, Eclipse builds fail too by the Circular dependency.
Eclipse error keyword is "A cyclic dependency in eclipse".

Workaround of eclipse build fail by cyclic dependency is
changing build severity.
Preferences > Java > Compiler > building > Build path problems.
Circular dependencies : Change value Error to Warning.

Below is error messages of Gradle.

* What went wrong:
Circular dependency between the following tasks:
:core:buildNeeded
\--- :testing-internal:buildNeeded
     +--- :core:buildNeeded (*)
     +--- :testing:buildNeeded
     |    +--- :core:buildNeeded (*)
     |    \--- :testing-internal:buildNeeded (*)
     \--- :testing-internal:buildNeeded (*)

(*) - details omitted (listed previously)


* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug
option to get more log output.

BUILD FAILED in 3s

== BUILD FAILED ==

All 7 comments

Oops~ let me check this.

It seems like we had this issue before #710 was merged. Let me dig into more and remove the circular dependency. Before that, I have a question for you. Does your eclipse fails suddenly? or has the problem before? And, ./gradlew build failed as well?

@minwoox gradle build is working fine. but, gradle buildNeeded is fail.

I updated gradle 3.1 to 4.0.2.
however Two gradle version and gradlew are same error.

Looks like a bug in Gradle: https://github.com/gradle/gradle/issues/1647

@trustin Do you think eclipse build ship has the same bug?
below is Eclipse Marker log.

A cycle was detected in the build path of project 'core'. The cycle consists of projects {core, testing-internal,  
more 17 lines ...

Well, they said this is the expected behavior. https://github.com/eclipse/buildship/issues/460

@trustin @minwoox Thank you for answers.

Was this page helpful?
0 / 5 - 0 ratings