glean: Find a way to synchronize the glean version in applications' build.gradle
Categories
(Data Platform and Tools :: Glean: SDK, enhancement, P3)
Tracking
(Not tracked)
People
(Reporter: mdroettboom, Unassigned)
References
Details
(Whiteboard: [telemetry:glean-rs:backlog])
Attachments
(1 file)
From 1515600, :sebastian reported:
I made a copy and paste error when copying the "apply" part into my build.gradle file and setting it up to use the same version as the dependency felt a bit cumbersome. I wonder how we could make that nicer in the future.
The gist here is that we need to keep the version of the build script in sync with the version of glean that is being used in an automated way.
Updated•6 years ago
|
Reporter | ||
Updated•6 years ago
|
Reporter | ||
Updated•6 years ago
|
Reporter | ||
Updated•6 years ago
|
Reporter | ||
Updated•6 years ago
|
Reporter | ||
Comment 1•6 years ago
|
||
Reporter | ||
Comment 2•6 years ago
|
||
The only/best way to do this is to probably publish what we currently have as a "gradle script" as a "gradle plugin" which could then be depended on in the same way as a library. That's a moderate-effort project to solve a problem that will naturally go away when applications use a tagged version of android-components rather than tracking snapshots.
Therefore, we've decided to defer solving this, and added a comment about the need for publishing snapshots immediately after merging changes to sdk_generator.gradle
.
The related bug 1541820 about the ability to build offline also remains unresolved, (and will remain unresolved even after moving off of snapshots), but that's a nice-to-have, not a requirement.
Reporter | ||
Updated•6 years ago
|
Reporter | ||
Updated•6 years ago
|
Updated•6 years ago
|
Updated•5 years ago
|
Updated•5 years ago
|
Reporter | ||
Updated•5 years ago
|
Description
•