Hi Jason,
This sounds like a really great idea.
Is there an issue or wiki page I can refer people to with regard to this
change? Seems like it should be an improvement noted on the deploy plugin
JIRA.
Cheers,
Matt
On 10/19/07, Jason van Zyl <[EMAIL PROTECTED]> wrote:
>
> I've been working on so
This is a not uncommon issue raised on the Users list, so I'm happy to
see you addressing it, Jason. The general suggestion until now has
been "run Archiva or similar" or "run cron every hour to set -r on all
artifacts in your repo" but a "native Maven solution" will be much
nicer.
Wayne
On 10/19
I think that's a reasonable assumption. The worst cases I can think of:
- it deploys again if the metadata is missing or is missing the
version, no worse than now
- it doesn't deploy again if the metadata thinks it is there and it
isn't (which we can state clearly with a message so there'll be
On 18 Oct 07, at 10:40 PM 18 Oct 07, Brett Porter wrote:
rock on.
How are you going to implement? I'm presuming you also don't want
to download the previous artifact, so either will trust the
metadata, or maybe have a wagon.exists() method check that can HEAD
the file on HTTP and (whatev
rock on.
How are you going to implement? I'm presuming you also don't want to
download the previous artifact, so either will trust the metadata, or
maybe have a wagon.exists() method check that can HEAD the file on
HTTP and (whatever else) on the others?
- Brett
On 19/10/2007, at 3:28 PM
This is an extremely welcome change.
As much as I try to educate developers that releases are immutable I
still get a few people who try to do it anyway and fail because the
artifact is in the local repo or in a proxy.
James
On Thu, 2007-10-18 at 22:28 -0700, Jason van Zyl wrote:
> I've been wor
Jason van Zyl wrote:
I've been working on some release/deployment tools lately for a client
and I modified their deployments so that you could not accidentally
release the same version of an artifact more then once. I can stop
this on the server side only when running a repository manager, bu
I've been working on some release/deployment tools lately for a
client and I modified their deployments so that you could not
accidentally release the same version of an artifact more then once.
I can stop this on the server side only when running a repository
manager, but we have some simp
