You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tuscany.apache.org by "Simon Nash (JIRA)" <de...@tuscany.apache.org> on 2010/09/18 12:59:26 UTC

[jira] Closed: (TUSCANY-3538) Travel sample mvn -Pselfcontained build shouldn't use NodeLauncher or DomainManagerLauncher

     [ https://issues.apache.org/jira/browse/TUSCANY-3538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Simon Nash closed TUSCANY-3538.
-------------------------------


> Travel sample mvn -Pselfcontained build shouldn't use NodeLauncher or DomainManagerLauncher
> -------------------------------------------------------------------------------------------
>
>                 Key: TUSCANY-3538
>                 URL: https://issues.apache.org/jira/browse/TUSCANY-3538
>             Project: Tuscany
>          Issue Type: Bug
>          Components: Java SCA Travel Sample
>            Reporter: Simon Nash
>            Assignee: Simon Nash
>
> Some of the launchers for the travel sample self-contained build (mvn -Pselfcontained) call the NodeLauncher or DomainManagerLauncher classes.  This causes problems because the NodeLauncher and DomainManagerLauncher classes automatically search for Tuscany runtime jars in various locations including <TUSCANY_HOME>/lib and <TUSCANY_HOME>/modules.  This conflcts with the purpose of the self-contained build which is to resolve all runtime dependencies using explicit dependencies in the Class-Path manifest entry of the launcher jar instead of using environment variable settings.

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