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
[EPIC] Provide Gradle Equivalents of Existing Maven Plugins #31
Comments
Relates to: |
+1 |
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 🤞. |
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?" |
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. 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 ;) |
Thanks @manusa ! I was not aware it was there. |
Right now we do
kubernetes-maven-plugin
andopenshift-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
k8s:undeploy
maven equivalent funtionality in Kubernetes Gradle Plugin #914k8s:push
equivalent functionalityk8sPush
for Kubernetes Gradle Plugin #935oc:push
maven equivalentocPush
gradle task to OpenShift Gradle Plugin #945k8s:debug
equivalent functionalityk8sDebug
for Kubernetes Gradle Plugin #950oc:debug
equivalent functionalityocDebug
for OpenShift Gradle Plugin #951k8s:helm
equivalent functionalityk8sHelm
for Kubernetes Gradle Plugin #1052oc:helm
equivalent functionalityocHelm
for OpenShift Gradle Plugin #1053k8s:helm-push
maven equivalent functionality in Kubernetes Gradle Plugin #1075oc:helm-push
equivalent functionalityocHelmPush
for OpenShift Gradle Plugin #1076k8s:watch
equivalent functionalityk8sWatch
for Kubernetes Gradle Plugin #1109oc:watch
equivalent functionalityocWatch
for OpenShift Gradle Plugin #1110build
>skip
is set totrue
#1197isApplicable
#1634isApplicable()
#1633watchPostTask
to KubernetesWatchTask in Kubernetes Gradle Plugin #1134k8sHelm
task can't pick maintainers, home, sources from project configuration #1073CQs
The text was updated successfully, but these errors were encountered: