This happens in the MyEclipse 2017 line — the last version of MyEclipse 2016 does not exhibit this isue.
I get a popup with this detail:
Failed while installing JPA 2.0.
Property not located:ISpringPersistenceFacetInstallDataModelProperties.ADD_SPRING_JPA_SUPPORT
I spent a bit of time drilling down to what is causing it — it doesn’t seem to like using Spring AND JPA
with persistence.xml together. I’ve attached a very simple project folder (with just a pom.xml and persistence.xml). You can import it cleanly as a maven project in 2016 and 2015, but 2017 gets the above error.
Sorry that you are seeing this issue with MyEclipse 2017. Thank you for the project files. I could replicate the issue at my end. I have filed a bug for the dev team to investigate further. We will keep you posted about the fix.
Hi. Is there an update on this issue? Either a workaround or a bug where we can track the status in detail? We are in the process of upgrading from MyEclipse 2015 to 2017 and are running into this problem.
We don’t have a public bug tracker, but I’m prioritizing this issue for the MyEclipse 2017 CI 9 release. Due to other commitments, we were unable to get it into CI 8 release that’s due in the next couple of days.
I do understand it can be a problem to have this popup when you’re trying to migrate to 2017, we’ll also look at whether any workarounds are possible with the current release.