Re: Need help for maven site plugin for Apache Helix

2021-11-17 Thread Olivier Lamy
not sure what is the content of your ~/.m2/settings.xml but it may have some references to some repositories? such http://restlet.talend.com , http://repository.apache.org/snapshots. note this http the recent change might be you upgrading to the last maven core version? [*INFO*] Generating

Re: Need help for maven site plugin for Apache Helix

2021-11-17 Thread Martin Gainty
caused by outdated reference to a dead codehaus repo setting codehaus repository enabled=false should mitigate e.g. HTH martin From: Junkai Xue Sent: Wednesday, November 17, 2021 6:04 PM To: users@maven.apache.org Subject: Need help for maven site

Need help for maven site plugin for Apache Helix

2021-11-17 Thread Junkai Xue
Hi, I was trying to deploy Apache Helix project website for new releases. Got exception on *SiteToolException: The site descriptor cannot be resolved from the repository: ArtifactResolutionException: Unable to locate site descriptor: Could not transfer artifact org.apache:apache:xml:site_en:13

Re: Help with Shading on ActiveMQ Artemis

2021-11-17 Thread Francois Marot
Hello Clebert I hope my comment will help you. In my experience, using the shade plugin is tricky because the rule of thumb I came up with is: "your shaded artifacts must be the last artifact to be built in your multi modules Maven project". Which can read "you must not depend onto your shaded

Re: Help with Shading on ActiveMQ Artemis

2021-11-17 Thread Clebert Suconic
although it's marked as an improvement for the IDEs to pick this up.. but I see other issues internally... On Wed, Nov 17, 2021 at 2:46 PM Clebert Suconic wrote: > > well.. that is a bug: > > https://issues.apache.org/jira/browse/MSHADE-269 > > On Wed, Nov 17, 2021 at 10:57 AM Clebert Suconic >

Re: Help with Shading on ActiveMQ Artemis

2021-11-17 Thread Clebert Suconic
well.. that is a bug: https://issues.apache.org/jira/browse/MSHADE-269 On Wed, Nov 17, 2021 at 10:57 AM Clebert Suconic wrote: > > I had to play with optional to have the dependency not picked up internally. > > It would be a lot easier if shaded worked internally without requiring > a

Re: Help with Shading on ActiveMQ Artemis

2021-11-17 Thread Clebert Suconic
I had to play with optional to have the dependency not picked up internally. It would be a lot easier if shaded worked internally without requiring a downstream dependency. As a matter of fact, I just looked on Netty, and they shade org.jctools into netty-common, which is the same pattern that

Re: Help with Shading on ActiveMQ Artemis

2021-11-17 Thread Clebert Suconic
Right.. This should happen by default. and it will only work if I'm using the shaded jar outside of my project. However if I use it within my project it will not work at all. I have created a minimal version of my issue on this github project:

Re: Help with Shading on ActiveMQ Artemis

2021-11-17 Thread Matt Benson
https://maven.apache.org/plugins/maven-shade-plugin/shade-mojo.html#createDependencyReducedPom On Tue, Nov 16, 2021, 10:47 PM Clebert Suconic wrote: > I’m not sure how you mean. > > Just get the Pom at the source level or am intermediate build process ? > > > How to do that ? > > On Tue, Nov