-Added a -y to the removal of the EDEX rpms so it auto removes them instead of waiting for the user
-Added a check to install git if it's not currently installed
Minor change to .gitignore to ignore a directory that gets built when building EDEX from eclipse
-Created a script (updateNDM.pl) that runs via cron daily to check the Unidata public repo for new NDM files and copies them into the NDM trigger directory to install
-Added a few files to be built into the RPM via component.spec
-Added an entry in the cron for awips to run the NDM script
-Added/moved from some spi files from configured or site to base
-Removed some spi files from cave/etc/basemaps to utility tree so we could update on the EDEX side
-Had to add back in the com.raytheon.uf.edex.plugin.loctables plugin so it knew what to do with some of the files in /awips2/edex/data/ndm
-Added files from the awips-ndm svn repo to be built by the awips2-edex rpm and get installed to /awips2/edex/data/ndm so that EDEX picks up the files and updates the databases and spi files.
- changed some of the titles in the AWIPS Tips blog list, to match the titles of the blog posts
- added a new entry for the NSHARP blog released yesterday
- set dialog to a reasonable height (previously way too tall for some screens, with no way to resize)
- allow proper resizing behavior
- change bulletlist behavior so it doesn't scroll to the top every time a user makes a selection
- remove the .setText() call on the instructionsLabel because it's never instantiated (throwing null pointer), and never actually used
- made the table portion of the dialog shorter, to accomodate smaller screen sizes and resolutions
- reduced the vertical margin at the bottom of the dialog to also help with this issue
- Changed "Delete Bundle" to "Delete Display"
- Changed "Alter Bundle on Loading" to "Alter Procedure Item on Loading"
- Changed History List dialog from "Alter Bundle" to "Alter Procedure Item" (not sure if this one is actually used in CAVE currently)
- Changed "Enter Bundle Name" to "Enter Procedure Item Name"
- added a section in the Install Cave page in the MacOS subsection mentioning a warning may pop up when running CAVE if running Monterey, but it can be ignored
- added similar section to the Common Problems page
- added a screenshot of the warning provided by user -- **this screenshot should be updated with a real screenshot (not photo from phone) when we have updated our machines to Monterey**
buildEnvironment.sh - changed the release from 1 to 2
build/setup.sh - added code to call awips_spalshscreen_updater jar and update splash.bmp to current build and release
- remove copy of rpms from robin to fserv
feature.xml (edex dataplugins feature) - remove reference to sports glmdecoder which is depricated
wrapper.conf - this is the file that has been dumping heap logs to /data/fxa so I changed the path to /awips2/data/fxa so it didn't fill up the main / mount
ldmd.conf - added GLMF entry (this is for the ISatSS gridded GLM data - for local use only, but won't hurt to have in)
- commented out GLM data from Eric Bruning
pqact.conf - Commented out Eric Bruning GLM entry since it's depricated
- Added new entry for ISatSS gridded GLM data
pqact.goesr - updated to match the pqact.conf
- updated comments to relfect which products were available
parameters.xml - changed all references of 1/s to /s
WWAResourceData
- Simplified the constructResource to always create and return a WarningsResource
- the actual implementation of the constructResource method doesn't quite align with how it originally seemed to be designed. None of the data is actually in the PluginDataObject at this point, all the data is in the LoadProperties. Because of that, differentiating between WatchResources and WarningResources doesn't work the way you would think it does. You end up going through this method once, for the entire load of the WWAs. Also, for some reason the way the WatchResource populated and eventually passed on its records for drawing, actually eliminated the watches. So, by using the WarningsResource class all the time, all the watches, warnings, and advisories are persisted.
WarningsResource
- the proper convention is for watches to show up as a shaded (thatched) area, and the warnings and advisories to show up with an outline
- in the initShape method, look to see what the significance of the record is, and if it's a watch, then create and set the shadedShape (logic taken from the WatchesResource), otherwise create and set the wireframeShape
