Now, they're referring to when uniqueVersion = false (which is not the
default). That feature has always been broken, it was only discovered
recently though, and when I attempted to fix it for 2.0.4 it caused a
performance degradation and I decided to hold off until it could be more
fully considered. It's all documented in JIRA, including the patch to
make it work if you can live with all the extra connections.
- Brett
On 3/07/2006 7:04 AM, Jesse Kuhnert wrote:
Maybe they've been deploying versions using a normal repository element
instead of defining a snapshot repository and -SNAPSHOT version ?
On 7/2/06, Jesse Kuhnert <[EMAIL PROTECTED]> wrote:
Yeah....Even though in my instance it wasn't what I wanted to happen (not
maven's fault, unrelated local patches..), I have seen definite
updates of
SNAPSHOT builds with the same version.
You can pretty easily infer why it works by looking at the timestamp
generated poms from them...
On 7/2/06, Carlos Sanchez <[EMAIL PROTECTED]> wrote:
>
> I don't know what you're saying, you are the first one complaining
> about it. SNAPSHOTS work for me
>
> On 7/2/06, [EMAIL PROTECTED] < [EMAIL PROTECTED]> wrote:
> > Unfortunately the SNAPSHOT-feature is broken (at least in 2.0.4):
When
> you have a copy of a snapshot versioned artifact, the jar is not
updated
> when a new jar with same snapshot version is uploaded to the
repository. I
> already filed this as a bug and hope it will be fixed in 2.0.5. It is
> annoying to increase version numbers during development or sending
mails
> around "please delete xyz in you local repository...
> >
> > Roger
> >
--
Brett Porter <[EMAIL PROTECTED]>
Apache Maven - http://maven.apache.org/
Better Builds with Maven - http://library.mergere.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
