David, Thanks for the reply: no wonder I was having trouble with the approach! I would like to use the customizer at some point, but for now I would like to figure out how the underlying mechanics work! I am focusing on the layout/decorations at the momoment... let me dig around some more.
Once I get it figured out, I will add it to the Wiki for you if you'd like so that you and others can help me get other newbies off the ground with jetspeed2. Thanks again, Randy Watler -----Original Message----- From: David Sean Taylor To: Jetspeed Users List Sent: 8/11/04 1:51 AM Subject: Re: JetSpeed2 Maven Plugin On Aug 10, 2004, at 11:27 PM, Randy Watler wrote: > After poking around in the CVS JetSpeed2 world off and on over the > last two > days, I have a quick question on how the existing Maven Plugin support > should be used. I would like to start building a customized portal. > Since > there is no jetspeed2:genapp goal yet, I assume that I should copy the > /portal directories as a starting point and use the > jetspeed2:build.portal > goal to merge/build jetspeed2 support into my customized version? Is > it safe > to say that one should not edit the contents of /portal? > > Just trying to get started on the right foot! > > Randy Watler > Jetspeed2 isn't meant to be 'merged' like Jetspeed1 is merged. We are trying hard to not repeat that pattern. Our goal is to make all resources deployable: - layouts - decorators - portlet applications If you develop a portlet application, simply drop it into the auto deploy directory You are right, you should not edit the portal or components directories unless you are planning on submitting a patch However if you develop your own component, such as the Portal's NavigationState Component or Aggregator Component for example, then you can extend the existing Jetspeed component if necessary, and develop your own component and assemble it in the jetspeed-spring.xml You can also assemble pipelines of request execution in the pipelines.xml, also based on Spring components To create your own portal layout on a page, you will still need to manually edit the PSML until our customizer is ready We have made some progress in the customizer recently, but its still not quite there For examples of creating deployable units of decorations and layout, see examples under portal/src/webapp/WEB-INF/decorations/ We really need more documentation in this area I'll try to get that up on the Wiki -- David Sean Taylor Bluesunrise Software [EMAIL PROTECTED] [office] +01 707 773-4646 [mobile] +01 707 529 9194 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
