What I did to solve the problem is: Setting the Eclipse Project dependencies (as without ivy) B -> A. Now you have the 'problem' that the projects are added twice (Ivy Managed Dependencies and Eclipse Project dependencies), but on the project Build Path you can adjust the order so that the workspace project is above the ivy managed dependencies. That works for me (including workspace modifications and compilation).
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Dienstag, 2. Dezember 2008 16:22 To: [EMAIL PROTECTED] Subject: Refactoring code in dependent projects I have this scenario. Project A depends on Project B Before using Ivy I would have Project A and B in my Eclipse workspace, and A would have B as a project on the Build Path. This meant that if I refactored something in B (e.g. rename a service) it would update references to it in A. Now I am using Ivy B ends up being a JAR, I publish it to a repository and then add a dependency to A's ivy.xml. This is fine, as A now relies on a version or latest.integration jar of B. But what if I am working on A and B at the same time and want to rename a service in B ? Do I just rename it in B, publish it, and then manually rename it in A ? Is there a smarter solution ? Target www.targetgroup.net Target is a trading name of Target Group Limited, registered in England and Wales No. 1208137 Registered office: Target House, Cowbridge Road East, Cardiff CF11 9AU ********************************************************************** DISCLAIMER. This message is intended only for the use of the Addressee and may contain information that is PRIVILEGED and CONFIDENTIAL. If you are not the intended recipient you must not copy, distribute or take any action or reliance upon it. The content of this message may also contain personal views of an employee of this company and does not necessarily represent the view of the company. ********************************************************************** This message has been scanned by Norton Anti-Virus. It has also been scanned by MAILsweeper to enforce our e-mail policy. If you have any concerns or comments about the content of this message, please e-mail [EMAIL PROTECTED] ********************************************************************** _____________________________________________________________________ This email has been scanned for all viruses by the MessageLabs Email Security System. For more information on a proactive email security service working around the clock, around the globe, visit http://www.messagelabs.com
