[jira] Reopened: (TUSCANY-3449) Dojo install script fails when running from binary distribution ant script

["Simon Nash (JIRA)" <de...@tuscany.apache.org>]

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

Simon Nash reopened TUSCANY-3449:
---------------------------------

      Assignee: Simon Nash  (was: Luciano Resende)

This issue was closed on 16 April even though it contained comments saying that the issue needed to be looked at for 1.x and 2.x.  The closure comment was "Fixed or not an issue now or record the work item somewhere out of jira".

I'm reopening this issue because the 1.6 fix needs to be merged into 1.x (as stated in the JIRA before it was closed). I'll leave it to others to determine what needs doing for 2.x

> Dojo install script fails when running from binary distribution ant script
> --------------------------------------------------------------------------
>
>                 Key: TUSCANY-3449
>                 URL: https://issues.apache.org/jira/browse/TUSCANY-3449
>             Project: Tuscany
>          Issue Type: Bug
>          Components: Java SCA Samples
>    Affects Versions: Java-SCA-2.x, Java-SCA-1.x
>            Reporter: Luciano Resende
>            Assignee: Simon Nash
>            Priority: Critical
>             Fix For: Java-SCA-2.x, Java-SCA-1.x
>
>
> Looks like there are some differences from when using the dojoxxx.zip from maven and directly from dojotoolkit download place.
> This is causing some problems in the 1.6 release, and it also seems that some samples are using different approaches to unzip the archives
> When the dojo-1.3.0.zip is retrieved from a maven repo, it will extract to dojo-1.3.0, thus matchin the pattern we have in the build-dojo.xml
>  <unzip src="${localRepository}/org/dojotoolkit/dojo/${dojo.version}/dojo-${dojo.version}.zip"
>                dest="${basedir}/target/dojo-unpack-temp/"
>                overwrite="false"
>         	   encoding="native-encoding">
>             <patternset>
>                 <include name="dojo-${dojo.version}/dojo/**"/>
>                 <exclude name="dojo-${dojo.version}/dojo/tests/**"/>
>                 <exclude name="dojo-${dojo.version}/dijit/**"/>
>                 <exclude name="dojo-${dojo.version}/dojox/**"/>
>                 <exclude name="dojo-${dojo.version}/util/**"/>
>             </patternset>
>         </unzip>
> The following samples are configured for this option : demos-bigbank, helloworld-dojo-webapp and simple-bigbank-spring
> When the dojo-1.3.0.zip is retrieved from a dojotolkit download website (http://download.dojotoolkit.org/release-${dojo.version}/dojo-release-${dojo.version}.zip), it will extract to dojo-release-1.3.0, and then we need something different in the build-dojo.xml
> <unzip src="${localRepository}/org/dojotoolkit/dojo/${dojo.version}/dojo-${dojo.version}.zip"
>                dest="${basedir}/target/dojo-unpack-temp/"
>                overwrite="false"
>         	   encoding="native-encoding">
>             <patternset>
>                 <include name="dojo-release-${dojo.version}/dojo/**"/>
>                 <exclude name="dojo-release-${dojo.version}/dojo/tests/**"/>
>                 <exclude name="dojo-release-${dojo.version}/dijit/**"/>
>                 <exclude name="dojo-release-${dojo.version}/dojox/**"/>
>                 <exclude name="dojo-release-${dojo.version}/util/**"/>
>             </patternset>
>         </unzip>
> The following samples are configured this way: alert-aggregator-webapp, bigbank-account

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