- Documentation (2.4.0)
- Release Notes
- Tutorials
- Reference
- Introduction
- Settings Files
- Ivy Files
- Ant Tasks
- artifactproperty
- artifactreport
- buildlist
- buildobr
- buildnumber
- cachefileset
- cachepath
- checkdepsupdate
- cleancache
- configure
- convertmanifest
- convertpom
- deliver
- dependencytree
- findrevision
- fixdeps
- info
- install
- listmodules
- makepom
- post resolve tasks
- publish
- repreport
- resolve
- resources
- retrieve
- report
- settings
- var
- Using standalone
- OSGi
- Developer doc
buildobr
since 2.3 From a set of jar artifacts, this task generates an OBR (OSGi Bundle Repository) descriptor. It could be then used by the obr resolver.
The set of jars which will be described by the OBR can be defined in 4 exclusive ways:
- via an Ivy resolver: every jar listed by the resolver will be taken into account
- by defining a root directory: every jar found recursively in that folder will be taken into account
- via the name of an Ivy cache: every artifact contained in the cache will be taken into account
- since 2.4 via a resolve: this task is a post resolve task (with all the behaviour and attributes common to all post resolve tasks), thus ever artifact which has been resolved will be taken into account; it is especially useful for building a target platform
Attributes
since 2.4 This is a post resolve task, with all the behaviour and attributes common to all post resolve tasks.Attribute | Description | Required |
---|---|---|
out | the location of the descriptor file to generate | Yes |
resolverName | the name of the resolver from which the jars should be to gathered | No |
cacheName | the name of the cache from which the jars should be to gathered | No |
baseDir | the folder into which the jars should be gather recursively | No |
sourceType | if used as a post resolve task, 'sourceType' define the type of artifacts which should be considered as source artifacts (defaults to 'source,sources,src') | No |
encoding | The encoding of the resulting xml file | No. Defaults to UTF-8 |
indent | Specify if the xml result file should be indented | No. Defaults to true |
quiet | Log as debug rather than warning the rejected jars as they are illformed | No. Defaults to false |
Examples
<ivy:buildobr baseDir="${eclipse.home}" out="${basedir}/target/repo-eclipse.xml" indent="true" />Builds an indented OBR descriptor from an Eclipse install, with their path relative to the Eclipse install.
<ivy:configure file="ivysettings.xml" />Configure an Ivy settings and builds an OBR descriptor from jars resolved by the defined resolver.
<ivy:buildobr resolverName="my-file-resolver" out="${basedir}/target/repo-eclipse.xml" />
<ivy:configure file="ivysettings.xml" />Configure an Ivy settings and builds an OBR descriptor from jars contained in the defined cache.
<ivy:buildobr cacheName="my-cache" out="${basedir}/target/repo-eclipse.xml" />
<ivy:configure file="ivysettings.xml" />Launch a resolve and then build an obr.xml describing the resolved artifacts.
<ivy:resolve file="ivy.xml" />
<ivy:buildobr out="${basedir}/target-platform-obr.xml" />