-
Notifications
You must be signed in to change notification settings - Fork 41
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
Migrate build system to gradle #70
Comments
Yes it is. But what fundamental advantage gives gradle? It seems to me that this is not a principle. |
I'll refer to any article like this one: http://www.drdobbs.com/jvm/why-build-your-java-projects-with-gradle/240168608 for Gradle virtues but I think that there are operative issues for this project to be taken in account. |
Currently ant project doesn't use ivy - I have copied all libraries to lib/runtime and lib/compile directories. And replaced some libraries to new versions. test and tools libraries aren't added to repo. All muCommander module sources was moved to trolCommander repo too (and I have updated them). I agree that this is not the best solution - store all libraries in repo. But it's easy and it works. And now trolCommander doesn't depends on third-party repositories. Yes, gradle is better than ant but for me (as trolCommander user) the main priority are bug fixes, new features, performance optimizations and memory consumption. |
I created 2 projects to start mavenization/gradlization : |
👍 |
The original mucommander is migrating to gradle which is a much modern build system in my opinion.
The text was updated successfully, but these errors were encountered: