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

Migrating to Gradle Builds #7

Closed
yevhenii-nadtochii opened this issue Jun 15, 2020 · 2 comments
Closed

Migrating to Gradle Builds #7

yevhenii-nadtochii opened this issue Jun 15, 2020 · 2 comments

Comments

@yevhenii-nadtochii
Copy link

Each time I wanted to drill down to under-hood of tornadoFX in order just to investigate how it works\to play with code\investigate a bug I was stopped by Maven and it still makes me cry (Am I the only one?)
I have nothing against mvn in tornadofx (as it was created in 2016). But could switching to gradle be at least considered\investigated for tornadofx2 ? I think there's no need in pointing out why gradle is better than mvn and for this project in particular. I would like to outline only two items:

  1. Most of tornadofx users are Kotlin developers and incidentally most of them are gradle users as well :)
  2. Download gradle-based project, switch dependency from remote repository to local gradle project and that's it. It would simplify life for potential future contributors.

I would appreciate any thoughts about this. Thank you!

@SKeeneCode
Copy link
Collaborator

Now that tornadofx2 is gradle based - we should close this.

@yevhenii-nadtochii
Copy link
Author

Thanks to everyone who was involved!

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

2 participants