Ron Wheeler <rwheeler <at> artifact-software.com> writes: > > Excellent. This looks like the guidance that I was seeking. > > I have a little trouble parsing your item 3. Can you clarify this? > > Aaron Evans wrote: > > > >3. I then setup a directory in that project called customizations where I > >create additional resources or manage any jetspeed resources I need to > >change. > >I have an ant task that installs all the customizations in the appropriate > >spots in the generated jetspeed portal files within the project. > >
Ok, so my eclipse workspace is located at c:\workspace. In there is the jetspeed portal project named 'portal'. This is the target of my j2:portal.genapp. So after running this maven goal, the contents of c:\workspace\portal looks like: core-build.xml full-portal.xml jetspeed-components.xml project-info.xml project.xml target I then added a directory called 'customizations' to the root of the project. This directory will *never* get overwritten by re-running j2:portal.genapp. So suppose I want to customize the default-page.psml (located in target/portal/WEB-INF/pages). I make a copy of it to customizations/WEB-INF/pages and do my changes there. I have an ant task that simply copies the contents of customizations to target/portal. As I mentioned, this has the benefit that I can easily update my jetspeed build by re-running j2:portal.genapp. This *will* overwrite anything I have changed in target/portal, but I just re-run my ant task and my customizations are re-installed. (Incidentally, I will NOT re-run j2:portal.genapp until the PortalAggregator bug you guys have found gets resolved cause mine is working). The other benefit is that it makes it easy to revert to a jetspeed vanilla install so that if one of my customizations doesn't seem to work, I can revert and see if it is my problem or a problem with jetspeed. Since jetspeed is big on maven, there is probably a *maven* way to add your customizations, but frankly, I have enough new stuff to learn with jetspeed and portlet development that I don't have time to learn the ins and outs of maven. So I'll stick with ant for now, it seems to be the industry standard anyway... --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
