I'm not sure I understand the workaround you're talking about... what do you mean by "settings specific to IvyDE which merely include your usual settings + load the properties file in which you define your versions" - what settings would that be?
On Mon, Aug 25, 2008 at 2:28 PM, Xavier Hanin <[EMAIL PROTECTED]> wrote: > On Mon, Aug 25, 2008 at 7:26 PM, Patrick Aikens <[EMAIL PROTECTED]> wrote: > >> I've asked this before and received no answers, so I want to try one more >> time >> before giving in to maintaining a patch on top of ivy or ivyde... >> >> We use ant properties in our ivy.xml files to point to an external file >> that >> defines the configurations used in our modules and specify versions of >> dependencies. IvyDE doesn't know how to deal with these properties - is >> there >> any way to make this work in Eclipse, or would we have to make IvyDE or ivy >> itself evaluate the properties in Eclipse? I can't imagine that we're the >> only >> ones using properties for dependency versions since it wouldn't be trivial >> to >> make sure that all ivy.xml files across a large set of projects keep the >> version >> of, say, log4j they use in sync. > > The workaround is to use settings specific to IvyDE which merely include > your usual settings + load the properties file in which you define your > versions. But I think there's an open issue in IvyDE JIRA asking to support > properties loading in IvyDE directly to avoid this 'trick', feel free to > submit a patch. > > Xavier > > > > -- > Xavier Hanin - Independent Java Consultant > http://xhab.blogspot.com/ > http://ant.apache.org/ivy/ > http://www.xoocode.org/ > -- SELECT * FROM users WHERE clue > 0
