beehive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rich Feit (JIRA)" <...@beehive.apache.org>
Subject [jira] Commented: (BEEHIVE-845) Need to be able to specify multiple content roots for Page Flow build
Date Tue, 23 Aug 2005 16:48:08 GMT
    [ http://issues.apache.org/jira/browse/BEEHIVE-845?page=comments#action_12319743 ] 

Rich Feit commented on BEEHIVE-845:
-----------------------------------

OK, that wasn't the best repro.  I'm attaching a new one, which builds from two content directories
(content1, content2) and a source directory (src), into a separate build directory (build/webapp).

    - Edit build.properties to refer to a valid beehive home.
    - Run 'ant build' from the root of the project -- you should see *no errors* about missing
JSPs.
    - Deploy the webapp at build/webapp.
    - Hit http://localhost:8080/webapp/foo/Controller.jpf


> Need to be able to specify multiple content roots for Page Flow build
> ---------------------------------------------------------------------
>
>          Key: BEEHIVE-845
>          URL: http://issues.apache.org/jira/browse/BEEHIVE-845
>      Project: Beehive
>         Type: Improvement
>   Components: NetUI
>     Versions: v1m1
>     Reporter: Rich Feit
>     Assignee: Alejandro Ramirez
>      Fix For: V1
>  Attachments: multipleContentRoots.zip
>
> The Page Flow annotation processor accepts an option ("web.content.root") that tells
it where to look for JSPs.  Some builds aggregate JSPs from multiple content roots.  This
option should accept a path, similar to web.source.roots, instead of just a single value.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Mime
View raw message