Yep. We can be opinionated, but we should allow others to follow their own opinions (even if they are "wrong")... we just don't have to make it easy!
On Tue 21 Feb 2017 at 22:16, Hervé BOUTEMY <herve.bout...@free.fr> wrote: > Maven tool can't check everything against developper's will: we already > have > bad reputation because we put contraints on the build. > > We can't force people, we can't enforce rules. > > We can define good conventions and ease their use. > > Regards, > > Hervé > > Le mardi 21 février 2017, 03:41:12 CET Christian Schulte a écrit : > > Am 02/19/17 um 04:38 schrieb Hervé BOUTEMY: > > > then I'm not sure checking rules on what is inside an artifact while > > > publishing in Central is the right thing to do: we don't do it > currently > > > (checking that package names are consistent with groupId), then I feel > we > > > should not do it either for module info > > > > If we would have checked that, there would not be this "redundant class > > files on class path coming from different coordinates" issue. > > > > > it's just a basic convention for normal cases, that will be applied > more > > > than 90% of time: and there will be less than 10% of time where > > > discrepency will happen, due to some special cases in code life > > > As usual > > > > Issue with the module names is the same as with the package or > > classnames. They can be deployed to different coordinates and then > > produce conflicts later when consumed. If we can avoid this with module > > names, we should. > > > > Regards, > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > > -- Sent from my phone
