Details
-
Improvement
-
Status: Closed
-
Minor
-
Resolution: Fixed
-
4.0.0-alpha-4
-
Apache Maven 4.0.0-alpha-4 (009cf4a7213aead8a7946a2397e2396c5927f30f)
Maven home: /Users/maarten/Tools/apache-maven-4.0.0-alpha-4
Java version: 17.0.6, vendor: Eclipse Adoptium, runtime: /Library/Java/JavaVirtualMachines/temurin-17.jdk/Contents/Home
Default locale: en_NL, platform encoding: UTF-8
OS name: "mac os x", version: "13.2.1", arch: "aarch64", family: "mac"Apache Maven 4.0.0-alpha-4 (009cf4a7213aead8a7946a2397e2396c5927f30f) Maven home: /Users/maarten/Tools/apache-maven-4.0.0-alpha-4 Java version: 17.0.6, vendor: Eclipse Adoptium, runtime: /Library/Java/JavaVirtualMachines/temurin-17.jdk/Contents/Home Default locale: en_NL, platform encoding: UTF-8 OS name: "mac os x", version: "13.2.1", arch: "aarch64", family: "mac"
Description
After invoking Mavens validate or later lifecycle phase, there is a consumerXXXpom file left in the build directory. Here, XXX is a bunch of numbers.
It is not harmful, but I dislike the fact that for every invocation of Maven, the file gets generated again and again. This can quickly lead to tens of files that are never used again anymore. I feel we should clean those files when we're done using them.
Attachments
Issue Links
- is related to
-
MNG-7707 ${project.basedir} directory creation when running plugin
- Closed
- links to