[mojo-dev] [jira] (MJAXB-100) Update xjc to 2.2.11

JIRA Tue, 18 Nov 2014 12:15:40 -0800

Title: Message Title

Lennart Jörelid commented on an issue

It is true that the jaxb release of 2.2.11+ has fixed the javadoc bugs as you point out.
However, the JAXB distribution itself has moved from the elder

                                                           <dependency>
            <groupId>com.sun.xml.bind</groupId>
            <artifactId>jaxb-xjc</artifactId>
            <version>${jaxb.version}</version>
        </dependency>
        <dependency>
            <groupId>com.sun.xml.bind</groupId>
            <artifactId>jaxb-jxc</artifactId>
            <version>${jaxb.version}</version>
            <exclusions>
                <exclusion>
                    <artifactId>jsr173_api</artifactId>
                    <groupId>javax.xml.bind</groupId>
                </exclusion>
            </exclusions>
        </dependency>

                                                

To a newer distribution consisting of

                                                            <!-- Use the modern, modularized JAXB structure -->
        <dependency>
            <groupId>javax.xml.bind</groupId>
            <artifactId>jaxb-api</artifactId>
            <version>${jaxb.version}</version>
        </dependency>
        <dependency>
            <groupId>org.glassfish.jaxb</groupId>
            <artifactId>jaxb-core</artifactId>
            <version>${jaxb.version}</version>
        </dependency>
        <dependency>
            <groupId>org.glassfish.jaxb</groupId>
            <artifactId>jaxb-runtime</artifactId>
            <version>${jaxb.version}</version>
            <exclusions>
                <exclusion>
                    <groupId>org.jvnet.staxex</groupId>
                    <artifactId>stax-ex</artifactId>
                </exclusion>
            </exclusions>
        </dependency>
        <dependency>
            <groupId>org.jvnet.staxex</groupId>
            <artifactId>stax-ex</artifactId>
            <version>${stax-ex.version}</version>
        </dependency>

                                                

Packaging has changed, implying that the jaxb2-maven-plugin cannot use the newer distribution without recoding.
This is not a problem in itself, but it also means that the jaxb2-maven-plugin cannot be run on JDK1.5.
The jaxb-parent contains two maven-enforcer-rules, as per the below. This is not a problem if we imply that the jaxb2-maven-plugin should require at least JDK 1.6 to run.... which is fair considering that the Oracle 1.6 JDK has reached end-of-life. How about other JDKs?

                                                    <requireJavaVersion><version>[1.6,)</version></requireJavaVersion>
<requireMavenVersion><version>[3.0.3,)</version></requireMavenVersion>

Add Comment

Mojo's JAXB-2 Maven Plugin /

MJAXB-100

Current 2.2.7 is used that generates incomaptible Javadoc with -Xdoclint:all (see https://java.net/jira/browse/JAXB-973). It is fixed in 2.2.11.

This message was sent by Atlassian JIRA



---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

[mojo-dev] [jira] (MJAXB-100) Update xjc to 2.2.11

Reply via email to