You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jetspeed-dev@portals.apache.org by Gonzalo Aguilar Delgado <ga...@aguilardelgado.com> on 2010/03/24 12:52:39 UTC

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.







____________________________________




  Gonzalo Aguilar Delgado
  Consultor CRM - Ingeniero en
Informática
        M. +34 607814276











---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org


Re: Current implementation seems to default to old rendering pipeline

Posted by Woonsan Ko <wo...@yahoo.com>.
Hi Gonzalo,

You have an archetype generated portal project there. Unfortunately, the new targets such as ui and min-ui have been added only in the root pom of Jetspeed-2 trunk.
We need to add those to the archetype as well. I think JS2-1121 could be reopened for this.

Regards,

Woonsan



----- Original Message ----
> From: Gonzalo Aguilar Delgado <ga...@aguilardelgado.com>
> To: Jetspeed Developers List <je...@portals.apache.org>
> 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'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-portal]
  
> deploy-pa            [install-pa, 
> deploy-pa]
  db                
>    [install-portal, db-portal, db]
  deploy-portal    
>     [install-portal, install-pa, install,
deploy-portal]
  
> portal-seed          [install-portal, 
> portal-seed]
  portal-seed-dbpsml   [install-portal, 
> portal-seed-dbpsml]
  deploy-portal-dbpsml [install-portal, 
> deploy-portal-dbpsml]
  all            
>       [install-portal, install-pa, install, db-portal,
db, 
> deploy-portal, deploy-pa, all]


Should I rebuild all from scratch with 
> a new project?

Thank 
> you.







____________________________________




  
> Gonzalo Aguilar Delgado
  Consultor CRM - Ingeniero 
> en
Informática
        M. +34 
> 607814276









El mié, 24-03-2010 a las 11:06 
> -0700, Woonsan Ko escribió:
> mvn jetspeed:mvn 
> -Dlist


---------------------------------------------------------------------
To 
> unsubscribe, e-mail: 
> ymailto="mailto:jetspeed-dev-unsubscribe@portals.apache.org" 
> href="mailto:jetspeed-dev-unsubscribe@portals.apache.org">jetspeed-dev-unsubscribe@portals.apache.org
For 
> additional commands, e-mail: 
> ymailto="mailto:jetspeed-dev-help@portals.apache.org" 
> href="mailto:jetspeed-dev-help@portals.apache.org">jetspeed-dev-help@portals.apache.org


      

---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org


Re: Current implementation seems to default to old rendering pipeline

Posted by Gonzalo Aguilar Delgado <ga...@aguilardelgado.com>.
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-portal]
  deploy-pa            [install-pa, deploy-pa]
  db                   [install-portal, db-portal, db]
  deploy-portal        [install-portal, install-pa, install,
deploy-portal]
  portal-seed          [install-portal, portal-seed]
  portal-seed-dbpsml   [install-portal, portal-seed-dbpsml]
  deploy-portal-dbpsml [install-portal, deploy-portal-dbpsml]
  all                  [install-portal, install-pa, install, db-portal,
db, deploy-portal, deploy-pa, all]


Should I rebuild all from scratch with a new project?

Thank you.







____________________________________




  Gonzalo Aguilar Delgado
  Consultor CRM - Ingeniero en
Informática
        M. +34 607814276









El mié, 24-03-2010 a las 11:06 -0700, Woonsan Ko escribió:
> mvn jetspeed:mvn -Dlist


---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org


Re: Current implementation seems to default to old rendering pipeline

Posted by Gonzalo Aguilar Delgado <ga...@aguilardelgado.com>.
Yes better to put new Jetui as default. Old behaviour seems to be
ooooolddd...









____________________________________




  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ó:
> On Wed, Mar 24, 2010 at 11:06 AM, Woonsan Ko <wo...@yahoo.com> 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 instead of `mvn jetspeed:mvn -Dtarget=min'.
> > You can also list all targets by `mvn jetspeed:mvn -Dlist'.
> 
> We are also planning for the installer to provide a Classic (/portal)
> and Jetui (/ui) option, defaulting to Jetui
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
> For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org


Re: Current implementation seems to default to old rendering pipeline

Posted by David Sean Taylor <d....@onehippo.com>.
On Wed, Mar 24, 2010 at 11:06 AM, Woonsan Ko <wo...@yahoo.com> 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 instead of `mvn jetspeed:mvn -Dtarget=min'.
> You can also list all targets by `mvn jetspeed:mvn -Dlist'.

We are also planning for the installer to provide a Classic (/portal)
and Jetui (/ui) option, defaulting to Jetui

---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org


Re: Current implementation seems to default to old rendering pipeline

Posted by Woonsan Ko <wo...@yahoo.com>.
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 instead of `mvn jetspeed:mvn -Dtarget=min'.
You can also list all targets by `mvn jetspeed:mvn -Dlist'.

Regards,

Woonsan




----- Original Message ----
> From: Gonzalo Aguilar Delgado <ga...@aguilardelgado.com>
> To: jetspeed-dev@portals.apache.org
> Sent: Wed, March 24, 2010 12:52:39 PM
> Subject: 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.







____________________________________




  
> Gonzalo Aguilar Delgado
  Consultor CRM - Ingeniero 
> en
Informática
        M. +34 
> 607814276











---------------------------------------------------------------------
To 
> unsubscribe, e-mail: 
> ymailto="mailto:jetspeed-dev-unsubscribe@portals.apache.org" 
> href="mailto:jetspeed-dev-unsubscribe@portals.apache.org">jetspeed-dev-unsubscribe@portals.apache.org
For 
> additional commands, e-mail: 
> ymailto="mailto:jetspeed-dev-help@portals.apache.org" 
> href="mailto:jetspeed-dev-help@portals.apache.org">jetspeed-dev-help@portals.apache.org


      

---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org