beehive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alejandro Ramirez (JIRA)" <>
Subject [jira] Closed: (BEEHIVE-845) Need to be able to specify multiple content roots for Page Flow build
Date Tue, 23 Aug 2005 22:09:09 GMT
     [ ]
Alejandro Ramirez closed BEEHIVE-845:

Verified fixed.  The <build-pageflows> macro is now called with a value of webcontentdir="${web.content.roots}"
 where "web.content.roots" is defined as:
<path id="web.content.roots">
            <pathelement path="${basedir}/content1"/>
            <pathelement path="${basedir}/content2"/>
        <property name="web.content.roots" refid="web.content.roots"/>

I built the attache repro webapp and I did not see any messages of missing pages.  I also
deployed the webapp and was able to access both pages:
  - content1\foo\content1.jsp
  - content2\foo\content2.jsp

> Need to be able to specify multiple content roots for Page Flow build
> ---------------------------------------------------------------------
>          Key: BEEHIVE-845
>          URL:
>      Project: Beehive
>         Type: Improvement
>   Components: NetUI
>     Versions: v1m1
>     Reporter: Rich Feit
>     Assignee: Alejandro Ramirez
>      Fix For: V1
>  Attachments:,
> 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:
For more information on JIRA, see:

View raw message