+1 Yeah, add automatic-module-name in MANIFEST is a good start that CXF can eventually move to module-path way.
Since CXF is actually already OSGi module based, we won’t run into such “split-package” issue in CXF, follow the common rule(root package name) to add automatic-module-name in each CXF module make sense to us for now. －－－－－－－－－－－－－ Freeman(Yue) Fang Red Hat, Inc. FuseSource is now part of Red Hat > On Apr 5, 2018, at 10:06 PM, Andriy Redko <[email protected]> wrote: > > Hi Dan, > > Yes, we are looking into this (not specifically related to the plugin but to > CXF as a whole). It was briefly > discussed on the mailing list, https://issues.apache.org/jira/browse/CXF-7600 > has been created, I am planning > to start working on it shortly if there are no objections. Thanks! > > Best Regards, > Andriy Redko > > > DK> I guess the question is: does anyone know what would be needed for the > cxf-xjc-runtime artifact (and maybe others) > DK> to have the needed module name or whatever to work better on Java 9/10? > I haven’t looked. If we are looking into Java9/10 things, might be good to > also look at. > > DK> That said, I wouldn’t say it’s critical and thus doesn’t need to hold > things up. > > DK> Dan > > >>> On Apr 5, 2018, at 4:43 AM, Colm O hEigeartaigh <[email protected]> wrote: >>> >>> Sure it makes sense. Is there anything else anyone wants to fixed in the >>> next release? >>> >>> Colm. >>> >>> On Tue, Apr 3, 2018 at 9:06 PM, Dennis Kieselhorst <[email protected]> wrote: >>> >>>> Hi, >>>> >>>> Freeman adapted cxf-xjc-plugin to work with Java 10. What about releasing >>>> this so that users have a working release version? >>>> >>>> Cheers >>>> Dennis >>>> >>> >>> >>> >>> -- >>> Colm O hEigeartaigh >>> >>> Talend Community Coder >>> http://coders.talend.com > >
