This sections discusses issues with modifying Platypus apps after they have been fielded.
A fielded app has several components contributing to the jar file.
com.pisoftware.platypus.production
. (These may be in a
separate jar file, but are relevant to this discussion.)
After the app has been fielded, and time passes, and a new version of Platypus is released, and you have new specs (or bugs) in the app: you might face the problem of rolling back your development environment.
If this roll-back is not properly done, you may find compatibility problems between the generated and hand-edited code.
We recommend snapshotting the entire app, including the generated directories, and the version of Platypus used to develop it.
When we are developing an app, we use CVS. We do not store all the directories in CVS. Typcially, we have only a few of the files in the app root directory, and the src/ tree. All the rest can be regenerated.
However, once an app has been developed, we recomment tar-balling all the directories, including the view/ directory, generated directory, output/ directoryand classes/ directory. This effectively allows the state of the Makefile system (which looks in all these directories) to be restored quickly and painlessly.