Hi all, 

I've just found this thread as a result of checking through the wiki page I
wrote on getting started with Archiva. 

Thanks to Wendy for added a quick comment or I would have not know there was
an issue. 

I think this whole episode just highlights the problems with not having
proper releases. Here the users are at the mercy of the developers. Should
something get changed or worse, broken, then it's the users who suffer, not
just the developers. Plus it makes it far more difficult for documentation
authors to update wiki content because they cannot mark changes against
versions and thus have to put comments in like "if your software is older
than ..." and "try this or this or this ..." etc.  

I think it's time archiva was given proper releases with version numbers and
change logs. It's time binary releases are put on the web site so users who
just want to use it can download, setup and be assured of the functionality
they are getting. So that next time someone makes a mistake or changes
something without realising the implications, ordinary users don't get
burned. 

I"m sorry if this sounds like a rant, but I seriously disagree with
development source code being presented to users as the only way to access
and use software. 

ciao
Derek


brettporter wrote:
> 
> Joakim,
> 
> Was this something that was changed?
> 
> - Brett
> 
> On 28/01/2007, at 9:37 AM, Wendy Smoak wrote:
> 
>> On 1/27/07, Brett Porter <[EMAIL PROTECTED]> wrote:
>>
>>> The instructions are incorrect - you acccess via the /repository/
>>> URL, which can be configured inside Archiva to proxy an external
>>> repository. Where did you see these instructions?
>>
>> http://docs.codehaus.org/display/MAVENUSER/Archiva+as+a+Proxy
>>
>> IME, unless you use the /proxy url, Archiva will not actually proxy
>> the requests.  Could be that's fixed now, this was a while ago.
>>
>> -- 
>> Wendy
> 
> 

-- 
View this message in context: 
http://www.nabble.com/Re%3A-proxying-was%3A-two-500-errors-tf3129411.html#a8840179
Sent from the archiva-dev mailing list archive at Nabble.com.

Reply via email to