Jeen,
Sorry, I must confess that I've never filed a CQ for any Maven plugins
used in any of the builds I manage. Furthermore, I have never reviewed
a project CQ, as Modeling PMC lead, that has done this. Hence my
surprise at seeing this at all.
Even looking at the example on the following page (referenced from the
mail thread that you referenced), it shows dependencies of test plugin
on libraries that are used to compile such plugins:
https://wiki.eclipse.org/Development_Resources/IP/Test_and_Build_Dependencies
My fundamental assumption is that CQs are about the code in my projects
and about the dependencies of my project's code on other libraries,
including those used purely for testing, not about all the build
infrastructure dependencies on goodness knows what as it changes over time.
I would personally have a canary if I had to report and track all the
Maven plugins used by all my builds.
I hope to see someone whose opinion is authoritative tell us that this
is not necessary.
Regards,
Ed
On 30.09.2020 06:47, Jeen Broekstra wrote:
Hi Ed,
This is nevertheless the method that was recommended to me earlier
(see https://www.eclipse.org/lists/incubation/msg00658.html).
If there are alternative approaches I'm keen to hear more though. How
do you file CQs for maven plugins then? Do you do a separate CQ for
each and every plugin?
Cheers,
Jeen
On Tue, Sep 29, 2020, at 15:18, Ed Merks wrote:
Jeen,
I've never seen a CQ that lists all the Maven dependencies of a
project's build. I've certainly never done such a thing for my
projects nor have I needed to approve such a thing for a Modeling
project. So this looks strange and surprising to me...
Regards,
Ed
On 29.09.2020 01:25, Jeen Broekstra wrote:
hi all,
For our build and test dependencies (things like maven plugins
etc), we have a single umbrella CQ that in its description has a
list of the various plugins, each with a version range. See
https://dev.eclipse.org/ipzilla/show_bug.cgi?id=20318 .
We now face a situation where we need to update that list: there's
one new plugin, and one of the other plugins is updated with a
version that is beyond the range stated in that CQ.
What is the best way to go about this? Should I log a new umbrella
CQ with an updated list and then withdraw the old one? Or can I just
add a comment on the existing CQ?
Jeen
_______________________________________________
incubation mailing list
[email protected] <mailto:[email protected]>
To unsubscribe from this list,
visithttps://www.eclipse.org/mailman/listinfo/incubation
_______________________________________________
incubation mailing list
[email protected] <mailto:[email protected]>
To unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/incubation
_______________________________________________
incubation mailing list
[email protected]
To unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/incubation
_______________________________________________
incubation mailing list
[email protected]
To unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/incubation
