-
-
Notifications
You must be signed in to change notification settings - Fork 60
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
Switch build to Gradle build tool #117
Comments
Sure, sounds great! I would prefer using Gradle as well. One question, would a user still be able to run the program using |
Feel free to get started on this! |
Yes, sure. |
Sounds good, I'll approve your PRs as they come. Afterwards, perhaps we can set up a GitHub Actions pipeline for Gradle. |
Once you implement this, it would be great if you could create a separate PR with documentation on how to use Gradle. |
Configures a basic Gradle Java app build. To stick to Gradle convention as closely as possible, this commit - adds several Gradle-specific directories / files to the git ignore list - moves the source code from src/ to app/src/main/java/ - adds a (dummy) test class in app/src/test/java It also updates the README and provides basic information on how to build + run the DNAnalyzer.
Configures a basic Gradle Java app build. To stick to Gradle convention as closely as possible, this commit - adds several Gradle-specific directories / files to the git ignore list - moves the source code from src/ to app/src/main/java/ - adds a (dummy) test class in app/src/test/java It also updates the README and provides basic information on how to build + run the DNAnalyzer.
Configures a basic Gradle Java app build. To stick to Gradle convention as closely as possible, this commit - adds several Gradle-specific directories / files to the git ignore list - moves the source code from src/ to app/src/main/java/ - adds a (dummy) test class in app/src/test/java It also updates the README and provides basic information on how to build + run the DNAnalyzer. Configure Gradle build. Implements VerisimilitudeX#117. Configures a basic Gradle Java app build. To stick to Gradle convention as closely as possible, this commit - adds several Gradle-specific directories / files to the git ignore list - moves the source code from src/ to app/src/main/java/ - adds a (dummy) test class in app/src/test/java It also updates the README and provides basic information on how to build + run the DNAnalyzer. copy files over from main branch that were messed up during merge move source back to src/ subdir (instead of app/src)
Configures a basic Gradle Java app build. To stick to Gradle convention as closely as possible, this commit - adds several Gradle-specific directories / files to the git ignore list - moves the source code from src/ to app/src/main/java/ - adds a (dummy) test class in app/src/test/java It also updates the README and provides basic information on how to build + run the DNAnalyzer. Configure Gradle build. Implements VerisimilitudeX#117. Configures a basic Gradle Java app build. To stick to Gradle convention as closely as possible, this commit - adds several Gradle-specific directories / files to the git ignore list - moves the source code from src/ to app/src/main/java/ - adds a (dummy) test class in app/src/test/java It also updates the README and provides basic information on how to build + run the DNAnalyzer. copy files over from main branch that were messed up during merge move source back to src/ subdir (instead of app/src)
Configures a basic Gradle Java app build. To stick to Gradle convention as closely as possible, this commit - adds several Gradle-specific directories / files to the git ignore list - moves the source code from src/ to src/main/java/ - adds a (dummy) test class in app/src/test/java It also updates the README and provides basic information on how to build + run the DNAnalyzer. cleanup README (merge old and new getting started) use up-to-date java files from upstream
…#117 Configure Gradle build. Implements #117.
Is your feature request related to a problem? Please describe.
Currently, building / running the project can only be done by executing
javac Main.java
/java Main
manually (or running Main from your IDE, e.g. Eclipse). This is especially confusing for new users, who are used to Maven or Gradle and simply wish to runto build their project without having to worry about the dependencies etc.
Also, gradle allows publishing the package to Maven Central, running the tests etc. in a very straight-forward way.
Describe the solution you'd like
I'd like a project setup that allows the user to simply execute
to build the project and
to run it.
Describe alternatives you've considered
An alternative to Gradle would be [Maven|https://maven.apache.org/]. Similar features, mostly a matter of preferences (personally, I prefer Gradle).
Additional context
If this sounds sensible to you, I'd be willing to implement it :-)
The text was updated successfully, but these errors were encountered: