Re: [jaxb-impl-dev] Rename packages in jaxb-impl and split the main impl

[Bill Shannon <bill.shannon@xxxxxxxxxx>]

I'm not sure what would be in each piece after the split but ideally
there would be a single jar file corresponding to all the required
components of the spec, with possibly some other jar file containing
optional features of the spec.  You don't want a customer to have to
assemble their own compatible implementation by choosing the right
collection of jar files.  At the very least there needs to be hard
dependencies between the required implementation jar files.

Lukas Jungmann wrote on 4/15/20 4:28 PM:
> Hi,
> 
>    with upcoming major version change, I believe it is the right time to split
> the main jaxb-impl.jar back into smaller parts which used to be there in older
> versions of jaxb-impl, last was 2.2.11 (I believe). The work which has been done
> was "reverted" and both separated components merged back into one jar in 2.3.x
> in order to solve the "split packages" problem on JPMS/JDK 9+ as at the time,
> changing the package name has not been allowed.
> 
>    Since the major version number has been already increased, version 3.0.0-M1
> which adopted jakarta.xml.bind packages is already available and corresponding
> TCKs seems to be updated and working, it is time for the next steps - doing the
> actual split of existing jaxb-impl.jar into smaller parts. To make adoption of
> this change easier, the plan is to spread the change through multiple M builds.
> 
>    I'm open for suggestions wrt new package names, I've chosen
> "org.glassfish.jaxb" prefix for now as it matches current maven group id, just
> keep in mind that there already exists "org.eclipse.persistence.jaxb" (used by
> MOXy) - using "org.eclipse.jaxb" could probably easily lead to confusion as in
> the past with "com.sun.xml.bind" vs. "com.sun.xml.internal.bind", so I prefer
> something with different prefix than "org.eclipse".
> 
>    As for motivation for this change - allow sharing code between multiple
> implementations of Jakarta XML Binding, mainly between jaxb-ri and moxy right now.
> 
>    Since this change as such is intrusive, possibly controversial and affects a
> lot of projects, it would be good to know how others feel about this. Feel free
> to reply here or provide comments in the PR with this change:
> https://github.com/eclipse-ee4j/jaxb-ri/pull/1428
> 
>    Expected adoption path, ie for GlassFish but applicable for other projects as
> well, would be:
> -take 3.0.0-M1 and adopt "javax.xml.bind" to "jakarta.xml.bind" change
> -take 3.0.0-M2 and adopt "com.sun.xml.bind.*" to "org.glassfish.jaxb.runtime"
> (or whatever else is chosen) change
> -take 3.0.0-M3 and adopt remaining "com.sun.xml.bind.*" to
> "org.glassfish.jaxb.core" (or whatever else is chosen) change
> 
>    Should there be no feedback or no strong no from anyone, I'll proceed with
> the change on Tue April 21 at the latest.
> 
> thanks,
> --lukas
> _______________________________________________
> jaxb-impl-dev mailing list
> jaxb-impl-dev@xxxxxxxxxxx
> To unsubscribe from this list, visit
> https://www.eclipse.org/mailman/listinfo/jaxb-impl-dev