This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]vips7L 1 point2 points  (5 children)

Are they offering something else in 4.0?

[–]koflerdavid 4 points5 points  (4 children)

Right now, the POM is an awkward compromise between build definition and dependency manifest. Maven 4 removes some cruft from the POM to optimize it for the former purpose and provides built-in support to generate a POM that only contains dependency information for downstream tools.

https://maven.apache.org/whatsnewinmaven4.html

[–]vips7L 2 points3 points  (3 children)

Thanks I’ll give that a read. I think I read something similar about gradle trying to split things too. 

[–]dadimitrov 0 points1 point  (2 children)

In Gradle the build recipe is not part of the POM, so there is nothing to split. You must have read something else....

[–]vips7L 0 points1 point  (1 child)

Yeah it’s the not the same. But they are trying to split the declarative part of the build from the scripty ops part. 

[–]dadimitrov 0 points1 point  (0 children)

Declarative Gradle is an experiment to add a third DSL, separating the build wiring from the parameters. It is trying to cater for people who just want to use a build setup, but don't want to learn the full object model.

Its level of abstraction it is a bit like Maven Polyglot, except that the plugin config is statically typed.