Re: IvyDE's workspace resolver taking directory structure into account

2014-01-22 Thread Andrew January
util-1 and util-2 are checked out and have the same content. Then a feature in project-1 requires an api incompatible change in util, so the developer makes those changes in util-1. Unfortunately, because of our workflow, those changes might be sitting around uncommitted on the developers m

Re: IvyDE's workspace resolver taking directory structure into account

2014-01-21 Thread Nicolas Lalevée
Le 15 janv. 2014 à 15:37, Andrew January a écrit : > Has there been any previous discussion around optionally taking directory > structure into account in IvyDE's workspace resolver? > > Our project structure is set up as: > >project-1/ >project-1 >util-1 >project-2/ >

IvyDE's workspace resolver taking directory structure into account

2014-01-15 Thread Andrew January
Has there been any previous discussion around optionally taking directory structure into account in IvyDE's workspace resolver? Our project structure is set up as: project-1/ project-1 util-1 project-2/ project-2 util-2 Where util-1 and util-2 are checked