On Jun 4, 2008, at 4:42 PM, JerodLass wrote:
It worked when I set the system props from the command line, which
is fine
until next week. When I started playing with it to see how else I
could do
it (the cmd settings were what I tried first), it no longer left
the network
to grab them, even after a gradle clean, because it already had the
hibernate (for example) .jar in what I assume is my local
MavenRepo. How
can I wipe that out to try adjusting the proxy settings a different
way?
Theoretically you find the cached jars in USER_HOME/.gradle/cache
But there is a bug in 0.1.4 (which is already fixed in svn) so that
sometimes USER_HOME/.ivy2/cache is also used.
By removing either the whole cache directories or just the relevant
subfolders you can have a fresh start.
- Hans
Like I said, this will be perfect until 1.5, I was just curious
because I'd
be more comfortable setting proxy configurations in a more internal
fashion.
Also, hooking in tasks worked perfectly. I don't know how I didn't
get that
from the manual and I'm a little embarrassed now. Anyway, thanks
again.
-Jerod
JerodLass wrote:
If I add a Maven2 repository resolver:
dependencies{
addMavenRepo()
}
How can I configure my Maven proxy settings? When I come up with a
settings.xml file, where do I need to put it in order for gradle
to grab
and use it? Thanks in advance for any help...
-Jerod
--
View this message in context: http://www.nabble.com/maven-
repository-tp17630249p17648430.html
Sent from the gradle-user mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
--
Hans Dockter
Gradle Project lead
http://www.gradle.org
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
