-
-
Notifications
You must be signed in to change notification settings - Fork 50
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
GroovyFX 8.0.0 artefact not on Maven Central #44
Comments
I am reliably informed that there have been attempts to solve this one that have not been successful, and that new attempts will be made soon. In the mean time the JCenter (Bintray) repository has the artefact. |
@russel I think it's considered a best practice these days to use |
I suspect:
is the de facto standard now, certainly it is the way Grapes works by default. I think altering the example build files to show this would be a good thing, not just as a workaround but as example of standard practice. I cannot do anything on this this morning, but this afternoon I can give it a go if it is agreed to be the right thing to do. I vote yes. |
The problem with not being on maven central is for Maven projects, that by default looks only in central. |
It appears that the 'org.groovyfx:groovyfx:8.0.0' artefact has not been propagated to Maven Central. This seems to mean that a @grab of the artefact in a Groovy script fails.
The text was updated successfully, but these errors were encountered: