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
Move project build to maven #1523
Comments
Implemented, leftover is migrate the deb packaging from 0.18 branch to master using maven. |
Hiya I tried building with maven - a couple of things:
but it built successfully |
Cool, btw, that warning is "ok". |
Yeah, build is here ok too. Really nice :) BTW: what made you switching? Some tests are failing (not sure if related to maven). testSnapshotOperations * 2 testRequiredRoutingMappingWithAlias testScriptFieldUsingSource testFiltersWithCustomeCacheKey |
@karussell switched because gradle made some changes in latest version that make it harder to get started without IDE support. Also, since I moved all the plugins to their own repos, then we can have a single module, and I never had major problems with maven on single module projects, its the multi module ones that caused me pain. |
Ah, ok. I'm now done with the migration of the deb pkg and ElasticSearch even starts ;) Pull request is coming ... |
So, are the plugins still hosted on Maven somewhere? Can't find them in their pre-0.19 location. |
Move to maven for the build system. Since we moved all the plugins, we can use a single module (maven crap with multi module), which makes things simpler.
mvn assembly:assembly -DskipTests
, it will be undertarget/releases
.The text was updated successfully, but these errors were encountered: