ant-ivy-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Barry Kaplan <grou...@memelet.com>
Subject IvyDE fails to resolve to project if jar does not exists
Date Sun, 31 Aug 2008 12:32:01 GMT

Well, I guess not jar specifically, but if the resolve otherwise fails. This
means that in order for a valid eclipse project classpath be configured the
module must compile and its artifact must have been installed to a
repository in the chain. 

This seems like a severe restriction for building up an IDE classpath. I
would think that if the dependency can be associated to a project then it
should be resolved to the project and the classpath container updated
appropriately -- independent of what is happening in the "outside" world. 

No?
-- 
View this message in context: http://www.nabble.com/IvyDE-fails-to-resolve-to-project-if-jar-does-not-exists-tp19241809p19241809.html
Sent from the ivy-user mailing list archive at Nabble.com.


Mime
View raw message