3 ms·

Java doesn't come with a package manager out of the box so most projects seem to go with Maven. If you've tried to understand a project with multiple pom.xml's

Java doesn't come with a package manager out of the box so most projects seem to go with Maven. If you've tried to understand a project with multiple pom.xml's then for me putting it in the con is a good call.

dotdi 7y ago
While this is true, it's not an inherent problem of maven, it's an inherent problem of dependency management is f*cking difficult™.
- coldtea 7y ago
  Maven is inherently bad too, though
  - edejong 7y ago
    In which way exactly? Having worked with many, many different package managers, I've come to appreciate Maven's way of doing things. Even though it has many drawbacks: - XML structure is verbose - Plugin architecture makes standard behaviour opaque - Default HTTP with no package signatures is recipe for security problems - "Stages" seem arbitrary and it's not always clear which stages are performed. - Community seems to move to newer systems such as Gradle (and SBT for Scala). But, there are also strengths. The configuration format can be extended easily using the plugin architecture. This provides a huge opportunity to extend the functionality. It is battle hardened over time, which means it is very stable and it has a huge plugin architecture.
    - coldtea 7y ago
      Well, I think you've covered the issues I was going to mention!
mister_hn 7y ago
and Maven is super bloated due to too many downloaded dependencies. An Hello World example with Maven can download up to 50MB of plugins and useless things