Skip to main content

Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Modeling » EMF "Technology" (Ecore Tools, EMFatic, etc)  » [Edapt] Adding a new EPackage cause NPE during Migration
[Edapt] Adding a new EPackage cause NPE during Migration [message #1852386] Fri, 13 May 2022 12:00
Sonja Riethig is currently offline Sonja RiethigFriend
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(
	at org.eclipse.emf.edapt.history.reconstruction.EcoreReconstructorSwitchBase.create(
	at org.eclipse.emf.edapt.internal.migration.execution.internal.MigrationReconstructor$MigrationReconstructorSwitch.caseCreate(

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 :-)
Previous Topic:(To be deleted)
Next Topic:Is there a way to automatically display the classes children of other classes?
Goto Forum:

Current Time: Wed Sep 27 16:40:57 GMT 2023

Powered by FUDForum. Page generated in 0.02307 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top