Obr repository file

Bundle dependencies are represented as requirement elements, such as the one for an imported package 3. For example, capabilities representing exported packages and requirements representing imported packages both have the package namespace.

A requirement is an LDAP query over the properties of a capability. So, to match a requirement to a capability, first the namespace must match. If that matches, the requirements LDAP query must match the properties supplied by the capabilities.

You can even integrate BIndex into in your build cycle so your repository is updated whenever your bundles change. All you need to do is grab the service implemented by OBR and use it.

The best way to familiarize you with how to use repositories is to give an example and explain what it does along the way. The programmatic entry point to the OBR specification is the RepositoryAdmin service, which is represented by the following interface:.

This RepositoryAdmin service provides centralized access to the federated repository. An OBR implementation implements this interface as well as the other types referenced by it. Figure 3 shows the relationships among the involved entities. The code in the following listing shows the code for the new obr-repo command. It uses RepositoryAdmin to add, remove, and list repositories as well as to discover resources.

The obr-repo command has the following subcommands: list-url, add-url, remove-url, and list. You implement the list-url subcommand 1 to list these repositories by retrieving the RepositoryAdmin service and calling its listRepositories method, which gives you access to the associated Repository objects. In this case, you loop through the repositories and print their names and URLs. You can add or remove repository URLs with the add-url and remove-url subcommands, respectively.

Finally, the list subcommand expects an LDAP query which it passes to discover-Repositories to discover resources 4. If no query is specified, all resources are listed. You loop through the discovered resources and print their presentation name, symbolic name, and version. Discovering bundles is one half of the OBR story; the other half is deploying them and their dependencies into the framework.

The RepositoryAdmin. You first get the Resolver from the RepositoryAdmin service. Then you use the RepositoryAdmin. If you find any resources, you add the first one to the Resolver and call resolve to resolve its dependencies from the available repositories 1.

Latest updates. Adding resources to your project. Configuring the plugin descriptor. Frequently used commands. Atlassian JavaDoc. Tutorials and guides. Product-specific tutorials. Writing and running plugin tests.

Adding SAL dependency. SAL code samples. SAL services. AMPS 8. AMPS 6. REST plugin 2. Plugin Framework FAQ. Writing your first plugin FAQ. Atlassian Marketplace. Asked 9 years, 8 months ago. Active 9 years, 8 months ago. Viewed 2k times. Improve this question. Add a comment. Active Oldest Votes. This plugin will add OBR metadata to any plugin you deploy. Improve this answer. Frank Lee Frank Lee 2, 16 16 silver badges 29 29 bronze badges.

Sign up or log in Sign up using Google. Sign up using Facebook.