We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hi,
I've started using the Split Local Repository feature, and noticed that flatten-maven-plugin now spews lines similar to this:
flatten-maven-plugin
[WARNING] The POM for <artifactN> is missing, no dependency information available
Of course, the flattened POMs reflect this (e.g. missing dependency exclusions) 😢
Edit: This only happens, when flatten.dependency.mode is set to all.
flatten.dependency.mode
all
Additional information: Maven 3.9.9 org.codehaus.mojo:flatten-maven-plugin:1.6.0 aether.enhancedLocalRepository.split=true aether.enhancedLocalRepository.splitLocal=true aether.enhancedLocalRepository.splitRemote=true flatten.dependency.mode=all
org.codehaus.mojo:flatten-maven-plugin:1.6.0
aether.enhancedLocalRepository.split=true
aether.enhancedLocalRepository.splitLocal=true
aether.enhancedLocalRepository.splitRemote=true
flatten.dependency.mode=all
Slightly related issue: #339
Is there any workaround?
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Hi,
I've started using the Split Local Repository feature, and noticed that
flatten-maven-plugin
now spews lines similar to this:Of course, the flattened POMs reflect this (e.g. missing dependency exclusions) 😢
Edit: This only happens, when
flatten.dependency.mode
is set toall
.Additional information:
Maven 3.9.9
org.codehaus.mojo:flatten-maven-plugin:1.6.0
aether.enhancedLocalRepository.split=true
aether.enhancedLocalRepository.splitLocal=true
aether.enhancedLocalRepository.splitRemote=true
flatten.dependency.mode=all
Slightly related issue: #339
Is there any workaround?
The text was updated successfully, but these errors were encountered: