|
Glad to know it was designed that way. My reasoning for saving the lib with the repository would be to allow the other developers to automatically know where the project originally was sent to. I have some miscellaneous projects that go into non-standard libraries (as compared to our normal development stuff). I know we should be communicating these sorts of things. It was more of an inquiry on my part to know how it worked. I can see your reasoning, but in our environment it doesn't work as well. This is something I can live with, I just thought I would ask about it. On 4/28/05, David Dykstal <david_dykstal@xxxxxxxxxx> wrote: > > The library associated with the project is stored as an eclipse > "persistent > property" of the project and isn't kept in the properties that are shared > in the repository. The reasoning was that this was to be a "scratch > library" in which builds could take place for an individual team member. > If there are several folks on a team and they are all using the same > associated library there is a lot of potential for conflicts to arise. > However, it might make sense to beef up the conflict detection/resolution > and let the associated library be a shared property instead. > > Deleting a project deletes the properties and hence the memory of the > associated library. If you just want to hide the project you could close > it and then when you want it later open it from the standard eclipse > resource Navigator and resynchronize (if necessary) with subversion. That > way the library is preserved. Is deleting a project something you would do > frequently? Do you have the potential for significant conflict among team > members if the associated library were shared? > _______________________ > David Dykstal > david_dykstal@xxxxxxxxxx > -- Mike Wills Midrange Programmer/Lawson Software Administrator koldark@xxxxxxxxx http://mikewills.name Want Gmail? Email koldark+gmail@xxxxxxxxx to get on my waiting list.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.