Community
Participate
Working Groups
We need to update the main platform readme for any changes in Kepler.
I have done my major update. Leaving open for documenting specific problems. http://git.eclipse.org/c/platform/eclipse.platform.releng.git/commit/?id=be5702edea46e690195ff844d1994e9fac0f2123
*** Bug 407824 has been marked as a duplicate of this bug. ***
The last two items in the 3.2.6 - SWT section should be removed. They are: - Toolbar controls on GTK are not properly sized - Navigation using tab and arrow keys
SWT: - BIDI Segments in text controls only work on Windows and GTK. => "Text" must be capitalized, since this is about the Text widget's addSegmentListener(..) API and doesn't apply to StyledText. JDT: - Some refactoring script operations fail with Sun 6.0 JREs => Remove the whole item. This works fine in current Oracle JREs.
Are "migration" issues listed here? If so, might want to document removal of org.junit4 stub bundle (bug 383240) and that typically consumes simply have to change their manifest to use "org.junit" instead of "org.junit4"?
(In reply to comment #5) > Are "migration" issues listed here? If so, might want to document removal of > org.junit4 stub bundle (bug 383240) and that typically consumes simply have > to change their manifest to use "org.junit" instead of "org.junit4"? That should really go in the porting guide. There is a very general section on migration in the readme but it is for the kind of information that doesn't change from year to year.
Ok, how about "known issues"? If so ... I'm not sure how to word it ... but we might want to mention that "inner jars" are not signed (bug 401098), and this can cause problems running unit tests that depend on using their own classloader (bug 408901). [There may be work arounds relaxing the JRE's security settings if simply running tests, but there might be other "running code" that would be effected where that would not be desirable. For an example, see bug 401098 comment 1 -- I'm assuming Tom's workaround would translate into using -Dosgi.support.class.certificate=false ... but, not positive].
(In reply to comment #7) > Ok, how about "known issues"? If so ... I'm not sure how to word it ... but > we might want to mention that "inner jars" are not signed (bug 401098), and > this can cause problems running unit tests that depend on using their own > classloader (bug 408901). [There may be work arounds relaxing the JRE's > security settings if simply running tests, but there might be other "running > code" that would be effected where that would not be desirable. For an > example, see bug 401098 comment 1 -- I'm assuming Tom's workaround would > translate into using > -Dosgi.support.class.certificate=false ... but, not positive]. No, I tried with users test case and didn't help ... must be specific to Tom's tests.
Re org.junit bundles: I've already added this to org.eclipse.jdt.doc.isv/porting/3.9/incompatibilities.html, see bug 400441. But the readme_eclipse.html only contains links to a (not yet existing) eclipse_4_3_porting_guide.html, which I assume will be the one from org.eclipse.platform.doc.isv/porting/. The readme_eclipse.html should either also refer to the JDT porting guide at /org.eclipse.jdt.doc.isv/porting/eclipse_3_9_porting_guide.html, or we retire the JDT porting guide and put stuff from there into the platform porting guide as well.
(In reply to comment #9) > The readme_eclipse.html should either also refer to the JDT porting guide at > /org.eclipse.jdt.doc.isv/porting/eclipse_3_9_porting_guide.html, or we > retire the JDT porting guide and put stuff from there into the platform > porting guide as well. I just started doing that last year because in the past I just linked into ViewCVS. I must have forgotten about the JDT porting guide. I made a note to include the JDT porting guide on the web site as well (the link you see in the readme and plan documents).
(In reply to comment #1) > I have done my major update. Leaving open for documenting specific problems. > > http://git.eclipse.org/c/platform/eclipse.platform.releng.git/commit/ > ?id=be5702edea46e690195ff844d1994e9fac0f2123 We (or at least I) usually used http://git.eclipse.org/c/platform/eclipse.platform.releng.git/tree/features/org.eclipse.platform-feature/rootfiles/readme?id=be5702edea46e690195ff844d1994e9fac0f2123 as master. Did you take all changes from there into the RCP version?
(In reply to comment #11) > We (or at least I) usually used > http://git.eclipse.org/c/platform/eclipse.platform.releng.git/tree/features/ > org.eclipse.platform-feature/rootfiles/ > readme?id=be5702edea46e690195ff844d1994e9fac0f2123 > as master. Did you take all changes from there into the RCP version? I don't see any changes from the platform-feature readme in the past 7 months so I think we are fine. I also can't see any evidence that copy of the readme is used anywhere. I have not updated it for Kepler, yet the Eclipse SDK and Eclipse Platform downloads do contain the most up to date readme with all my recent changes. I will continue updating just the RCP one for now, since that is the one that is appearing in our builds. I will update the platform-feature copy at the very end just in case it appears somewhere. After Kepler we should try removing the platform-feature copy and see if that has any effect.
(In reply to comment #3) > The last two items in the 3.2.6 - SWT section should be removed. They are: > - Toolbar controls on GTK are not properly sized > - Navigation using tab and arrow keys Done. (In reply to comment #4) > SWT: > - BIDI Segments in text controls only work on Windows and GTK. > => "Text" must be capitalized, since this is about the Text widget's > addSegmentListener(..) API and doesn't apply to StyledText. > > JDT: > - Some refactoring script operations fail with Sun 6.0 JREs > => Remove the whole item. This works fine in current Oracle JREs. Fixed.
(In reply to bug 397226 comment #23) > 1) You need to add this after the setenv: "Then restart your Mac." -> This is still missing. - The title should be: <h4>Problems with non-ASCII file names on Mac OS X</h4> or: <h4>Cannot access files/folders with non-ASCII names on Mac OS X</h4> - There's still a reference to "MacOS X" (should be "Mac OS X").
(In reply to comment #14) > (In reply to bug 397226 comment #23) > > 1) You need to add this after the setenv: "Then restart your Mac." > -> This is still missing. > > - The title should be: > <h4>Problems with non-ASCII file names on Mac OS X</h4> > or: > <h4>Cannot access files/folders with non-ASCII names on Mac OS X</h4> > > - There's still a reference to "MacOS X" (should be "Mac OS X"). Fixed in master.
(In reply to comment #12) > I will continue updating just the RCP > one for now, since that is the one that is appearing in our builds. Indeed! > I will > update the platform-feature copy at the very end just in case it appears > somewhere. After Kepler we should try removing the platform-feature copy and > see if that has any effect. +1. Filed bug 409375 for that.
Released update to Platform UI known issues. http://git.eclipse.org/c/platform/eclipse.platform.releng.git/commit/?id=28aff176d9423c92418bbb3b2af41548638d5bb1 PW
Verified in I20130605-2000, that the readme is in our build. The "last revised" date is wrong as it was not updated along with the last change. I fixed this with: http://git.eclipse.org/c/platform/eclipse.platform.releng.git/commit/?id=27de2207dfc41f5beb7d5a87b466971d20e44455 so that it will be picked up, in case there will be another build for Kepler, and to ensure that the readme on the download page is correct. Not worth to request a rebuild for this though. I've also updated the copy in the platform-feature with: http://git.eclipse.org/c/platform/eclipse.platform.releng.git/commit/?id=d9c4aaae3e48dfe76cc1ba81c7607a4c475673dd and added the current version to our Web site: http://www.eclipse.org/eclipse/development/readme_eclipse_4.3.php
