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

Migrate build system to gradle #70

Open
adobni opened this issue Feb 19, 2015 · 5 comments
Open

Migrate build system to gradle #70

adobni opened this issue Feb 19, 2015 · 5 comments

Comments

@adobni
Copy link

adobni commented Feb 19, 2015

The original mucommander is migrating to gradle which is a much modern build system in my opinion.

@trol73
Copy link
Owner

trol73 commented Feb 20, 2015

Yes it is. But what fundamental advantage gives gradle? It seems to me that this is not a principle.
However, this is an open source project, and anyone can send a pull request

@adobni
Copy link
Author

adobni commented Feb 20, 2015

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 the ant project depends on the original project ivy repository. Because they are migrating to Maven dependencies they might decide to shutdown it.
I'm not sure of the impact if you want to update dependencies in the project for newer ones.
Also the original mucommander project seems to be refactoring the modules still referenced in the build that doesn't seem are forked here.
I started writing a Gradle script to contribute but realized that there some problems interpreting the Ivy repository structure, maybe a Gradle bug or limitation. It would be better to refactor the project like the original to use subprojects and Maven repositories but some dependencies seems to not available or at least I haven't been able to find them.

@trol73
Copy link
Owner

trol73 commented Feb 20, 2015

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.

@turiot
Copy link

turiot commented Mar 31, 2015

I created 2 projects to start mavenization/gradlization :
https://github.com/turiot/mucommander-trol
https://github.com/turiot/mucommander-deps
Maybe it can help.

@nawa
Copy link

nawa commented Apr 2, 2015

👍

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

4 participants