beehive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rich Feit (JIRA)" <beehive-...@incubator.apache.org>
Subject [jira] Updated: (BEEHIVE-845) Need to be able to specify multiple content roots for Page Flow build
Date Wed, 06 Jul 2005 21:44:10 GMT
     [ http://issues.apache.org/jira/browse/BEEHIVE-845?page=all ]

Rich Feit updated BEEHIVE-845:
------------------------------

    Attachment: multipleContentRoots.zip

Repro webapp, which contains two content roots: content1 and content2.  A page flow ("foo/Controller.jpf")
in content1 refers to a JSP in content2.  I edited the build.xml script to pass both content1
and content2 as "web.content.dir" to the Page Flow compiler.  Deploy the Beehive runtime into
the attached app, and do 'ant build' in content1/WEB-INF/src -- you should see no warnings
about JSPs not found.

> 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: Rich Feit
>      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