as stated before we are not cutting RC build at CI level. We must stay
with snapshot until it is closed to release date, this is where we will use
CI friendly RC ( ie no more snaphots)
Clarification of to your problem statements:
1. QA needs projects built from the same revision and each
Dan,
Thank you for clarifying the problem more. I think I understand better now.
It sounds like there are really 2 problems:
1. QA needs projects built from the same revision.
2. When the projects are built from the same revision, no one can verify
that easily because the build numbers are
@Dan see here
https://github.com/apache/maven/blob/master/maven-resolver-provider/src/main/java/org/apache/maven/repository/internal/RemoteSnapshotMetadata.java
On Mon, Sep 16, 2019, 00:35 Dan Tran wrote:
> Please keep in mind QA is not a maven user. All download/deployment and
> testing are
Please keep in mind QA is not a maven user. All download/deployment and
testing are mostly automated, however, when come to reporting they have to
use something concrete which is the exact snapshot downloaded for them
They also come to accept that each artifact has its own buildNo/snapshotNo,
Hi Francois and Dan,
I understood it the same way as Francois mentioned. Not sure if NN in the
format "artifactId-version-timestamp-NN" is a bug. Who cares is probably
someone who downloads the artifact manually, maybe the QA.
Also downloading the artifacts from Nexus never was so trivial for QA
I'm sorry to insist but nevertheless I insist ;). I may have misunderstood
the problem but as I understand it, the whole problem can be sumed up by:
" the fact that the repository adds a number at the end of the deployed
files is a problem because not all artifacts deployed from the same reactor
Found this JIRA at MDEPLOY
* https://issues.apache.org/jira/projects/MDEPLOY/issues/MDEPLOY-217
* https://issues.apache.org/jira/projects/MDEPLOY/issues/MDEPLOY-199
Looks the place to look for is at maven-resolver? which responsible to
download maven-metadata and calculate next build
On Sat, 14 Sep 2019 07:17:16 +0200, Dan Tran wrote:
Still waiting for the maven dev team to chime in if there is possible
solution
Tamás is dev team member :)
I don't know which code is responsible for adding the buildnumer.
Personally I'd like to invest in MNG-5666[1], which should already
, is just an
> > implementation
> > > > detail. You should never end up accessing those files by their name.
> > > > Let me explain: if you want to get all the 3 latest artifacts,
> whatever
> > > the
> > > > file name and the timestamp versio
t; those
> > > 3 artifacts declared as dependencies and use maven dependency plugin (
> > >
> >
> https://maven.apache.org/plugins/maven-dependency-plugin/plugin-info.html
> > > )
> > > to copy those artifacts in a directory. Use the "-U" f
gt; > get the latest version. This way, maven will care about the file names,
> but
> > you will not.
> >
> > I hope I can help
> >
> >
> >
> >
> >
> > On Fri, 13 Sep 2019 at 22:42, Tamás Cservenák
> wrote:
> >
> > > How
t;
>
>
>
>
> On Fri, 13 Sep 2019 at 22:42, Tamás Cservenák wrote:
>
> > Howdy,
> >
> > so what Dan is asking for is I think the following thing:
> > On multi module snapshot deploy, the last bit of snapshot timestamped
> > version is "buildNo".
>
s I think the following thing:
> On multi module snapshot deploy, the last bit of snapshot timestamped
> version is "buildNo".
>
> Consider following scenario: you have a 3 module reactor build:
> i) you deploy first time: the buildNo is -1
> ii) you deploy second time
for is I think the following thing:
> On multi module snapshot deploy, the last bit of snapshot timestamped
> version is "buildNo".
>
> Consider following scenario: you have a 3 module reactor build:
> i) you deploy first time: the buildNo is -1
> ii) you deploy second time
Howdy,
so what Dan is asking for is I think the following thing:
On multi module snapshot deploy, the last bit of snapshot timestamped
version is "buildNo".
Consider following scenario: you have a 3 module reactor build:
i) you deploy first time: the buildNo is -1
ii) you deploy s
can you tell us a little bit more about your problem please ?
You say "Currently, artifact deployed as snapshot at Maven repository has
the following format: artifactId-version-timestamp-NN ". Do youmean the
filename in the repo ? If so, why is it a problem for you ?
Share more with us and I
You never established that you're talking about the projects' versions, as
in the part between the tags. Is that what you're talking about?
If so, did you say the artifactId is part of the version? Can you take
artifactId out of the version and make all projects in your reactor have
the same
Maybe you'd want to deployAtEnd?
https://maven.apache.org/plugins/maven-deploy-plugin/deploy-mojo.html#deployAtEnd
On Fri, Sep 13, 2019 at 12:03 PM Dan Tran wrote:
> Looks like I need to clear thing a little bit
>
> Assume I have a reactor of few hundreds of maven modules and my CI
> build
Looks like I need to clear thing a little bit
Assume I have a reactor of few hundreds of maven modules and my CI
build deploys snapshots, first few good builds, each module deployed to
maven repository have same snapshot number
Once we encounter a build failure at a module, the snapshot number
Dan,
Are you running a single 'mvn deploy' or do you have multiple runs?
I have never seen weird behaviours in multi module projects
Cheers
Enrico
Il ven 13 set 2019, 08:19 Dan Tran ha scritto:
> Hello, Maven dev
>
> any suggestion/thoughts on this issue are very much appreciated
>
> Regards
>
Hello, Maven dev
any suggestion/thoughts on this issue are very much appreciated
Regards
-D
On Wed, Sep 11, 2019 at 7:06 PM Dan Tran wrote:
> Hello Maven Users and Development Team
>
> Currently, artifact deployed as snapshot at Maven repository has the
> following format
>
>
Hello Maven Users and Development Team
Currently, artifact deployed as snapshot at Maven repository has the
following format
artifactId-version-timestamp-NN
where NN auto-incremented at each maven module and the number varies
Is there a way to use same snapshot NN for the entire
I am using Cruise Control for continuous integration and I run nightly
snapshot builds using the deploy goal. I would like to use the same tag
(UTC + build number) that is applied to the deployed jars to tag the
source in subversion. That way I would always be able to check out the
source that
Question: How can I get Maven to deploy version-less SNAPSHOT files to
our SNAPSHOT repository?
Background:
It appears to me as if the mvn deploy command on a SNAPSHOT version
does only deploy numbered snapshot files, but not unnumbered ones. The
mvn install command in contrary puts an unnumbered
.
Andreas
-Original Message-
From: Beyer,Nathan [mailto:[EMAIL PROTECTED]
Sent: Thursday, August 24, 2006 1:21 PM
To: Maven Users List
Subject: RE: SNAPSHOT Deploy
I believe you need to add uniqueVersionfalse/uniqueVersion to the
'distributionManagement' repository/snapshotRepository
I think so too. I believe in Maven 1 you had both worlds.
Andreas
-Original Message-
From: Beyer,Nathan [mailto:[EMAIL PROTECTED]
Sent: Thursday, August 24, 2006 2:20 PM
To: Maven Users List
Subject: RE: SNAPSHOT Deploy
Sounds like an enhancement request. :)
-Original Message
Subject: SNAPSHOT Deploy
Question: How can I get Maven to deploy version-less SNAPSHOT files to
our SNAPSHOT repository?
Background:
It appears to me as if the mvn deploy command on a SNAPSHOT version
does only deploy numbered snapshot files, but not unnumbered ones. The
mvn install command in contrary
Sounds like an enhancement request. :)
-Original Message-
From: Andreas Guther [mailto:[EMAIL PROTECTED]
Sent: Thursday, August 24, 2006 4:07 PM
To: Maven Users List
Subject: RE: SNAPSHOT Deploy
Nathan,
Thank you for your help. Indeed that forces Maven to generate a non
unique
On 8/25/06, Andreas Guther [EMAIL PROTECTED] wrote:
Question: How can I get Maven to deploy version-less SNAPSHOT files to
our SNAPSHOT repository?
Background:
It appears to me as if the mvn deploy command on a SNAPSHOT version
does only deploy numbered snapshot files, but not unnumbered ones.
You can't do both but if you are ok with having only the latest
version available, you can tweak the
distributionManagement/repository/uniqueVersion/ element in your pom.
Set the value to true.
On 5/17/06, Eric White [EMAIL PROTECTED] wrote:
I'm starting to migrate my maven1 projects over to
I'm starting to migrate my maven1 projects over to maven2. I need to
publish snapshot artifacts to a maven1 repository from a maven 2 build.
I have my repo set up in legacy mode, and the artifact publishes and
converts the snapshot to a date encoded version number just like it's
supposed to.
31 matches
Mail list logo
