|[p2-dev] Transitive Dependencies in p2|
Alright, this is a bit of a loaded question, but what is the proper way to do transitive dependencies in p2?
The basic scenario:
Team A publishes feature A hosted at http://example/features/a-feature/site
Feature A depends on feature B hosted at http://example/features/b-feature/site
Team C would like to consume feature A by, say, adding the a-feature/site to its Target Platform. But Team C shouldn't have to know about all of A's dependencies including B feature.
Is there any sort of metadata that could be included in the a-feature/site that could reference the b-feature/site? That way p2 could go to A and follow it to B to resolve A's dependencies? How would you add this metadata?
Or does p2 simply not support this functionality?
This E-Mail (including any attachments) may contain privileged or confidential information. It is intended only for the addressee(s) indicated above.
The sender does not waive any of its rights, privileges or other protections respecting this information.
Any distribution, copying or other use of this E-Mail or the information it contains, by other than an intended recipient, is not sanctioned and is prohibited.
If you received this E-Mail in error, please delete it and advise the sender (by return E-Mail or otherwise) immediately.
This E-Mail (including any attachments) has been scanned for viruses.
It is believed to be free of any virus or other defect that might affect any computer system into which it is received and opened.
However, it is the responsibility of the recipient to ensure that it is virus free.
The sender accepts no responsibility for any loss or damage arising in any way from its use.
E-Mail received by or sent from RBC Capital Markets is subject to review by Supervisory personnel.
Such communications are retained and may be produced to regulatory authorities or others with legal rights to the information.
IRS CIRCULAR 230 NOTICE: TO COMPLY WITH U.S. TREASURY REGULATIONS, WE ADVISE YOU THAT ANY U.S. FEDERAL TAX ADVICE INCLUDED IN THIS COMMUNICATION IS NOT INTENDED OR WRITTEN TO BE USED, AND CANNOT BE USED, TO AVOID ANY U.S. FEDERAL TAX PENALTIES OR TO PROMOTE, MARKET, OR RECOMMEND TO ANOTHER PARTY ANY TRANSACTION OR MATTER.