Same snapshot number for entired build? possible

[Dan Tran <da...@gmail.com>]

Hi

We have a large build with a few artifacts are consumed by QA (2 vmware
OVAs).  However, each artifact  has its own maven module and therefore has
its own snapshot number

is it possible to fix up deploy-maven-plugin to allow the user configuring
the snapshot number (yes timestamp should be different) so our QA can
correlate/relate the snapshots under test?

Basically, we can auto-detect the current top-level parent snapshot number
at maven repo, and then increment by one and use the same number for the
entire build

Advice is greatly appreciated

-D

Re: Same snapshot number for entired build? possible

[Dan Tran <da...@gmail.com>]

I am just looking for the technical possibility to allow this scenario

    artifact1-timestamp-buildNum.xxx
    artifact2-timestamp-buidNum.xxx

for Maven snapshot build where maven deploy-plugin generates the
timestamp-buildNum parts and they are no guarantee to be the same

I just need the buildNum part to be the same and the ability to specify at
maven-deploy-plugin

Thanks

-D

On Fri, May 3, 2019 at 3:48 AM Tibor Digana <ti...@apache.org> wrote:

> I don't like deploying snapshots, but if you want to do it, you can
> deplyAtEnd=true and eliminate race conditioning on repo. You won't prevent
> from if on 100% with this config.
> Why adding a number manually to SNAPSHOT version, and why not to make an
> ordinal release (using maven-release-plugin) with release candidate
> versions by one person in dev or QA?
> I would personally prefer using Staging server instead of Snapshot repo,
> because staging repo is temporary and release version with release
> candidates on the Staging (marked by Git Tags) can tested in QA. Final
> release candidate would be promoted to public repo and the temporary
> staging repo is deleted. So if you have big deployment files cancalled by
> your QA, don't be afraid that they persist in the repo.
>
> On Thu, May 2, 2019 at 7:49 AM Dan Tran <da...@gmail.com> wrote:
>
> > Hi
> >
> > We have a large build with a few artifacts are consumed by QA (2 vmware
> > OVAs).  However, each artifact  has its own maven module and therefore
> has
> > its own snapshot number
> >
> > is it possible to fix up deploy-maven-plugin to allow the user
> configuring
> > the snapshot number (yes timestamp should be different) so our QA can
> > correlate/relate the snapshots under test?
> >
> > Basically, we can auto-detect the current top-level parent snapshot
> number
> > at maven repo, and then increment by one and use the same number for the
> > entire build
> >
> > Advice is greatly appreciated
> >
> > -D
> >
>

Re: Same snapshot number for entired build? possible

[Tibor Digana <ti...@apache.org>]

I don't like deploying snapshots, but if you want to do it, you can
deplyAtEnd=true and eliminate race conditioning on repo. You won't prevent
from if on 100% with this config.
Why adding a number manually to SNAPSHOT version, and why not to make an
ordinal release (using maven-release-plugin) with release candidate
versions by one person in dev or QA?
I would personally prefer using Staging server instead of Snapshot repo,
because staging repo is temporary and release version with release
candidates on the Staging (marked by Git Tags) can tested in QA. Final
release candidate would be promoted to public repo and the temporary
staging repo is deleted. So if you have big deployment files cancalled by
your QA, don't be afraid that they persist in the repo.

On Thu, May 2, 2019 at 7:49 AM Dan Tran <da...@gmail.com> wrote:

> Hi
>
> We have a large build with a few artifacts are consumed by QA (2 vmware
> OVAs).  However, each artifact  has its own maven module and therefore has
> its own snapshot number
>
> is it possible to fix up deploy-maven-plugin to allow the user configuring
> the snapshot number (yes timestamp should be different) so our QA can
> correlate/relate the snapshots under test?
>
> Basically, we can auto-detect the current top-level parent snapshot number
> at maven repo, and then increment by one and use the same number for the
> entire build
>
> Advice is greatly appreciated
>
> -D
>