Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

generateGlobalLock fails with springboot gradle plugin #121

Closed
marvertin opened this issue Mar 31, 2017 · 4 comments
Closed

generateGlobalLock fails with springboot gradle plugin #121

marvertin opened this issue Mar 31, 2017 · 4 comments

Comments

@marvertin
Copy link

Minimal project with this issue is
https://github.com/marvertin/nebula-dependency-lock-not-work-withspringboot

command:
gradlew clean build generateGlobalLock

end with this result:

:innerprj:clean
:innerprj:compileJava
:innerprj:processResources NO-SOURCE
:innerprj:classes
:innerprj:findMainClass
:innerprj:jar
:innerprj:bootRepackage
:innerprj:assemble
:innerprj:compileTestJava NO-SOURCE
:innerprj:processTestResources NO-SOURCE
:innerprj:testClasses UP-TO-DATE
:innerprj:test NO-SOURCE
:innerprj:check UP-TO-DATE
:innerprj:build
:generateGlobalLock FAILED

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':generateGlobalLock'.
> Could not resolve all dependencies for configuration ':innerprj:detachedConfiguration37'.
   > Project :innerprj declares a dependency from configuration 'detachedConfiguration37' to configuration 'archives' which is not declared in the descriptor for project :innerprj.

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

BUILD FAILED

Total time: 6.955 secs

@ItamarBenjamin
Copy link

👍

@hoplers
Copy link

hoplers commented Jun 25, 2017

any update regarding this?

@DanielThomas
Copy link
Contributor

Certainly reproducible, but odd error - we usually see this kind of thing where there are dependency cycles, but that doesn't seem to be the case here:

gradle/gradle#1638

Avoid global locks in preference for per-project locks. Uncertain if we'll fix this, as we're phasing out the use of global locks internally.

@rpalcolea
Copy link
Member

As @DanielThomas , we won't fix this as we don't recommend global locks.

Gradle might introduce this concept in their core locking at some point but from nebula perspective, we will stick with current opinions and lean towards adopting Gradle's as it is inspired by our implementation

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants