Hi, When migrating a (test) project from 4.8.10.1 to 5.20 I encounter the following error when the migration wizard tries to migrate the java libraries: System.NullReferenceException: Object reference not set to an instance of an object. at Mendix.Modeler.WebUI.Deployment.WebUIDeploymentWorker.GenerateFiles(IProject project, IProgressInfo info, Boolean updateRunningProject) in c:\jenkins\workspace\AppStudio-WebUI-Modeler\modeler\Mendix.Modeler.WebUI\Deployment\WebUIDeploymentWorker.cs:line 118 at Mendix.Modeler.WebUI.Deployment.WebUIDeploymentWorker.DoWork(DeploymentPhase phase, IProject project, DeploymentSettings settings, IProgressInfo info) in c:\jenkins\workspace\AppStudio-WebUI-Modeler\modeler\Mendix.Modeler.WebUI\Deployment\WebUIDeploymentWorker.cs:line 36 at Mendix.Modeler.Deployment.DeploymentProcessBuilder.<>c__DisplayClass7.<AddBuildStepsForPhase>b__6(IProgressInfo info) in c:\jenkins\workspace\AppStudio-Modeler\src\Mendix.Modeler.Core\Deployment\DeploymentProcessBuilder.cs:line 117 at Mendix.Modeler.Deployment.FileIOExceptionHandlingProcess.CatchDiskException(Action action) in c:\jenkins\workspace\AppStudio-Modeler\src\Mendix.Modeler.Core\Deployment\FileIOExceptionHandlingProcess.cs:line 28 at Mendix.Modeler.Deployment.FileIOExceptionHandlingProcess.<>c__DisplayClass2.<AddStep>b__0(IProgressInfo info) in c:\jenkins\workspace\AppStudio-Modeler\src\Mendix.Modeler.Core\Deployment\FileIOExceptionHandlingProcess.cs:line 19 at Mendix.Modeler.Utility.Progress.ProcessRunner.RunStep(Step step) in c:\jenkins\workspace\AppStudio-Modeler\src\Mendix.Modeler.UIFramework\Progress\ProcessRunner.cs:line 85 at Mendix.Modeler.Utility.Progress.ProcessRunner.worker_DoWork(Object sender, DoWorkEventArgs e) in c:\jenkins\workspace\AppStudio-Modeler\src\Mendix.Modeler.UIFramework\Progress\ProcessRunner.cs:line 67 at System.ComponentModel.BackgroundWorker.OnDoWork(DoWorkEventArgs e) at System.ComponentModel.BackgroundWorker.WorkerThreadStart(Object argument) Note that my test project only contains the (non modified) appstore modules: community commons, Excel importer and MxModelReflection and no 'custom' java. Any recommendations on how to prevent this issue?
asked
Brian Golsteijn
1 answers
3
If you are sure this happens while updating Java files, the following should work:
Rename javasource folder.
create empty javasource folder.
Have the modeller regenerate the Java files.
Do the conversion.
Put the old javasource folder back
Manually fix any compilation errors (by deleting the complete contents, you're upgrading the app store modules anyway I would guess).