commit | 8f96ff2981bdd97b1f01967f65337be81a1e4efc | [log] [tgz] |
---|---|---|
author | Jörg Kubitz <jkubitz-eclipse@gmx.de> | Wed Aug 03 10:57:36 2022 +0200 |
committer | Jörg Kubitz <jkubitz-eclipse@gmx.de> | Wed Aug 03 10:57:36 2022 +0200 |
tree | 217a6abd737def5f496892fbd26a1dfce75dd22e | |
parent | 17d8b45dcf4e4f442d4e3becd2ae4ea1418be6dc [diff] |
Synchronize Maven: resolve using batches use RepositorySystem.resolveArtifacts() per plugin instead of RepositorySystem.resolveArtifact() per file opens less TCP connections and is reproducible faster. like ~ 8min -> 3min on my setup Also use eclipse resource API instead of java file api. Change-Id: Idf0f1f0265cc775890eaf797a1a2fefdb8db730f
Eclipse TEA™ is a tasking orchestration engine that can be run from within the Eclipse IDE or headlessly. It is immediately concerned with tasks related to building and managing plug-ins for the Eclipse Platform, but is general enough to support other types of tasks and builds.
Eclipse TEA's major component is the so called TaskingEngine. This engine can be created and run both from the IDE, as well as headlessly (with a headless presentation engine – thus the PlatformUI.getWorkbench() DOES work – in case a task requires “UI” but still should run headlessly). This allows to create reproducible and stable TaskChains that can be used by both developers and automated builds to create the same, reproducible results for certain tasks.
See our Website at https://www.eclipse.org/tea/ and additional information can be found at https://projects.eclipse.org/projects/technology.tea