Closed pizzi80 closed 3 months ago
Yes there were a bunch of things off. We've fixed this via:
Now it works again.
To be clear, current build procedure is:
5.0
branch of https://github.com/jakartaee/facesapi
module.mvn clean install -Pstaging
master
branch of https://github.com/eclipse-ee4j/mojarramvn clean install -Pstaging
<dependency>
<groupId>jakarta.faces</groupId>
<artifactId>jakarta.faces-api</artifactId>
<version>5.0.0-SNAPSHOT</version>
</dependency>
<dependency>
<groupId>org.glassfish.mojarra</groupId>
<artifactId>mojarra</artifactId>
<version>5.0.0-SNAPSHOT</version>
</dependency>
Noted should be that GF8 as used by TCK currently refuses to start with Mojarra 5.0.0. This will be worked on.
Note that -Pstaging
is only necessary when the pom happens to reference JEE dependencies not yet in Maven Central. If you don't want to use -Pstaging
every time, then add this to your ~/.m2/settings.xml
:
<repositories>
<repository>
<id>jakarta-staging</id>
<url>https://jakarta.oss.sonatype.org/content/repositories/staging</url>
<snapshots />
</repository>
</repositories>
After the split of Faces API I'm not sure how it's better to locally build/install Mojarra snapshot and how to contribute with PR to the master
May someone create a release or pre-release or whatever of 4.1 and or 5.0 ?
I've made a lot of changes in my fork and I would like to align and make some PR to the master one day, but at the moment I'm stuck in the middle of nowhere