Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [tm-dev] Gerrit problem

I've tried setting compliance level to 1.6, and the Preference Page (in Mars M5) tells me that a real 1.6 JRE must be installed and activated for this to work properly.
I do have one registered, and I don't see any errors even if compliance is 1.6 .

So maybe only the 1.6 compliance || 1.8 JRE Only combination causes issues. And the Pref page even warns about these issues.

FWIW, the original terminal widget (including TerminalTextDataStore) at one time even worked with JavaME (CDC/Foundation-1.1) and could run inside eRCP.
But at some point we stopped supporting this since it just caused effort at no visible gain.
So having the BREE at 1.6 now should also be the compliance level IMO.

Thanks,
Martin
--
Martin Oberhuber, SMTS / Product Owner – Development Tools, Wind River
direct +43.662.457915.85  fax +43.662.457915.6


-----Original Message-----
From: tm-dev-bounces@xxxxxxxxxxx [mailto:tm-dev-bounces@xxxxxxxxxxx] On Behalf Of Greg Watson
Sent: Wednesday, February 18, 2015 8:03 PM
To: TM project developer discussions
Subject: Re: [tm-dev] Gerrit problem

The error was on line 298 (plus some others).

I have a 1.8 JRE registered and execution environments for 1.6, 1.7, and 1.8. 

I set the compliance level for Eclipse to 1.7 (it was 1.6) and the errors went away. I’m not sure why this affected the project settings, but it seems to be ok now.

Thanks,
Greg



> On Feb 18, 2015, at 12:23 PM, Stieber, Uwe <Uwe.Stieber@xxxxxxxxxxxxx> wrote:
> 
> Hi Greg,
> 
> The compiler compliance is set to be taken from the JavaSE-1.6 execution environment, for all o.e.tm.terminal plug-ins. I do not get any build errors in my workspace and also the master build job is running through, which getting the compiler level settings from the projects execution environment setting too.
> 
> Which line you get the error? Could be also that you don't have a 1.6 JRE registered in the Eclipse preferences? It's hard to tell without seeing your actual environment.
> 
> Best regards, Uwe :)
> 
> 
> 
>> -----Original Message-----
>> From: tm-dev-bounces@xxxxxxxxxxx [mailto:tm-dev-bounces@xxxxxxxxxxx] 
>> On Behalf Of Greg Watson
>> Sent: Mittwoch, 18. Februar 2015 17:43
>> To: TM project developer discussions
>> Subject: Re: [tm-dev] Gerrit problem
>> 
>> Another question. In my workspace I’m seeing errors in 
>> TerminalTextDataStore.java because Object can’t be cast to char[]. I 
>> have the compliance level set to Java 1.6, so I think this is 
>> correct. I think TM gets compiled with Java 1.7, so the build 
>> succeeds. What Java version does TM require and should we be compiling with this level?
>> 
>> Greg
>> 
>>> On Feb 18, 2015, at 8:55 AM, Stieber, Uwe 
>>> <Uwe.Stieber@xxxxxxxxxxxxx>
>> wrote:
>>> 
>>> Hi Greg,
>>> 
>>> It had been just bad luck. Your change got submitted between the 
>>> update of
>> the pom.xml/build.properties files and the update of the execution 
>> environment in the manifest files. I have rebased your change and the 
>> gerrit build job turned green again.
>>> 
>>> Sorry for the inconvenience.
>>> 
>>> Best regards, Uwe :)
>>> 
>>> 
>>> 
>>>> -----Original Message-----
>>>> From: tm-dev-bounces@xxxxxxxxxxx 
>>>> [mailto:tm-dev-bounces@xxxxxxxxxxx]
>>>> On Behalf Of Stieber, Uwe
>>>> Sent: Mittwoch, 18. Februar 2015 09:04
>>>> To: TM project developer discussions
>>>> Subject: Re: [tm-dev] Gerrit problem
>>>> 
>>>> Hi Greg,
>>>> 
>>>> I'll look at it. Stay tuned.
>>>> 
>>>> Best regards, Uwe :)
>>>> 
>>>> 
>>>> 
>>>>> -----Original Message-----
>>>>> From: tm-dev-bounces@xxxxxxxxxxx 
>>>>> [mailto:tm-dev-bounces@xxxxxxxxxxx]
>>>>> On Behalf Of Greg Watson
>>>>> Sent: Mittwoch, 18. Februar 2015 02:48
>>>>> To: TM project developer discussions
>>>>> Subject: [tm-dev] Gerrit problem
>>>>> 
>>>>> Uwe,
>>>>> 
>>>>> My Gerrit patch is failing to build for some strange reason, 
>>>>> however the hudson build of TM master works. It looks like the 
>>>>> Java compiler or compliance level has changed, and somehow the 
>>>>> Gerrit build is doing something differently from the main build. I 
>>>>> noticed you made some commits to the master branch without going 
>>>>> through Gerrit. Do you think these might have introduced a change 
>>>>> that may be causing the
>>>> problem?
>>>>> 
>>>>> Greg
>>>>> _______________________________________________
>>>>> tm-dev mailing list
>>>>> tm-dev@xxxxxxxxxxx
>>>>> To change your delivery options, retrieve your password, or 
>>>>> unsubscribe from this list, visit 
>>>>> https://dev.eclipse.org/mailman/listinfo/tm-dev
>>>> _______________________________________________
>>>> tm-dev mailing list
>>>> tm-dev@xxxxxxxxxxx
>>>> To change your delivery options, retrieve your password, or 
>>>> unsubscribe from this list, visit 
>>>> https://dev.eclipse.org/mailman/listinfo/tm-dev
>>> _______________________________________________
>>> tm-dev mailing list
>>> tm-dev@xxxxxxxxxxx
>>> To change your delivery options, retrieve your password, or 
>>> unsubscribe from this list, visit 
>>> https://dev.eclipse.org/mailman/listinfo/tm-dev
>> 
>> _______________________________________________
>> tm-dev mailing list
>> tm-dev@xxxxxxxxxxx
>> To change your delivery options, retrieve your password, or 
>> unsubscribe from this list, visit 
>> https://dev.eclipse.org/mailman/listinfo/tm-dev
> _______________________________________________
> tm-dev mailing list
> tm-dev@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or 
> unsubscribe from this list, visit 
> https://dev.eclipse.org/mailman/listinfo/tm-dev

_______________________________________________
tm-dev mailing list
tm-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/tm-dev

Back to the top