Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • T tor-browser-build
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 219
    • Issues 219
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 11
    • Merge requests 11
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • The Tor Project
  • Applications
  • tor-browser-build
  • Issues
  • #33936
Closed
Open
Created Apr 18, 2020 by Georg Koppen@gkDeveloper

Make our fetch-gradle-dependencies script smarter regarding dependency location

We fetch gradle dependencies with our fetch-gradle-dependencies script but don't really care where exactly we put them in that process. We should change that, though, because otherwise we need to do things like cp -r $gradle_repo/m2/* $gradle_repo in build scripts to adjust the paths so that gradle can find them.

That's a thing our script should do in the first place to avoid complexity in our build scripts.

Edited Oct 03, 2020 by Georg Koppen
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking