Hi,
I asked this already on the Sonar mailinglist and the suggested to go for the
artifactory community.
We try to configure Artifactory that it resolves the Sonar artifacts
(http://www.sonarsource.org/). The Sonar installation brings its own maven
repository which we tried to include in
Also, before trying to download from the remote, zap its caches. To do it
login as admin, go to the tree browser, right click on the sonar cache and
click on the zap action.
On Thu, Sep 2, 2010 at 13:00, Yossi Shaul yos...@jfrog.org wrote:
Hi,
The sonar repository is treated as any other
I don't think 403 is going to help in this case, since you want maven to
respond to an auth challenge which will only happen for a 401.
2010/9/1 Marcin Zajączkowski msz...@wp.pl
Dnia 1-09-2010 o godz. 0:26 Yoav Landman napisał(a):
http://../This behavior is by design. Let me explain -
You can turn on debug by modifying the logback config file at:
$artifactory_home/etc/logback.xml. Change the logger named org.artifactory
from INFO to DEBUG.
Artifactory will reload the configuration automatically, so try to download
again
from the remote repository (not the cache) and send me
Hi Yossi,
I hope I have extracted all relevant lines
2010-09-02 15:08:39,330 [pool-1-thread-26] [DEBUG] (o.a.w.s.RepoFilter :83) -
Entering request GET (172.16.15.221)
/sonar/org/codehaus/sonar/runtime/sonar-core-maven-plugin/20100809115828/sonar-core-maven-plugin-20100809115828.pom.
The sonar remote repo receives 503 Service Unavailable when it tries to
connect to the
sonar server. Maybe there are some restrictions accessing sonar from the
machine
Artifactory runs on.
What do you see in sonar access logs (there should be some access logs if
the requests
reaches sonar)?
Can
Hi,
they are running on the same machine just on different ports. But of course it
can be some network restrictions. Ah it must be - I remember a while ago we
used Nexus and had the same issues. But there one can give a filesystem path as
location of a repository and so Sonar was
Hi,
ok it was a network issue... i had a proxy defined as systemwide proxy. as this
is an internal request it failed.
after removing the proxy from the sonar repository its working.
Thanks again
-Original Message-
From: Yossi Shaul yos...@jfrog.org
To: artifactory-users
Dnia 2-09-2010 o godz. 12:08 Yoav Landman napisał(a):
I don't think 403 is going to help in this case, since you want maven to respond to an auth challenge which will only happen for a 401.
I'm not sure what point you are writing about. If about RTFACT-3479 then Yossi wrote about 401 for
2010/9/2 Marcin Zajączkowski msz...@wp.pl
Dnia 2-09-2010 o godz. 12:08 Yoav Landman napisał(a):
I don't think 403 is going to help in this case, since you want maven to
respond to an auth challenge which will only happen for a 401.
I'm not sure what point you are writing about. If about
Hello Everyone:
Okay, so I have a Java Project in Eclipse with 2 dependencies specified in
an ivy.xml file; one for commons-collections and another for junit. This is
a toy example to test ivy and artifactory.
My Ivy settings file is posted below, and when I go to resolve the
dependencies
Hi,
I suspect some issue with IvyIDE cache mechanism.
Did you try first with /repo and switch to /libs-releases ?
Can you get the full stack trace of the NPE appearing in Ivy ?
HTH,
Fred.
On Fri, Sep 3, 2010 at 3:36 AM, matthew.madson
matthew.madson.pub...@gmail.com wrote:
Hello Everyone:
12 matches
Mail list logo
