This content has been marked as final. Show 6 replies
Your developers should be able to tell you what software is available to you to do that in your company. Otherwise give them a zip file and let them do it.
They have it all wrong: they need to "wrap it in a .war file" (that's a .zip file for UNIX). Our release engineering folks do that as part of the application build. When the users open the application the first time, the app "unwraps" the .war file for them.
"They" are the ones who should be doing the heavy lifting on this one!
Hello factormax -
Leon "MergeThis" is right.
We deploy our app via a WAR file and it includes all of the Help files. I designed the Help to reside in a separate subdirectory of the application and the app calls-to-help point to that relative location. Only a single XML file gets updated during deployment.
I ZIP the generated Help project and give it to the build manager. He extracts/inserts into his build environment, builds the app and deploys as a WAR file.
Gen your Webhelp to a local drive, ZIP it up and give it to the build team.
A further detail:
The developer explodes the zip file into the package that becomes the war file. So in my case, when I update help files, the application developer prefers to get the whole new package zipped up (with a time/date line embedded in the launch topic).
And launching, too.