Closed Bug 974199 Opened 11 years ago Closed 11 years ago

Copy apk-factory-library under build

Categories

(Marketplace Graveyard :: Integration, defect)

Product:
Marketplace Graveyard
Component:
Integration
Version:
Avenir
Platform:
x86
macOS
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: ozten, Unassigned)

References

Details

We discovered in stage that the system currently writes to the lib/ext/apk-factory-library/bin directory. We should copy apk-factory-library into a new working directory related to the build destination directory.
Blocks: 958329
It seems like the prototype also wrote here. I've taken a stab at fixing this, to unblock staging. Creating a copy of apk-factory-library under build dir. Example: create /tmp/andorid-projects/com.testmanifest.test1003.p50827d8fae4cae002aaf1f9328ff36c9 create /tmp/andorid-projects/com.testmanifest.test1003.p50827d8fae4cae002aaf1f9328ff36c9-library copy contents of apk-factory-library into com.testmanifest.test1003.p50827d8fae4cae002aaf1f9328ff36c9-library Fixed in https://github.com/mozilla/apk-factory-service/commit/aba5184b094d19ef27acf4ccb9ec67e8e0b2567b
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
James, can you sanity check this approach? Thanks!
Flags: needinfo?(jhugman)
Blocks: 974020
AFAIT, you're making a copy of the library for every project? This is feasible, and probably advisable while we are still compiling the library project. If and when we move to an approach based on aar files, this would be less sensible.
Flags: needinfo?(jhugman)
Pirate files, got it. AAR!
You need to log in before you can comment on or make changes to this bug.