I use
From: Wayne Beaton
To: cross-project-issues-dev@eclipse.org,
Date: 05/17/2013 02:06 PM
Subject: Re: [cross-project-issues-dev]
Libraty piggy-back CQs
Sent by: cross-project-issues-dev-boun...@eclips
bject:Re: [cross-project-issues-dev] Libraty piggy-back CQs
Sent by:cross-project-issues-dev-boun...@eclipse.org
The issue is one of tracking who is using what third-party library.
Right now, the tools that I use to scan the downloads directory almost do a
good enough job to elim
The issue is one of tracking who is using what third-party library.
Right now, the tools that I use to scan the downloads directory
almost do a good enough job to eliminate piggyback CQs altogether.
Almost. The problem is that the tool only detects libraries that ar
Hi
Thanks; that's clear but is hardly sensible. I have a handful of PB
CQs to raise and I suspect many other projects must do too.
Since we are strongly encouarged to track the latest Orbit version,
shouldn't there be an auto-PB CQ for any project that has a PB
I believe that the Contribution Questionnaire page in the wiki [1]
answers this. If it is unclear, either take a crack at clarifying it
yourself or let me know I can take another run at it.
The short version is that you need CQ for any library that project
code uses
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
