Discussions
Categories
Groups
Community Home
Categories
INTERNAL ENABLEMENT
POPULAR
THRUST SERVICES & TOOLS
CLOUD EDITIONS
Quick Links
MY LINKS
HELPFUL TIPS
Back to website
Home
Web CMS (TeamSite)
Building a spar (sanity check)
nipper
OK, so I am moving SP from a dev server to a prod server.
I have a bunch of TS configs, components, .page, etc.
It looks like I make a folder
/tmp/something with folders (component meta-inf template toolkit workarea_root and workflow) and copy everything in.
create a manifest and zip (calling it .spar)
Where does Ant come in ?
re: the tk.war file, cna I just build the GUI in TS and copy the one local\config\lib\content_center\livesite_customer_out\livesite_customer.tk.war ?
Find more posts tagged with
Comments
Stokes
Ant is a great tool for creating .zip structures--sometimes with its zipfileset you can avoid copying things to a temporary directory as you described--but it's not needed. If you prefer some other way to create the zip-file-named-.spar, then use that.
Stokes.
PaulW
i also would like to know where should that war come from? i want the cusotmer.tk.war and the livesite_customer.tk.war to be copied across.
so am i meant to merge them into a custom war? or build a new toolkit from within local/configs/lib/content_center, with both of those wars in the lib folder?
tec_iwov
i would recomend you just copy the custumer toolkits you use and then run
the build script under the livesite_customer toolkit to rebuild everything