First, you are right... I misread. When I look at the maven plugins in
pluginManagement I see v2 and v3: clean=3.1.0, compiler=3.8.1,
surefire=2.22.1, jar=3.0.2, install=2.5.2, deploy=2.8.2, site=3.7.1,
project-info-reports=3.0.0. Still, it is > 2.0 so LATEST is no longer
supported as a
It became very clear to me that my current approach of googling
tutorials, guides and solutions is a wildly inadequate approach to learn
Maven. Mainly because all of those are either far too basic for "real
life" projects, or because they assume prior knowledge that I don't yet
have.
So, I
:33 AM, Bruno Melloni wrote:
I wrote and used a custom library that includes some log4j aware
classes. Was working perfectly when built as a standard Java JAR. I
am converting the POM to rely on a few Spring Boot starters as a way
to simplify it.
All went well until I run "Maven In
I wrote and used a custom library that includes some log4j aware
classes. Was working perfectly when built as a standard Java JAR. I am
converting the POM to rely on a few Spring Boot starters as a way to
simplify it.
All went well until I run "Maven Install", when I got the following
Given that the whole point of using Maven is to "not have to worry about
dependencies" I am having the most ironic (and probably trivial) problem:
- Using Maven in Eclipse.
- I wrote a very simple utility. It builds as part of a JAR that will
normally be used by other apps, but this utility
