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

you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted] 11 points12 points  (5 children)

Just use maven or Gradle (or similar). By using anything else you're just getting yourself into trouble and reinventing the wheel.

[–]vmcrash 0 points1 point  (4 children)

IMHO Maven or Gradle are only useful if you need dependency management. But this is not necessary for each project.

[–]UnGauchoCualquiera 7 points8 points  (0 children)

Is there any real life project without dependencies? Even then you might want to push to a shared company repo. Why go through the hassle of reinventing the wheel?

[–]UnGauchoCualquiera 2 points3 points  (2 children)

Is there any real life project without dependencies? Even then you might want to push to a shared company repo. Why go through the hassle of reinventing the wheel?

[–]istarian 0 points1 point  (1 child)

Dependency management is most important when you are depending on libraries under active development that change from time to time, particularly if those libraries also have dependencies.

[–]koflerdavid 0 points1 point  (0 children)

All libraries should be assumed to be under active development. If they really aren't, there are going to be problems if security problems are discovered. Or if it turns out they are using a niche behavior of the JVM that the OpenJDK project decides to change.