Open Bug 1960941 Opened 1 month ago Updated 16 days ago

Gradle support for a future where app-services is "in tree"

Categories

(Firefox Build System :: Android Studio and Gradle Integration, enhancement)

enhancement

Tracking

(Not tracked)

People

(Reporter: markh, Assigned: markh)

References

(Blocks 1 open bug)

Details

(Whiteboard: [fxsync-])

Attachments

(1 file)

As part of the app-services monorepo work, I'd like to land "preliminary" support for app-services to mozilla-central - ie, to add support for building app-services to mozilla-central even before app-services is actually moved.

This adds some complexity to the gradle files and will leave us with code branches which can't be effectively tested directly, but will make the vendoring process simpler (and ideally scriptable) - ie, just move app-services to moz-central, and the gradle build should magically work.

The idea is to add a new config option, --with-appservices-in-tree (which takes a bool, default value is based on whether app-services is actually on the file system), which provides a MOZ_APPSERVICES_IN_TREE config value.

This will allow mozilla-central to build app servics locally when it
is inside mozilla central. It adds a new config option, --with-appservices-in-tree
(which takes a bool, default value is based on whether app-services is actually on
the file system), which provides a MOZ_APPSERVICES_IN_TREE config value.

Assignee: nobody → markh
Whiteboard: fxsync-
Whiteboard: fxsync- → [fxsync-]
Attachment #9479425 - Attachment description: WIP: Bug 1960941 - Update m-c gradle files to optionally work with a local app-services. r=android-reviewers → WIP: Bug 1960941 - Update m-c gradle files to optionally work with a local app-services.
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: