T
Tim Kuehn
Guest
Because the end goal of the original question is to get to a place where PDS can be used w/out the tool getting bogged down by the size of the code base. Splitting the application into projects is one way to accomplish that goal, but it is also an artificial division of the code base that may or may not reflect the target compile / deployment environment. If that division is not appropriate for the fully assembled code base, then .project and .propath files should be for local use only and shouldn't be part of the final system. If these files fit in with environment from development to deployment, then OP is certainly free to add those files to his code base and proceed accordingly.
Continue reading...
Continue reading...