I haven't figured out what is going on yet but if I do then I can probably
manage to keep it up to date. I'm not actually sure what Arjan is referring
to about the eclipse project files as I wasn't aware that there were any in
the source to start with. However I'm hoping to get a bit more time to look
into this over the weekend.
From: Manfred Riem [mailto:manfred.riem_at_oracle.com]
Sent: 03 July 2013 14:13
To: dev_at_javaserverfaces.java.net
Cc: arjan tijms
Subject: Re: Container dependencies downloading
HI Arjan and/or Anthony,
Can either one of you keep it up to date?
Thanks!
Manfred
On 7/3/2013 4:39 AM, arjan tijms wrote:
Hi guys,
On Mon, Jul 1, 2013 at 4:09 PM, Manfred Riem <manfred.riem_at_oracle.com>
wrote:
I am afraid that I don't know how Eclipse deals with it then. Note that the
ant
build file relies on those properties so if in Eclipse they are not used
then it
could show the problem you are seeing.
A while ago I encountered the exact same issue.
There are a few independent project files committed for Eclipse, but at
least a while ago they were all severely outdated. Eclipse can run the ant
build file(s), but that's an isolated action and doesn't effect the Eclipse
native project files. Meaning, you'll end up with a useable build but there
are a lot of errors shown in the source files so you can't really use any of
the Eclipse editor features like navigate into, open call hierarchy, etc.
I think someone should either update the Eclipse project files and keep them
up to date with changes in the ant build file, or just remove the Eclipse
project files entirely. As it stands the situation is indeed a little
confusing.
Kind regards,
Arjan Tijms