polyglot-maven

With Polyglot Maven, you don't even need it in Maven either! https://github.com/takari/polyglot-maven

As the most extreme counterexample of your ... experience[1], someone made a plugin that allowed writing pom files in languages other than XML: https://github.com/takari/polyglot-maven/tree/polyglot-0.7.2... With an especial nod to https://github.com/takari/polyglot-maven/tree/polyglot-0.7.2... given this submission 1: I believe that you encountered errors, programming is packed to the gills with them, but correlation is not causation in that just because it did not immediately work in your setup does not mean it's impossible or forbidden

Yeah, some kind people over Reddit also shared some nice repositiories like this one: https://github.com/takari/polyglot-maven Which would have been great if I found it earlier, since it allows you to use maven but write Java. The only edge 1JPM has compared to that project is that auto-complete and even more advanced features of your IDE work with it, since you can also move your JPM.java file into ./src/main/java.

And with Polyglot Maven [1] you don't even have to deal with all the XML markup either. [1] - https://github.com/takari/polyglot-maven

And you don't even need to use XML with Polyglot Maven https://github.com/takari/polyglot-maven

It seems merely adding a file to the .mvn directory will do as you wish: https://github.com/takari/polyglot-maven#usage I have avoided that road because it's one more thing that is a snowflake in the very area where I don't want to blazing trails. But I have personally tried their approach before and can confirm it does work as advertised. I can't recall if IJ lost its mind over pulling a stunt like that, but arguably if it did, then filing a YouTrack is an appropriate next step

You could do something like that with polygot-maven. https://github.com/takari/polyglot-maven

> Maven is very unpleasant because of its declarative XML language Maven was intended to be configured via a GUI. If you want to configure it directly, try Polyglot Maven at https://github.com/takari/polyglot-maven which is a very light wrapper around Maven enabling you to use many other languages instead, e.g. Scala, Clojure, and Ruby as well as Apache Groovy. The Gradle people marketed their product by slagging the XML which was never intended to be directly manipulated by humans. If you really want to use Gradle (and get a coffee whenever it builds something), it also lets you use Kotlin for writing build files.

The Maven POM syntax might look bloaty to modern post-XML eyes, but it's not actually complicated: a typical POM only specifies the name of the project and its dependencies. The rest is typically all done by convention. It's also purely declarative so ordering doesn't matter. M4 and sh are very concise languages. Nonetheless autotools is orders of magnitude more complex than Maven. You really can't compare at all. At any rate, if you want a more concise syntax there is gradle (but it's a bit slower as it's actually executing a real scripting language) and, perhaps a nice middle ground, a thing called Polyglot Maven which is the same build engine but with a variety of non-XML syntaxes. The YAML one is quite nice: https://github.com/takari/polyglot-maven/blob/master/poms/po... That way you get simple syntax and a simple model, but still wit

You can use the maven polyglot plugin [1] to write your POM in something other than XML. It's fairly new, but it's there. We use it in JRuby to write our POMs in Ruby. As an example of a loop: https://github.com/jruby/jruby/blob/8e29ae1302e7aa989b8808f7... [1] -- https://github.com/takari/polyglot-maven

You can use Polyglot-Maven [1] with Maven if you want to use a programming language syntax atop the XML. Polyglot-Maven enables not only Groovy, but also Ruby, Clojure, or Scala to be used with Maven. [1] https://github.com/takari/polyglot-maven

Because Maven (the tool) offers XML as the language, we can put any other language atop it, e.g. with https://github.com/takari/polyglot-maven we can use Clojure, Groovy, Ruby, or Scala as the language. Gradle offers only Groovy, nothing else, so we don't have any choice over how to interact with the build API.

> Android Studio and the Gradle plugin are really, really coming along Too bad Gradle only allows us to use one language (i.e. Groovy) to configure the builds. Because Maven uses generic XML, any language can sit atop it. E.g. Polyglot Maven [1] not only allows us to use Groovy, but also Clojure, Scala, and Ruby to configure its builds. [1] https://github.com/takari/polyglot-maven

"Groovy" isn't mentioned even once on this page. Are the Gradle people embarrassed about their sole offering of Groovy for the build DSL? Because Maven uses XML, any programming language can sit on top and be used as a configuration DSL. https://github.com/takari/polyglot-maven not only offers Groovy, but also Clojure, Scala, and Ruby.

> Will Groovy survive outside of Gradle? It might not survive even inside of Gradle. As Gradle becomes more popular, I can't imagine Groovy remaining the only scripting language available for Gradle build scripts. Virtually all serious software offers a choice of scripting languages for configuration, e.g. Maven which can be configured not only with Groovy but also Clojure, Scala, and Ruby, see https://github.com/takari/polyglot-maven . Gradle 2.0 has virtually no Groovy code in its codebase, only what was essential for hosting Groovy for build scripts, so that might give a clue about their future intentions. One snag may be the retrenched Groovy programmer employed by Gradleware after VMware/Pivotal abandoned Groovy: he might sabotage any effort by Gradleware to diversify from Groovy as a scripting language for Gradle builds.