"partyk1d24" wrote:
I was posting because I thought it might be useful to keep track of issues and I couldn't find the issue repo.
...
Again just thought it would help to bring this up I apologize if there was an issue list I missed.
Unfortunately, there currently is no publicly exposed bug tracking system.
So, this is the right place to bring up issues.
I've noted in older developer forum threads that the BrightScript plugin is only supported under the environments listed in Eclipse's production release target environment matrices, but perhaps we should add that information to the Eclipse plugin guide in the SDK docs for clarity.
"partyk1d24" wrote:
There is an early access download with preliminary Java8 support...did you download that and install that?
No but I am really not sure it is needed unless you are using the actual Java8 jre for your project.
Probably right, but hard to say for sure without combing through the embodied code changes and additions (which I have not done). It's entirely possible that the early access download includes changes/additions to the core Eclipse platform, not just the java language support elements in the JDT.
In any case, I was just asking about your environment to quickly see if that download could be eliminated as a potential workaround.
"partyk1d24" wrote:
I am serious about trying to make the community better and just want to make sure I am posting in the right area.
That's appreciated, and yes, this is the right place to post for discussing eclipse plugin issues.
"partyk1d24" wrote:
...one day Eclipse will fully support Java8 and the problem will probably still be there.
Not necessarily.
We've seen numerous apparent plugin issues in the past that were ultimately caused by bugs in Eclipse, the dependent plugins (DLTK, EMF), and specific minor releases of the JRE.
Between here and official support by Eclipse of JRE8, it's likely JRE8 specific bugs in Eclipse and/or DLTK will get fixed, which in turn may eliminate upstream manifestations in 3rd party plugins, such as BrightScript. For the BrightScript plugin, it's happen before.
Note, I'm not stating definitively that what you are experiencing is a JRE8 related bug. But the first step in tracking down the source of the problem is eliminating the unsupported environment.
The fact that you haven't seen problems in other eclipse plugins running under jre8 so far is great, but that's a black swan argument - it doesn't prove the JRE version you are using isn't the source of the problem.
"partyk1d24" wrote:
Also the plugin still functions, so it is probably a menial change,
Again, that would assume this is a bug in the plugin, which hasn't been established.
If you run your eclipse instance in a supported environment - for Eclipse 4.3 (aka Kepler), see:
http://www.eclipse.org/projects/project-plan.php?projectid=eclipse#target_environments ( but upgraded to 1.7 for any O/S that lists JRE 1.6 ), and you still have the same issue, I'd be happy to continue working with you to track down the source of the problem.
"partyk1d24" wrote:
I would be happy to look into it if the plugin code is out there somewhere.
Thanks for the offer, but the plugin isn't an open-source project at present. It's maintained as Roku-owned code in a company-internal repo.
Cheers