Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jdt-core-dev] Patch Build: 4.6.0 P-Build: P20160303-1000 - BUILD FAILED

You are correct.  My memory was faulty and the code was using M5 as the "base".

Bug 488967- [BETA_JAVA9] Patch builds using M5, instead of latest I-build

I will change to use the latest I-build.

Unless I am mistaken, this does have implications for what we tell people they need to have installed in order to use/apply the patch.

I will also plan to change the "metadata" so that users must have at least I20160301-1230 installed before applying/using the patch produced this week.  

Please comment in the bug about implications for "Market Place Client" contributions. (I think they should normally be "for milestones", with this one week as the possible exception, due to EclipseCon. But suggest we "change" back to milestones after M6 and contribute that too to Market Place Client. And hope nothing else breaks between now and M6. :) If I am wrong, or others have better ideas, please explain in Bug 488967.

It will take me a while to correct the metadata, so I expect the rebuild will start around 2:00 PM Eastern.

Thanks,







From:        "Noopur Gupta" <noopur_gupta@xxxxxxxxxx>
To:        "Eclipse JDT Core developers list." <jdt-core-dev@xxxxxxxxxxx>,
Date:        03/03/2016 11:00 AM
Subject:        Re: [jdt-core-dev] Patch Build: 4.6.0 P-Build: P20160303-1000        -        BUILD        FAILED
Sent by:        jdt-core-dev-bounces@xxxxxxxxxxx




These are the same old compile errors as seen in the previous build failure. No new changes have gone in after that.
Looks like the patch build is not based on the latest I-build (I20160301-1230).

Regards,
Noopur

Inactive hide details for "David M Williams" ---03/03/2016 09:17:50 PM---It seems a little odd there would be compile errors in"David M Williams" ---03/03/2016 09:17:50 PM---It seems a little odd there would be compile errors in the patch build, but not in the "Y-build".

From:
"David M Williams" <david_williams@xxxxxxxxxx>
To:
"Eclipse JDT Core developers list." <jdt-core-dev@xxxxxxxxxxx>
Date:
03/03/2016 09:17 PM
Subject:
Re: [jdt-core-dev] Patch Build: 4.6.0 P-Build: P20160303-1000 - BUILD FAILED
Sent by:
jdt-core-dev-bounces@xxxxxxxxxxx




It seems a little odd there would be compile errors in the patch build, but not in the "Y-build".
See

http://download.eclipse.org/eclipse/downloads/drops4/P20160303-1000/compilelogs/plugins/org.eclipse.jdt.ui_3.12.0.qualifier/@dot.html

The patch build is based on recompiling only the "known BETA_JAVA9 bundles, with the latest I-build as the "base".
The latest I build was Tuesday at 12:30;

http://download.eclipse.org/eclipse/downloads/drops4/I20160301-1230/

Have there been "real" changes since then, or could something be wrong with our patch build?







From:
e4Builder@xxxxxxxxxxx
To:
David M Williams/Raleigh/IBM@IBMUS, jdt-core-dev@xxxxxxxxxxx,
Date:
03/03/2016 10:20 AM
Subject:
[jdt-core-dev] Patch Build: 4.6.0 P-Build: P20160303-1000 - BUILD FAILED
Sent by:
jdt-core-dev-bounces@xxxxxxxxxxx




Eclipse downloads:

http://download.eclipse.org/eclipse/downloads/drops4/P20160303-1000/

Build logs and/or test results (eventually):
http://download.eclipse.org/eclipse/downloads/drops4/P20160303-1000/testResults.php_______________________________________________
jdt-core-dev mailing list
jdt-core-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit

https://dev.eclipse.org/mailman/listinfo/jdt-core-dev

_______________________________________________
jdt-core-dev mailing list
jdt-core-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit

https://dev.eclipse.org/mailman/listinfo/jdt-core-dev

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



Back to the top