aries-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alasdair Nottingham (JIRA)" <>
Subject [jira] Resolved: (ARIES-335) Update OBR Application Resolver to use OBR 1.6
Date Tue, 15 Jun 2010 10:55:24 GMT


Alasdair Nottingham resolved ARIES-335.

    Resolution: Fixed

> Update OBR Application Resolver to use OBR 1.6
> ----------------------------------------------
>                 Key: ARIES-335
>                 URL:
>             Project: Aries
>          Issue Type: Improvement
>          Components: Application
>    Affects Versions: 0.2
>            Reporter: Alasdair Nottingham
>            Assignee: Alasdair Nottingham
>             Fix For: 0.2
> In the initial OBRApplicationResolver we had to do some pretty nasty things to get it
to work because of the way OBR works. The two biggest are:
> 1. We had to generate a repository.xml for the application by value content to resolve
against, this had to be written to disk and then removed to add it to OBR.
> 2. We had to add a private repository (the application by value content) as a global
repository. This meant that if someone else used OBR they could have ended up with invalid
results. Also it meant we could only resolve one application at a time.
> 3. The application was resolved against the current framework, and the bundles in the
current framework would be excluded from the results. Since the resolution info can be stored
in the application in the DEPLOYMENT.MF which could be used in a different JVM with different
bundles in the framework you could end up with an app not working in the target framework.
> The latest level of OBR has fixes for these 3 issues, so we should try to update it so
it works against OBR 1.6.
> Oh and OBR 1.6 appears to be faster at parsing the repo.xml files, so every performance
improvement helps.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message