Thanks for that. Our artifactory release predates 7.68 so this could well
be the culprit.

On Tue, Oct 15, 2024 at 7:16 AM Richard Eckart de Castilho <r...@apache.org>
wrote:

> Hi
>
> > On 14. Oct 2024, at 01:31, Dale Ogilvie <dale_ogil...@trimble.com>
> wrote:
> >
> > The trick is, the generated maven-metadata.xml is fine when we use maven
> > 3.8.5. This is a very mature build pipeline, and we have just started
> > noticing this, after a switch to 3.9.x
> >
> > I'm taking a look at this off of our build infrastructure.
>
> If you see this problem when deploying to Artifactory, it might be due to
> a bug in Artifactory.
>
> RTDEV-35001
>
>
> https://jfrog.com/help/r/jfrog-release-information/artifactory-7.68.11-self-hosted
>
> Cheers,
>
> -- Richard
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>

-- 
Dale Ogilvie
Senior Software Engineer,
Technical and Process Coach,
Business Systems
11 Birmingham Drive, Christchurch, New Zealand
+64-22-6005437 Mobile
dale_ogil...@trimble.com
<https://www.linkedin.com/in/dale-ogilvie-527a9151>

Reply via email to