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

Gradle build #1

Closed
wants to merge 1 commit into from
Closed

Gradle build #1

wants to merge 1 commit into from

Conversation

aalmiray
Copy link
Contributor

@aalmiray aalmiray commented Oct 6, 2015

This pull request proposes the following changes

  • Migrate build to multi project Gradle structure
  • Apply license headers to all files

Tried to keep the original structure but it was easier to relocate all source files to their expected locations. Apply any of the following commands to build and run the projects

  • gradle jar. Creates all artifact jars.
  • gradle build. Builds all artifacts, checks all source files.
  • gradle run. Runs the main demo.
  • gradle bintrayUpload. Uploads a new version to bintray.com
  • gradle licenseFormat. Applies formatting to license headers

These new settings allow the project to be published on bintray.com, simply put: Github for binaries.

Apply license headers to all files
@spyhunter99
Copy link

no love for maven?

@aalmiray
Copy link
Contributor Author

aalmiray commented Oct 7, 2015

After spending 7 years with Maven and 5 more with Gradle I cans say with good confidence that Gradle is the superior build tool. Besides migrating from Ant to Gradle is easier than from Ant to Maven.

@jfoenixadmin
Copy link
Collaborator

thanks it's very appreciated, however we want to keep the ant build files. if you can pull the latest changes and just add Gradle build files it would be great. also we applied license headers to all java files so no need to worry about it. thanks again

@aalmiray
Copy link
Contributor Author

aalmiray commented Oct 8, 2015

Sure, no problem. Would it be OK to relocate classes to follow the Maven/Gradle conventions? Now that I know more about the layout and how the sources work I could also keep the old one if you like.

@aalmiray
Copy link
Contributor Author

aalmiray commented Oct 8, 2015

I'll close this PR and send a different one

@aalmiray aalmiray closed this Oct 8, 2015
jfoenixadmin pushed a commit that referenced this pull request Aug 26, 2017
jfoenixadmin pushed a commit that referenced this pull request Nov 9, 2017
jfoenixadmin pushed a commit that referenced this pull request Feb 5, 2018
yushijinhun pushed a commit to yushijinhun/JFoenix that referenced this pull request Oct 20, 2018
Fix high CPU usage on OpenJFX 10 & Update readme
jfoenixadmin pushed a commit that referenced this pull request Feb 12, 2020
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

Successfully merging this pull request may close these issues.

3 participants