Commit: https://bitbucket.org/nfreese/nowlanfork-igb/commits/d03c4c7871b19fc856846aad38bbb00b0e10c37b

To test:
Fetch my branch and clean and build in Netbeans and then run from Netbeans and IntelliJ, the two IDEs the core team is using.
There should be no errors such as "unable to resolve".
Once IGB is running check that all bundles are active: http://localhost:7080/system/console/bundles

Note: My understanding of the shared-lib-wrapper pom.xml is limited, but it seems like dependencies/artifactItem need to be included to properly run through Netbeans, as I do not see the same errors if something is missing from shared-lib-wrapper when running maven through the terminal. Likewise, if something is missing from the main pom.xml but included in the shared-lib-wrapper then IGB seems to build fine from Netbeans but throws errors when building through the terminal.

For future reference, when testing a change that affects a library/dependency entry in a POM, need to test IGB running in IDEs as well as from command line and from installer.

See this case study on issues with running IGB in development mode: https://canvas.instructure.com/courses/1164217/files/67490997?module_item_id=19105206

I have a verbal confirmation that testing was successful for Kaushik, so I have included the pull request below.

Pull request: https://bitbucket.org/lorainelab/integrated-genome-browser/pull-requests/931

Status:
i) no errors were found while running the application in IDE development mode.
ii) all bundles are in active mode.

Merged and building master branch installers.

Since the error is visible during development mode and the change has solved the development mode issue, skipping further testing. Moving to Done.