https://issues.apache.org/jira/browse/MNG-4059
maybe?
On Tue, Jul 7, 2020 at 8:58 PM Elliotte Rusty Harold
wrote:
> Thank you. That's exactly what I needed to know. The behavior did
> indeed change from 3.0 to 3.1 so I should not be surprised that my PR
> that updates the dependency plugin to
Thank you. That's exactly what I needed to know. The behavior did
indeed change from 3.0 to 3.1 so I should not be surprised that my PR
that updates the dependency plugin to 3.1 should have to update this
detail in the tests.
On Tue, Jul 7, 2020 at 2:52 PM Stephen Connolly
wrote:
>
> So there’s
So there’s a setting for the repo which allows controlling whether to
deploy plain snapshot or timestamp snapshots
https://maven.apache.org/pom.html#repository
Specifically `uniqueVersion`
IIRC there was a deliberate break of that to always be true in Maven 3.0.x
for reasons that only Benjamin
My understanding is that it's "SNAPSHOT" when installing to the local repo
but a snapshot version when deploying to a remote repo. But a rarely look
in the local repo so I could be wrong.
/Anders (mobile)
Den tis 7 juli 2020 13:08Elliotte Rusty Harold skrev:
> Let me correct that. On further
Let me correct that. On further investigation it seems the Maven 3.1
artifact installer writes
expanded-snapshot-2.0-SNAPSHOT.jar
whereas the Maven30Installer would write
expanded-snapshot-2.0-20130710.122148-1.pom
Is this working as intended?
On Mon, Jul 6, 2020 at 5:05 PM Elliotte Rusty
This is a long shot, but does anyone happen to know whether anything
changed with respect to pom installation between Maven 3.0 and 3.1? In
particular, I'm seeing in a test of the copy dependencies Mojo that
expanded-snapshot-2.0.pom
is written into the expected location but
