Mailing-List: contact repository-help@apache.org; run by ezmlm
Precedence: bulk
Reply-To: repository@apache.org
Received-SPF: unknown (nike.apache.org: error in processing during lookup of
 brianf@sonatype.com)
MIME-Version: 1.0
In-Reply-To: <4AC36D2D.2030603@apache.org>
References: <4AC35577.1040806@sun.com> <4AC36D2D.2030603@apache.org>
From: Brian Fox <brianf@sonatype.com>
Date: Wed, 30 Sep 2009 08:25:54 -0700
Message-ID: <e9b1dfc0909300825h7fb1f6l4a1b24b3928a66c2@mail.gmail.com>
Subject: Re: forcing a sync to the maven 2 repository
To: repository@apache.org
Content-Type: text/plain; charset=ISO-8859-1

Only new files are pulled in, like Simon said you need to change the
version if you want them to be updated. Even if we manually loaded
your jars, anyone in the world that already has a copy would not get
the new ones and it would just create chaos because it would work for
some and not others.

Release artifacts are immutable. It's a fundamental tenet of Maven.
(and good CM practice to boot)

On Wed, Sep 30, 2009 at 7:37 AM, Simon Kitching <skitching@apache.org> wrote:
> Rick Hillegas wrote:
>> Hello,
>>
>> I hope that this is the correct mailing list for this question. If it
>> isn't, please point me in the right direction.
>>
>> The Derby project has been learning how to deploy our build artifacts to
>> the maven 2 repository. This has involved a fair amount of learning for
>> us because we don't use maven in our project builds--we use ant instead.
>> However, I think that we have learned a fair amount and we are getting
>> close to being able to deploy our artifacts correctly.
>>
>> A while ago we copied broken artifacts to the staging area at
>> /www/people.apache.org/repo/m2-ibiblio-rsync-repository/org/apache/derby
>> and they were successfully sync'd to the corresponding maven 2 locations
>> at http://repo1.maven.org/maven2/org/apache/derby After we were told
>> that our artifacts were broken, we copied corrected versions to
>> /www/people.apache.org/repo/m2-ibiblio-rsync-repository/org/apache/derby
>> However, those corrected versions have not been sync'd to the maven 2
>> locations. How do we force a sync to occur?
>
> Maven artifacts should never be replaced/overwritten/removed after
> deployment. It causes all sorts of caching problems for maven users.
>
> The usual solution is simply to deploy a new version; users will get the
> latest version (ie the fixed one) unless they have specifically
> requested otherwise.
>
> Regards,
> Simon
>
> Note: I'm not a repo administrator..
>