Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Release/0007 #163

Merged
merged 1 commit into from
Dec 8, 2023
Merged

Release/0007 #163

merged 1 commit into from
Dec 8, 2023

Conversation

Gcolon021
Copy link
Contributor

Release/0007

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 ''.
@Gcolon021 Gcolon021 self-assigned this Dec 4, 2023
@Gcolon021 Gcolon021 merged commit 0f908f3 into master Dec 8, 2023
7 checks passed
@Gcolon021 Gcolon021 deleted the release/0007 branch December 8, 2023 21:13
Gcolon021 added a commit that referenced this pull request Dec 8, 2023
* [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 <lucas.skina@gmail.com>
Gcolon021 added a commit that referenced this pull request Dec 21, 2023
* [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 <lucas.skina@gmail.com>

* [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 <lucas.skina@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant