| Re: [ide-dev] Some Java dev stories where Eclipse > IDEA |
My understanding from recent discussions was that JDT was planning on supporting multiple classpaths per project. It's what makes the most sense, IMHO.On Wed, Jan 27, 2016 at 8:05 AM, Mickael Istria <mistria@xxxxxxxxxx> wrote:_______________________________________________On 01/27/2016 01:38 PM, Max Rydahl Andersen wrote:
At dev-time, what matters is mostly assistance and error reporting. As I suggest in bug 486032, m2e/BuildShip would have a specific builder that would report errors on Java files that use illegal classes. It wouldn't prevent JDT for compiling, but user would see the error as a red cross, just like some compile error.Sure, it would make sense to me that the BS/m2e class path container would take as argument/path what scope it is so I could add scoped class path containers to Eclipse launch configurations; but if JDT won't honor them when compiling test vs source folders they have extremely limited value afaics.
From a user perspective, it would be the same as having JDT compilation failing. The result would be that the IDE reports the error as expected, but some parts of it would "tolerate" it so some higher-level operations would still be possible even with this error.
--
Mickael Istria
Eclipse developer at JBoss, by Red Hat
My blog - My Tweets
ide-dev mailing list
ide-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/ide-dev