Cool, I will have to check that out! On Tue, Jun 24, 2008 at 11:27 AM, Serkan Camurcuoglu <[EMAIL PROTECTED]> wrote: > I haven't used maven yet but you can make XSL transformations with Ant for > XML/DOM manipulation.. I think you could easily add nodes to a portlet.xml > using a simple XSL stylesheet.. > > > Aaron Evans wrote: >> >> This would be with my old maven 1 build (still on JS 2.1, haven't had >> time to upgrade). >> >> If in 2.1.3 modifying the existing portlet.xml in place works, that >> will be fine. >> >> The only problem with that is that in order to automate that task as >> part of our build process, we'll have to take a copy of portlet.xml >> and apply our change, save that in our SVN repo and use maven or ant >> to copy it out to the installed jetspeed instance post-install. This >> is fine except we'll have to remember to re-apply our change for every >> subsequent jetspeed upgrade. >> >> If only ant/maven could handle XML/DOM manipulation. :) >> >> One source of confusion for me though was in my generated portal >> project (maven1 genapp goal), I can find no trace of the >> jetspeed-layouts app. So I couldn't even modify it before I do the >> final install. >> >> Does the maven build just pull down a copy of the jetspeed layouts war >> from a maven repository as part of the installation? >> >> cheers, >> aaron >> >> On Tue, Jun 24, 2008 at 2:32 AM, David Sean Taylor >> <[EMAIL PROTECTED]> wrote: >> >>> >>> On Jun 13, 2008, at 7:42 AM, 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. >>>> >>>> >>> >>> You should be able to simply update the portlet.xml in the deployed area >>> and >>> it will pick it up >>> At least that works in 2.1.3, just tested it >>> >>> As for automating the portlet.xml override in a Maven build, is it a >>> Maven-1 >>> or Maven-2 build? >>> Either way, recommend creating a modified jetspeed-layouts.war with your >>> portlet.xm inside it >>> >>> With Maven-1, you can pretty easily write a goal to do that for you >>> With Maven-2, I was hoping you could put this project into your custom >>> project under applications >>> Unfortunately this will not be treated as a local application, we don't >>> have >>> a local-application prototype >>> >>> >>> >>> --------------------------------------------------------------------- >>> 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] > >
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
