Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
* [ALS-5422] Add persistence.xml to visualization resource (#161) (#162) The visualization resource is failing to start due to an error injecting persistence unit into CDI managed bean. It is unable to find a persistence unit named ''. * Sync new Release/0008 with Master (#168) * [ALS-5422] Add persistence.xml to visualization resource (#161) The visualization resource is failing to start due to an error injecting persistence unit into CDI managed bean. It is unable to find a persistence unit named ''. * [ALS-0000] Fix aggregate resource - Very confused as to how this was working before * [ALS-5422] Add persistence.xml to visualization resource (#161) (#162) (#163) The visualization resource is failing to start due to an error injecting persistence unit into CDI managed bean. It is unable to find a persistence unit named ''. --------- Co-authored-by: Luke Sikina <[email protected]> * [ALS-5061] Remove HSAPIResource (#166) [ALS-5061] Remove HSAPIResource (#166) * [ALS-3978] Update version handling in multiple pom.xml files (#167) * [ALS-3978] Update version handling in multiple pom.xml files This commit removes hardcoded versions of dependencies from individual pom.xml files and introduces them into the root pom.xml's properties section. This centralizes the control of dependency versions to prevent inconsistencies and makes future updates more straightforward. This change covers several libraries including Guava, JUnit Jupiter, Mockito, and others. * Update library versions and clean up pom.xml Upgraded dependencies including Jackson, Guava, JUnit, Hibernate, HttpClient, and Commons-IO. Also, improved the management of versions via property variables and cleaned up inconsistent formatting. Removed an unnecessary comment related to Mockito version compatibility. * Remove specific version references in pom.xml files The changes encompass the removal of explicit version references in the project's pom.xml files. By relying on property variables, this maintenance update enhances dependency management flexibility. Specific version comments also have been removed to eliminate clutter and improve overall file readability. * Update pom.xml to use property variables for versions The changes primarily involve updating the pom.xml file to use property variables instead of hardcoding the version numbers. This is a better approach as it improves the flexibility in managing dependencies. This change also results in cleaner and more readable code by removing unnecessary explicit version references. * Downgrade Spring version in pom.xml The Spring version has been downgraded in the pom.xml file from 6.1.1 to 5.3.31. This is due to java version requirement of 17+ for 6.x --------- Co-authored-by: Luke Sikina <[email protected]>
- Loading branch information