[ANN] Maven Indexer 6.2.0 released

2022-05-05 Thread Tamás Cservenák
Howdy,

The Apache Maven Team is pleased to announce the release of the Maven
Indexer version 6.2.0.

Most notable changes:
- IndexReader provides OOTB resource handlers
- Search API w/ 2 backends
- Bugs squashed

IMPORTANT: Next release planned will use the Lucene version to 9.x, and
that will imply Java 11. Hence, this is the LAST planned Java 8 release of
Maven Indexer.

Site: https://maven.apache.org/maven-indexer/


  org.apache.maven.indexer
  indexer-core
  6.2.0



Release Notes - Maven Indexer - Version 6.2.0
** Bug
* [MINDEXER-121] - ChunkReaderIterator leaks InputStreams
* [MINDEXER-144] - IndexOutOfBoundsException during indexing
* [MINDEXER-146] - Fix issues reported by Lucene 9
** New Feature
* [MINDEXER-124] - IndexReader modules should provide resource handler
implementations
* [MINDEXER-143] - Introduce Search API and provide backends
** Task
* [MINDEXER-145] - Update parent POM and dependencies
* [MINDEXER-147] - Move rootGroups and allGroups fields out of index
* [MINDEXER-149] - Deprecate Maven1 support


Have fun,
-The Apache Maven Team


Maven Reactor and plugin "local" dependencies

2022-05-05 Thread Florent Biville
Hello everyone,

TL;DR? https://github.com/fbiville/mvn-plugin-dependency-reactor-issue

I recently noticed that, within the big multi-module project of my company,
a specific module is listed as a dependency to plugins such as Maven
Checkstyle plugin or com.mycila:license-maven-plugin.

The problem occurs when I try one of these plugins against another specific
module.
Maven CLI will basically complain that it cannot resolve the module needed
by the plugin and fail, even if I explicitly list that module in the
project list.

That occurs both with Maven 3 and 4.

The obvious workaround is to install the required module first and then run
the plugin but I'm trying to get rid of the need for `mvn install` entirely.

Is there a particular reason plugin dependencies are not considered by
Maven Reactor?
Is module-as-plugin-dependency a Maven antipattern?

Thanks a lot for your help!
Florent


Problem with an Maven Build

2022-05-05 Thread Nelligan, Steven M
Please any assistance would be appreciated
 
Building a maven project is getting the following error(s)
 I have not changed anything in the project, so I assume something changed in 
the repositories
How can I get this project built?

INFORMATION FOLLOWS:

__
I am running maven version 3.6.3:
   C:\dev\projects\muleextcharge>mvn -version
Apache Maven 3.6.3 (cecedd343002696d0abb50b32b541b8a6ba2883f)
Maven home: C:\Program Files\apache-maven-3.6.3\bin\..
Java version: 1.7.0_80, vendor: Oracle Corporation, runtime: C:\Program 
Files\Java\jdk1.7.0_80\jre
Default locale: en_US, platform encoding: Cp1252
OS name: "windows 8.1", version: "6.3", arch: "amd64", family: "windows"

__
While building I get the following error (if I run maven with dependency:tree, 
surefire does NOT show in the tree)
C:\dev\projects\muleextcharge>mvn -P vDev2 clean install -U 
-Dmaven.test.skip=true
[INFO] Scanning for projects...
[INFO]
[INFO] -< edu.uiuc.fs:muleextcharge 
>--
[INFO] Building Mule Muleextcharge Application 1.0.0
[INFO] [ mule 
]
Downloading from java.net-Public: 
https://maven.java.net/content/groups/public/org/apache/maven/plugins/maven-resources-plugin/maven-metadata.xml
Downloading from central: 
https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-resources-plugin/maven-metadata.xml
Downloaded from central: 
https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-resources-plugin/maven-metadata.xml
 (874 B at 1.6 kB/s)
Downloading from java.net-Public: 
https://maven.java.net/content/groups/public/org/apache/maven/plugins/maven-surefire-plugin/maven-metadata.xml
Downloading from central: 
https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-surefire-plugin/maven-metadata.xml
Downloaded from central: 
https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-surefire-plugin/maven-metadata.xml
 (1.9 kB at 25 kB/s)
Downloading from central: 
https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-deploy-plugin/maven-metadata.xml
Downloading from java.net-Public: 
https://maven.java.net/content/groups/public/org/apache/maven/plugins/maven-deploy-plugin/maven-metadata.xml
Downloaded from central: 
https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-deploy-plugin/maven-metadata.xml
 (783 B at 14 kB/s)
[INFO]
[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ muleextcharge 
---
[INFO] Deleting C:\dev\projects\muleextcharge\target
[INFO]
[INFO] --- maven-mule-plugin:1.9:attach-test-resources 
(default-attach-test-resources) @ muleextcharge ---
[INFO] attaching test resource 
C:\dev\projects\muleextcharge\src\main\app
[INFO]
[INFO] --- maven-resources-plugin:3.2.0:resources (default-resources) @ 
muleextcharge ---
[INFO] Using 'Cp1252' encoding to copy filtered resources.
[INFO] Using 'Cp1252' encoding to copy filtered properties files.
[INFO] Copying 0 resource
[INFO]
[INFO] --- maven-mule-plugin:1.9:filter-resources 
(default-filter-resources) @ muleextcharge ---
[INFO]
[INFO] --- maven-compiler-plugin:3.1:compile (default-compile) @ 
muleextcharge ---
[INFO] Nothing to compile - all classes are up to date
[INFO]
[INFO] --- maven-resources-plugin:3.2.0:testResources 
(default-testResources) @ muleextcharge ---
[INFO] Not copying test resources
[INFO]
[INFO] --- maven-compiler-plugin:3.1:testCompile (default-testCompile) 
@ muleextcharge ---
[INFO] Not compiling test sources
[INFO]
[INFO] --- maven-surefire-plugin:3.0.0-M6:test (default-test) @ 
muleextcharge ---
[WARNING] Error injecting: 
org.apache.maven.plugin.surefire.SurefirePlugin
java.lang.TypeNotPresentException: Type 
org.apache.maven.plugin.surefire.SurefirePlugin not present
at org.eclipse.sisu.space.URLClassSpace.loadClass 
(URLClassSpace.java:147)
at org.eclipse.sisu.space.NamedClass.load (NamedClass.java:46)
at org.eclipse.sisu.space.AbstractDeferredClass.get 
(AbstractDeferredClass.java:48)
at com.google.inject.internal.ProviderInternalFactory.provision 
(ProviderInternalFactory.java:85)
at 
com.google.inject.internal.InternalFactoryToInitializableAdapter.provision 
(InternalFactoryToInitializableAdapter.java:57)
at com.google.inject.internal.ProviderInternalFactory$1.call 
(ProviderInternalFactory.java:66)
at

Re: Problem with an Maven Build

2022-05-05 Thread Antoine Mottier
Starting with version 3.0.0-M6 maven-surefire-plugin requires Java 8  
or higher. As you are running it using Java 7 this explains your issue.


You can either get back to version 3.0.0-M5 or upgrade to a newer  
version of Java.


Regards,
--
Antoine Mottier

"Nelligan, Steven M"  a écrit :


Please any assistance would be appreciated

Building a maven project is getting the following error(s)
 I have not changed anything in the project, so I assume something  
changed in the repositories

How can I get this project built?

INFORMATION FOLLOWS:

__
I am running maven version 3.6.3:
   C:\dev\projects\muleextcharge>mvn -version
Apache Maven 3.6.3 (cecedd343002696d0abb50b32b541b8a6ba2883f)
Maven home: C:\Program Files\apache-maven-3.6.3\bin\..
Java version: 1.7.0_80, vendor: Oracle Corporation, runtime:  
C:\Program Files\Java\jdk1.7.0_80\jre

Default locale: en_US, platform encoding: Cp1252
OS name: "windows 8.1", version: "6.3", arch: "amd64",  
family: "windows"


__
While building I get the following error (if I run maven with  
dependency:tree, surefire does NOT show in the tree)
	C:\dev\projects\muleextcharge>mvn -P vDev2 clean install -U  
-Dmaven.test.skip=true

[INFO] Scanning for projects...
[INFO]
	[INFO] -< edu.uiuc.fs:muleextcharge  
>--

[INFO] Building Mule Muleextcharge Application 1.0.0
	[INFO] [ mule  
]
	Downloading from java.net-Public:  
https://maven.java.net/content/groups/public/org/apache/maven/plugins/maven-resources-plugin/maven-metadata.xml
	Downloading from central:  
https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-resources-plugin/maven-metadata.xml
	Downloaded from central:  
https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-resources-plugin/maven-metadata.xml (874 B at 1.6  
kB/s)
	Downloading from java.net-Public:  
https://maven.java.net/content/groups/public/org/apache/maven/plugins/maven-surefire-plugin/maven-metadata.xml
	Downloading from central:  
https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-surefire-plugin/maven-metadata.xml
	Downloaded from central:  
https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-surefire-plugin/maven-metadata.xml (1.9 kB at 25  
kB/s)
	Downloading from central:  
https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-deploy-plugin/maven-metadata.xml
	Downloading from java.net-Public:  
https://maven.java.net/content/groups/public/org/apache/maven/plugins/maven-deploy-plugin/maven-metadata.xml
	Downloaded from central:  
https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-deploy-plugin/maven-metadata.xml (783 B at 14  
kB/s)

[INFO]
[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ muleextcharge 
---
[INFO] Deleting C:\dev\projects\muleextcharge\target
[INFO]
	[INFO] --- maven-mule-plugin:1.9:attach-test-resources  
(default-attach-test-resources) @ muleextcharge ---

[INFO] attaching test resource 
C:\dev\projects\muleextcharge\src\main\app
[INFO]
	[INFO] --- maven-resources-plugin:3.2.0:resources  
(default-resources) @ muleextcharge ---

[INFO] Using 'Cp1252' encoding to copy filtered resources.
[INFO] Using 'Cp1252' encoding to copy filtered properties files.
[INFO] Copying 0 resource
[INFO]
	[INFO] --- maven-mule-plugin:1.9:filter-resources  
(default-filter-resources) @ muleextcharge ---

[INFO]
	[INFO] --- maven-compiler-plugin:3.1:compile (default-compile) @  
muleextcharge ---

[INFO] Nothing to compile - all classes are up to date
[INFO]
	[INFO] --- maven-resources-plugin:3.2.0:testResources  
(default-testResources) @ muleextcharge ---

[INFO] Not copying test resources
[INFO]
	[INFO] --- maven-compiler-plugin:3.1:testCompile  
(default-testCompile) @ muleextcharge ---

[INFO] Not compiling test sources
[INFO]
	[INFO] --- maven-surefire-plugin:3.0.0-M6:test (default-test) @  
muleextcharge ---

[WARNING] Error injecting: 
org.apache.maven.plugin.surefire.SurefirePlugin
	java.lang.TypeNotPresentException: Type  
org.apache.maven.plugin.surefire.SurefirePlugin not present

at org.eclipse.sisu.space.URLClassSpace.loadClass 
(URLClassSpace.java:147)
at org.eclipse.sisu.space.NamedClass.load (NamedClass.java:46)
		at org.eclipse.sisu.space.AbstractDeferredClass.get  
(AbstractDeferredClass.java:48)
		at com.google.inject.internal.ProviderInternalFactory.provision  
(ProviderInternalFactory.java:85)
		at  
com.google.inject.internal.InternalFactoryToInitializableAdapter.provision  
(InternalFactoryToIn

Re: Problem with an Maven Build

2022-05-05 Thread Tibor Digana
It should not be any issue if you switch to JDK8 and add maven sniffer
plugin along with compiler 1.7.
T

Dňa št 5. 5. 2022, 16:00 Antoine Mottier 
napísal(a):

> Starting with version 3.0.0-M6 maven-surefire-plugin requires Java 8
> or higher. As you are running it using Java 7 this explains your issue.
>
> You can either get back to version 3.0.0-M5 or upgrade to a newer
> version of Java.
>
> Regards,
> --
> Antoine Mottier
>
> "Nelligan, Steven M"  a écrit :
>
> > Please any assistance would be appreciated
> >
> > Building a maven project is getting the following error(s)
> >  I have not changed anything in the project, so I assume something
> > changed in the repositories
> > How can I get this project built?
> >
> > INFORMATION FOLLOWS:
> >
> >
> __
> > I am running maven version 3.6.3:
> >C:\dev\projects\muleextcharge>mvn -version
> > Apache Maven 3.6.3 (cecedd343002696d0abb50b32b541b8a6ba2883f)
> > Maven home: C:\Program Files\apache-maven-3.6.3\bin\..
> > Java version: 1.7.0_80, vendor: Oracle Corporation, runtime:
> > C:\Program Files\Java\jdk1.7.0_80\jre
> > Default locale: en_US, platform encoding: Cp1252
> > OS name: "windows 8.1", version: "6.3", arch: "amd64",
> > family: "windows"
> >
> >
> __
> > While building I get the following error (if I run maven with
> > dependency:tree, surefire does NOT show in the tree)
> >   C:\dev\projects\muleextcharge>mvn -P vDev2 clean install -U
> > -Dmaven.test.skip=true
> >   [INFO] Scanning for projects...
> >   [INFO]
> >   [INFO] -< edu.uiuc.fs:muleextcharge
> > >--
> >   [INFO] Building Mule Muleextcharge Application 1.0.0
> >   [INFO] [ mule
> > ]
> >   Downloading from java.net-Public:
> >
> https://maven.java.net/content/groups/public/org/apache/maven/plugins/maven-resources-plugin/maven-metadata.xml
> >   Downloading from central:
> >
> https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-resources-plugin/maven-metadata.xml
> >   Downloaded from central:
> >
> https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-resources-plugin/maven-metadata.xml
> (874 B at 1.6
> > kB/s)
> >   Downloading from java.net-Public:
> >
> https://maven.java.net/content/groups/public/org/apache/maven/plugins/maven-surefire-plugin/maven-metadata.xml
> >   Downloading from central:
> >
> https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-surefire-plugin/maven-metadata.xml
> >   Downloaded from central:
> >
> https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-surefire-plugin/maven-metadata.xml
> (1.9 kB at 25
> > kB/s)
> >   Downloading from central:
> >
> https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-deploy-plugin/maven-metadata.xml
> >   Downloading from java.net-Public:
> >
> https://maven.java.net/content/groups/public/org/apache/maven/plugins/maven-deploy-plugin/maven-metadata.xml
> >   Downloaded from central:
> >
> https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-deploy-plugin/maven-metadata.xml
> (783 B at 14
> > kB/s)
> >   [INFO]
> >   [INFO] --- maven-clean-plugin:2.5:clean (default-clean) @
> muleextcharge ---
> >   [INFO] Deleting C:\dev\projects\muleextcharge\target
> >   [INFO]
> >   [INFO] --- maven-mule-plugin:1.9:attach-test-resources
> > (default-attach-test-resources) @ muleextcharge ---
> >   [INFO] attaching test resource
> C:\dev\projects\muleextcharge\src\main\app
> >   [INFO]
> >   [INFO] --- maven-resources-plugin:3.2.0:resources
> > (default-resources) @ muleextcharge ---
> >   [INFO] Using 'Cp1252' encoding to copy filtered resources.
> >   [INFO] Using 'Cp1252' encoding to copy filtered properties files.
> >   [INFO] Copying 0 resource
> >   [INFO]
> >   [INFO] --- maven-mule-plugin:1.9:filter-resources
> > (default-filter-resources) @ muleextcharge ---
> >   [INFO]
> >   [INFO] --- maven-compiler-plugin:3.1:compile (default-compile) @
> > muleextcharge ---
> >   [INFO] Nothing to compile - all classes are up to date
> >   [INFO]
> >   [INFO] --- maven-resources-plugin:3.2.0:testResources
> > (default-testResources) @ muleextcharge ---
> >   [INFO] Not copying test resources
> >   [INFO]
> >   [INFO] --- maven-compiler-plugin:3.1:testCompile
> > (default-testCompile) @ muleextcharge ---
> >   [INFO] Not compiling test sources
> >   [INFO]
> >   [INFO] --- maven-surefire-plugin:3.0.0-M6:test (default-test) @
> > muleextcharge ---
> >   [WARNING] Error injecting:
> org.apache.maven.plugin.surefire.SurefirePlugin
> >   java.lang.TypeNotPresentExcept

RE: Problem with an Maven Build

2022-05-05 Thread Nelligan, Steven M

This is the only reference I have to "surefire" in my POM file.
...snip...



org.apache.maven.plugins
maven-javadoc-plugin
2.9

${jdk-source.version}



org.apache.maven.plugins
maven-surefire-report-plugin
2.15

...snip...

I am assuming that some other dependency is pulling in maven-surefire-plugin.

I have also tried to comment out  ...  and I still get 
the error.

STEVEN M NELLIGAN


-Original Message-
From: Antoine Mottier  
Sent: Thursday, May 5, 2022 9:00 AM
To: Maven Users List 
Subject: Re: Problem with an Maven Build

Starting with version 3.0.0-M6 maven-surefire-plugin requires Java 8 or higher. 
As you are running it using Java 7 this explains your issue.

You can either get back to version 3.0.0-M5 or upgrade to a newer version of 
Java.

Regards,
--
Antoine Mottier

"Nelligan, Steven M"  a écrit :

> Please any assistance would be appreciated
>
> Building a maven project is getting the following error(s)  I have not 
> changed anything in the project, so I assume something changed in the 
> repositories
> How can I get this project built?
>
> INFORMATION FOLLOWS:
>
> __
> 
> I am running maven version 3.6.3:
>C:\dev\projects\muleextcharge>mvn -version
> Apache Maven 3.6.3 (cecedd343002696d0abb50b32b541b8a6ba2883f)
> Maven home: C:\Program Files\apache-maven-3.6.3\bin\..
> Java version: 1.7.0_80, vendor: Oracle Corporation, runtime:  
> C:\Program Files\Java\jdk1.7.0_80\jre
> Default locale: en_US, platform encoding: Cp1252
> OS name: "windows 8.1", version: "6.3", arch: "amd64",
> family: "windows"
>
> __
>  While building I get the following error (if 
> I run maven with dependency:tree, surefire does NOT show in the tree)
>   C:\dev\projects\muleextcharge>mvn -P vDev2 clean install -U 
> -Dmaven.test.skip=true
>   [INFO] Scanning for projects...
>   [INFO]
>   [INFO] -< edu.uiuc.fs:muleextcharge
> >--
>   [INFO] Building Mule Muleextcharge Application 1.0.0
>   [INFO] [ mule
> ]
>   Downloading from java.net-Public:  
> https://urldefense.com/v3/__https://maven.java.net/content/groups/public/org/apache/maven/plugins/maven-resources-plugin/maven-metadata.xml__;!!DZ3fjg!_ga88ihhLeSlWaW2vzU5ZbFjYMb664Wo9VZ01XjN_Hf9M5yIYlv1BUs_RmLQHljx3sXbektttY998yI15I6mvK5Sor5R$
>  
>   Downloading from central:  
> https://urldefense.com/v3/__https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-resources-plugin/maven-metadata.xml__;!!DZ3fjg!_ga88ihhLeSlWaW2vzU5ZbFjYMb664Wo9VZ01XjN_Hf9M5yIYlv1BUs_RmLQHljx3sXbektttY998yI15I6mvFfzy85k$
>  
>   Downloaded from central:  
> https://urldefense.com/v3/__https://repo.maven.apache.org/maven2/org/a
> pache/maven/plugins/maven-resources-plugin/maven-metadata.xml__;!!DZ3f
> jg!_ga88ihhLeSlWaW2vzU5ZbFjYMb664Wo9VZ01XjN_Hf9M5yIYlv1BUs_RmLQHljx3sX
> bektttY998yI15I6mvFfzy85k$  (874 B at 1.6
> kB/s)
>   Downloading from java.net-Public:  
> https://urldefense.com/v3/__https://maven.java.net/content/groups/public/org/apache/maven/plugins/maven-surefire-plugin/maven-metadata.xml__;!!DZ3fjg!_ga88ihhLeSlWaW2vzU5ZbFjYMb664Wo9VZ01XjN_Hf9M5yIYlv1BUs_RmLQHljx3sXbektttY998yI15I6mvPpcbd1G$
>  
>   Downloading from central:  
> https://urldefense.com/v3/__https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-surefire-plugin/maven-metadata.xml__;!!DZ3fjg!_ga88ihhLeSlWaW2vzU5ZbFjYMb664Wo9VZ01XjN_Hf9M5yIYlv1BUs_RmLQHljx3sXbektttY998yI15I6mvKT-QjwK$
>  
>   Downloaded from central:  
> https://urldefense.com/v3/__https://repo.maven.apache.org/maven2/org/a
> pache/maven/plugins/maven-surefire-plugin/maven-metadata.xml__;!!DZ3fj
> g!_ga88ihhLeSlWaW2vzU5ZbFjYMb664Wo9VZ01XjN_Hf9M5yIYlv1BUs_RmLQHljx3sXb
> ektttY998yI15I6mvKT-QjwK$  (1.9 kB at 25
> kB/s)
>   Downloading from central:  
> https://urldefense.com/v3/__https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-deploy-plugin/maven-metadata.xml__;!!DZ3fjg!_ga88ihhLeSlWaW2vzU5ZbFjYMb664Wo9VZ01XjN_Hf9M5yIYlv1BUs_RmLQHljx3sXbektttY998yI15I6mvOlEQUtO$
>  
>   Downloading from java.net-Public:  
> https://urldefense.com/v3/__https://maven.java.net/content/groups/public/org/apache/maven/plugins/maven-deploy-plugin/maven-metadata.xml__;!!DZ3fjg!_ga88ihhLeSlWaW2vzU5ZbFjYMb664Wo9VZ01XjN_Hf9M5yIYlv1BUs_RmLQHljx3sXbektttY998yI15I6mvNok_rYB$
>  
>   Downloaded from central:  
> https://urldefense.com/v3/__https://repo.maven.apache.org/maven2/org/a
> pache/maven/plugins/maven-deploy-plugin/maven-metadata.xm

Re: Problem with an Maven Build

2022-05-05 Thread Tibor Digana
Obviously, the reporting is not the only one sectipn of pom where you use
the latest version of this plugin. See your logs and the goal=test of the
plugin.
T

Dňa št 5. 5. 2022, 16:14 Nelligan, Steven M 
napísal(a):

>
> This is the only reference I have to "surefire" in my POM file.
> ...snip...
> 
> 
> 
> org.apache.maven.plugins
> maven-javadoc-plugin
> 2.9
> 
> ${jdk-source.version}
> 
> 
> 
> org.apache.maven.plugins
> maven-surefire-report-plugin
> 2.15
> 
> ...snip...
>
> I am assuming that some other dependency is pulling in
> maven-surefire-plugin.
>
> I have also tried to comment out  ...  and I still
> get the error.
>
> STEVEN M NELLIGAN
>
>
> -Original Message-
> From: Antoine Mottier 
> Sent: Thursday, May 5, 2022 9:00 AM
> To: Maven Users List 
> Subject: Re: Problem with an Maven Build
>
> Starting with version 3.0.0-M6 maven-surefire-plugin requires Java 8 or
> higher. As you are running it using Java 7 this explains your issue.
>
> You can either get back to version 3.0.0-M5 or upgrade to a newer version
> of Java.
>
> Regards,
> --
> Antoine Mottier
>
> "Nelligan, Steven M"  a écrit :
>
> > Please any assistance would be appreciated
> >
> > Building a maven project is getting the following error(s)  I have not
> > changed anything in the project, so I assume something changed in the
> > repositories
> > How can I get this project built?
> >
> > INFORMATION FOLLOWS:
> >
> > __
> > 
> > I am running maven version 3.6.3:
> >C:\dev\projects\muleextcharge>mvn -version
> > Apache Maven 3.6.3 (cecedd343002696d0abb50b32b541b8a6ba2883f)
> > Maven home: C:\Program Files\apache-maven-3.6.3\bin\..
> > Java version: 1.7.0_80, vendor: Oracle Corporation, runtime:
> > C:\Program Files\Java\jdk1.7.0_80\jre
> > Default locale: en_US, platform encoding: Cp1252
> > OS name: "windows 8.1", version: "6.3", arch: "amd64",
> > family: "windows"
> >
> > __
> >  While building I get the following error (if
> > I run maven with dependency:tree, surefire does NOT show in the tree)
> >   C:\dev\projects\muleextcharge>mvn -P vDev2 clean install -U
> > -Dmaven.test.skip=true
> >   [INFO] Scanning for projects...
> >   [INFO]
> >   [INFO] -< edu.uiuc.fs:muleextcharge
> > >--
> >   [INFO] Building Mule Muleextcharge Application 1.0.0
> >   [INFO] [ mule
> > ]
> >   Downloading from java.net-Public:
> >
> https://urldefense.com/v3/__https://maven.java.net/content/groups/public/org/apache/maven/plugins/maven-resources-plugin/maven-metadata.xml__;!!DZ3fjg!_ga88ihhLeSlWaW2vzU5ZbFjYMb664Wo9VZ01XjN_Hf9M5yIYlv1BUs_RmLQHljx3sXbektttY998yI15I6mvK5Sor5R$
> >   Downloading from central:
> >
> https://urldefense.com/v3/__https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-resources-plugin/maven-metadata.xml__;!!DZ3fjg!_ga88ihhLeSlWaW2vzU5ZbFjYMb664Wo9VZ01XjN_Hf9M5yIYlv1BUs_RmLQHljx3sXbektttY998yI15I6mvFfzy85k$
> >   Downloaded from central:
> > https://urldefense.com/v3/__https://repo.maven.apache.org/maven2/org/a
> > pache/maven/plugins/maven-resources-plugin/maven-metadata.xml__;!!DZ3f
> > jg!_ga88ihhLeSlWaW2vzU5ZbFjYMb664Wo9VZ01XjN_Hf9M5yIYlv1BUs_RmLQHljx3sX
> > bektttY998yI15I6mvFfzy85k$  (874 B at 1.6
> > kB/s)
> >   Downloading from java.net-Public:
> >
> https://urldefense.com/v3/__https://maven.java.net/content/groups/public/org/apache/maven/plugins/maven-surefire-plugin/maven-metadata.xml__;!!DZ3fjg!_ga88ihhLeSlWaW2vzU5ZbFjYMb664Wo9VZ01XjN_Hf9M5yIYlv1BUs_RmLQHljx3sXbektttY998yI15I6mvPpcbd1G$
> >   Downloading from central:
> >
> https://urldefense.com/v3/__https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-surefire-plugin/maven-metadata.xml__;!!DZ3fjg!_ga88ihhLeSlWaW2vzU5ZbFjYMb664Wo9VZ01XjN_Hf9M5yIYlv1BUs_RmLQHljx3sXbektttY998yI15I6mvKT-QjwK$
> >   Downloaded from central:
> > https://urldefense.com/v3/__https://repo.maven.apache.org/maven2/org/a
> > pache/maven/plugins/maven-surefire-plugin/maven-metadata.xml__;!!DZ3fj
> > g!_ga88ihhLeSlWaW2vzU5ZbFjYMb664Wo9VZ01XjN_Hf9M5yIYlv1BUs_RmLQHljx3sXb
> > ektttY998yI15I6mvKT-QjwK$  (1.9 kB at 25
> > kB/s)
> >   Downloading from central:
> >
> https://urldefense.com/v3/__https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-deploy-plugin/maven-metadata.xml__;!!DZ3fjg!_ga88ihhLeSlWaW2vzU5ZbFjYMb664Wo9VZ01XjN_Hf9M5yIYlv1BUs_RmLQHljx3sXbektttY998yI15I6mvOlEQUtO$
> >   Downloading from java.net-Public:
> >
> https://urldefense.com/v3/__https

Re: Problem with an Maven Build

2022-05-05 Thread Slawomir Jaranowski
Hi,

Try a newer version of maven, 3.8.5 - you will see a warning for plugins
without the version specified.

You defined a version of surefire in the reporting section.

Please add version of surefire in build -> plugins or build ->
pluginsManagment




czw., 5 maj 2022 o 15:48 Nelligan, Steven M 
napisał(a):

> Please any assistance would be appreciated
>
> Building a maven project is getting the following error(s)
>  I have not changed anything in the project, so I assume something changed
> in the repositories
> How can I get this project built?
>
> INFORMATION FOLLOWS:
>
>
> __
> I am running maven version 3.6.3:
>C:\dev\projects\muleextcharge>mvn -version
> Apache Maven 3.6.3 (cecedd343002696d0abb50b32b541b8a6ba2883f)
> Maven home: C:\Program Files\apache-maven-3.6.3\bin\..
> Java version: 1.7.0_80, vendor: Oracle Corporation, runtime:
> C:\Program Files\Java\jdk1.7.0_80\jre
> Default locale: en_US, platform encoding: Cp1252
> OS name: "windows 8.1", version: "6.3", arch: "amd64", family:
> "windows"
>
>
> __
> While building I get the following error (if I run maven with
> dependency:tree, surefire does NOT show in the tree)
> C:\dev\projects\muleextcharge>mvn -P vDev2 clean install -U
> -Dmaven.test.skip=true
> [INFO] Scanning for projects...
> [INFO]
> [INFO] -< edu.uiuc.fs:muleextcharge
> >--
> [INFO] Building Mule Muleextcharge Application 1.0.0
> [INFO] [ mule
> ]
> Downloading from java.net-Public:
> https://maven.java.net/content/groups/public/org/apache/maven/plugins/maven-resources-plugin/maven-metadata.xml
> Downloading from central:
> https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-resources-plugin/maven-metadata.xml
> Downloaded from central:
> https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-resources-plugin/maven-metadata.xml
> (874 B at 1.6 kB/s)
> Downloading from java.net-Public:
> https://maven.java.net/content/groups/public/org/apache/maven/plugins/maven-surefire-plugin/maven-metadata.xml
> Downloading from central:
> https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-surefire-plugin/maven-metadata.xml
> Downloaded from central:
> https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-surefire-plugin/maven-metadata.xml
> (1.9 kB at 25 kB/s)
> Downloading from central:
> https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-deploy-plugin/maven-metadata.xml
> Downloading from java.net-Public:
> https://maven.java.net/content/groups/public/org/apache/maven/plugins/maven-deploy-plugin/maven-metadata.xml
> Downloaded from central:
> https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-deploy-plugin/maven-metadata.xml
> (783 B at 14 kB/s)
> [INFO]
> [INFO] --- maven-clean-plugin:2.5:clean (default-clean) @
> muleextcharge ---
> [INFO] Deleting C:\dev\projects\muleextcharge\target
> [INFO]
> [INFO] --- maven-mule-plugin:1.9:attach-test-resources
> (default-attach-test-resources) @ muleextcharge ---
> [INFO] attaching test resource
> C:\dev\projects\muleextcharge\src\main\app
> [INFO]
> [INFO] --- maven-resources-plugin:3.2.0:resources
> (default-resources) @ muleextcharge ---
> [INFO] Using 'Cp1252' encoding to copy filtered resources.
> [INFO] Using 'Cp1252' encoding to copy filtered properties files.
> [INFO] Copying 0 resource
> [INFO]
> [INFO] --- maven-mule-plugin:1.9:filter-resources
> (default-filter-resources) @ muleextcharge ---
> [INFO]
> [INFO] --- maven-compiler-plugin:3.1:compile (default-compile) @
> muleextcharge ---
> [INFO] Nothing to compile - all classes are up to date
> [INFO]
> [INFO] --- maven-resources-plugin:3.2.0:testResources
> (default-testResources) @ muleextcharge ---
> [INFO] Not copying test resources
> [INFO]
> [INFO] --- maven-compiler-plugin:3.1:testCompile
> (default-testCompile) @ muleextcharge ---
> [INFO] Not compiling test sources
> [INFO]
> [INFO] --- maven-surefire-plugin:3.0.0-M6:test (default-test) @
> muleextcharge ---
> [WARNING] Error injecting:
> org.apache.maven.plugin.surefire.SurefirePlugin
> java.lang.TypeNotPresentException: Type
> org.apache.maven.plugin.surefire.SurefirePlugin not present
> at org.eclipse.sisu.space.URLClassSpace.loadClass
> (URLClassSpace.java:147)
> at org.eclipse.sisu.space.NamedClass.load
> (NamedClass.java:46)
> at

RE: Problem with an Maven Build

2022-05-05 Thread Nelligan, Steven M

This appears to have solved the problem.

Thanks for the help.

STEVEN M NELLIGAN


-Original Message-
From: Tibor Digana  
Sent: Thursday, May 5, 2022 9:10 AM
To: Maven Users List 
Subject: Re: Problem with an Maven Build

It should not be any issue if you switch to JDK8 and add maven sniffer plugin 
along with compiler 1.7.
T

Dňa št 5. 5. 2022, 16:00 Antoine Mottier 
napísal(a):

> Starting with version 3.0.0-M6 maven-surefire-plugin requires Java 8 
> or higher. As you are running it using Java 7 this explains your issue.
>
> You can either get back to version 3.0.0-M5 or upgrade to a newer 
> version of Java.
>
> Regards,
> --
> Antoine Mottier
>
> "Nelligan, Steven M"  a écrit :
>
> > Please any assistance would be appreciated
> >
> > Building a maven project is getting the following error(s)  I have 
> > not changed anything in the project, so I assume something changed 
> > in the repositories
> > How can I get this project built?
> >
> > INFORMATION FOLLOWS:
> >
> >
> __
> 
> > I am running maven version 3.6.3:
> >C:\dev\projects\muleextcharge>mvn -version
> > Apache Maven 3.6.3 (cecedd343002696d0abb50b32b541b8a6ba2883f)
> > Maven home: C:\Program Files\apache-maven-3.6.3\bin\..
> > Java version: 1.7.0_80, vendor: Oracle Corporation, runtime:
> > C:\Program Files\Java\jdk1.7.0_80\jre
> > Default locale: en_US, platform encoding: Cp1252
> > OS name: "windows 8.1", version: "6.3", arch: "amd64",
> > family: "windows"
> >
> >
> __
> 
> > While building I get the following error (if I run maven with 
> > dependency:tree, surefire does NOT show in the tree)
> >   C:\dev\projects\muleextcharge>mvn -P vDev2 clean install -U 
> > -Dmaven.test.skip=true
> >   [INFO] Scanning for projects...
> >   [INFO]
> >   [INFO] -< edu.uiuc.fs:muleextcharge
> > >--
> >   [INFO] Building Mule Muleextcharge Application 1.0.0
> >   [INFO] [ mule
> > ]
> >   Downloading from java.net-Public:
> >
> https://urldefense.com/v3/__https://maven.java.net/content/groups/publ
> ic/org/apache/maven/plugins/maven-resources-plugin/maven-metadata.xml_
> _;!!DZ3fjg!7wLWx20tpsnGr41tp0AyTXgACl8LKalDISpXrN6D54Ykt3Ui-4hz9LqweZn
> _iKr582lVltQIofiD8N9R-tCGSDkq$
> >   Downloading from central:
> >
> https://urldefense.com/v3/__https://repo.maven.apache.org/maven2/org/a
> pache/maven/plugins/maven-resources-plugin/maven-metadata.xml__;!!DZ3f
> jg!7wLWx20tpsnGr41tp0AyTXgACl8LKalDISpXrN6D54Ykt3Ui-4hz9LqweZn_iKr582l
> VltQIofiD8N9R-uyJJqwO$
> >   Downloaded from central:
> >
> https://urldefense.com/v3/__https://repo.maven.apache.org/maven2/org/a
> pache/maven/plugins/maven-resources-plugin/maven-metadata.xml__;!!DZ3f
> jg!7wLWx20tpsnGr41tp0AyTXgACl8LKalDISpXrN6D54Ykt3Ui-4hz9LqweZn_iKr582l
> VltQIofiD8N9R-uyJJqwO$
> (874 B at 1.6
> > kB/s)
> >   Downloading from java.net-Public:
> >
> https://urldefense.com/v3/__https://maven.java.net/content/groups/publ
> ic/org/apache/maven/plugins/maven-surefire-plugin/maven-metadata.xml__
> ;!!DZ3fjg!7wLWx20tpsnGr41tp0AyTXgACl8LKalDISpXrN6D54Ykt3Ui-4hz9LqweZn_
> iKr582lVltQIofiD8N9R-j9mxeOo$
> >   Downloading from central:
> >
> https://urldefense.com/v3/__https://repo.maven.apache.org/maven2/org/a
> pache/maven/plugins/maven-surefire-plugin/maven-metadata.xml__;!!DZ3fj
> g!7wLWx20tpsnGr41tp0AyTXgACl8LKalDISpXrN6D54Ykt3Ui-4hz9LqweZn_iKr582lV
> ltQIofiD8N9R-qpY0FL0$
> >   Downloaded from central:
> >
> https://urldefense.com/v3/__https://repo.maven.apache.org/maven2/org/a
> pache/maven/plugins/maven-surefire-plugin/maven-metadata.xml__;!!DZ3fj
> g!7wLWx20tpsnGr41tp0AyTXgACl8LKalDISpXrN6D54Ykt3Ui-4hz9LqweZn_iKr582lV
> ltQIofiD8N9R-qpY0FL0$
> (1.9 kB at 25
> > kB/s)
> >   Downloading from central:
> >
> https://urldefense.com/v3/__https://repo.maven.apache.org/maven2/org/a
> pache/maven/plugins/maven-deploy-plugin/maven-metadata.xml__;!!DZ3fjg!
> 7wLWx20tpsnGr41tp0AyTXgACl8LKalDISpXrN6D54Ykt3Ui-4hz9LqweZn_iKr582lVlt
> QIofiD8N9R-i9a4W6R$
> >   Downloading from java.net-Public:
> >
> https://urldefense.com/v3/__https://maven.java.net/content/groups/publ
> ic/org/apache/maven/plugins/maven-deploy-plugin/maven-metadata.xml__;!
> !DZ3fjg!7wLWx20tpsnGr41tp0AyTXgACl8LKalDISpXrN6D54Ykt3Ui-4hz9LqweZn_iK
> r582lVltQIofiD8N9R-iIte4yE$
> >   Downloaded from central:
> >
> https://urldefense.com/v3/__https://repo.maven.apache.org/maven2/org/a
> pache/maven/plugins/maven-deploy-plugin/maven-metadata.xml__;!!DZ3fjg!
> 7wLWx20tpsnGr41tp0AyTXgACl8LKalDISpXrN6D54Ykt3Ui-4hz9LqweZn_iKr582lVlt
> QIofiD8N9R-i9a4W6R$
> (783 B at 14
> > kB/s)
> >   [INFO]
> >   [INFO] --- maven-clean-plugin:2.5:clean (default-clean) @
> mulee

Re: Maven Reactor and plugin "local" dependencies

2022-05-05 Thread Francois Marot
Hello Florent,

I have had this problem a few years ago, and from what I can remember it is
the expected behavior. Or at least this is the way it is right now.
Sorry, It is from memory and I do not have any link to share nor
explanation about it, but at least you know you are not alone !

Regards

François



Le jeu. 5 mai 2022 à 15:11, Florent Biville  a
écrit :

> Hello everyone,
>
> TL;DR? https://github.com/fbiville/mvn-plugin-dependency-reactor-issue
>
> I recently noticed that, within the big multi-module project of my company,
> a specific module is listed as a dependency to plugins such as Maven
> Checkstyle plugin or com.mycila:license-maven-plugin.
>
> The problem occurs when I try one of these plugins against another specific
> module.
> Maven CLI will basically complain that it cannot resolve the module needed
> by the plugin and fail, even if I explicitly list that module in the
> project list.
>
> That occurs both with Maven 3 and 4.
>
> The obvious workaround is to install the required module first and then run
> the plugin but I'm trying to get rid of the need for `mvn install`
> entirely.
>
> Is there a particular reason plugin dependencies are not considered by
> Maven Reactor?
> Is module-as-plugin-dependency a Maven antipattern?
>
> Thanks a lot for your help!
> Florent
>


Re: Maven Reactor and plugin "local" dependencies

2022-05-05 Thread Tamás Cservenák
Florent,

Not directly related to your question, but reading your mail caught
my attention one sentence.
Can you shed some light on why "... but I'm trying to get rid of the need
for `mvn install` entirely."?

Thanks
Tamas

On Thu, May 5, 2022 at 3:11 PM Florent Biville 
wrote:

> Hello everyone,
>
> TL;DR? https://github.com/fbiville/mvn-plugin-dependency-reactor-issue
>
> I recently noticed that, within the big multi-module project of my company,
> a specific module is listed as a dependency to plugins such as Maven
> Checkstyle plugin or com.mycila:license-maven-plugin.
>
> The problem occurs when I try one of these plugins against another specific
> module.
> Maven CLI will basically complain that it cannot resolve the module needed
> by the plugin and fail, even if I explicitly list that module in the
> project list.
>
> That occurs both with Maven 3 and 4.
>
> The obvious workaround is to install the required module first and then run
> the plugin but I'm trying to get rid of the need for `mvn install`
> entirely.
>
> Is there a particular reason plugin dependencies are not considered by
> Maven Reactor?
> Is module-as-plugin-dependency a Maven antipattern?
>
> Thanks a lot for your help!
> Florent
>


Re: Maven Reactor and plugin "local" dependencies

2022-05-05 Thread Thomas Broyer
Because it is an antipattern?
https://www.cloudbees.com/blog/maven-and-install-hack

If you do rely on "mvn install", which one of your commit is your snapshot
in your local repository from? How can you tell? And it gets worse if you
deploy snapshots to a repository, as now it could also be from someone
else's commit (you might not have pulled from your git repo, but the
snapshot comes from the origin/master that someone else pushed)

Maven is among the only (modern) build tools requiring you to "install"
part of your project to some widely shared place (shared with all you local
projects) to use it from within itself!


Le jeu. 5 mai 2022 à 21:22, Tamás Cservenák  a écrit :

> Florent,
>
> Not directly related to your question, but reading your mail caught
> my attention one sentence.
> Can you shed some light on why "... but I'm trying to get rid of the need
> for `mvn install` entirely."?
>
> Thanks
> Tamas
>
> On Thu, May 5, 2022 at 3:11 PM Florent Biville 
> wrote:
>
> > Hello everyone,
> >
> > TL;DR? https://github.com/fbiville/mvn-plugin-dependency-reactor-issue
> >
> > I recently noticed that, within the big multi-module project of my
> company,
> > a specific module is listed as a dependency to plugins such as Maven
> > Checkstyle plugin or com.mycila:license-maven-plugin.
> >
> > The problem occurs when I try one of these plugins against another
> specific
> > module.
> > Maven CLI will basically complain that it cannot resolve the module
> needed
> > by the plugin and fail, even if I explicitly list that module in the
> > project list.
> >
> > That occurs both with Maven 3 and 4.
> >
> > The obvious workaround is to install the required module first and then
> run
> > the plugin but I'm trying to get rid of the need for `mvn install`
> > entirely.
> >
> > Is there a particular reason plugin dependencies are not considered by
> > Maven Reactor?
> > Is module-as-plugin-dependency a Maven antipattern?
> >
> > Thanks a lot for your help!
> > Florent
> >
>


Re: Maven Reactor and plugin "local" dependencies

2022-05-05 Thread Tamás Cservenák
Florent,

created response on reproducer
https://github.com/fbiville/mvn-plugin-dependency-reactor-issue/issues/1

HTH
T

On Thu, May 5, 2022 at 3:11 PM Florent Biville 
wrote:

> Hello everyone,
>
> TL;DR? https://github.com/fbiville/mvn-plugin-dependency-reactor-issue
>
> I recently noticed that, within the big multi-module project of my company,
> a specific module is listed as a dependency to plugins such as Maven
> Checkstyle plugin or com.mycila:license-maven-plugin.
>
> The problem occurs when I try one of these plugins against another specific
> module.
> Maven CLI will basically complain that it cannot resolve the module needed
> by the plugin and fail, even if I explicitly list that module in the
> project list.
>
> That occurs both with Maven 3 and 4.
>
> The obvious workaround is to install the required module first and then run
> the plugin but I'm trying to get rid of the need for `mvn install`
> entirely.
>
> Is there a particular reason plugin dependencies are not considered by
> Maven Reactor?
> Is module-as-plugin-dependency a Maven antipattern?
>
> Thanks a lot for your help!
> Florent
>


Re: Maven Reactor and plugin "local" dependencies

2022-05-05 Thread Tamás Cservenák
Hm,

By reading this blog entry from 2012 (!), I see it summarizes nicely at the
end:
* You may be using some broken plugins that you will need to fix, or
replace.
* You may be battling a circular dependency hell (which was why you used
dependency:copy in the first place) which indicates a bad build smell that
you should eradicate.
* You may not have the time… well think of all the time you are wasting
running "mvn install" when you could get away without going so far along
the lifecycle.

Can you point me to some "reproducer" project (of ANY of these issues
mentioned in this 10 year old blog), that
* will reproduce this with modern Maven, think 3.8.x
* is NOT broken topologically (cycles), is not using broken (by using
broken plugins) and developers does have time?

Thanks
T

On Thu, May 5, 2022 at 9:58 PM Thomas Broyer  wrote:

> Because it is an antipattern?
> https://www.cloudbees.com/blog/maven-and-install-hack
>
> If you do rely on "mvn install", which one of your commit is your snapshot
> in your local repository from? How can you tell? And it gets worse if you
> deploy snapshots to a repository, as now it could also be from someone
> else's commit (you might not have pulled from your git repo, but the
> snapshot comes from the origin/master that someone else pushed)
>
> Maven is among the only (modern) build tools requiring you to "install"
> part of your project to some widely shared place (shared with all you local
> projects) to use it from within itself!
>
>
> Le jeu. 5 mai 2022 à 21:22, Tamás Cservenák  a écrit
> :
>
> > Florent,
> >
> > Not directly related to your question, but reading your mail caught
> > my attention one sentence.
> > Can you shed some light on why "... but I'm trying to get rid of the need
> > for `mvn install` entirely."?
> >
> > Thanks
> > Tamas
> >
> > On Thu, May 5, 2022 at 3:11 PM Florent Biville <
> florent.bivi...@gmail.com>
> > wrote:
> >
> > > Hello everyone,
> > >
> > > TL;DR? https://github.com/fbiville/mvn-plugin-dependency-reactor-issue
> > >
> > > I recently noticed that, within the big multi-module project of my
> > company,
> > > a specific module is listed as a dependency to plugins such as Maven
> > > Checkstyle plugin or com.mycila:license-maven-plugin.
> > >
> > > The problem occurs when I try one of these plugins against another
> > specific
> > > module.
> > > Maven CLI will basically complain that it cannot resolve the module
> > needed
> > > by the plugin and fail, even if I explicitly list that module in the
> > > project list.
> > >
> > > That occurs both with Maven 3 and 4.
> > >
> > > The obvious workaround is to install the required module first and then
> > run
> > > the plugin but I'm trying to get rid of the need for `mvn install`
> > > entirely.
> > >
> > > Is there a particular reason plugin dependencies are not considered by
> > > Maven Reactor?
> > > Is module-as-plugin-dependency a Maven antipattern?
> > >
> > > Thanks a lot for your help!
> > > Florent
> > >
> >
>


Re: Maven Reactor and plugin "local" dependencies

2022-05-05 Thread Tamás Cservenák
IMHO the antipattern here is the idea that "mvn install" is bad.

But let's take it step by step. For simplicity sake, let's ignore remote
deploys/downloads for now.
Also, let's assume a developer workstation for the same reason (simplicity).

Q: which one of your commit is your snapshot in your local repository from?
A: the last one you `mvn install`-ed?

Q: how can you tell?
A: Your build should be reproducible (
https://maven.apache.org/guides/mini/guide-reproducible-builds.html) so you
can sha target/XXX.jar and local repo? But if unsure, just `mvn install` :D

Maven does not require anything to install, or at least, am not getting
what you are saying.
OTOH, you DO need to install, if you plan to deploy (but, we can exclude
this part, as we agreed, let's stick to developer workstation case, and
developer do not deploy, CI is).

HTH
T

On Thu, May 5, 2022 at 9:58 PM Thomas Broyer  wrote:

> Because it is an antipattern?
> https://www.cloudbees.com/blog/maven-and-install-hack
>
> If you do rely on "mvn install", which one of your commit is your snapshot
> in your local repository from? How can you tell? And it gets worse if you
> deploy snapshots to a repository, as now it could also be from someone
> else's commit (you might not have pulled from your git repo, but the
> snapshot comes from the origin/master that someone else pushed)
>
> Maven is among the only (modern) build tools requiring you to "install"
> part of your project to some widely shared place (shared with all you local
> projects) to use it from within itself!
>
>
> Le jeu. 5 mai 2022 à 21:22, Tamás Cservenák  a écrit
> :
>
> > Florent,
> >
> > Not directly related to your question, but reading your mail caught
> > my attention one sentence.
> > Can you shed some light on why "... but I'm trying to get rid of the need
> > for `mvn install` entirely."?
> >
> > Thanks
> > Tamas
> >
> > On Thu, May 5, 2022 at 3:11 PM Florent Biville <
> florent.bivi...@gmail.com>
> > wrote:
> >
> > > Hello everyone,
> > >
> > > TL;DR? https://github.com/fbiville/mvn-plugin-dependency-reactor-issue
> > >
> > > I recently noticed that, within the big multi-module project of my
> > company,
> > > a specific module is listed as a dependency to plugins such as Maven
> > > Checkstyle plugin or com.mycila:license-maven-plugin.
> > >
> > > The problem occurs when I try one of these plugins against another
> > specific
> > > module.
> > > Maven CLI will basically complain that it cannot resolve the module
> > needed
> > > by the plugin and fail, even if I explicitly list that module in the
> > > project list.
> > >
> > > That occurs both with Maven 3 and 4.
> > >
> > > The obvious workaround is to install the required module first and then
> > run
> > > the plugin but I'm trying to get rid of the need for `mvn install`
> > > entirely.
> > >
> > > Is there a particular reason plugin dependencies are not considered by
> > > Maven Reactor?
> > > Is module-as-plugin-dependency a Maven antipattern?
> > >
> > > Thanks a lot for your help!
> > > Florent
> > >
> >
>