Task #11575 (closed)
Opened 6 years ago
Closed 3 years ago
RFE: Separate the 3rd party libs and OME artefacts
| Reported by: | bpindelski | Owned by: | jamoore |
|---|---|---|---|
| Priority: | minor | Milestone: | Unscheduled |
| Component: | Deployment | Version: | n.a. |
| Keywords: | n.a. | Cc: | mtbcarroll |
| Resources: | n.a. | Referenced By: | n.a. |
| References: | n.a. | Remaining Time: | n.a. |
| Sprint: | n.a. |
Description
A discussion has been started on https://github.com/openmicroscopy/openmicroscopy/pull/1625 and in the "green" room wrt. resolving jars from maven repos and the fact that "./build.py clean" deletes the resolved dependencies cache.
The initial situation was the following:
- set up Ivy to resolve 3rd party JARs online,
- execute a build (Ivy cache gets created),
- execute "clean" (Ivy cache gets deleted),
- drop internet connection,
- build will fail (lacking local cache of JARs).
Josh suggested 2 fixes:
1) remove cleanup of lib/cache from build.xml,
2) also move Ivy cache to ~/.m2 (typical maven cache location).
The rationale for deleting "lib/cache" on "./build.py clean" is that each build is currently (mis?)using lib/cache for storing files. But we would only want the 3rd party jars stored there, not our build artifacts. If we can have them under "target/" then any regular "./build.py clean" would delete the "dangerous" artifacts (in the sense of "/target" growing without bound).
Change History (4)
comment:1 Changed 6 years ago by jburel
comment:2 Changed 3 years ago by jamoore
Referencing ticket #11609 has changed sprint.
comment:3 Changed 3 years ago by jamoore
Referencing ticket #11609 has changed sprint.
comment:4 Changed 3 years ago by sbesson
- Resolution set to fixed
- Status changed from new to closed
Recent improvements should now use the Maven repository for caching the 3d party libraries and the local repository should have been largely cleaned barring what is not available in Central Maven.
Referencing ticket #11609 has changed sprint.