Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[jakartaee-platform-dev] History of Mojarra dependency?

Hi,
This question is probably targeted at Bill, but while I was looking to update the pom in jakartaee-api for a Jakarta EE 9 Milestone/RC API, I came across this dependency on Mojarra:

        <!-- work around for GLASSFISH-19861  -->
        <dependency>
            <groupId>org.glassfish</groupId>
            <artifactId>jakarta.faces</artifactId>
            <version>${mojarra.version}</version>
            <optional>true</optional>
        </dependency>

I know all about the JSF API being dependent on Mojarra, but we're already bringing in the JSF API as a separate dependency.  I looked up the Issue that is referencedand it was closed back in 2013...  It looks like there was a discussion between Ed and Bill about whether this dependency on com.sun.faces had to be removed or not...  The end result looks like leaving these references was an okay operation for Mojarra.

But, I'm confused as to what this is doing for the generation of the API jar files.  Whether I have this dependency in or out of the pom, it looks to still generate the API jar files (without the com.sun.faces classes).  Any ideas?

---------------------------------------------------
Kevin Sutter
STSM, MicroProfile and Jakarta EE architect @ IBM
e-mail:  sutter@xxxxxxxxxx     Twitter:  @kwsutter
phone: tl-553-3620 (office), 507-253-3620 (office)    
LinkedIn:
https://www.linkedin.com/in/kevinwsutter

Back to the top