Skip to content
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

Open
16 tasks done
rohanKanojia opened this issue Dec 18, 2019 · 8 comments
Open
16 tasks done

[EPIC] Provide Gradle Equivalents of Existing Maven Plugins #31

rohanKanojia opened this issue Dec 18, 2019 · 8 comments
Labels
component/gradle-plugin Related to the Gradle Plugins enhancement New feature or request
Milestone

Comments

@rohanKanojia
Copy link
Member

rohanKanojia commented Dec 18, 2019

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

CQs

@rohanKanojia rohanKanojia self-assigned this Dec 18, 2019
@manusa
Copy link
Member

manusa commented Dec 18, 2019

Relates to:

@manusa manusa added the enhancement New feature or request label Mar 11, 2020
@manusa manusa added this to Planned in Sprint #181 Mar 11, 2020
@rohanKanojia rohanKanojia removed this from Planned in Sprint #181 Mar 31, 2020
@manusa manusa added this to the 1.1.0 milestone Jul 8, 2020
@matthiaszimmermann
Copy link

+1

@edeandrea
Copy link

Any updates on this? Its been over a year since this issue was created and yet the Gradle community still has nothing.

@manusa
Copy link
Member

manusa commented Jan 11, 2021

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 🤞.

@manusa manusa modified the milestones: 1.1.0, 1.2.0 Jan 12, 2021
@manusa manusa modified the milestones: 1.2.0, 1.3.0 Mar 23, 2021
@erizzo
Copy link

erizzo commented Apr 19, 2021

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.

@manusa
Copy link
Member

manusa commented Apr 19, 2021

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.

@manusa
Copy link
Member

manusa commented Feb 21, 2022

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 ;)

@edeandrea
Copy link

Thanks @manusa ! I was not aware it was there.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component/gradle-plugin Related to the Gradle Plugins enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

5 participants