We currently have around a dozen composite projects, which all use the same set of API. The reason we use so much projects instead of a single big one is for performance reasons. When an API change ...
Status changed:
New Idea
to Accepted for Discussion
Hi,
this is an interesting idea, however I want to avoid having references across projects.
You write that one reason is performance, what number of APIs are we talking about?
I want to find out if there can be another way to solve this.
Best regards,
Matti Hjelm