[
https://issues.apache.org/jira/browse/MYFACES-4568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17691575#comment-17691575
]
Paul Nicolucci commented on MYFACES-4568:
-----------------------------------------
Yes, that is exactly what I was in the process of doing :)
> Migrate Quarkus PrimeFaces Support out of MyFaces
> -------------------------------------------------
>
> Key: MYFACES-4568
> URL: https://issues.apache.org/jira/browse/MYFACES-4568
> Project: MyFaces Core
> Issue Type: Improvement
> Affects Versions: 2.3-next-M7, 4.0.0-RC4
> Reporter: Melloware
> Assignee: Thomas Andraschko
> Priority: Major
> Fix For: 2.3-next-M8, 4.0.0-RC5
>
>
> Currently the Quarkus extension in MyFaces has built in support for
> PrimeFaces. This is being removed in 2.3-next-m8 and 4.0 final. To use
> PrimeFaces with Quarkus users must migrate to the new PrimeFaces specific
> Quarkus extension found here:
> [https://github.com/quarkiverse/quarkus-primefaces]
> And by adding this to their pom.xml:
> {code:java}
> <dependency>
> <groupId>io.quarkiverse.primefaces</groupId>
> <artifactId>quarkus-primefaces</artifactId>
> <version>2.12.0</version>
> </dependency> {code}
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
