rolandz
01-19-2007, 06:57 PM
Hi,
Does it make sense to put into the project tree Spring.Net (among with Spring.Integration) and NHibernate sources using vendor tree scenario being explained in the SVN documentation?
The idea is to put into the repository vendors' branch containing external sources and then copying them into the working branch.
I must emphasize that I _will_ modify projects existing in the branch so the Spring.Integration.NHibernate12 project does not reference to Spring.Core but to the Spring.Core project. And so on... This way I can always have full debug or build release (incl. possibility of enter into any external library with debugger).
The doubt only is whether this makes sense. What are pros and cons. The trees could become complex. Furthermore, most of the source becomes unused (potentially could be deleted).
Does it make sense to put into the project tree Spring.Net (among with Spring.Integration) and NHibernate sources using vendor tree scenario being explained in the SVN documentation?
The idea is to put into the repository vendors' branch containing external sources and then copying them into the working branch.
I must emphasize that I _will_ modify projects existing in the branch so the Spring.Integration.NHibernate12 project does not reference to Spring.Core but to the Spring.Core project. And so on... This way I can always have full debug or build release (incl. possibility of enter into any external library with debugger).
The doubt only is whether this makes sense. What are pros and cons. The trees could become complex. Furthermore, most of the source becomes unused (potentially could be deleted).