We need to update the note in 3.2.9 SP1 Release Notes about "Removal of quarkus-bootstrap-maven-plugin". We need to update the note asap. 

Here is the mail thread:

******************************************************************************

 
On Tue, Jan 16, 2024 at 6:42 PM Davide Scrimieri <dscrimie@redhat.com> wrote:

Thank you for your feedback. This is indeed a plugin that the customer is using on a "normal" app. I will let the customer know asap, and tell them to switch plugin to quarkus-maven-plugin. @Thomas Qvarnstrom  thank you also for your input, as the Customer is very reliant upon the documentation, so if this information can be found there too it would be very helpful.
 
Thanks!
DAVIDE SCRIMIERI 

TAM OPENSHIFT / MIDDLEWARE

Red Hat Srl

Via Andrea Doria, 41M 00192 Roma (RM) - ITALY

dscrimie@redhat.com M: +39 3453004091

TRIED. TESTED. TRUSTED.

On Tue, Jan 16, 2024 at 2:11 PM Sangeeta Raghu Punnadi <sraghupu@redhat.com> wrote:

Hi Thomas, 
We will update the migration note with details about custom extensions and keep this group posted on the updates.

Thanks and regards,

Sangeeta Raghu-Punnadi

She/Her/Hers

Senior Content Strategist - Runtimes
CCS

Red Hat - APAC, Pune
 
sraghupu@redhat.com   
M: [+91-9890625023|tel:+91-9890625023]     IM: sraghupu

On Tue, Jan 16, 2024 at 5:02 PM Thomas Qvarnstrom <tqvarnst@redhat.com> wrote:

+1. Please make sure that the customer is building a custom extension since the plugin they should use for "normal" app development is quarkus-maven-plugin. We should probably have been more explicit that this migration note is only if you are building custom extensions. @Sangeeta Raghu Punnadi Can we change the migration note to more clearly state that only if you are building custom extension you need to change the artifact from io.quarkus:quarkus-bootstrap-maven-plugin to io.quarkus:quarkus-extension-maven-plugin.
 
Cheers
Thomas

 

---

Thomas Qvarnström
Sr. Pr. Product Manager
Red Hat, Inc.

On Tue, Jan 16, 2024 at 12:10 PM Alexey Loubyansky <alexey.loubyansky@redhat.com> wrote:

Hi Davide, 
just to be sure, could you please confirm the customer is developing custom Quarkus extensions in addition to Quarkus applications?
 
This plugin is for Quarkus extension development, it's not used for application development.
 
So far Quarkus extension projects would depend on "io.quarkus" artifact versions instead of "io.quarkus.platform" or "com.redhat.quarkus.platform" versions.
io.quarkus and *.quarkus.platform artifacts are released from different code repositories and may have different versions. We could consider re-publishing the extension-maven-plugin as part of the platform release to make it more convenient for customers to build custom (private) extensions.
 
Alexey

On Tue, Jan 16, 2024 at 11:14 AM Davide Scrimieri <dscrimie@redhat.com> wrote:

ERRATA: the quarkus extension maven plugin is here

On Tuesday, January 16, 2024 at 11:05:29 AM UTC+1 Davide Scrimieri wrote:

Hello,

According to the Quarkus 3.x docs found here 

the plugin io.quarkus:quarkus-bootstrap-maven-plugin has been replaced with io.quarkus:quarkus-extension-maven-plugin

Customer is asking why the new io.quarkus:quarkus-extension-maven-plugin extension that can be added to the project's pom can be found here has a versioning different from the Quarkus build.

He noticed the Quarkus build and plugin build versions are:

           <quarkus.version>3.2.9.Final-redhat-00003</quarkus.version>
            <quarkus.extension.maven.plugin.version>3.2.9.Final-redhat-00002</quarkus.extension.maven.plugin.version>

While doing the build he has some errors in importing the plugin's dependencies so he was wondering if these differences in versioning did play a role?

In case they do not play a role, he still would like to know if there are any issues in using different versions of quarkus bom and plugin version?

Thanks,

Davide