|Re: [cross-project-issues-dev] dependencies, build and P2|
On Dec 18, 2010, at 1:45 PM, Miles Parker wrote: > OT a bit now, but this resolves some confusion I had when trying to put together SDKs (complete AMP based IDEs) because it sounds like slicer is used for RCP/Product builds as well -- I saw that I needed to create a separate feature for the SDK and wondered why. Would a simple rule then be: never use include (except as above when you *know* it won't be provisioned from anywhere else) in the "project" features defining a complete set of features, and instead to always put includes in separate projects that wrap up all of the dependencies that you are packaging. ? I've mentioned before the thought that there could be a different project for products altogether with corresponding artifacts, and an extreme reading of that would simply dis-allow depends on in products/platforms and **includes in features**. From what I've seen of examples that work well this seems to be the best practice. Duh, the latter part doesn't make any sense because you'd still want to be able to package up composite features within projects.
Back to the top