On 12 May 2013, at 2:47 AM, Joe Osowski wrote:
> Yes, you are correct. However, the problem with release/snapshots is that
> maven assumes a revision in the VCS is a release. But in reality, a release
> is the binary built by maven.
A release is never just the binary built by maven, those ar
Yes, you are correct. However, the problem with release/snapshots is that
maven assumes a revision in the VCS is a release. But in reality, a release is
the binary built by maven. Using snapshots with multiple snapshot dependencies
introduces changes at release time that a release engineer ha
On 11 May 2013, at 10:17 PM, Joe Osowski wrote:
>>> the build to make sure the latest dependencies are downloaded, as we
>>> sometimes
>>> change the non snapshot released binaries on our local maven repository.
>>
>> You do realize that this is a really bad idea, and it will eventually
>> bite
On May 11, 2013, at 1:04 PM, Wayne Fay wrote:
>> the build to make sure the latest dependencies are downloaded, as we
>> sometimes
>> change the non snapshot released binaries on our local maven repository.
>
> You do realize that this is a really bad idea, and it will eventually
> bite you, r
> the build to make sure the latest dependencies are downloaded, as we sometimes
> change the non snapshot released binaries on our local maven repository.
You do realize that this is a really bad idea, and it will eventually
bite you, right?
> [INFO] --- maven-clean-plugin:2.3:clean (default-cle
I'm trying to use the dependency plugin to purge a few dependencies prior to
the build to make sure the latest dependencies are downloaded, as we sometimes
change the non snapshot released binaries on our local maven repository. My
configuration noted below:
org.apache.maven.plu
