On 2012/06/15 15:56:08, tbroyer wrote:
https://gwt-code-reviews.appspot.com/1727808/diff/16001/distro-source/build.xml
File distro-source/build.xml (right):
https://gwt-code-reviews.appspot.com/1727808/diff/16001/distro-source/build.xml#newcode39
distro-source/build.xml:39: <zipfileset
file="${gwt.build.lib}/gwt-elemental.jar" prefix="${project.distname}"
/>
On 2012/06/15 15:39:27, rdayal wrote:
> Will this cause the build to fail if gwt-elemental.jar is not
present?
No.
If you use "ant -quiet clean dist", you'll see the "Building SDK
without
Elemental" warning from above and then "BUILD SUCCESSFUL".
At least with Ant 1.8.2.
https://gwt-code-reviews.appspot.com/1727808/diff/16001/maven/lib-gwt.sh
File maven/lib-gwt.sh (right):
https://gwt-code-reviews.appspot.com/1727808/diff/16001/maven/lib-gwt.sh#newcode136
maven/lib-gwt.sh:136: maven-deploy-file $mavenRepoUrl $mavenRepoId
"$JAVADOC_FILE_PATH" $gwtPomFile javadoc || warnJavaDoc "gwt-${i}"
On 2012/06/15 15:39:27, rdayal wrote:
> Will the javadoc target generate the javadoc for elemental?
No.
Would you like me to generate the javadoc for Elemental?
It probably makes sense to do so. We can do it in a separate CL though.
I don't think we want to tie it to the general javadoc target. We should
probably have an elemental-javadoc target that generates the javadoc in
a separate jar. We don't need to make this target depend on elemental;
we can just fail if the gwt-elemental.jar is not present.
We'll have to modify the lib-gwt.sh script to handle the different
javadoc jar for elemental.
https://gwt-code-reviews.appspot.com/1727808/
--
http://groups.google.com/group/Google-Web-Toolkit-Contributors
