-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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
Do we need both gradle and maven? #16
Comments
@maniksurtani nope ... the plan was to eventually remove the maven build. Probably a good time to pull the trigger. |
The only real thing not yet ported to Gradle is my bootclasspath.properties hack for run-test-{client,server}. For Gradle, we need some way of actually running the test server/client. "gradle run" seems to be able to do what we need, but we would need to figure out how to specify the bootclasspath with the correct ALPN version. |
The majority of this has been addressed by #39. I'll prepare one more PR to tie up any loose ends and remove the pom.xml files. |
Thanks On 26 January 2015 at 15:31, Nathan Mittler notifications@github.com
|
Maven build removed by #41 |
Keeping dependencies and other details in
pom.xml
andbuild.gradle
will become a tedious overhead. Any reason to support two build systems?The text was updated successfully, but these errors were encountered: