IvyDE is the most elegant solution. However, it is quite flaky - i.e.
not as polished as the Maven 2 classpath container.

If you can use the last stable version (1.4x) of IvyDE, you'll probably
be ok. Even that version is flaky and can routinely corrupt your
classpath (fixable by right-clicking on the IvyDE classpath item node
and selecting "Refresh") or cause Eclipse to hang (fixable by killing
Eclipse, deleting the IvyDE plugin, restarting Eclipse, turning
auto-compile off and re-installing the IvyDE plugin).

If you want smooth integration, an Ant task with XSL is currently the
most reliable way to generate Eclipse classpaths. This strategy will
necessarily involve and extra setup step in your project.

In the end, what works best for you is what is recommended.

Gerard Fernandes 

-----Original Message-----
From: Brown, Carlton [mailto:[EMAIL PROTECTED] 
Sent: 08 February 2008 16:04
To: [email protected]
Subject: Options for using Ivy to maintain Eclipse classpath

Hi all,

 

I have seen a couple of different options out there for using Ivy to
maintain an Eclipse classpath - IvyDE, eclim, etc.   What is the most
current and accepted technique for doing this?

 

Thanks,

Carlton




-----------------------------------------
====================================================
This message contains PRIVILEGED and CONFIDENTIAL information that is
intended only for use by the named recipient. If you are not the named
recipient, any disclosure, dissemination, or action based on the
contents of this message is prohibited. In such case please notify us
and destroy and delete all copies of this transmission.  Thank you.
====================================================
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 
- - - -

This message is intended only for the personal and confidential use of the 
designated recipient(s) named above.  If you are not the intended recipient of 
this message you are hereby notified that any review, dissemination, 
distribution or copying of this message is strictly prohibited.  This 
communication is for information purposes only and should not be regarded as an 
offer to sell or as a solicitation of an offer to buy any financial product, an 
official confirmation of any transaction, or as an official statement of Lehman 
Brothers.  Email transmission cannot be guaranteed to be secure or error-free.  
Therefore, we do not represent that this information is complete or accurate 
and it should not be relied upon as such.  All information is subject to change 
without notice.



Reply via email to