What the new user is missing is that the concept up-to-date is
overloaded and means very different things depending on whether it is
applied to a snapshot or to a release.
To make a long story short: if a released package needed repair then
the repaired version needed a new version number. This
very much.
-M
-Original Message-
From: [EMAIL PROTECTED] on behalf of Carlos Sanchez
Sent: Mon 10/6/2008 7:06 PM
To: Maven Users List
Subject: Re: maven repository update.
no, there is not.
Artifacts are not supposed to change after being released. You'd have
to manually copy/delete
On Tue, Oct 7, 2008 at 10:51 AM, Marco Villalobos
[EMAIL PROTECTED] wrote:
This convention makes sense. I wish it was more clearly documented though,
and easier
to find the rule behind this convention.
Where specifically would you expect to see such documentation? As a
new user to Maven,
/introduction-to-repositories.html
-M
-Original Message-
From: Wayne Fay [mailto:[EMAIL PROTECTED]
Sent: Tue 10/7/2008 11:52 AM
To: Maven Users List
Subject: Re: maven repository update.
On Tue, Oct 7, 2008 at 10:51 AM, Marco Villalobos
[EMAIL PROTECTED] wrote:
This convention makes
/introduction/introduction-to-repositories.html
-M
-Original Message-
From: Wayne Fay [mailto:[EMAIL PROTECTED]
Sent: Tue 10/7/2008 11:52 AM
To: Maven Users List
Subject: Re: maven repository update.
On Tue, Oct 7, 2008 at 10:51 AM, Marco Villalobos
[EMAIL PROTECTED] wrote
Perhaps the wording: Forces a check for new snapshots on remote repositories.
Is better, because the words updated releases makes people think the short
version of -U will also update releases, not just snapshots.
But its not just snapshots, its also new versions of releases (updates)...
2008/10/7 Wayne Fay [EMAIL PROTECTED]:
Perhaps the wording: Forces a check for new snapshots on remote
repositories.
Is better, because the words updated releases makes people think the short
version of -U will also update releases, not just snapshots.
But its not just snapshots, its
clear.
This is just my opinion though, and I am sincerely trying to help.
-M
-Original Message-
From: Stephen Connolly [mailto:[EMAIL PROTECTED]
Sent: Tue 10/7/2008 2:23 PM
To: Maven Users List
Subject: Re: maven repository update.
2008/10/7 Wayne Fay [EMAIL PROTECTED]:
Perhaps the wording
: Stephen Connolly [mailto:[EMAIL PROTECTED]
Sent: Tue 10/7/2008 2:23 PM
To: Maven Users List
Subject: Re: maven repository update.
2008/10/7 Wayne Fay [EMAIL PROTECTED]:
Perhaps the wording: Forces a check for new snapshots on remote
repositories.
Is better, because the words updated
: Tue 10/7/2008 2:23 PM
To: Maven Users List
Subject: Re: maven repository update.
2008/10/7 Wayne Fay [EMAIL PROTECTED]:
Perhaps the wording: Forces a check for new snapshots on remote
repositories.
Is better, because the words updated releases makes people think the
short version
.
-M
-Original Message-
From: Stephen Connolly [mailto:[EMAIL PROTECTED]
Sent: Tue 10/7/2008 2:23 PM
To: Maven Users List
Subject: Re: maven repository update.
2008/10/7 Wayne Fay [EMAIL PROTECTED]:
Perhaps the wording: Forces a check for new snapshots on remote
repositories
Hello,
I have a repository called Red, and a build machine called Ark.
Naturally, when you do a build, Ark has its own local repository.
Somebody deployed artifact widget-1.1 to Red.
Ark already has widget-1.1 in its local repository. But it is an older
version. You can tell by
no, there is not.
Artifacts are not supposed to change after being released. You'd have
to manually copy/delete the file
On Mon, Oct 6, 2008 at 6:51 PM, Marco Villalobos
[EMAIL PROTECTED] wrote:
Hello,
I have a repository called Red, and a build machine called Ark.
Naturally, when you
On Mon, Oct 6, 2008 at 6:51 PM, Marco Villalobos
[EMAIL PROTECTED] wrote:
I have a repository called Red, and a build machine called Ark.
Naturally, when you do a build, Ark has its own local repository.
Somebody deployed artifact widget-1.1 to Red.
Ark already has widget-1.1 in its local
14 matches
Mail list logo
