-
Notifications
You must be signed in to change notification settings - Fork 5
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
Setting attribute value of candidate
prevents from project configuration
#39
Comments
This looks to be a duplicate of #17.
A workaround is to explicitly add the
|
To expand on what @bigdaz is saying, what your component metadata rule does is define the value of the attribute for a specific dependency. And to put in writing what we discussed, the request would be to not have to add this information, by assuming that if you use such a dependency - by declaring it - then it is assumed that its I do not think implementing such a logic makes sense. While there is a bit of duplication, its presence clarifies the intent. With the specific attribute (or a method having the same effect), it is clear that you want this dependency, including the override behavior. Without it, or if it was implicit, a question could always remain. |
Thanks for the quick feedback. I think I might be losing something? I made these changes -> 2d94381 to iterate over the dependencies and add the attribute Also adding the attribute explicity doesn't seem to work as suggested above -> b96efd8 |
@rpalcolea This set of changes will work, with one minor fix: use
This actually causes the test to get further, and it then fails resolving |
whoa @bigdaz , yeah using |
Closing issue now |
When we detect a version that it's a Release Candidate, we set the
status
tocandidate
.This is broken starting with
5.0-20180923235913+0000
release.Running the
MyPluginSpec
test from https://github.com/nebula-plugins/gradle-nebula-integration/tree/master/broken-release-candidate-attribute will generate the following exception:Ideally, we should be able to set the
status
tocandidate
.The text was updated successfully, but these errors were encountered: