egeria: [BUG] Egeria Intellij build failure
Existing/related issue?
No response
Current Behavior
I pulled the up to date egeria repo from main and after the maven build I tried to run the build from the intellij interface and I got an error:
~/egeria/open-metadata-test/open-metadata-fvt/open-types-fvt/open-types-test/src/test/java/org/odpi/openmetadata/fvt/opentypes/server/TestBeansToAccessOMRS.java:126766:36 java: variable primitivePropertyValueForMap is already defined in method testCreateAgreementItem()
The class that fails is generated code and declares multiple times the same variable.
The issue is not only on my setup, I checked with a colleague and we got the error.
Expected Behavior
The build finishes successfully.
Steps To Reproduce
No response
Environment
- Egeria: 3.15-SNAPSHOT
- OS: MacOS Monterey v12.6.2
- Java: 11
- Browser (for UI issues): -
- Additional connectors and integration: -
- Intellij Version my machine: IntelliJ IDEA 2022.3.1 (Ultimate Edition)
- Intellij Version colleague machine: IntelliJ IDEA 2021.1.3 (Ultimate Edition)
Any Further Information?
No response
About this issue
- Original URL
- State: closed
- Created a year ago
- Comments: 15 (15 by maintainers)
Commits related to this issue
- #7324 skip javadoc (long!) for auto generated tests Signed-off-by: Nigel Jones <nigel.l.jones+git@gmail.com> — committed to planetf1/egeria by planetf1 a year ago
- #7324 skip javadoc (long!) for auto generated tests Signed-off-by: Nigel Jones <nigel.l.jones+git@gmail.com> — committed to planetf1/egeria by planetf1 a year ago
- #7324 fix typo in pr build Signed-off-by: Nigel Jones <nigel.l.jones+git@gmail.com> — committed to planetf1/egeria by planetf1 a year ago
- #7324 remove open types fvt from codeQL build Signed-off-by: Nigel Jones <nigel.l.jones+git@gmail.com> — committed to planetf1/egeria by planetf1 a year ago
- Merge pull request #7327 from planetf1/issue7324 #7324 Ensure Open Types tests are run (gradle) — committed to odpi/egeria by planetf1 a year ago
I’m looking at why the tests don’t run in our build. I can’t see anything changed in maven for years . However with our upcoming move to gradle I’ll focus my fix there. Just experimenting at the moment - WITHOUT your fix, as first I went to see a compile failure! Then I will try together with your fix.