Every time you run a build with Maven, or PDE Build, you resolve all your dependencies in a transitive manner.
What that means is that you read all the poms, all the manifests, and jump on the next pom, the next manifest.
You gather all the dependencies together. You validate them, throw a few errors and start building.
With Buildr, you’ll do the same BUT you won’t do it every time you run a build.
We keep builds reproducible.
We will arrange the dependencies in one YAML file named dependencies.yml at the root of the project.
That file will be structured as followed:
project id:
resolver:
dependencies:
- group:artifact:extension:version
- group:artifact:extension:version
projects:
- project id
- project idGrammar
project id is the id of the project.
resolver is the name of the resolver used for resolution. We have two main cases: :osgi or :pom.
Artifacts are listed under the artifacts node.
Projects are listed under the projects node.
Here is an example of a dependencies.yml:
container:foo:
osgi:
artifacts:
- com.example:foo:jar:1.0
- com.example:foo2:jar:1.0
projects: []
container:bar:
pom:
artifacts: []
projects:
- container:fooTo get access to the dependencies defined in the file, you can use this API:
compile.with dependencies(resolver)
It will bring all the artifacts and projects as a flat list.
From the command line:
buildr resolve:resolver
In practice:
buildr resolve:osgi
h3. Installing and uploading dependencies
When you resolve your dependencies, you might be using jars that are not part of a Maven repository.
We help users install dependencies in their local Maven repository.
buildr resolve:resolver:install
h4. Upload the dependencies to your remote Maven repository
In the same way you can install dependencies, you can also upload them.
buildr resolve:resolver:upload