Hi,
I'm trying to show dependency conflicts using "mvn dependency:tree
-Dverbose -Dincludes=commons-collections" as described in the
documentation[1]. Unfortunately, this gives the following error:
"Verbose not supported since maven-dependency-plugin 3.0"
I tested it with Maven 3.3.9 and
On 11-09-18 10:56, Nicolas Peifer wrote:
Hi,
I'm trying to show dependency conflicts using "mvn dependency:tree
-Dverbose -Dincludes=commons-collections" as described in the
documentation[1]. Unfortunately, this gives the following error:
"Verbose not supported since maven-dependency-plugin
On 11.09.2018 12:36, Mark Prins wrote:
On 11-09-18 10:56, Nicolas Peifer wrote:
I'm trying to show dependency conflicts using "mvn dependency:tree
-Dverbose -Dincludes=commons-collections" as described in the
documentation[1]. Unfortunately, this gives the following error:
"Verbose not
>
> It is configured on the maven-compiler-plugin [1].
Do you mean archetype depends on maven-compiler-plugin? So, how can I use a
specific JDK version when I create a new project with archetype?
Bruce Wen
On Mon, Sep 10, 2018 at 2:20 PM Anders Hammar wrote:
> The Java version is decided by
The archetype is a template which either does explicitly configure
maven-compiler-plugin with a Java version. Or if not, the default (for the
used version of maven-compiler-plugin) value is used.
In either case, you can after the Maven project has been generated change
the Java version to a
Yes.
A Maven project generated by an archetype typically needs some tweaking to
fit your needs.
/Anders
On Tue, Sep 11, 2018 at 4:28 PM Bruce Wen wrote:
> >
> > In either case, you can after the Maven project has been generated change
> > the Java version to a version of your choice.
>
>
>
We need your help to make the Apache Washington DC Roadshow on Dec 4th a
success.
What do we need most? Speakers!
We're bringing a unique DC flavor to this event by mixing Open Source
Software with talks about Apache projects as well as OSS CyberSecurity,
OSS in Government and and OSS Career
Either change the artifact (if you can) so it generates a pom.xml with the
appropriate source/target version [1], or indeed change the project pom.xml
(after it's been generated by the archetype)
[1] and possibly a profile for JDK 9+ that uses , assuming the
target is <= 8; otherwise use instead
>
> In either case, you can after the Maven project has been generated change
> the Java version to a version of your choice.
Does that mean I have to do the change *AFTER *the project was generated?
On Tue, Sep 11, 2018 at 1:48 PM Anders Hammar wrote:
> The archetype is a template which
