maven-polyglot
Does anyone have any experience with https://www.baeldung.com/maven-polyglot they can share? Cheers, Eric - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: maven-polyglot
Hello, This is probably not what you're looking for, but a colleague and I created this example for an internal training on Apache Maven that we're giving in a regular basis: https://github.com/learning-maven/pom-as-yaml Hope it helps, Florent On Mon, Oct 9, 2023, 23:16 Eric Kolotyluk wrote: > Does anyone have any experience with > https://www.baeldung.com/maven-polyglot they can share? > > Cheers, Eric > > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > >
Re: maven-polyglot
I have looked into maven-polyglot before, and come to the conclusion that it is a proof of concept, and something that few if any people actually use, because: 1. Professional programmers are not actually offended by using XML in the POM, only novices would complain about such a thing. 2. All tooling will expect a pom.xml, e.g. IDEs, CI tools, linters, etc. If any of those things are able to handle a polyglot POM in non-XML, that's a tiny miracle. 3. maven-polyglot gets mentioned when people complain about Maven using XML, as 'look, you don't have to, you can use whatever you want' but no one actually does. 4. The first suspect when something doesn't work right in your build will always be maven-polyglot, because no one uses it, so it's potentially not compatible with every plugin. Then you get to convert back to pom.xml and try again. So better to skip the effort and stay with XML in the first place.
Re: maven-polyglot
Howdy, I am aware for example the JRuby uses polyglot: https://github.com/jruby/jruby AFAIK, not all languages are "same done" or maybe I may risk "same quality", for example JRuby/pom.rb is nicely maintained, unsure for other ones... Thanks T On Mon, Oct 9, 2023 at 11:35 PM Greg Chabala wrote: > I have looked into maven-polyglot before, and come to the conclusion that > it is a proof of concept, and something that few if any people actually > use, because: > >1. Professional programmers are not actually offended by using XML in >the POM, only novices would complain about such a thing. >2. All tooling will expect a pom.xml, e.g. IDEs, CI tools, linters, etc. >If any of those things are able to handle a polyglot POM in non-XML, > that's >a tiny miracle. >3. maven-polyglot gets mentioned when people complain about Maven using >XML, as 'look, you don't have to, you can use whatever you want' but no > one >actually does. >4. The first suspect when something doesn't work right in your build >will always be maven-polyglot, because no one uses it, so it's >potentially not compatible with every plugin. Then you get to convert > back >to pom.xml and try again. So better to skip the effort and stay with > XML in >the first place. >
Re: maven-polyglot
That is a good example of the tradeoffs as well. In several places the pom.rb is forced to generate a pom.xml to satisfy other tooling, as mentioned here: https://github.com/jruby/jruby/blob/047188902e8d1d307d1f9e51d1bdc60ec1d09bc9/BUILDING.md#hacking-the-build-system On Mon, Oct 9, 2023 at 4:49 PM Tamás Cservenák wrote: > Howdy, > > I am aware for example the JRuby uses polyglot: > https://github.com/jruby/jruby > > AFAIK, not all languages are "same done" or maybe I may risk "same > quality", for example JRuby/pom.rb is nicely maintained, unsure for other > ones... > > Thanks > T > > > > On Mon, Oct 9, 2023 at 11:35 PM Greg Chabala > wrote: > > > I have looked into maven-polyglot before, and come to the conclusion that > > it is a proof of concept, and something that few if any people actually > > use, because: > > > >1. Professional programmers are not actually offended by using XML in > >the POM, only novices would complain about such a thing. > >2. All tooling will expect a pom.xml, e.g. IDEs, CI tools, linters, > etc. > > If any of those things are able to handle a polyglot POM in non-XML, > > that's > >a tiny miracle. > >3. maven-polyglot gets mentioned when people complain about Maven > using > >XML, as 'look, you don't have to, you can use whatever you want' but > no > > one > >actually does. > >4. The first suspect when something doesn't work right in your build > >will always be maven-polyglot, because no one uses it, so it's > >potentially not compatible with every plugin. Then you get to convert > > back > >to pom.xml and try again. So better to skip the effort and stay with > > XML in > >the first place. > > >
Re: maven-polyglot
Agreed, Personally, I'd make POM XML (as de facto standard and supported in many tools/apps/libs/etc) mandatory, so it could be: a) you author POM XML (as today in vanilla maven), or b) you author POM in your fave lang (as today in vanilla polyglot) and Maven makes sure POM XML is present and up to date? [this needs maven some internals change] Btw, initial polyglot capabilities have been lifted into Maven 4 as well. HTH Tamas On Tue, Oct 10, 2023 at 12:10 AM Greg Chabala wrote: > That is a good example of the tradeoffs as well. In several places the > pom.rb is forced to generate a pom.xml to satisfy other tooling, as > mentioned here: > > https://github.com/jruby/jruby/blob/047188902e8d1d307d1f9e51d1bdc60ec1d09bc9/BUILDING.md#hacking-the-build-system > > On Mon, Oct 9, 2023 at 4:49 PM Tamás Cservenák > wrote: > > > Howdy, > > > > I am aware for example the JRuby uses polyglot: > > https://github.com/jruby/jruby > > > > AFAIK, not all languages are "same done" or maybe I may risk "same > > quality", for example JRuby/pom.rb is nicely maintained, unsure for other > > ones... > > > > Thanks > > T > > > > > > > > On Mon, Oct 9, 2023 at 11:35 PM Greg Chabala > > wrote: > > > > > I have looked into maven-polyglot before, and come to the conclusion > that > > > it is a proof of concept, and something that few if any people actually > > > use, because: > > > > > >1. Professional programmers are not actually offended by using XML > in > > >the POM, only novices would complain about such a thing. > > >2. All tooling will expect a pom.xml, e.g. IDEs, CI tools, linters, > > etc. > > >If any of those things are able to handle a polyglot POM in non-XML, > > > that's > > >a tiny miracle. > > >3. maven-polyglot gets mentioned when people complain about Maven > > using > > >XML, as 'look, you don't have to, you can use whatever you want' but > > no > > > one > > >actually does. > > >4. The first suspect when something doesn't work right in your build > > >will always be maven-polyglot, because no one uses it, so it's > > >potentially not compatible with every plugin. Then you get to > convert > > > back > > >to pom.xml and try again. So better to skip the effort and stay with > > > XML in > > >the first place. > > > > > >
Re: maven-polyglot
Excellent response... thanks.
Poking around, I appreciate your POC comment the most. I will only use
maven-polyglot in my recreational programming as a learning experience
until there becomes some compelling advantage otherwise.
1. good point... I concur
2. good point... yes, understandable synergy problems
3. good point... yes, many people claim things are easier, better than
they really are
4. good point... yes, the sophistication of our tools increasingly
makes diagnostics and troubleshooting more difficult
Working in a Gradle shop, many of these points also apply to my
frustration with Gradle, and SBT from previous shops...
Cheers, Eric
On 2023-10-09 2:35 p.m., Greg Chabala wrote:
I have looked into maven-polyglot before, and come to the conclusion that
it is a proof of concept, and something that few if any people actually
use, because:
1. Professional programmers are not actually offended by using XML in
the POM, only novices would complain about such a thing.
2. All tooling will expect a pom.xml, e.g. IDEs, CI tools, linters, etc.
If any of those things are able to handle a polyglot POM in non-XML, that's
a tiny miracle.
3. maven-polyglot gets mentioned when people complain about Maven using
XML, as 'look, you don't have to, you can use whatever you want' but no one
actually does.
4. The first suspect when something doesn't work right in your build
will always be maven-polyglot, because no one uses it, so it's
potentially not compatible with every plugin. Then you get to convert back
to pom.xml and try again. So better to skip the effort and stay with XML in
the first place.
