The one in the Dev Java Net repo looks like this:
org.jvnet.jaxb2.maven2
maven-jaxb2-plugin
0.1
0.5
0.5
0.1
0.2
0.4
0.4.M1
0.4.M2
0.4.M3
0.5
20071215123957
The one in archiva looks like this:
org.jvnet.jaxb2
maven2
maven-jaxb2-plugin
20071215123957
On Tue, 2008-01-29 at
On Jan 29, 2008 1:44 PM, Eric Miles <[EMAIL PROTECTED]> wrote:
> Figured out my problem although not sure why it's NOT a problem when I
> don't use Archiva. This particular plugin (and no others) requires that
> I specify the version in order for the dependency to be downloaded.
> This isn't desir
Figured out my problem although not sure why it's NOT a problem when I
don't use Archiva. This particular plugin (and no others) requires that
I specify the version in order for the dependency to be downloaded.
This isn't desirable as I'd like to have the upgrades to the plugins
when they happen,
I have a managed repository that I intend to use as a proxy for several
remote repositories. I'm doing a test and can't get the proxy to
resolve a plugin dependency to save my life. It will however resolve
regular dependencies to same remote repository. I am attempting to
proxy the Dev Java Net
2007/4/23, nicolas de loof <[EMAIL PROTECTED]>:
Archiva downloads artifacts on demand via HTTP using wagon-http. I use a
similar config with no issue, but I don't have any proxy to set to access
repo1.
Ok, I've solved the issue. The problem had nothing to do with archiva,
but with our network
hing) works fine. I can retrieve
artifacts I deployed manually, can deploy artifacts via webdav, but
proxied repositories don't seem to work.
Now I wanted to ask how Archiva proxies a repository. Somewhere I've
read Archiva loads artifacts from demand, so I guess it recognizes a
HTTP GET o
Hi there,
I've set up Archiva and (almost everything) works fine. I can retrieve
artifacts I deployed manually, can deploy artifacts via webdav, but
proxied repositories don't seem to work.
Now I wanted to ask how Archiva proxies a repository. Somewhere I've
read Archiva loads
> a directory listing. Is that just standard tomcat doing that or
is it
>> archiva making that page for me?
>>
>> -Ben
>>
>> nicolas de loof wrote:
>> > Your right about the "download on request" behaviour :
>> > Archiva will ask the proxie
how it accesses
>> .../repository? When I go to the website and look at /repository, I
get
>> a directory listing. Is that just standard tomcat doing that or
is it
>> archiva making that page for me?
>>
>> -Ben
>>
>> nicolas de loof wrote:
>>
o Observer affect how it accesses
>> .../repository? When I go to the website and look at /repository, I
get
>> a directory listing. Is that just standard tomcat doing that or is it
>> archiva making that page for me?
>>
>> -Ben
>>
>> nicolas de loof wrote:
>
itory, I
get
>> a directory listing. Is that just standard tomcat doing that or is it
>> archiva making that page for me?
>>
>> -Ben
>>
>> nicolas de loof wrote:
>> > Your right about the "download on request" behaviour :
>> > Archiva w
ory listing. Is that just standard tomcat doing that or is it
archiva making that page for me?
-Ben
nicolas de loof wrote:
> Your right about the "download on request" behaviour :
> Archiva will ask the proxied repositories for any artifact missing in
the
> managed repositor
er affect how it accesses
.../repository? When I go to the website and look at /repository, I get
a directory listing. Is that just standard tomcat doing that or is it
archiva making that page for me?
-Ben
nicolas de loof wrote:
> Your right about the "download on request" behaviour :
&
that just standard tomcat doing that or is it
archiva making that page for me?
-Ben
nicolas de loof wrote:
Your right about the "download on request" behaviour :
Archiva will ask the proxied repositories for any artifact missing in the
managed repository.
You need to grant the "gues
ownload on request" behaviour :
Archiva will ask the proxied repositories for any artifact missing in the
managed repository.
You need to grant the "guest" user the observer role so that it can
download
artifacts. Maybe this is the issue you get.
Nico.
2007/3/29, Ben Tatham <[EM
Your right about the "download on request" behaviour :
Archiva will ask the proxied repositories for any artifact missing in the
managed repository.
You need to grant the "guest" user the observer role so that it can download
artifacts. Maybe this is the issue you get.
Ni
Hello All,
I am trying to use archiva on our company network to "proxy" the central
repos...my understanding is that this means that if a developer runs
Maven and requests an artifact from the archiva repository, that if
archiva does not already have it in its own repository, it will get it
fr
17 matches
Mail list logo