Closed fhuberts closed 7 years ago
This requires support from all plugins. Seems better to clean out the workspace and any home directory?
What does this really mean though? Use whatever you have cached but don't download any newer repo indexes or jars? If so, you may want to look at https://github.com/bndtools/bnd/pull/469
I think he wants to use only the bundles built in the workspace, without the cached bundles. I guess local repositories can still be used?
Move to abeyance, will need better specification (and preferably a patch)
We now (mostly) have this for 3.3 with the new RepositoryPlugins that use HttpClient. See https://github.com/bndtools/bnd/pull/1673
When running gradle with --offline, this will set the Workspace in offline mode and direct the HttpClient to not access the network. Older repository plugins which do not use HttpClient will not understand offline mode.
Changes in Bndtools to support this will come in 3.4: https://github.com/bndtools/bndtools/pull/1536.
I would really like an -offline instruction to enforce an offline build, with NO cache access.
Use-case is a self-contained build. For example for products that must be supported and re-buildable long-term.