Description of problem: Description Resource Path Location Type JAR file "sportsclub-domain.jar" cannot be resolved persistence.xml /sportsclub-jpa-dao/src/main/resources/META-INF line 5 JPA Problem Version-Release number of selected component (if applicable): Spring 2.5, Spring 3.0, Spring 3.1 How reproducible: Always Steps to Reproduce: 1. Import Spring example into JBDS 5.Beta1e Actual results: Error marker occurs. Expected results: There are no errors in the imported example Additional info:
Looks like an Eclipse issue
Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: The JAR file sportsclub-domain.jar cannot be resolved to persistence.xml/sportsclub-jpa-dao/src/main/resources/META-INF.
Technical note updated. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. Diffed Contents: @@ -1 +1 @@ -The JAR file sportsclub-domain.jar cannot be resolved to persistence.xml/sportsclub-jpa-dao/src/main/resources/META-INF.+The JAR file sportsclub-domain.jar cannot be resolved to persistence.xml in sportsclub-jpa-dao/src/main/resources/META-INF. This does not influence the application itself.
Added matching JBIDE defect.
Max Rydahl Andersen <max.andersen> made a comment on jira JBIDE-11534 Could we please get an example of a project that has this issue?
please give it on JBIDE-11534 and somewhere Exadel can work on it too. (download.devel.redhat.com requires vpn) Is there no matching community example we can use ?
I've just tried to import the sportsclub example from https://github.com/snowdrop/snowdrop-examples. The error occurs here too.
Karel Piwko <kpiwko> made a comment on jira JBIDE-11534 Max et all, Sportsclub from https://github.com/snowdrop/snowdrop-examples has the same issue, as mentioned in bz.
Dmitry Geraskov <dgeraskov> made a comment on jira JBIDE-11534 In the patch we check if there is a project in classpath with the same name as jar and don't show problem marker in this case
changing status as upstream issue is not resolved yet
Marking as RN not required. This is a minor issue.
Migrated to JIRA. https://issues.jboss.org/browse/WFK2-79