Maven projects with persistence.xml and Spring do not import cleanly.

This topic contains 3 replies, has 4 voices, and was last updated by Profile photo of Brian Fernandes Brian Fernandes 1 month ago.

Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • #521570 Reply
    Profile photo of tvail
    tvail
    Participant

    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.

    Thanks,

    -Tim Vail

    Attachments:
    You must be logged in to view attached files.
    #521674 Reply
    Profile photo of support-swapna
    support-swapna
    Moderator

    Tim,

    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.

    Apologies for inconvenience caused.

    –Swapna
    MyEclipse Support

    #536501 Reply
    Profile photo of djpittner
    djpittner
    Participant

    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.

    Thank you,
    Douglas

    #536636 Reply
    Profile photo of Brian Fernandes
    Brian Fernandes
    Moderator

    Douglas,

    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.

Viewing 4 posts - 1 through 4 (of 4 total)
Reply To: Maven projects with persistence.xml and Spring do not import cleanly.