Hi Deng,

Thanks very much for this, exactly what I needed.

Regards,
Jonathan

-----Original Message-----
From: odeach...@gmail.com [mailto:odeach...@gmail.com] On Behalf Of Deng
Ching
Sent: Monday, 18 April 2011 2:45 a.m.
To: users@archiva.apache.org
Cc: Jonathan Opperman
Subject: Re: Repository not working in archiva

Hi Jonathan,

I think a wget on the artifact would work (ex. wget
http://localhost:8080/archiva/repository/[groupId_path]/[artifactId_path
]/[version]/[artifact_filename])

Thanks,
Deng

On Sat, Apr 16, 2011 at 10:31 AM, Jonathan Opperman
<jonathan.opper...@ecngroup.co.nz> wrote:
>
>
>
> -----Original Message-----
> From: odeach...@gmail.com on behalf of Deng Ching
> Sent: Fri 4/15/2011 10:04 PM
> To: users@archiva.apache.org
> Subject: Re: Repository not working in archiva
>
> On Fri, Apr 15, 2011 at 5:17 PM, Jonathan Opperman
> <jonathan.opper...@ecngroup.co.nz> wrote:
>> Sorry, subject should read: Repository not working in archiva
>>
>> -----Original Message-----
>> From: Jonathan Opperman [mailto:jonathan.opper...@ecngroup.co.nz]
>> Sent: Fri 4/15/2011 9:13 PM
>> To: users@archiva.apache.org
>> Subject: Repository now working in archiva
>>
>> Hi All,
>>
>> I've added:
>>
>> <remoteRepository>
>>
<url>http://maven.alfresco.com/nexus/content/repositories/activiti/</url
>
>> <username/>
>> <password/>
>> <id>activiti</id>
>> <name>activiti</name>
>> </remoteRepository>
>>
>> and
>>
>> <proxyConnector>
>> <order>14</order>
>> <sourceRepoId>internal</sourceRepoId>
>> <targetRepoId>activiti</targetRepoId>
>> <proxyId>local_squid_proxy</proxyId>
>> <policies>
>> <propagate-errors-on-update>always</propagate-errors-on-update>
>> <cache-failures>no</cache-failures>
>> <releases>hourly</releases>
>> <propagate-errors>stop</propagate-errors>
>> <snapshots>hourly</snapshots>
>> <checksum>fail</checksum>
>> </policies>
>> </proxyConnector>
>>
>> But when I search for activiti in archiva it does not find it?
>
>>>Hi Jonathan,
>>>
>>>The artifacts need to be requested first before it would be available
>>>in Archiva. And the artifacts need to be in a managed repository
first
>>>before it can be searchable from the webapp.
>>>
>>>I'm not sure if you've already read it, but just in case not, this
>>>document might help:
>>>
>>>http://archiva.apache.org/docs/1.3.4/adminguide/proxy-connectors.html
>>>
>>>Thanks,
>>>Deng
>
> Hi Deng,
>
> Thanks for this, I tested with nexus and it behaves differently....how
can I simulate
> a "request"? What's the process on how to add it to a managed
repository?
>
>
> Thanks in advance.
>
> Jonathan
>
>> I do not
>> know where to look at in more depth, enabled all the logging to DEBUG
>> but still no more information?
>>
>> Managed to get the other errors cleared(thanks Wendy) but yet we
>> are unable the get this to work, thought it was a bug in ver 1.2.2
>> so upgraded to 1.3.4 but this is still not working. This is
>> hindering our devs to use this repo, any help/advice will
>> be greatly appreciated.
>>
>> Regards,
>> Jonathan
>>
>>
########################################################################
#############
>> This e-mail message has been scanned for Viruses and Content and
cleared
>> by MailMarshal
>>
########################################################################
#############
>>
>>
>>
########################################################################
#############
>> This e-mail message has been scanned for Viruses and Content and
cleared
>> by MailMarshal
>>
########################################################################
#############
>>
>
>
>
########################################################################
#############
> This e-mail message has been scanned for Viruses and Content and
cleared
> by MailMarshal
>
########################################################################
#############
>
#####################################################################################
This e-mail message has been scanned for Viruses and Content and cleared 
by MailMarshal
#####################################################################################

Reply via email to