Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When this project was created, in #1, it included a
kubernetes/build.gradle
and related files. It also included a Mavenkubernetes/pom.xml
, oh and a Scala-stylekubernetes/build.sbt
for good measure. The initialkubernetes/.travis.yml
suggests that this was all just dumped here by Swagger, not deliberate. Later in #5, #73, etc. the structure was rearranged, all assuming a Maven build—as does the current (top-level).travis.yml
andREADME.md
. In fact the current structure has a root POM and declares thekubernetes
subdirectory as amodule
, which implies that it is to be built via Maven. Thebuild.gradle
is clearly out of date—for example, it does not reflect #453.My practical interest in this is that the NetBeans IDE currently prefers
build.gradle
topom.xml
when both are present in a directory, so thekubernetes
subdirectory gets opened as a Gradle project and it is a mess. If build scripts and related metadata are not actually current and usable, they are better deleted to avoid confusion.