Mailing-List: contact archiva-dev-help@maven.apache.org; run by ezmlm
Precedence: bulk
Reply-To: archiva-dev@maven.apache.org
Received-SPF: pass (athena.apache.org: domain of nicolas.deloof@gmail.com
 designates 66.249.92.175 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references;
        b=XN5IawgOFQCqdBjI+BhPiF6L61LAZwPdz6PNVJGU1RS0XMleparpftYzzeyQvB+9fIE+qHpwcQyqr43XBhtmK12EAjdowl8Br7HH7jJaQ/O4YjfmkgHyGLbpH/0UcxanQ4nCjp3IcOq545auInXvI2F6Sr1IOW7XFyJiskkMlsQ=
Message-ID: <4c39e3030708070717j16644bddk12bac6b5a6829388@mail.gmail.com>
Date: Tue, 7 Aug 2007 16:17:57 +0200
From: "nicolas de loof" <nicolas.deloof@gmail.com>
To: archiva-dev@maven.apache.org
Subject: Re: [VOTE] Release Archiva-1.0-beta-1
In-Reply-To: <46B87E48.6040503@erdfelt.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_38505_23168531.1186496277720"
References: <46B74AF4.5030904@exist.com>
	 <1a57a2980708061949s7ce0c269t4ab14fe8172f38d0@mail.gmail.com>
	 <58C7C08B-16E6-4940-B42C-4438A6D4DB3A@apache.org>
	 <4c39e3030708070145k5d3d5de9t345fb9e4223d9f38@mail.gmail.com>
	 <4c39e3030708070155u1422519cv4ab5f0a0c8641d68@mail.gmail.com>
	 <B20826BB-BC93-46F8-9BCE-56B7E33B70A9@apache.org>
	 <4c39e3030708070220g3dd0d528h5bfa91f3d3b59b7f@mail.gmail.com>
	 <4c39e3030708070235h7bc848a0l66db14525cd1d7a2@mail.gmail.com>
	 <4c39e3030708070519l29bdcdb4gc00c6cabdd4f2353@mail.gmail.com>
	 <46B87E48.6040503@erdfelt.com>

------=_Part_38505_23168531.1186496277720
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Why is this no longer valid ?
When I ask for a snapshot that is allready present in the managed repo, the
proxied repository are not fetched as the "hasRessource" return true...

I'll prepare a testCase for snapshots updates and attach it to jira, so it
can be better tested.

2007/8/7, Joakim Erdfelt <joakim@erdfelt.com>:
>
> I'm the one that closed that jira.
> I only closed it as won't fix because there wasn't an option "no longer
> valid". ;-)
>
> The CacheFailurePolicy catch was good, thanks! it'll be fixed in svn
> shortly.
> If I could trouble you to report any snapshot bugs you find into jira
> (that would be wonderful) as snapshot functionality is important, but
> poorly tested.
>
> - Joakim
>
> nicolas de loof wrote:
> > The snapshot issue is reported in MRM-320 that has been closed as "won't
> > fix".
> > Doesn't archiva support snapshots updates ;-p ?
> >
> > 2007/8/7, nicolas de loof <nicolas.deloof@gmail.com>:
> >
> >> Without those configuration issues, you get my +1 for a beta.
> >>
> >> the "repository/*" url works fine for both maven1 and maven2 requests.
> >> The only feature I'm still missing is having archiva
> internally  handling
> >> relocation for artifacts requested by maven1... maybe in beta-3 ?
> >>
> >> I also notice the ProxiedDavServer "get" method still use hasResource()
> >> and bypass fetching from propxies if present, so there's no way to get
> newer
> >> snapshots. This may change with the separation between webdav and "GET"
> >> urls.
> >>
> >> Nico.
> >>
> >>
> >>
> >> 2007/8/7, nicolas de loof <nicolas.deloof@gmail.com>:
> >>
> >>> MRM-460 created.
> >>> The typo is only in CacheFailurePolicy log message.
> >>> The main issue is about the archiva default config that refers to an
> >>> invalid "cache" value.
> >>>
> >>>
> >>> Abnother issue with the proposed beta : I had to edit wrapper.conf to
> >>> set
> >>>    wrapper.java.initmemory=8
> >>> as I got (on windows, using run.bat) :
> >>> jvm 1    | [ERROR] Specified initial heap size (3 MB) is less than the
> >>> minimum required initial heap size (8 MB).
> >>> jvm 1    | Could not create the Java virtual machine.
> >>>
> >>>
> >>> 2007/8/7, Brett Porter <brett@apache.org>:
> >>>
> >>>> Is this actually the checksum policy checker, or is it a typo in the
> >>>> description too?
> >>>>
> >>>> Can you put this as a patch in jira? :)
> >>>>
> >>>> - Brett
> >>>>
> >>>> On 07/08/2007, at 6:55 PM, nicolas de loof wrote:
> >>>>
> >>>>
> >>>>> It seems to be a typo in CachedFailuresPolicy
> >>>>>
> >>>>> "
> >>>>>     public boolean applyPolicy( String policySetting, Properties
> >>>>> request,
> >>>>> File localFile )
> >>>>>     {
> >>>>>         if ( !options.contains( policySetting ) )
> >>>>>         {
> >>>>>             // No valid code? false it is then.
> >>>>>             getLogger().error( "Unknown checksum policyCode [" +
> >>>>> policySetting + "]" );
> >>>>>             return false;
> >>>>>         }
> >>>>> "
> >>>>>
> >>>>> That beeing said, the constant is set to "cached" and the default
> >>>>> config to
> >>>>> "cache".
> >>>>> Editing the network-proxies and setting to "cached" solved this.
> >>>>>
> >>>>>
> >>>>> 2007/8/7, nicolas de loof <nicolas.deloof@gmail.com>:
> >>>>>
> >>>>>> I cannot get any artifact from proxy due to some strange checksum
> >>>>>> policy
> >>>>>> error :
> >>>>>>
> >>>>>> According to log, the proxied-repo is set to policy[checksum]:fix :
> >>>>>>     ProxyConnector[
> >>>>>>     jvm 1    |
> >>>>>> source:ArchivaRepository[internal,file://D:\temp\.....data/
> >>>>>> repositories/internal]
> >>>>>>     jvm 1    |   target:ArchivaRepository[central,
> >>>>>> http://repo1.maven.org/maven2]
> >>>>>>     jvm 1    |   proxyId:
> >>>>>>     jvm 1    |   policy[releases]:once
> >>>>>>     jvm 1    |   policy[checksum]:fix
> >>>>>>     jvm 1    |   policy[snapshots]:disabled
> >>>>>>     jvm 1    |   policy[cache-failures]:cache
> >>>>>>     jvm 1    | ]
> >>>>>>
> >>>>>> But latter, I get an Error about Unknown checksum policyCode
> >>>>>>
> >>>> [cache]
> >>>>
> >>>>>> jvm 1    | 2007-08-07 10:37:20,481 [SocketListener0-1] ERROR
> >>>>>> org.apache.maven.archiva.policies.PreDownloadPolicy:cache-failures
>   -
> >>>>>> Unknown checksum policyCode
> >>>>>>
> >>>>>>
> >>>>>> I also had to delete my old $HOME/.m2/archiva.xml as I cannot make
> >>>>>> any
> >>>>>> change in the configuration "cannot save configuration when 2
> >>>>>> sources are
> >>>>>> used".
> >>>>>> Is there any update guide to convert old-style configuration into
> >>>>>> archiva
> >>>>>> 1.0 ? If none, why does archiva still read this deprecated and
> >>>>>> uneditable
> >>>>>> archiva.xml file ?
> >>>>>>
> >>>>>> Nico.
> >>>>>>
> >>>>>>
> >>>
> >
> >
>
>
> --
> - Joakim Erdfelt
>   joakim@erdfelt.com
>   Open Source Software (OSS) Developer
>
>

------=_Part_38505_23168531.1186496277720--