-
Notifications
You must be signed in to change notification settings - Fork 101
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
Gradle wizard searching Maven central for latest versions #464
Conversation
Ok, this is kinda ridiculous demand. We can fix this to be better... |
…ould happen... reduce the log level
I also reduced the log level to INFO. It is better UX I think. Errors are to be expected.. to some degree. With INFO they still come to the application log and all. So maybe it is enough. Now they don't bother the user. |
I'll merge this in 12h if no objections. I think it is production ready. I still tweaked the version handling to more straightforward model in code. |
Resolves #371
Alright.. Now, if Maven API is up, we initialize the user project with latest versions of libraries. And automatically display latest versions of jME to choose from. If Maven API is down, it doesn't matter, we have a set of hard coded versions to choose from. This is just an enhancement that is provided for our and users' convenience.
Maven API wasn't working that great this past two weeks. Now it seems to be up again. How this is designed, is that there is zero wait for the user. So there might be inconsistent results in users' perspective as we might catch latest versions at some random point in time.
In my experience, the Maven API either responds immediately or it is simply down. Meaning that this strategy is viable. The Maven is accessed in highly parallel way, zero locks still. And only once per lifetime of the SDK instance.
Ok, the caveats:
test-data
andawt-dialogs
might be missing from some versions, yet they are hard coded to be included (not the latter, yet)edit: added library version filtering to avoid weird version types (minie and heart)