You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@aries.apache.org by "Joe Bohn (JIRA)" <ji...@apache.org> on 2010/09/22 00:21:32 UTC
[jira] Reopened: (ARIES-411) Apache Aries blog example currently
uses the no-op resolver instead of the obr resolver to resolve the app
[ https://issues.apache.org/jira/browse/ARIES-411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Joe Bohn reopened ARIES-411:
----------------------------
Assignee: Emily Jiang (was: Mark Nuttall)
I just discovered that this change wasn't quite complete - so I'm reopening the jira.
The changes to date did update the blog-itests - but it didn't update the equinox assemblies that we have for Blog or AriesTrader that used to use the no-op resolver and now are not including the obr-resolver. I have local changes that I could easily check-in to fix this and get the samples working again ... but I'm wondering if perhaps we should instead wait and use the no-op obr bundle that Emily has mentioned she is creating. Thoughts?
> Apache Aries blog example currently uses the no-op resolver instead of the obr resolver to resolve the app
> -----------------------------------------------------------------------------------------------------------
>
> Key: ARIES-411
> URL: https://issues.apache.org/jira/browse/ARIES-411
> Project: Aries
> Issue Type: Bug
> Components: Samples
> Reporter: Emily Jiang
> Assignee: Emily Jiang
> Priority: Minor
> Attachments: jira-411.txt
>
>
> Currently our blog samples does not use the obr resolver to resolve the application. We need to make the blog sample exercises the resolving logic.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.