Re: Overwriting the "central" from settings.xml when importing bom pom files
Thanks Thomas. mirrors are an option, but I was wondering if there is a reason that only for nested boms the override of "central" doesn't work -- Sent from: http://maven.40175.n5.nabble.com/Maven-Users-f40176.html - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Overwriting the "central" from settings.xml when importing bom pom files
Hi team, When resolving bom artifacts, the following method is invoked - org.apache.maven.model.building.DefaultModelBuilder#configureResolver( ModelResolver modelResolver, Model model, DefaultModelProblemCollector problems, boolean replaceRepositories ) The 'replaceRepositories' parameter is invoked with a value of 'true' which means that Maven looks up the lineage of of projects to find a repository. This has the effect that if for example you have in your settings.xml a repository with the id "central" set to "REPO A" it will replace that with repo1. Is this the desired behavior? Is there a way to tell Maven not to override the repositories that I have in my Maven settings.xml as this causes unsable builds if you are behind a company firewall and must use a middle-man (Nexus/Artifactory). Thanks, Tomer -- Sent from: http://maven.40175.n5.nabble.com/Maven-Users-f40176.html - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Removing classpath entries for shaded aritfacts
Hello Maven team, I have the following scenario. I have several libraries which I am building, and an application which depends on those libraries. While I am building using the maven-jar-plugin, a manifest is created with several entries, including the classpath, which naturally include all the libraries. However, I am also trying to create a shaded version of my application which shades the libraries I am building. What happens is that the libraries get shaded fine, but the manifest still has the original classpath created by the maven-jar-plugin embedded in it. Is there a way to exclude the included shaded libraries from the manifest of the shaded application jar? Thanks -- View this message in context: http://maven.40175.n5.nabble.com/Removing-classpath-entries-for-shaded-aritfacts-tp5865658.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org