<jpa:repositories> element causing xml error markers in STS 3.1.0.RELEASE

[matthewadams]

Hi all,

I'm getting an xml problem marker that others have seen with SD JPA, and they just started appearing. I saw this first with SD JPA 1.2.0.RELEASE a couple of days ago and now I'm still seeing it with SD JPA 1.3.0.RELEASE.

Referenced file contains errors (http://www.springframework.org/schema/tool/spring-tool.xsd).  For more information, right click on the message in the Problems View and select "Show Details..."

Right-clicking on the message yields the following error message (repeated 6 times with different schema names):

sch-props-correct.2: A schema cannot contain two global components with the same name; this schema contains two occurrences of 'http://www.springframework.org/schema/tool,annotation'.

Like others have noticed, if I comment the <jpa:repositories> element, the error goes away (see attached screenshots).

Can the SD team figure out what is going on here? While it's not a showstopper for me (I ignore plenty of eclipse error markers), other developers at our client who are new to Java & STS/eclipse are going to freak out a bit, and I'd like to avoid that.

Thanks,
Matthew

[siwatson]

I have the same problem and would also like to find a solution. Thanks.

[pepbr]

Same thing here, no matter what I try, even fooling around with libraries versions I cannot get rid of this red X. And curiously it started happening this week, before that everything was ok.

[matthewadams]

...curiously it started happening this week, before that everything was ok.

I noticed that, too. It started happening out of nowhere. Harumph.

[dalrympm]

Phew... glad I'm not going crazy. This just started happening to me as well and without having made any code changes. I've gone back to multiple tagged releases that never expressed this and still get the same problem. I'm not using STS just a fairly generic J2EE Eclipse Helios installation. I'll keep digging into it but I'm currently suspecting:

1. An externally referenced schema changed... but I thought the schemas were all pulled from the JARs.
2. A corrupt Maven artifact with a bogus schema is floating around out there. I can't say for sure but I feel like this started appearing when I did a force update of dependencies.

Hoping to find a solution since these red X's do not sit well with my OCD ;-)

[pepbr]

2. A corrupt Maven artifact with a bogus schema is floating around out there. I can't say for sure but I feel like this started appearing when I did a force update of dependencies.

Yeah, I remember doing this too!