You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@archiva.apache.org by Maria Odea Ching <oc...@exist.com> on 2007/08/06 18:23:16 UTC
[VOTE] Release Archiva-1.0-beta-1
Hi All,
Archiva 1.0-beta-1 is now ready for release.
The highlights of this release are:
- reporting
- repository purge
- fixes in configuration, search and browse
You can access the release notes for Archiva 1.0-beta-1 here:
http://jira.codehaus.org/secure/ReleaseNote.jspa?version=13604&styleName=Text&projectId=10980&Create=Create
<http://jira.codehaus.org/secure/ReleaseNote.jspa?version=13604&styleName=Text&projectId=10980&Create=Create>
While the binaries including the sources, checksums and signatures can
be found in:
http://people.apache.org/builds/maven/archiva/1.0-beta-1/
Everyone is encouraged to vote and give their feedback.
[ ] +1 Release it!
[ ] 0
[ ] -1 Don't release it, because...
The vote will be open for 72 hours. So, cast your votes now ;-)
Here's my +1
Thanks,
Deng
Re: [VOTE] Release Archiva-1.0-beta-1
Posted by John Tolentino <jo...@gmail.com>.
+1 :-)
On 8/7/07, Maria Odea Ching <oc...@exist.com> wrote:
>
> Hi All,
>
> Archiva 1.0-beta-1 is now ready for release.
>
> The highlights of this release are:
> - reporting
> - repository purge
> - fixes in configuration, search and browse
>
>
> You can access the release notes for Archiva 1.0-beta-1 here:
>
>
> http://jira.codehaus.org/secure/ReleaseNote.jspa?version=13604&styleName=Text&projectId=10980&Create=Create
> <
> http://jira.codehaus.org/secure/ReleaseNote.jspa?version=13604&styleName=Text&projectId=10980&Create=Create
> >
>
>
>
> While the binaries including the sources, checksums and signatures can
> be found in:
>
> http://people.apache.org/builds/maven/archiva/1.0-beta-1/
>
>
> Everyone is encouraged to vote and give their feedback.
>
> [ ] +1 Release it!
> [ ] 0
> [ ] -1 Don't release it, because...
>
>
> The vote will be open for 72 hours. So, cast your votes now ;-)
>
>
> Here's my +1
>
>
> Thanks,
> Deng
>
>
>
>
Re: [VOTE] Release Archiva-1.0-beta-1
Posted by Brett Porter <br...@apache.org>.
On 07/08/2007, at 6:45 PM, nicolas de loof wrote:
> 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 thought this was a known issue - I got it in the alpha's as well.
Using "ignore failures" on the proxy connector works for me.
> 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 ?
That's my fault - sorry. You can remove the dummy conf/archiva.xml
file as well to retain the use of ~/.m2/archiva.xml (the format and
location have not changed). I added some code to fail fast in
situations where the configuration might look like it was saved and
is not (ie, when you have an appserver config and a user config).
I've filed an issue to both make this clearer and more elegant.
Really, we should just ban list items existing in both.
- Brett
Re: [VOTE] Release Archiva-1.0-beta-1
Posted by Maria Odea Ching <oc...@exist.com>.
Noted. I'll look into that wrapper problem.. Thanks!
-Deng
nicolas de loof wrote:
> 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 <br...@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 <ni...@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.
>>>>
>>>>
>
>
Re: [VOTE] Release Archiva-1.0-beta-1
Posted by Jesse McConnell <je...@gmail.com>.
+1
I gave it a run through...indexing is working fine, the find artifact works
like a charm...some nice progress on archiva recently
should be a good beta :)
jesse
--
jesse mcconnell
jesse.mcconnell@gmail.com
Re: [VOTE] Release Archiva-1.0-beta-1
Posted by nicolas de loof <ni...@gmail.com>.
I just reopenned it.
Seems there was confusion between ProxyRequestHandler and ProxiedDavServer.
Having to handle snapshots requires to bypass any optimisation of searching
for existing artifacts. Maybe we could detect the request to point to an
artifact (or meta-datas) ? Or maybe this should be delegated to the
managedRepository itself, so that such optimisation gets out of the servlet
scope.
Nico.
2007/8/7, Joakim Erdfelt <jo...@erdfelt.com>:
>
> I closed it because the points raised were in areas / objects / classes
> that I felt no longer existed in the current codebase.
>
> I COULD BE WRONG! (quite likely actually)
>
> Feel free to reopen any ticket you feel needs more attention.
> Don't be afraid to reopen tickets, especially with an explanation, I
> personally consider that to be a normal operation of a issue tracking
> system. I won't get offended by it, honest! :-)
>
> - Joakim
>
> nicolas de loof wrote:
> > 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 <jo...@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 <ni...@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 <ni...@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.confto
> >>>>> 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 <br...@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 <ni...@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.
> >>>>>>>>
>
>
Re: [VOTE] Release Archiva-1.0-beta-1
Posted by Joakim Erdfelt <jo...@erdfelt.com>.
I closed it because the points raised were in areas / objects / classes
that I felt no longer existed in the current codebase.
I COULD BE WRONG! (quite likely actually)
Feel free to reopen any ticket you feel needs more attention.
Don't be afraid to reopen tickets, especially with an explanation, I
personally consider that to be a normal operation of a issue tracking
system. I won't get offended by it, honest! :-)
- Joakim
nicolas de loof wrote:
> 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 <jo...@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 <ni...@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 <ni...@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 <br...@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 <ni...@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.
>>>>>>>>
Re: [VOTE] Release Archiva-1.0-beta-1
Posted by nicolas de loof <ni...@gmail.com>.
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 <jo...@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 <ni...@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 <ni...@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 <br...@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 <ni...@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
>
>
Re: [VOTE] Release Archiva-1.0-beta-1
Posted by Joakim Erdfelt <jo...@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 <ni...@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 <ni...@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 <br...@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 <ni...@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
Re: [VOTE] Release Archiva-1.0-beta-1
Posted by nicolas de loof <ni...@gmail.com>.
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 <ni...@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 <ni...@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 <br...@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 <ni...@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.
> > > >>
> > >
> >
> >
>
Re: [VOTE] Release Archiva-1.0-beta-1
Posted by nicolas de loof <ni...@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 <ni...@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 <br...@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 <ni...@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.
> > >>
> >
>
>
Re: [VOTE] Release Archiva-1.0-beta-1
Posted by nicolas de loof <ni...@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 <br...@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 <ni...@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.
> >>
>
Re: [VOTE] Release Archiva-1.0-beta-1
Posted by Brett Porter <br...@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 <ni...@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.
>>
Re: [VOTE] Release Archiva-1.0-beta-1
Posted by nicolas de loof <ni...@gmail.com>.
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 <ni...@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.
>
Re: [VOTE] Release Archiva-1.0-beta-1
Posted by nicolas de loof <ni...@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.
Re: [VOTE] Release Archiva-1.0-beta-1
Posted by Brett Porter <br...@apache.org>.
I also found an issue related to my configuration changes that a
filed for beta-2. None of these are blocking...
On 07/08/2007, at 12:49 PM, Maria Odea Ching wrote:
> Sorry, I forgot to include the known issues for this release.
>
> Here they are:
> - MRM-454 (Index not updated after repository purge)
> - MRM-455 (Repository Browse not updated after repository purge
> although the
> database is updated during the purge)
>
>
> Thanks,
> Deng
>
>
> On 8/7/07, Maria Odea Ching <oc...@exist.com> wrote:
>>
>> Hi All,
>>
>> Archiva 1.0-beta-1 is now ready for release.
>>
>> The highlights of this release are:
>> - reporting
>> - repository purge
>> - fixes in configuration, search and browse
>>
>>
>> You can access the release notes for Archiva 1.0-beta-1 here:
>>
>>
>> http://jira.codehaus.org/secure/ReleaseNote.jspa?
>> version=13604&styleName=Text&projectId=10980&Create=Create
>> <
>> http://jira.codehaus.org/secure/ReleaseNote.jspa?
>> version=13604&styleName=Text&projectId=10980&Create=Create
>>>
>>
>>
>>
>> While the binaries including the sources, checksums and signatures
>> can
>> be found in:
>>
>> http://people.apache.org/builds/maven/archiva/1.0-beta-1/
>>
>>
>> Everyone is encouraged to vote and give their feedback.
>>
>> [ ] +1 Release it!
>> [ ] 0
>> [ ] -1 Don't release it, because...
>>
>>
>> The vote will be open for 72 hours. So, cast your votes now ;-)
>>
>>
>> Here's my +1
>>
>>
>> Thanks,
>> Deng
>>
>>
>>
>>
Re: [VOTE] Release Archiva-1.0-beta-1
Posted by Maria Odea Ching <oc...@exist.com>.
Sorry, I forgot to include the known issues for this release.
Here they are:
- MRM-454 (Index not updated after repository purge)
- MRM-455 (Repository Browse not updated after repository purge although the
database is updated during the purge)
Thanks,
Deng
On 8/7/07, Maria Odea Ching <oc...@exist.com> wrote:
>
> Hi All,
>
> Archiva 1.0-beta-1 is now ready for release.
>
> The highlights of this release are:
> - reporting
> - repository purge
> - fixes in configuration, search and browse
>
>
> You can access the release notes for Archiva 1.0-beta-1 here:
>
>
> http://jira.codehaus.org/secure/ReleaseNote.jspa?version=13604&styleName=Text&projectId=10980&Create=Create
> <
> http://jira.codehaus.org/secure/ReleaseNote.jspa?version=13604&styleName=Text&projectId=10980&Create=Create
> >
>
>
>
> While the binaries including the sources, checksums and signatures can
> be found in:
>
> http://people.apache.org/builds/maven/archiva/1.0-beta-1/
>
>
> Everyone is encouraged to vote and give their feedback.
>
> [ ] +1 Release it!
> [ ] 0
> [ ] -1 Don't release it, because...
>
>
> The vote will be open for 72 hours. So, cast your votes now ;-)
>
>
> Here's my +1
>
>
> Thanks,
> Deng
>
>
>
>
Re: [VOTE] Release Archiva-1.0-beta-1
Posted by Joakim Erdfelt <jo...@erdfelt.com>.
+1 from me too.
- Joakim
Maria Odea Ching wrote:
> Hi All,
>
> Archiva 1.0-beta-1 is now ready for release.
>
> The highlights of this release are:
> - reporting
> - repository purge
> - fixes in configuration, search and browse
>
>
> You can access the release notes for Archiva 1.0-beta-1 here:
>
> http://jira.codehaus.org/secure/ReleaseNote.jspa?version=13604&styleName=Text&projectId=10980&Create=Create
> <http://jira.codehaus.org/secure/ReleaseNote.jspa?version=13604&styleName=Text&projectId=10980&Create=Create>
>
>
>
>
> While the binaries including the sources, checksums and signatures can
> be found in:
>
> http://people.apache.org/builds/maven/archiva/1.0-beta-1/
>
>
> Everyone is encouraged to vote and give their feedback.
>
> [ ] +1 Release it!
> [ ] 0
> [ ] -1 Don't release it, because...
>
>
> The vote will be open for 72 hours. So, cast your votes now ;-)
>
>
> Here's my +1
>
>
> Thanks,
> Deng
>
>
>
--
- Joakim Erdfelt
joakim@erdfelt.com
Open Source Software (OSS) Developer
Re: [VOTE] Release Archiva-1.0-beta-1
Posted by Emmanuel Venisse <em...@venisse.net>.
+1, works well
Emmanuel
Maria Odea Ching a écrit :
> Hi All,
>
> Archiva 1.0-beta-1 is now ready for release.
>
> The highlights of this release are:
> - reporting
> - repository purge
> - fixes in configuration, search and browse
>
>
> You can access the release notes for Archiva 1.0-beta-1 here:
>
> http://jira.codehaus.org/secure/ReleaseNote.jspa?version=13604&styleName=Text&projectId=10980&Create=Create
> <http://jira.codehaus.org/secure/ReleaseNote.jspa?version=13604&styleName=Text&projectId=10980&Create=Create>
>
>
>
>
> While the binaries including the sources, checksums and signatures can
> be found in:
>
> http://people.apache.org/builds/maven/archiva/1.0-beta-1/
>
>
> Everyone is encouraged to vote and give their feedback.
>
> [ ] +1 Release it!
> [ ] 0
> [ ] -1 Don't release it, because...
>
>
> The vote will be open for 72 hours. So, cast your votes now ;-)
>
>
> Here's my +1
>
>
> Thanks,
> Deng
>
>
>
>
>
>
Re: [VOTE] Release Archiva-1.0-beta-1
Posted by Maria Odea Ching <oc...@exist.com>.
The vote has passed with the following results:
5 Binding Votes (Brett, Jesse, John T., Emmanuel, Joakim)
1 Non-binding Vote (Myself)
I'll finalize the release and send an announcement.
Thanks,
Deng
Brett Porter wrote:
> +1
>
> The licenses and signatures are all in place, and it appears to be
> running fine.
>
> I tested the plexus-runtime version and it deleted 2/3 of my
> repository - just like I asked it to :)
>
> Cheers,
> Brett
>
> On 07/08/2007, at 2:23 AM, Maria Odea Ching wrote:
>
>> Hi All,
>>
>> Archiva 1.0-beta-1 is now ready for release.
>>
>> The highlights of this release are:
>> - reporting
>> - repository purge
>> - fixes in configuration, search and browse
>>
>>
>> You can access the release notes for Archiva 1.0-beta-1 here:
>>
>> http://jira.codehaus.org/secure/ReleaseNote.jspa?version=13604&styleName=Text&projectId=10980&Create=Create
>> <http://jira.codehaus.org/secure/ReleaseNote.jspa?version=13604&styleName=Text&projectId=10980&Create=Create>
>>
>>
>>
>>
>> While the binaries including the sources, checksums and signatures
>> can be found in:
>>
>> http://people.apache.org/builds/maven/archiva/1.0-beta-1/
>>
>>
>> Everyone is encouraged to vote and give their feedback.
>>
>> [ ] +1 Release it!
>> [ ] 0
>> [ ] -1 Don't release it, because...
>>
>>
>> The vote will be open for 72 hours. So, cast your votes now ;-)
>>
>>
>> Here's my +1
>>
>>
>> Thanks,
>> Deng
>>
>>
>
Re: [VOTE] Release Archiva-1.0-beta-1
Posted by Brett Porter <br...@apache.org>.
+1
The licenses and signatures are all in place, and it appears to be
running fine.
I tested the plexus-runtime version and it deleted 2/3 of my
repository - just like I asked it to :)
Cheers,
Brett
On 07/08/2007, at 2:23 AM, Maria Odea Ching wrote:
> Hi All,
>
> Archiva 1.0-beta-1 is now ready for release.
>
> The highlights of this release are:
> - reporting
> - repository purge
> - fixes in configuration, search and browse
>
>
> You can access the release notes for Archiva 1.0-beta-1 here:
>
> http://jira.codehaus.org/secure/ReleaseNote.jspa?
> version=13604&styleName=Text&projectId=10980&Create=Create <http://
> jira.codehaus.org/secure/ReleaseNote.jspa?
> version=13604&styleName=Text&projectId=10980&Create=Create>
>
>
>
> While the binaries including the sources, checksums and signatures
> can be found in:
>
> http://people.apache.org/builds/maven/archiva/1.0-beta-1/
>
>
> Everyone is encouraged to vote and give their feedback.
>
> [ ] +1 Release it!
> [ ] 0
> [ ] -1 Don't release it, because...
>
>
> The vote will be open for 72 hours. So, cast your votes now ;-)
>
>
> Here's my +1
>
>
> Thanks,
> Deng
>
>