I'm not sure what problem this is trying to solve. How is it intended to use the facility?
On Tue, 4 Jun 2019 at 17:35, Matt Sicker <boa...@gmail.com> wrote: > > This sounds like a shade feature, yes. However, in order to > automatically extract the version extra data and detect a version > keyword like "alpha" may require some additional code, though maybe > the shade plugin already supports that. > > Alternatively, JUnit 5.x uses a tool called API Guardian for marking > which APIs are stable or not: > https://github.com/apiguardian-team/apiguardian > > On Tue, 4 Jun 2019 at 05:53, Gilles Sadowski <gillese...@gmail.com> wrote: > > > > Hello. > > > > Does someone see a practical way to automate package names > > and source files conversions so that each all alpha/beta releases > > can be used together (e.g. to compare their behaviours). > > > > I mean, for release version "1.0-alpha1", the top-level package > > name "o.a.c.compid" would be turned into "o.a.c.compid.alpha1". > > > > This would also solve issues with compatibility checkers (with the > > added bonus that JAR hell could never happen). > > > > Couldn't the "shade" plugin be put to use (so that all artefacts have > > their top-level package transparently set to "o.a.c.compid.alpha1" > > and all the tools operate on that)? > > > > > > Regards, > > Gilles > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > > For additional commands, e-mail: dev-h...@commons.apache.org > > > > > -- > Matt Sicker <boa...@gmail.com> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
