[
https://issues.apache.org/jira/browse/TUSCANY-2408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12610618#action_12610618
]
Simon Laws commented on TUSCANY-2408:
-------------------------------------
See also 2409
The issue of only being able to run tests from the test directory is because
the new node is now not going off and searching magically for the composite.
Personally I don't think the node should but that would mean that we would need
a $TUSCANY evn variable to tell ant where the install is if you need to run it
outside of the sample dir. Any how more input to the API debate.
> itest/osgi-tuscany is broken due to recent changes in Tuscany modules
> ---------------------------------------------------------------------
>
> Key: TUSCANY-2408
> URL: https://issues.apache.org/jira/browse/TUSCANY-2408
> Project: Tuscany
> Issue Type: Bug
> Components: Java SCA OSGi Integration
> Affects Versions: Java-SCA-1.3
> Reporter: Rajini Sivaram
> Assignee: Rajini Sivaram
> Fix For: Java-SCA-1.3
>
>
> Due to recent changes in many Tuscany modules and samples, itest/osgi-tuscany
> is broken.
> Samples based on the new node implementation no longer work unless run from
> the directory containing the sample. Even though this is much easier to fix
> in the samples, I will fix the osgi test harness instead to avoid changes to
> samples.
> Since itest/osgi-tuscany is the only way to run Tuscany inside an OSGi
> runtime at the moment, I would like to fix the 1.3 branch as well if
> possible. There is one minor change in the node2-api pom.xml to generate a
> new OSGi import package since this module dynamically import a class from
> node2-impl. Apart from that all the other changes are contained in
> itest/osgi-tuscany (which is not built during the main build process, so
> there is no risk).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
