...
- Documents
- Requirements
- UML
Implementation
Java
- Coding standards
- Java Other languages
- CVS
- Exception handling
- I18N & L10N aka G11N
- Java
- Other Preferences
- Defaults
- Changeable by users
- Third-party libraries
- UI
- Eclipse
- Other
Other languages
Testing
- Target
- Unit tests
Documentation
- Comments
- JavaDoc
- Other
- Help
Release
- Plugin
- Feature
- Product
...
Implementation
Java Coding Standards
...
- Package names start with edu.stanford.slac.
...
Java Exception Handling
- You should never throw/catch a generic exception (an instance of Exception, Throwable, or Error).
- Exceptions resulting from AIDA/EPICS data errors should be logged via Err.
...
Java G11N Practices
- All meaningful strings should be externalized.
...
How To Release A New Plugin
- Increment the version of your pluginReset target to DEFAULT.
- Check out all features SEAL/CSS plugin projects from CVS into your Workspace.
- Delete features from the target directory. (but NOT the plugins!) Note: This is a very wrong step that seems to originate from an Eclipse bug in how features are built against a target.
- Increment the version of each updated feature.
- Remove plugins/features from the update site.
- Export RELEASE feature to SEAL update site (Export... => Plug-in Development => Deployable features)
- Check out the "update.seal" project from CVS.
- Update the names and versions of the features in site.xml.
- Export site.xml to SEAL update site. (Export => General => File System)
- Start SEAL in "admin"- mode.
- Update SEAL.
- Build product using "seal.applications" (note: the order of the features matters!)
- Test your product.
- Copy the product to /afs/slac/g/lcls/physics/seal.new/product and update the "current" link.
- Build JavaDoc. (optional)
- Commit all changes to CVS.Remove all old plugins from the installation site
- Reload your Plug-in Development target.
- Remove all unnecessary projects from your workspace.
- Reload your Plug-in Development target.
...