Re: Current implementation seems to default to old rendering pipeline

- Original Message > From: Gonzalo Aguilar Delgado > To: Jetspeed Developers List > Sent: Thu, March 25, 2010 11:43:47 AM > Subject: Re: Current implementation seems to default to old rendering pipeline > > Hi Woonsan, This is a custom build of the portal and don'

Re: Current implementation seems to default to old rendering pipeline

Hi Woonsan, This is a custom build of the portal and don't have such options... Available jetspeed:mvn targets: install-pa [install-pa] install-portal [install-portal] install [install-portal, install-pa, install] db-portal[install-portal, db-port

Re: Current implementation seems to default to old rendering pipeline

Yes better to put new Jetui as default. Old behaviour seems to be olddd... Gonzalo Aguilar Delgado Consultor CRM - Ingeniero en Informática M. +34 607814276 El mié, 24-03-2010 a las 11:13 -0700, David Sean Taylor escribió: >

Re: Current implementation seems to default to old rendering pipeline

On Wed, Mar 24, 2010 at 11:06 AM, Woonsan Ko wrote: > Hi Gonzalo, > > During deployment, you can use `mvn jetspeed:mvn -Dtarget=ui' to turn on the > new ui pipeline instead of `mvn jetspeed:mvn -Dtarget=demo'. > Or you can use `mvn jetspeed:mvn -Dtarget=min-ui' to turn on the new ui > pipeline i

Re: Current implementation seems to default to old rendering pipeline

;. You can also list all targets by `mvn jetspeed:mvn -Dlist'. Regards, Woonsan - Original Message > From: Gonzalo Aguilar Delgado > To: jetspeed-dev@portals.apache.org > Sent: Wed, March 24, 2010 12:52:39 PM > Subject: Current implementation seems to default to old

Current implementation seems to default to old rendering pipeline

Hi all, I've just installed the trunk version of the portal and the rendering method seems to have changed to the old rendering pipeline. Is that normal? Or is a temporary change? What's the correct method to set the render pipeline? Thank you.