A very rough cut at supporting HOCON is available at
https://github.com/gnodet/maven-hocon-extension. It currently requires
https://github.com/gnodet/maven/tree/polyglot (mainly to add the maven
model as an attached artifact during the build so that it can be consumed
by the hocon parser generator)
Maybe let's stabilize XML and ensure we can make it evolving properly in
time before supporting any other format which will impact negatively the
ecosystem IMHO since a lot of descriptor parsers are not org.apache.maven
(which is a very good thing IMHO, means we have a portable enough format to
be
So perhaps it is easier to translate other formats to XML instead of adding
support directly to the main code. My idea wasn't so much to replace XML,
rather it was to translate other formats to XML and then use the existing XML
implementations. I think that makes the work easier without impac
Please note that Tycho uses polyglot very extensively (and develop it
actively), so please don't assume it is "dead" just because you are not
aware of its usages!
For me using XML or JSON or ... for THE SAME THING does not add much
value, but Tycho extends polyglot to the extend of deriving ma
Dead by its usage by end users, was abandonned years ago by its dzv, then
reudated then re etc.didnt say nobody uses it, just it is not sane for
us probably to absorb such project.
Issue with conversion the one mentionned: you need to run anything before
loading it, -1 if an ide or any tool ca
Mmh ,thé XML has not been really modified since maven 3.0, so I think it's
quite stable now :-)
Le mer. 7 juin 2023, 18:06, Romain Manni-Bucau a
écrit :
> Maybe let's stabilize XML and ensure we can make it evolving properly in
> time before supporting any other format which will impact negative
Le mer. 7 juin 2023 à 19:24, Guillaume Nodet a écrit :
> Mmh ,thé XML has not been really modified since maven 3.0, so I think it's
> quite stable now :-)
>
Im happy with that Guillaume but would mean we dont add all the
attributes/tags you want - this is the part I'd like to stabilize, how we
c
I can answer the question about why HOCON. 1) it has nice syntax, 2) you can
use values in any part, in any other part which means you don't have to write
the plugin name's 3 or 4 times unnecessarily (which you can do only with
properties currently) and 3) because you can include external docu
Fully got it Hunter...but this has the same yaml pitfall: designed for
human, not embraced as much as planned (thanks k8s to showed it)...you
would also note that all that is doable in xml so question remains: how
much do we want to break our ecosystem?
Personally I'd love the main core descriptor
Big +1 for an alternative format, but not sure HOCON is the best of all
those out there.
It surely is one of the better ones, though.
Big plus is easiness to humans, no deps, external docs.
However, TOML gained some popularity. I'd say Maven should ship no more
than one alternative to XML. And w
10 matches
Mail list logo