[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [modeling-pmc] CQ needed for Gradle plug-in?
|
Henrik,
Comments below.
On 30.03.2020 15:45, Henrik
Rentz-Reichert (hrr) wrote:
Hi,
Eclipse eTrice uses a
combined Maven and Gradle build. The Gradle part uses the
already built generator to generate code for the tests.
Gradle uses our own generator plug-ins for this task.
Those Gradle plug-ins
are not tied with our Eclipse project and just use a passed
class path plus a convention to call the generators.
Now we have two options:
- We leave the sources for the Gradle plug-ins
in our eTrice repository and create another build which
builds and deploys them
- We host the sources independently of eTrice
at GitHub (we already started with this, see [1])
The second option has
the advantage that we can factor out code which isn’t
strictly a part of the eTrice project and can be maintained
separately.
Yes, I suppose a separate repo makes sense, but for EMF I just
keep them in the same repo in a releng folder.
https://git.eclipse.org/c/emf/org.eclipse.emf.git/tree/releng
If we go that way, two
questions arise
- Do we need a CQ for this (I already filed
[2])?
I suppose so, though build dependencies get more into a gray zone
because you don't redistribute this content. So it's more of a
WORKSWITH dependency. It never hurts to file one. :-P
- Is there anything that we’ve overlooked such
that 1) is the preferred/better option?
Whatever makes the most sense for your project and is easiest and
cleanest to maintain seems fine.
_______________________________________________
modeling-pmc mailing list
modeling-pmc@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/modeling-pmc
