Hi Seidita,
You must configure a remote repository (Repositories menu), and a
proxy connector (Proxy Connectors menu) between the remote repository
and a local repository (I have one named proxy) for each remote
repository you want archiva to use (central, codehaus, ...).
Greetings
2009/2/4 Seid
tory won't be indexed, or it will use a
default value?
Thank you
2009/1/26 Maria Odea Ching :
> On Mon, Jan 26, 2009 at 5:47 PM, Marc Canaleta wrote:
>
>> Hi,
>>
>> I'm using apache archiva 1.1.3 as internal repository and as external
>> repositories p
Hi,
I'm using apache archiva 1.1.3 as internal repository and as external
repositories proxy (central, codehaus, ...). What is the correct
approach?
- A single repository (internal) as repository for internal projects
and external repositories proxy.
- One internal repository for internal projects
Hello,
If "manually loaded jar" means copying the jar file into the repository at
file system level, I supose that its not enough (that jar has no metadata).
A correct way to upload a 3rd party JAR is described here (using maven):
http://maven.apache.org/guides/mini/guide-3rd-party-jars-remote.ht
This is how I think it works, and the common practice in my opinion:
- Every time you deploy an snapshot version, a version with SNAPSHOT
replaced by the timestamp is created.
- This snapshot is never replaced.
- Archiva can purge snapshots based on age or number of snapshots.
- You declare depende