| Updates |
|
Official plug-in version ID from 1.0 Rollup2 is 1.0.2 (also see
build notes).
These patches are not yet part of
any official release or rollup; but provide an early access to the next delivery for quality assessment. If you find any regression using these patches,
please inform the JDT/Core team by entering a bug report.
Patches listed here are Jck1.3a and Jck1.4 compliant.
|
 |
1.0.7 preview : address verify error with nested try statements
 |
posted on 2002/08/21, 3,203 KB |
| applies to |
R1.0 Rollup2 and better |
| description |
Patch resolving verification errors at runtime when source contains nested try/synchronized statements (bug 19916) and a sanity check error for debug attributes of unused local
variables (bug 8832),
it also includes 1.0.6 patch.
Corresponding sources are versioned using tag v_146
(also see corresponding build notes).
This patch can be applied by expanding the zip archive into the <install>/eclipse/plugins/ directory
NOTE: Plug-in revision ID is now "1.0.7".
In case this plug-in revision does not match the one currently installed,
the JDT feature may require to be edited accordingly (in <install>/eclipse/features/org.eclipse.jdt_x.y.z/feature.xml,
change the version to "1.0.7" for plugin which id is "org.eclipse.jdt.core").
|
|
|
1.0.6 preview : address issue where fully qualified class names break superclass visibility
|
posted on 2002/07/17, 3,198 KB |
| applies to |
R1.0 Rollup2 and better |
| description |
Patch resolving unexpected compilation error against some qualified superclass names. Resolves the bug 20400,
it also includes 1.0.5 patch.
Corresponding sources are versioned using tag v_145
(also see corresponding build notes).
This patch can be applied by expanding the zip archive into the <install>/eclipse/plugins/ directory
NOTE: Plug-in revision ID is now "1.0.6".
In case this plug-in revision does not match the one currently installed,
the JDT feature may require to be edited accordingly (in <install>/eclipse/features/org.eclipse.jdt_x.y.z/feature.xml,
change the version to "1.0.6" for plugin which id is "org.eclipse.jdt.core").
|
|
|
1.0.5 preview : address issue where changing read-only '.classpath' creates inconsistencies
|
posted on 2002/07/12, 3,198 KB |
| applies to |
R1.0 Rollup2 and better |
| description |
Patch resolving silent failures when attempting to write the .classpath file if read-only. Such a failure is now explicit, and properly rollbacks previous
settings, opening an error dialog to tell the user.
Resolves the bug 13905,
it also includes 1.0.4 patch.
Corresponding sources are versioned using tag v_144a
(also see corresponding build notes).
This patch can be applied by expanding the zip archive into the <install>/eclipse/plugins/ directory
NOTE: Plug-in revision ID is now "1.0.5".
In case this plug-in revision does not match the one currently installed,
the JDT feature may require to be edited accordingly (in <install>/eclipse/features/org.eclipse.jdt_x.y.z/feature.xml,
change the version to "1.0.5" for plugin which id is "org.eclipse.jdt.core").
|
|
|
1.0.4 preview : address builder crash when no debug attributes
|
posted on 2002/04/19, 3,203 KB |
| applies to |
R1.0 Rollup2 and better |
| description |
Patch resolving the exception thrown during the build if the debug attributes generation is turned off (note that there is no preference for this in 1.0, but debug attributes could be turned off programmatically using org.eclipse.jdt.core.JavaCore API).
Resolves the bug 11410,
and also includes 1.0.3 patch.
Corresponding sources are versioned using tag v_143
(also see corresponding build notes).
This patch can be applied by expanding the zip archive into the <install>/eclipse/plugins/ directory
NOTE: Plug-in revision ID is now "1.0.4".
In case this plug-in revision does not match the one currently installed,
the JDT feature may require to be edited accordingly (in <install>/eclipse/features/org.eclipse.jdt_x.y.z/feature.xml,
change the version to "1.0.4" for plugin which id is "org.eclipse.jdt.core").
|
|
|
1.0.3 preview : address issue where editing and saving read-only .java source file may cause lost of data
|
posted on 2002/07/12, 3,197 KB |
| applies to |
R1.0 Rollup2 and better |
| description |
Patch resolving issue where modifying read-only files could result in a loss of data. ClearCase repositories are tagging files as read-only by default.
Resolves the bug 7390,
Corresponding sources are versioned using tag v_142
(also see corresponding build notes).
This patch can be applied by expanding the zip archive into the <install>/eclipse/plugins/ directory
NOTE: Plug-in revision ID is now "1.0.3".
In case this plug-in revision does not match the one currently installed,
the JDT feature may require to be edited accordingly (in <install>/eclipse/features/org.eclipse.jdt_1.0.x/feature.xml,
change the version to "1.0.3" for plugin which id is "org.eclipse.jdt.core").
|
|
| Getting the sources |
- Define a CVS connection to server
pserver:anonymous@dev.eclipse.org:/cvsroot/eclipse
- Check out the
ECLIPSE_1_0 branch of the project org.eclipse.jdt.core.
- Make sure to import the prerequisite plug-ins (usually from the latest SDK R1.0.x build). Prerequisite plug-ins are already referenced on the project build path (
.classpath file).
- The sources of this project are either 1.3 or 1.4 compatible, however for 1.3 backward compatibility (Eclipse is primarily aimed for 1.3 runtimes),
the compiler compliance setting should be set to 1.3 and the default JRE should be a 1.3 JRE.
- In case willing to work on a different code stream, you may want to check out a different version of the project
- version
v_140c : source version for 1.0 Rollup 2
|
