I don't follow your suggestion "you deploy separately classified artifacts
from the same reactor".

The only item in the build section of our pom.xml is the
maven-source-plugin.

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.


On Mon, Oct 14, 2024 at 10:26 AM Tamás Cservenák <ta...@cservenak.net>
wrote:

> The only thing I can imagine this to happen is if you do something
> funky about deployment, like you deploy separately classified
> artifacts from the same reactor?
>
> Thanks
> T
>
> On Sun, Oct 13, 2024 at 11:24 PM Tamás Cservenák <ta...@cservenak.net>
> wrote:
> >
> > Howdy,
> >
> > can you create a reproducer that reproduces this behaviour?
> >
> > Thanks
> > T
> >
> > On Sun, Oct 13, 2024 at 9:55 PM Dale Ogilvie <dale_ogil...@trimble.com>
> wrote:
> > >
> > > 3.9.9 demonstrates similar behaviour, where one of the
> snapshotVersions in
> > > maven-metadata.xml lags one build behind. In this case it is not the
> jar,
> > > but the sources which lags.
> > >
> > > Should this be an issue in maven jira?
> > >
> > >
> > >
> > > On Fri, Oct 11, 2024 at 4:52 PM Dale Ogilvie <dale_ogil...@trimble.com
> >
> > > wrote:
> > >
> > > > Hello,
> > > >
> > > > we do builds up against the latest snapshot in our dev environment.
> After
> > > > switching our builds from maven 3.8.5 to 3.9.7 we find that the
> > > > maven-metadata.xml generated for our snapshot libraries is incorrect,
> > > > resulting in a build up against the **previous** snapshot. Switching
> back
> > > > to 3.8.5 fixes the issue.
> > > >
> > > > The incorrect metadata is generated when we "mvn deploy" our
> library. I
> > > > took a look at the release logs for 3.9.8 and 3.9.9 and could not
> see any
> > > > fixed issues which seemed to resemble this problem. We will try out
> 3.9.9
> > > > once we get it installed on our build system.
> > > >
> > > > We are using an updatePolicy of always on our snapshot repo.
> > > >
> > > >         <repository>
> > > >           <snapshots>
> > > >             <enabled>true</enabled>
> > > >             <updatePolicy>always</updatePolicy>
> > > >           </snapshots>
> > > >           <id>our-snapshot</id>
> > > >           <name>our-snapshots</name>
> > > >           <url>https://someurlhere</url>
> > > >         </repository>
> > > >
> > > > Example incorrect file below. The *jar snapshotVersion *is one build
> > > > number back, it should be 516
> > > >
> > > > <?xml version="1.0" encoding="UTF-8"?>
> > > > <metadata modelVersion="1.1.0">
> > > >   <groupId>redacted</groupId>
> > > >   <artifactId>also-redacted</artifactId>
> > > >   <version>0.30.17-SNAPSHOT</version>
> > > >   <versioning>
> > > >     <snapshot>
> > > >       <timestamp>20241010.231422</timestamp>
> > > >       <buildNumber>516</buildNumber>
> > > >     </snapshot>
> > > >     <lastUpdated>20241010231529</lastUpdated>
> > > >     <snapshotVersions>
> > > >       <snapshotVersion>
> > > >         <classifier>sources</classifier>
> > > >         <extension>jar</extension>
> > > >         <value>0.30.17-20241010.231422-516</value>
> > > >         <updated>20241010231422</updated>
> > > >       </snapshotVersion>
> > > >       <snapshotVersion>
> > > >         <extension>jar</extension>
> > > >         <value>0.30.17-20241010.215322-515</value>
> > > >         <updated>20241010215322</updated>
> > > >       </snapshotVersion>
> > > >       <snapshotVersion>
> > > >         <extension>pom</extension>
> > > >         <value>0.30.17-20241010.231422-516</value>
> > > >         <updated>20241010231422</updated>
> > > >       </snapshotVersion>
> > > >     </snapshotVersions>
> > > >   </versioning>
> > > > </metadata>
> > > >
> > > > Thanks!
> > > >
> > > >
> > >
> > > --
> > > 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>
>
> ---------------------------------------------------------------------
> 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