|[cross-project-issues-dev] Libraty piggy-back CQs|
Hi Wayne Can you clarify the policy on library piggy-back CQs?For MDT/OCL we initially used Guava indirectly through Xtext and so might not need a PB CQ although we did raise one since Xtext auto-generates source code for us with direct calls to the Injector class. Subsequently we have some manually written code that exploits Guava too.
Our PB CQ has not updated from version 10, although Guava in Orbit is charging along through 11, 12 with 14 on the horizon.
Are we at fault through not raising more PB CQs? Do I misunderstand the policy? Is the policy inappropriate for major evolving libraries?
Regards Ed Willink
Back to the top