I'm fine with deprecating it. There has often been a "tradition" of having external file for listing things, which IMHO is a Maven anti-pattern. All configuration should be in the POM. (Most likely though it comes from some use case where the file names are produced externally and put in a separate file.)
/Anders On Wed, Dec 24, 2014 at 11:11 PM, Lennart Jörelid <lennart.jore...@gmail.com > wrote: > Hello all, > > The jaxb2 maven plugin currently contains a parameter called > schemaListFile with the declaration and documentation as shown below. > > I'm wondering what the use case for having this configuration parameter is > - or if we could simply deprecate it for version 2 of the jaxb maven > plugin. I can't find any ITs testing this property, although it is > implemented in the current Mojo. > > So, basically: why is it beneficial to generate a file holding a list of > paths [to XSD files] as opposed to printing that list of paths directly > into the POM? My inclination is to simply remove this option in version 2 > of the plugin unless someone lets me know why that would be a bad choice. > > The configuration option in question is: > > /** > * A filename containing the list of files to use for schemas, comma > delimited. > * If none, then all xsd files are used in the schemaDirectory.<br> > * Note: you can only use either the 'schemaFiles' or the 'schemaListFileName' > * option (you may not use both at once!). > */ > @Parameter > protected String schemaListFileName; > > > -- > > -- > +==============================+ > | Bästa hälsningar, > | [sw. "Best regards"] > | > | Lennart Jörelid > | EAI Architect & Integrator > | > | jGuru Europe AB > | Mölnlycke - Kista > | > | Email: l...@jguru.se > | URL: www.jguru.se > | Phone > | (skype): jgurueurope > | (intl): +46 708 507 603 > | (domestic): 0708 - 507 603 > +==============================+ > >
