[irshaad18]

Hello,

We are upgrading from MyEclipse 10 to MyEclipse 2014. The migration process failed with the following error detail:

Cannot initialize migration process of project MLIRE.
Cannot initialize migration process of project MLIRE.
java.lang.NullPointerException
Cannot initialize migration process of project MLIRE.
java.lang.NullPointerException

Here is what I got from the stack trace:

java.lang.NullPointerException
at com.genuitec.eclipse.reporting.migration.InstallBirtFacet.detectFacetVersion(InstallBirtFacet.java:101)
at com.genuitec.eclipse.migration.core.project.AbstractFacetInstallingProjectMigrationDelegate.initialize(AbstractFacetInstallingProjectMigrationDelegate.java:55)
at com.genuitec.eclipse.reporting.migration.InstallBirtFacet.initialize(InstallBirtFacet.java:54)
at com.genuitec.eclipse.migration.core.project.internal.ProjectMigrationOperation.<init>(ProjectMigrationOperation.java:41)
at com.genuitec.eclipse.migration.core.project.internal.MigratingProject.initilizeMigrationProcess(MigratingProject.java:1082)
at com.genuitec.eclipse.migration.core.project.internal.ProjectsMigrationJob.run(ProjectsMigrationJob.java:94)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)

I’ve also attached the .setting folder.

Any help will be much appreciated.

Thanks,
Irshaad

Attachments:

You must be logged in to view attached files.

[support-swapna]

Irshaad,

Sorry that you are seeing this issue. Thank you for the .settings folder.

Is your project a web project? The org.eclipse.wst.common.component file is missing from the .settings folder. The migration error is due to this missing file.

I am attaching a sample org.eclipse.wst.common.component file for your reference. The file is uploaded as a text file but it has to be a copied as a COMPONENT file type into the .settings folder. Please edit the file according to your project,add this file to the .settings folder and try to migrate again.

If you are still seeing issues, please send us all the .* files (.settings,.classpath,.project,.mymetadata etc) of the project excluding the source code for further investigation. Also send us the .log file which is located at workspace dir/.metadata/.log.Before trying the migration again, delete all the contents of the .log file and replicate the issue.

Let us know how it works for you.

–Swapna
MyEclipse Support

• This reply was modified 10 years, 5 months ago by support-swapna.

Attachments:

You must be logged in to view attached files.

[irshaad18]

Hi Swapna,

I’ve added the org.eclipse.wst.common.component file as suggested but the migration is still failing. Please find attached the .* files you requested. Unfortunately my project don’t seems to have the .log file (should i enable logging or something to get that?)

Thanks,
Irshaad

Attachments:

You must be logged in to view attached files.

[support-swapna]

Irshaad,

Sorry that you are still seeing this issue. Thank you for the files.

Can you please try these steps and check if the migration succeeds ?

1. Remove the report nature from the .project file of the project.
Delete this entry : com.genuitec.eclipse.reporting.reportnature
and save the .project file. Refresh the project.

2. Go to MyEclipse > Migrate Workspace and select the project to migrate. The project should now migrate successfully.

Let us know how it works for you.

–Swapna
MyEclipse Support

[support-tony]

Irshaad,

As an alternative to the workaround mentioned by Swapna, if you don’t want to remove the report nature, try replacing the contents of the org.eclipse.wst.common.project.facet.core.xml (in the .settings folder) file with something like following:

<?xml version="1.0" encoding="UTF-8"?>
<faceted-project>
  <fixed facet="jst.jsf"/>
  <installed facet="java" version="1.6"/>
  <installed facet="jst.web" version="2.5"/>
  <installed facet="wst.jsdt.web" version="1.0"/>
  <installed facet="jst.jsf" version="1.2"/>
</faceted-project>

You may need to alter the versions (apart from wst.jsdt.web) if you are using different versions of the various APIs. Then rerun the migration.

Please let us know if either of these workarounds fix the problem.

[Author]

Posts