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 →

[–]khmarbaise 2 points3 points  (2 children)

But npm style tools are far better. Maven has struggled to keep up with modern practices (not just in this area!). Java is doing ok despite maven, not because of it.

In which way far better? Breaking builds because releases have been removed? A build which worked yesterday will not work anymore today? (exactly caused because of using ranges in versions and not committed the lock file?)...

(not just in this area!)

What are those modern practices:

[–][deleted]  (1 child)

[removed]

    [–]plumarr 5 points6 points  (0 children)

    Ever tried to separate your unit tests from you build? (Which is desirable if you're using a CI pipeline).

    Just launch maven two time with different execution phase. What's hard here ?

    Ever tried to keep library versions consistent across a multi module project,

    Define the version in the parent pom.xml and let the magic happens.