Yeah, you can just make a copy of the existing exploded jetspeed-layouts app,. modify the portlet.xml, war it back up and drop it in WEB-INF/deploy.
If you are on 2.1.3, try just modifying the portlet.xml as David suggests. On Tue, Jun 24, 2008 at 2:08 AM, Serkan Camurcuoglu <[EMAIL PROTECTED]> wrote: > Hi Aaron, > I also need to deploy a new two column layout portlet with different widths. > Have you found a better way of doing this? If I want to do it the way you > told, shall I deploy it as a normal portlet application? (e.g. by copying it > to webapps/jetspeed/WEB-INF/deploy/ ) > > Regards, > > SerkanC > > > Aaron Evans wrote: >> >> Just an update to this: >> >> I was able to take a copy of the exploded jetspeed-layouts from my >> jetspeed implementation, add my changes and then war it up and >> re-deploy it and that worked. >> >> However, I would really like to make this part of my build process and >> also be able to make changes to the layouts configs and then run some >> maven command to build and deploy just the jetspeed layouts. >> >> However, in my generated portal project (again, I did the binary build >> using the plugin), I cannot find any trace of the jetspeed-layouts >> application, so I'm not sure how I would go about doing this. >> >> -aaron >> >> On Thu, Jun 12, 2008 at 9:21 PM, Aaron Evans <[EMAIL PROTECTED]> >> wrote: >> >>> >>> I have a jetspeed 2.1 portal installation with the default layouts >>> that came with it. >>> >>> I built it using the maven plugin a while back. >>> >>> I would like to add another layout. Basically it's another instance >>> of MultiColumnPortlet only with different init params (i want to use a >>> custom layout velocity template). >>> >>> Adding a new portlet to the portlet.xml of the layouts app in place >>> and restarting tomcat doesn't do the trick. I guess you have to >>> re-deploy the app to jetspeed so it picks up the new portlet instance? >>> >>> Anyhow, I am just looking for the quickest and easiest way to make >>> this happen. Any suggestions welcome... >>> >>> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> >> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
