Details
-
Bug
-
Status: Reopened
-
Critical
-
Resolution: Unresolved
-
Java-SCA-2.x, Java-SCA-1.x
-
None
Description
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