Re: [cdt-dev] Trouble going to Java 1.8

[Doug Schaefer <dschaefer@xxxxxxx>]

I guess I was more curious why these settings were there and whether removing them breaks anyone.

If no one speaks up, we'll have to assume it's OK to remove them.

Doug.

---

From: cdt-dev-bounces@xxxxxxxxxxx [cdt-dev-bounces@xxxxxxxxxxx] on behalf of Marc Khouzam [marc.khouzam@xxxxxxxxxxxx]
Sent: Tuesday, September 29, 2015 9:08 AM
To: CDT General developers list.
Subject: Re: [cdt-dev] Trouble going to Java 1.8

To avoid similar issues later, I've pushed a patch to gerrit that removes those lines from the other few plugins that had them:
https://git.eclipse.org/r/#/c/56946

There is more to do for plugins that want to go to Java 8, but these seemed to be less obvious so I went ahead with them.

---

From: cdt-dev-bounces@xxxxxxxxxxx [cdt-dev-bounces@xxxxxxxxxxx] on behalf of Doug Schaefer [dschaefer@xxxxxxx]
Sent: September 28, 2015 10:30 AM
To: CDT General developers list.
Subject: Re: [cdt-dev] Trouble going to Java 1.8

Found it. The build.properties had the compiler version in it. I imaging that's a relic of the old PDE build. I've removed it and the build is progressing.

Something to keep an eye on as we move other plug-ins to Java 8.

Doug.

---

From: cdt-dev-bounces@xxxxxxxxxxx [cdt-dev-bounces@xxxxxxxxxxx] on behalf of Doug Schaefer [dschaefer@xxxxxxx]
Sent: Monday, September 28, 2015 9:46 AM
To: CDT General developers list.
Subject: Re: [cdt-dev] Trouble going to Java 1.8

All indications are that it's running against Java 8, both on hudson and on my local machine. It builds fine in the IDE just not under maven. And I think we have Java 8 specified everywhere we need it to but I may be missing one.

Doug.

---

From: cdt-dev-bounces@xxxxxxxxxxx [cdt-dev-bounces@xxxxxxxxxxx] on behalf of Alex Blewitt [alex.blewitt@xxxxxxxxx]
Sent: Monday, September 28, 2015 5:26 AM
To: CDT General developers list.
Subject: Re: [cdt-dev] Trouble going to Java 1.8

I’ve seen that before when Maven is picking up a Java 1.7 runtime, and so doesn’t know about BREE-1.8. 

You can run mvn —version and it’ll print out stats, including which version of Java it’s picked up. If it’s a local IDE change, you should also check that the Window -> Preferences -> Java -> Installed JREs lists a Java 1.8 runtime, along with the Execution Environments underneath.

Alex

On 28 Sep 2015, at 05:18, Doug Schaefer <DSchaefer@xxxxxxx> wrote:

Yes, there's one up on Gerrit under my name. And the failed verify builds this weekend are from it. But maybe I did it wrong. You could also just change cdt.core locally and see if it works.

Sent from my BlackBerry 10 smartphone on the Rogers network.

From: Sergey Prigogin

Sent: Monday, September 28, 2015 12:15 AM

To: CDT General developers list.

Reply To: CDT General developers list.

Subject: Re: [cdt-dev] Trouble going to Java 1.8

Do you have to patch to look at?

-sergey

On Sun, Sep 27, 2015 at 9:12 PM, Doug Schaefer <dschaefer@xxxxxxx> wrote:

Hey gang,

I'm having trouble getting cdt.core to build in maven after changing the execution environment to 1.8. I get the following error message:

Resolution errors:

   Bundle org.eclipse.cdt.core - Missing Constraint: Bundle-RequiredExecutionEnvironment: JavaSE-1.8

Anyone else want to give it a try? It's frustrating since we've been using Java 1.8 in our internal stuff and it builds fine. There's something in the CDT build that's not quite right.

Thanks,

Doug.

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

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