jkube
jkube copied to clipboard
eclipse-jkube
[EPIC] Provide Gradle Equivalents of Existing Maven Plugins
Right now we do kubernetes-maven-plugin and openshift-maven-plugin. But we also need to provide equivalents for gradle since gradle is also very popular these days. We would first need to get #30 fixed in order to achieve this.
Tasks
- #764
- #769
- #800
- #765
- #808
- #849
- #835
- #834
- #837
- #882
- #880
- #881
- #921
- #914
- #922
- #934
- #935
- #945
- #949
- #950
- #951
- #952
- #850
- #903
- #851
- #838
- #1029
- #1052
- #1053
- #1075
- #1076
- #1109
- #1110
- #1049
- #931
- #1051
- #1047
- #1048
- #1146
- #1147
- #1148
- #1149
- #1150
- #1151
- #1201
- #1202
- #1203
- #1204
- #1205
- #1206
- #1207
- #1208
- #1210
- #1211
- #1214
- #1236
- #1237
- #1238
- #1239
- #1240
- #1248
- #1250
- #1256
- #1257
- #1258
- #1259
- #1260
- #1261
- #1262
- #1297
- #1298
- #1299
- #1301
- #1302
- #1303
- #1308
- #1310
- #1311
- #1312
- #1336
- #1197
- #1050
- #1243
- #900
- #899
- #901
- #867
- #1512
- #1634
- #1633
- #2180
- #1134
- #1184
- #1185
- #836
- #1073
- #147
CQs
- [X] org.codehaus.groovy:groovy-all:2.4.7
- [X] org.gradle:gradle-base-services:6.1.1
- [X] org.gradle:gradle-base-services-groovy:6.1.1
- [X] org.gradle:gradle-core:6.1.1
- [X] org.gradle:gradle-core-api:6.1.1
- [x] org.gradle:gradle-dependency-management:6.1.1
- [X] org.gradle:gradle-logging:6.1.1
- [X] org.gradle:gradle-messaging:6.1.1
- [X] org.gradle:gradle-model-core:6.1.1
- [X] org.gradle:gradle-native:6.1.1
- [X] org.gradle:gradle-plugins:6.1.1
- [X] org.gradle:gradle-platform-jvm:6.1.1
- [X] org.gradle:gradle-process-services:6.1.1
- [X] org.gradle:gradle-test-kit:6.1.1
- [X] org.gradle:gradle-tooling-api:6.1.1
- [X] org.mockito:mockito-core:3.11.2
Any updates on this? Its been over a year since this issue was created and yet the Gradle community still has nothing.
We'll start working on this issue soon. With the most recent changes, every piece of logic has been moved to the JKube Kit component, so implementing the plugins should be very straightforward.
The feature is/was planned for 1.1, however we had to shift the team's priorities during the past few weeks to deliver Fabric8 Kubernetes Client 5.0.0.
We'll probably release 1.1 without the Gradle plugins and do a subsequent release in the following weeks with the Gradle plugins included :crossed_fingers:.
I see this has been pushed to 1.3.0. Is that realistic, or just a case of "we didn't get to it, maybe next time?" I'm starting a new project and am trying to push for using Gradle, but I have to make sure tooling all supports it as much as possible.
The Gradle plugins are one of our main priorities. We really want to provide a preview of the feature ASAP so we can start getting feedback.
However, we count with very limited resources, this is the reason it keeps getting pushed to the next minor release. We released 1.2.0 on the 31st of March, so depending on the community needing an additional release in the coming weeks, this feature might be pushed again.
It's also important to highlight that the first implementations of the plugins won't be feature complete (as compared with the Maven equivalents). So if you plan to use the Gradle plugins with many customizations it will probably be a while until everything works like it does with Maven.
Hi @matthiaszimmermann, @edeandrea, @erizzo (@OneCricketeer, @moley, @danduke, @antmordel, @typekpb, @MaximVasin)
You expressed your interest for this feature. It's been available as a preview since 1.5.
Did you have a chance to try the new Gradle Plugins?
It would be great to have your feedback ;)