[ http://nagoya.apache.org/jira/browse/BEEHIVE-28?page=history ]
     
Steve Hanson resolved BEEHIVE-28:
---------------------------------

     Assign To:     (was: Steve Hanson)
    Resolution: Fixed

These issues have been resolved for the v1Beta branch (rev. ).

Issue 1: ant target deps (e.g. does build.dist.docs depend on docs)
Answer: Yes, "build.dist.docs" has been made to depend on "docs".
Issue 2: what forms do the doc archives come in? (zip? tar.gz?)
Answer 2: The doc are packaged in a distribution-build as an unarchived 
(exploded) directory.  Since the distribution is already zip'ed/tar.gz'ed, 
there isn't much point in making the docs a zip within a zip. 
If you want to make a stand-alone docs jar file, you can call 
"build.dist.docs.jar".  

Issue 3: internal layout of the docs tree
Answer 3: There is now a top level docs directory (trunk/docs).  However this 
directory is really only a *source* directory; nothing ever gets built into 
this directory (e.g., there is no trunk/docs/build file created when docs are 
built).  This is because it would involve copying from-peer-to-peer directories 
(e.g., copying trunk/controls/build  --> trunk/docs/build).  Instead the build 
results are copied into trunk/build.   


Issue 4: What docs go in the docs jar(s) vs the distribution jar(s)? 
There are no docs JAR within the distribution, only an exploded docs directory. 
 If you want to make a docs jar, call "build.dist.docs.jar".

Also, it is not possible to call 'trunk/build.xml> docs' without first calling 
'trunk/build.xml> deploy'.  This is possible because the <netui> taglib doc 
build now checks to see if the necessary resources are available (namely, the 
TLD files).  
If the TLD files are *not* present, then 'trunk/build.xml>ant deploy' is called 
before the taglib doc build is attempted.  
If they *are* present, the taglib doc build is attempted immediately.  
This also avoids the strange 'infinite loop' behavior that was observed when 
'trunk/build.xml> docs' was made to directly depend upon 'trunk/build.xml> 
deploy'.

> Clean up docs build
> -------------------
>
>          Key: BEEHIVE-28
>          URL: http://nagoya.apache.org/jira/browse/BEEHIVE-28
>      Project: Beehive
>         Type: Improvement
>   Components: Documentation
>     Versions: V1Beta
>     Reporter: Kenneth Tam
>      Fix For: V1Beta

>
> Right now the relevant build targets at the top-level for beehive are:
> build.dist.docs
> build.dist.docs.jar 
> Some issues to think about that need to be resolved:
> ant target deps (e.g. does build.dist.docs depend on docs)
> what forms do the doc archives come in? (zip? tar.gz?)
> internal layout of the docs tree
> what docs go in the docs jar(s) vs the distribution jar(s)?

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://nagoya.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira

Reply via email to