sorry i think my comment was a little confused. i was in the midst of
trying to find a way to be able to set a global default for the
useOrigin attr, for the tasks that use it. anyways ...
if you look at InstallEngine.java, line 139:
/ resolveEngine.downloadArtifacts(report,
getCacheManager(cache), *false*, artifactFilter);/
it passes a hard coded value of false for useOrigin. that means that
ivy:install will always populate the cache. this just seems wrong. the
cache shouldn't be populated when an artifact is being installed, right?
regardless, this doesn't solve the larger problem for me. trying to
implement a settable global default for useOrigin proved to be more
challenging than i thought.
Xavier Hanin wrote:
On 7/2/07, Jeffrey Blattman <[EMAIL PROTECTED]> wrote:
this was unexpected. i was exploring ways to modify the code to be able
to set a default value for /useOrigin/, and found out that my use of
/ivy:install/ was populating it anyway.
i can see where it might do this as a shortcut w/ the expectation that
if it's installed into a repo then it's going to be accessed, but it
doesn't seem to fit with the definition of install ... ?
Could you give more details, I'm not sure to understand what you mean by
populating useOrigin in install?
Xavier
or am i missing something?
thanks.
