On 12-02-23 04:37 AM, Chas Emerick wrote:
On Feb 23, 2012, at 1:01 AM, Chris Graham wrote:
Remember that 'deploy' still calls 'install'.
Very true for `mvn`. Not true in Aether; this would seem to be a userland tool
convention, and not a fundamental characteristic of the 'deploy' operation.
However, even Aether leaves some resolver-status and metadata files in the
local repository after completing a 'deploy'...although I can't determine the
significance of them.
One thing I've discovered is that an installed SNAPSHOT will always take
precedence over SNAPSHOTs from remote repositories, whereas this is not the
case for SNAPSHOTs that are deployed to a local repository. So, there's one
significant difference at least.
It's unfortunate that the most fundamental things in Maven are essentially
undocumented AFAICT: what 'deploy' and 'install' do, the various contents (and
potential contents) of repositories in different contexts and their semantics,
and so on.
Very true. It would be great to get your findings documented. Btw I
still think the best thing to do is to do the same as Maven does .. just
so you dont create slight differences in behaviour. The potential
debugging problems are way more of a time waste then just doing the
install like maven does even if that is a bit inefficient..
just my 2c though..
manfred
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org