diff options
| author |   jhh <jorge.hernandez-herrero@att.com> | 2020-04-09 13:31:38 -0500 |
|---|---|---|
| committer | jhh <jorge.hernandez-herrero@att.com> | 2020-04-09 13:35:04 -0500 |
| commit | f9f55b74950a2fb39f76209c5392676d3e4d0e77 (patch) | |
| tree | fd4d12eaa7c4ce8465e4c52ba30f55392c9afe2f /integrity-monitor/src/main/resources/META-INF | |
| parent | a2ca5ed5782f32ca54d14ffde2cbcfa0e4c3fea3 (diff) | |
rename jpa persistence file
After inspecting the fat jar generated by brmsgw, noticed that
the persistence.xml included from here it was overriden by another
one, therefore the persistence unit was not available. This
may solve the issue for the brmsgw, as with a far jar build, there
are the risks of collisions such as this of files with the same
name.
Issue-ID: POLICY-2471
Signed-off-by: jhh <jorge.hernandez-herrero@att.com>
Change-Id: I91cf2b6d3d2f5086d77795e08800ca96d984c214
Diffstat (limited to 'integrity-monitor/src/main/resources/META-INF')
| -rw-r--r-- | integrity-monitor/src/main/resources/META-INF/persistenceIM.xml (renamed from integrity-monitor/src/main/resources/META-INF/persistence.xml) | 0 |
1 files changed, 0 insertions, 0 deletions
diff --git a/integrity-monitor/src/main/resources/META-INF/persistence.xml b/integrity-monitor/src/main/resources/META-INF/persistenceIM.xml index 7aff9219..7aff9219 100644 --- a/integrity-monitor/src/main/resources/META-INF/persistence.xml +++ b/integrity-monitor/src/main/resources/META-INF/persistenceIM.xml |