[
https://issues.apache.org/jira/browse/TUSCANY-3726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12922092#action_12922092
]
Simon Nash commented on TUSCANY-3726:
-------------------------------------
It turns out that there's another change needed to make this work. There's some
code in node-launcher/NodeLauncherUtil.java that creates a runtime classpath
from all the jars in the modules and lib directories with a few selected jars
filtered out. I've updated this filtering to exclude the *-dojo jars.
I have made this change under revision r1023825.
> The store-dojo sample and its runtime dependencies should be included in the
> binary distribution
> ------------------------------------------------------------------------------------------------
>
> Key: TUSCANY-3726
> URL: https://issues.apache.org/jira/browse/TUSCANY-3726
> Project: Tuscany
> Issue Type: Bug
> Components: Java SCA Samples
> Affects Versions: Java-SCA-1.6
> Reporter: Simon Nash
> Assignee: Simon Nash
> Fix For: Java-SCA-1.6.1
>
>
> The store-dojo sample and its runtime dependencies should be included in the
> Tuscany SCA Java binary distribution.
> This requires the following jar files to be added to the modules folder of
> the binary distribution:
> tuscany-binding-atom-js-dojo
> tuscany-binding-jsonrpc-js-dojo
> tuscany-implementation-widget-runtime-dojo
> tuscany-web-javascript-dojo
> tuscany-host-tomcat
> The runtime dependencies of these jars need to be added to the lib folder of
> the binary distribution.
> These jars can't be added to tuscany-sca-all and tuscany-sca-manifest because
> of classpath conflicts with other modules already present there.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
