My understanding is that there has been some strong pushback about
supporting additional languages from the community.
Did I misunderstood ? I don't mind the location, so if I need to put
it elsewhere, that's not a problem.
Technically, the extension I wrote the past days is better, as it
support
On Thu, 13 Mar 2025 at 22:14, Guillaume Nodet wrote:
>
> FYI, I came up with the following extension:
> https://github.com/maveniverse/mason
What status will be of the project
https://github.com/apache/maven-hocon-extension as you implement
something similar somewhere else ...
>
> A first 0.1.
FYI, I came up with the following extension:
https://github.com/maveniverse/mason
A first 0.1.0 has been released, so you're welcome to try it out.
It supports Yaml, Json, Hocon (with a custom parser) and Toml (limited
as it has no location tracking).
Le mer. 5 mars 2025 à 17:16, Guillaume Node
I'm well aware of the Takari Polyglot project. However I don't want to
spend time to rewrite it all to Maven 4. The Maven 4 architecture allows a
much better support for additional syntaxes by leveraging a new clear SPI
and the fact that we have the consumer POM and build POM. The build POM is
t
I see the interest of improving maintainability of build POM beyond what has
already been
achieved with inference (did I say I loved your presentation [4] and this term?)
But as already expressed, I fear the risk of confusion and time taken...
Your approach of not just discussing but providing
but it would also mean IDE which will stay the main blocker
for adoption
m2e already support polyglot extension because it uses mavens
model-reader to read the "real" pom so there is no need for an IDE to
adopt to every format.
Beside that, as polyglot is already there [1], why not put it in
Hi,
-1 from me.
It has nothing to do with all the things you can dislike about YAML.
It's a matter of what we spend our time on.
I don't think we should invest too much effort in having additional
formats for the POM in Maven itself. We now have one format (XML) for
the POM. This, together
Nice work! However, if may clash, it's used differently in executions.
Better use g:, a: and v:, and other fields instead of one long id. Makes
updates easier, too, as well as scrolling through the document.
What do you think?
Otherwise, like tamas said: go for it. I also like the idea of creating
I agree that yaml is not great. It's just too easy to make mistakes with a
space in the wrong place.
Gary
On Wed, Mar 5, 2025, 15:17 Elliotte Rusty Harold wrote:
> Please no. YAML is a utter mess full of sharp edges to hurt the
> unwary. It's poorly understood, poorly specified, and poorly
> do
Guess the main question is what do we do of all extensions, we can maybe
create a maven-extension-proposal repo and put all the draft and tests
there and promote them to top level repo if users adopt it (but it would
also mean IDE which will stay the main blocker for adoption IMHO).
In terms of fo
Please no. YAML is a utter mess full of sharp edges to hurt the
unwary. It's poorly understood, poorly specified, and poorly
documented. It's not clear there are any confomrant parsers or indeed
that the concept of conformance even makes sense for something so ill
specified. If you must have somet
Looks good! Thanks a lot for sharing.
I am wondering whether this should rather be based on SnakeYaml Engine (YAML
1.2 processor) instead of the legacy SnakeYaml (YAML 1.1).
Also I am wondering if you disable deserialisation of potentially dangerous
YAML (compare with https://en.wikipedia.org/wi
Good to know https://github.com/takari/polyglot-maven.
Just my two cents: I often find YAML easy to be wrong due to its
implicit type conversion (1.20 cam be "1.2", while 1.19 can be "1.19")
and indents changing meaning. In the Cargo ecosystem, we use TOML to
describe build logic, and it works ver
+1 go for it!
On Wed, Mar 5, 2025, 17:17 Guillaume Nodet wrote:
> Hey !
>
> A while ago, I created a Hocon based POM parser [1], leveraging Maven
> 4 new capabilities to support new syntaxes for POMs.
> However, as much as that syntax seems interesting, I've been pointed
> that it's not really s
I assume you are also aware of the yaml support in Polyglot Maven
https://github.com/takari/polyglot-maven
Feel free to check that out and pull relevant bits for it all to go
upstream.
Manfred
On 2025-03-05 8:16 a.m., Guillaume Nodet wrote:
Hey !
A while ago, I created a Hocon based POM pa
Hey !
A while ago, I created a Hocon based POM parser [1], leveraging Maven
4 new capabilities to support new syntaxes for POMs.
However, as much as that syntax seems interesting, I've been pointed
that it's not really supported. So I never actually released it.
But I'd still like to get out a new
16 matches
Mail list logo
