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.
If we go that way, two questions arise
- Do we need a CQ for this (I already filed [2])?
- Is there anything that we’ve overlooked such that 1) is the preferred/better option?
Thanks for your feedback,
Henrik
[1] https://github.com/protossoftware/etrice-gradle-plugin
[2]
https://dev.eclipse.org/ipzilla/show_bug.cgi?id=21859
______________________________
Dr. Henrik Rentz-Reichert
E-Mail:
henrik.rentz-reichert@xxxxxxxxx
Mobile: 0049 176 30682514
PROTOS Software GmbH - Agnes-Pockels-Bogen 1 - D-80992 München
Website: http://www.protos.de
Geschäftsführer: Thomas Schütz, Dr. Henrik Rentz-Reichert
Registergericht: Amtsgericht München HRB 115580 - Sitz: München
Umsatzsteuer-Identifikationsnummer: DE185446589
Unsere aktuelle Datenschutzerklärung nach DSGVO, sowie Kontaktformulare für Ihre Einwilligung und Datenschutzrechte finden Sie unter >
https://www.protos.de/datenschutz/