On Tue, Oct 22, 2019 at 19:02, Mark H. Wood <[email protected]> wrote: > On Tue, Oct 22, 2019 at 09:34:46PM +0100, Paul Hammant wrote: > > Maven's XML is too element normal for my liking. Attributes where > > appropruate would be good. > > Yes. But changing now would be quite a wrench, even with tools to > translate the old dialect to the new. A lot of other code also > understands POM documents nowadays.
Feels like it’s something that could be achieved with a bump in the pom version to support the changes. As an interchange format in maven repos i think you’d still want the maximally supported current version but for dev it would be a nice option. > > Also deps and GAVs needs a shakeup, IMO: > > > > <deps> > > <compile> > > <dep>com.thoughtworks.xstream:xsteam:1.4.3</dep> > > </compile> > > <test> > > <dep>org.junit:junit:4.12</dep> > > <dep>org.seleniumhq.selenium:selenium-java:3.14159</dep> > > </test> > > Please, no. <dependency group='org.junit' artifact='junit' > version='4.12'/> > perhaps. > > > Not being able to grep for specific GAVs is a critical flaw. > > Wrong tool. grep is for text, not structured documents. Try XQuery. Personally I prefer the tool at hand even if not perfect. If I’m diagnosing a problem on CI I would prefer not to be distracted by rabbit holes. Its rare to work directly with XML these days so it adds both the burden of getting the tool and remembering the syntax to extract what you want. The compact notation would easily work with grep and is already employed by a number of other build tools (gradle, buildr, bazel). It’s still the coordinate but the component parts aren’t as granular. > But this is wandering away from "how can we avoid rebuilding unchanged > stuff?" > > -- > Mark H. Wood > Lead Technology Analyst > > University Library > Indiana University - Purdue University Indianapolis > 755 W. Michigan Street > Indianapolis, IN 46202 > 317-274-0749 > www.ulib.iupui.edu > -- Nathan Fisher w: http://junctionbox.ca/
