| [Edapt] Adding a new EPackage cause NPE during Migration [message #1852386] |
Fri, 13 May 2022 12:00 |
 Sonja Riethig
Messages: 4
Registered: May 2019 |
Junior Member |
|
|
Hi everyone,
we have a EMF/GMF/Edapt project with a long history.
There are already three separate ecore packages all tracked by one edapt history file.
Now we wanted to add a new ecore package but when edapt runs into the migration step "EPackage {foo} has been created" the migration fails with a NullPointerException:
Caused by: java.lang.NullPointerException: null
at org.eclipse.emf.edapt.history.reconstruction.EcoreReconstructorSwitchBase.add(EcoreReconstructorSwitchBase.java:49)
at org.eclipse.emf.edapt.history.reconstruction.EcoreReconstructorSwitchBase.create(EcoreReconstructorSwitchBase.java:95)
at org.eclipse.emf.edapt.internal.migration.execution.internal.MigrationReconstructor$MigrationReconstructorSwitch.caseCreate(MigrationReconstructor.java:388)
When debugging you can see that the MigrationConstructor wants to create the package but the EContainer and the reference are null. Basically the new EPackage is dangling in the air and can't be created.
Is adding a new package possible? And if so, what do we have to do to resolve the NPE?
Thanks in advance :-)
|
|
|
Powered by
FUDForum. Page generated in 0.01912 seconds
] 
Search
Help
Register
Login
Home
