ant-ivy-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hiller, Dean (Contractor)" <>
Subject running into error with ${project_loc}
Date Tue, 18 Jan 2011 16:32:29 GMT
I am running into this issue on startup BUT with Ivy...


I naturally don't want to use ${project_loc:<projectname>} as one poster
suggested since many people check out 2 versions(one being on the
production branch and one on the latest).  Checking out 2 versions
requires 2 different names(and both may not match what I specify in my


I was reading through the variable list of choices.  Is there any other
choice than ${project_loc} that might work so the ivy_settings file can
be found on startup and we won't get those errors?


OR is there a way to turn off IvyDE from trying to resolve dependencies
on startup on per project basis so colleagues inherit my changes and
stop seeing the error?


I should have asked a while ago but I guess I finally got annoyed enough
that I keep getting the error and others asking about it as well.




This message and any attachments are intended only for the use of the addressee and
may contain information that is privileged and confidential. If the reader of the 
message is not the intended recipient or an authorized representative of the
intended recipient, you are hereby notified that any dissemination of this
communication is strictly prohibited. If you have received this communication in
error, please notify us immediately by e-mail and delete the message and any
attachments from your system.

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message