Hi Jacques,

We definitely still need docs-all (it's one of the targets for buildbot), not sure about the other two.

Regards
Scott

HotWax Media
http://www.hotwaxmedia.com

On 25/11/2009, at 12:23 PM, [email protected] wrote:

Author: jleroux
Date: Tue Nov 24 23:23:02 2009
New Revision: 883922

URL: http://svn.apache.org/viewvc?rev=883922&view=rev
Log:
I put descriptions for committers tasks
* docs-all
* build-website
* copy-dtds
But I wonder now if the 2 1st are still needed. It seems that we no longer have JavaDoc on the site (It's automatically built now, isn'it ?)

Modified:
   ofbiz/trunk/build.xml

Modified: ofbiz/trunk/build.xml
URL: 
http://svn.apache.org/viewvc/ofbiz/trunk/build.xml?rev=883922&r1=883921&r2=883922&view=diff
= = = = = = = = ======================================================================
--- ofbiz/trunk/build.xml (original)
+++ ofbiz/trunk/build.xml Tue Nov 24 23:23:02 2009
@@ -232,7 +232,7 @@
    </target>

  <target name="docs-all" depends="build,ofbiz-init"
- description="Build all javadoc into one tree for easier viewing by the community"> + description="For committers : Build all javadoc into one tree for easier viewing by the community">

<echo message="[docs-all] ========== Start Building (JavaDoc) =========="/>

@@ -269,7 +269,8 @@
<!-- WebSite Targets --> <!-- ================================================================== -->

-    <target name="build-website">
+    <target name="build-website"
+ description="For committers : Update dtds and JavaDoc from OFBiz intance to site">
        <antcall target="copy-dtds"/>
        <antcall target="docs"/>
        <antcall target="copy-apis"/>
@@ -291,7 +292,8 @@
        </copy>
    </target>

-    <target name="copy-dtds">
+    <target name="copy-dtds"
+ description="For committers : Copy all dtds from OFBiz instance to website">
        <mkdir dir="${site.dir}/dtds"/>
<copy todir="${site.dir}/dtds" flatten="true" overwrite="true">
            <fileset dir="${basedir}" includes="**/*.dtd"/>



Attachment: smime.p7s
Description: S/MIME cryptographic signature

Reply via email to