Eclipse Platform Build Notes 
Java Development Tooling Core

What's new in this drop

Problem Reports Fixed

Problem Reports Closed

Eclipse Platform Build Notes 
Java Development Tooling Core

What's new in this drop

Problem Reports Fixed

Problem Reports Closed

Eclipse Platform Build Notes 
Java Development Tooling Core

What's new in this drop

Problem Reports Fixed

Problem Reports Closed

Eclipse Platform Build Notes 
Java Development Tooling Core

What's new in this drop

Problem Reports Fixed

Problem Reports Closed

Eclipse Platform Build Notes 
Java Development Tooling Core

What's new in this drop

Problem Reports Fixed

Problem Reports Closed

Eclipse Platform Build Notes 
Java Development Tooling Core

What's new in this drop

• switched to branch R2_0_1
• increased plug-in revision ID to 2.0.1

Problem Reports Fixed

Problem Reports Closed

Eclipse Platform Build Notes 
Java Development Tooling Core

What's new in this drop

Problem Reports Fixed

Problem Reports Closed

Eclipse Platform Build Notes 
Java Development Tooling Core

What's new in this drop

Problem Reports Fixed

Problem Reports Closed

Eclipse Platform Build Notes 
Java Development Tooling Core

What's new in this drop

• Changed ASCII/binary property for entire project.

Problem Reports Fixed

Problem Reports Closed

Eclipse Platform Build Notes 
Java Development Tooling Core

What's new in this drop

• Changed ASCII/binary property for 'about.html' file to ASCII.

Problem Reports Fixed

Problem Reports Closed

Eclipse Platform Build Notes 
Java Development Tooling Core

What's new in this drop

Problem Reports Fixed

Problem Reports Closed

Eclipse Platform Build Notes 
Java Development Tooling Core

What's new in this drop

• Updated about.html file.

Problem Reports Fixed

Problem Reports Closed

Eclipse Platform Build Notes 
Java Development Tooling Core

What's new in this drop

Problem Reports Fixed

Problem Reports Closed

Eclipse Platform Build Notes 
Java Development Tooling Core

What's new in this drop

Problem Reports Fixed

Problem Reports Closed

Eclipse Platform Build Notes 
Java Development Tooling Core

What's new in this drop

• Updated about.html file with reference to CPL 1.0.

Problem Reports Fixed

Problem Reports Closed

Eclipse Platform Build Notes 
Java Development Tooling Core

What's new in this drop

• Removed deprecated 2.0 temporary API: IWorkingCopy#findSharedWorkingCopy() which was no longer used anyway. Proper API is taking a IBufferFactory in argument.

Problem Reports Fixed

Problem Reports Closed

Eclipse Platform Build Notes 
Java Development Tooling Core

What's new in this drop

Problem Reports Fixed

Problem Reports Closed

Eclipse Platform Build Notes 
Java Development Tooling Core

What's new in this drop

• Added protection around listener callback invocations (using ISafeRunnable).
• Removed 2 unused deprecated constants on IJavaSearchConstants: READ_REFERENCES and WRITE_REFERENCES. They were annoted with intention to discard before 2.0 since were temporarily introduced and deprecated (due to bad naming).

  	/** 
  	 * @deprecated - use WRITE_ACCESSES instead (will be discarded before 2.0)
  	 * @since 2.0
  	 */
  	int WRITE_REFERENCES = WRITE_ACCESSES;
  	

Problem Reports Fixed

Problem Reports Closed

Eclipse Platform Build Notes 
Java Development Tooling Core

What's new in this drop

• Removed deprecated API on IJavaProject. These were not in 1.0, and shouldn't have been introduced (incorrectly resurrected from 0.9).
  • IJavaProject#getClasspath(...) --> IJavaProject#getRawClasspath(...)
  • IJavaProject#setClasspath(...) --> IJavaProject#setRawClasspath(...)
  • IJavaProject#newProjectEntry(...) --> JavaCore#newProjectEntry(...)
  • IJavaProject#newLibraryEntry(...) --> JavaCore#newLibraryEntry(...)
  • IJavaProject#newSourceEntry(...) --> JavaCore#newSourceEntry(...)

Problem Reports Fixed

Problem Reports Closed

Eclipse Platform Build Notes 
Java Development Tooling Core

What's new in this drop

• The resource copy exclusion filter now tolerates whitespaces inside the filter pattern, they will be trimmed when used. e.g. " .* , foo/ " is now accepted.

Problem Reports Fixed

Problem Reports Closed

Eclipse Platform Build Notes 
Java Development Tooling Core

What's new in this drop

• Changing 2.0 API for refreshing external JARs so as to pass in a collection of *elements* to restrain the scope of the update (see IJavaModel#refreshExternalArchives(IJavaElement[],IProgressMonitor). Elements can either be package fragment roots, projects or Java model.

Problem Reports Fixed

Problem Reports Closed

Eclipse Platform Build Notes 
Java Development Tooling Core

What's new in this drop

• Compiler can now optionally report unused imports. See option named "" on JavaCore#getDefaultOptions comment

  	 * COMPILER / Reporting Unused Import
  	 *    When enabled, the compiler will issue an error or a warning for unused import 
  	 *    reference 
  	 *     - option id:		"org.eclipse.jdt.core.compiler.problem.unusedImport"
  	 *     - possible values:	{ "error", "warning", "ignore" }
  	 *     - default:		"ignore"
  

  Note that if import problems (separate settings) are disabled, unused imports will not be reported either. This option is also available to the batch compiler ("-warn:unusedImports"). Implementations of IProblemRequestor can identify this new problem through its ID IProblem#UnusedImport.
• Added API on IType so as to tell whether a type is anonymous, local or member.
• Changing 2.0 API for refreshing external JARs so as to pass in a collection of projects to restrain the scope of the update (see IJavaModel#refreshExternalJARs(IJavaProject[],IProgressMonitor).

Problem Reports Fixed

Problem Reports Closed

Eclipse Platform Build Notes 
Java Development Tooling Core

What's new in this drop

Problem Reports Fixed

Problem Reports Closed

Eclipse Platform Build Notes 
Java Development Tooling Core

What's new in this drop

• Added API to retrieve cached flags on type hierarchies (see ITypeHierarchy#getCachedFlags(IType)). Note that these flags can help answering both isClass/isInterface queries as well (see Flags.isInterface(int)
• Added API to trigger a Java model refresh with respect to external JARs: IJavaModel#refreshExternalJARs.

/**
 * Triggers an update of the JavaModel with respect to the referenced external JARs.
 * This operation will issue a JavaModel delta describing the discovered changes, in term
 * of Java element package fragment roots added, removed or changed.
 * 
 * @param monitor - a progress monitor used to report progress
 * @exception JavaModelException in one of the corresponding situation:
 *    - an exception occurs while accessing project resources 
 * 
 * @see IJavaElementDelta
 * @since 2.0
 */
void refreshExternalJARs(IProgressMonitor monitor) throws JavaModelException;

• Added flag for notifying a JAR content change during Java delta notification: IJavaElementDelta#F_ARCHIVE_CONTENT_CHANGED

Problem Reports Fixed

Problem Reports Closed

Eclipse Platform Build Notes 
Java Development Tooling Core

What's new in this drop

• '.classpath' file is now written using platform line delimiters (used to be only using LFs). It is recommanded to convert it to 'text' format so as to avoid surfacing delimiter differences in between incompatible platforms.
• The setting allowing for filtering resource copy now also supports folder filtering. Folder names are recognized by their '/' suffix, e.g. "META-INF/" specifies filtering out all folder named 'META-INF' (and their contents)

Problem Reports Fixed

Problem Reports Closed

Eclipse Platform Build Notes 
Java Development Tooling Core

What's new in this drop

• Added ToolFactory.createDefaultClassFileReader(IClassFile classfile, int decodingFlag) as an helper method to create a classfile reader for classfile elements.

Problem Reports Fixed

Problem Reports Closed

Eclipse Platform Build Notes 
Java Development Tooling Core

What's new in this drop

• New compiler option added to control max number of problems reported on a unit. Default is 100. See JavaCore#getDefaultOptions()

	 * COMPILER / Maximum number of problems reported per compilation unit
	 *    Specify the maximum number of problems reported on each compilation unit.
	 *     - option id:			"org.eclipse.jdt.core.compiler.maxProblemPerUnit"
	 *     - possible values:	"" where  is zero or a positive integer (if zero then all problems are reported).
	 *     - default:			"100"
    

• By default, the Java builder is now aborting build process on projects with classpath problems. This option can be disabled through the Java preferences: Window>Preferences>Java>Builder>

Problem Reports Fixed

Problem Reports Closed

Eclipse Platform Build Notes 
Java Development Tooling Core

What's new in this drop

• Java compiler never record more than 100 markers for compilation problems. All APIs using IProblemRequestor still see them all. This change is intended to prevent the task list from being overhelmed with tons of secondary problems.
• Added APIs that allow to create a type hierarchy with a set of working copies that take precendence over their original compilation unit:
  • IType.newSuperTypeHierarchy(IWorkingCopy[], IProgressMonitor)
  • IType.newTypeHierarchy(IWorkingCopy[], IProgressMonitor)
  Note that change notification and refreshing is not supported on these hierarchies.

Problem Reports Fixed

Problem Reports Closed

Eclipse Platform Build Notes 
Java Development Tooling Core

What's new in this drop

• Added org.eclipse.jdt.core.dom.Message#Message(String, int, int). This new constructor allows to set the length field. The constructor org.eclipse.jdt.core.dom.Message#Message(String, int) still exists and set the length to 0. There is no need to use the new constructor if the length is never used.
• Renamed org.eclipse.jdt.core.dom.Message#getSourcePosition() to org.eclipse.jdt.core.dom.Message#getStartPosition(). This is more consistent with the DOM/AST API. The old method has been deprecated and will be removed in a close future.
• Added org.eclipse.jdt.core.dom.Message#getLength() allowing to retrieve the length of the node on which the message has been reported.
• Added JavaCore#getSharedWorkingCopies(IBufferFactory) allowing to retrieve all registered working copies for a given buffer factory.
• JavaBuilder no longer build projects for which prerequisite projects aborted the build process. This considerably reduces the number of secondary errors when dealing with workspace setup problems.
• Added IWorkingCopy#reconcile(boolean forceProblemDetection, IProgressMonitor monitor) allowing to force problem refresh even if working copy was already consistent.
• Added IClasspathContainer new kind constant K_DEFAULT_SYSTEM to denote system libraries implicitely contributed by a runtime.
• Classpath container path can have more than 2 segments. First one is still the container ID, the remaining ones are forming the hints passed to the resolution phase (ClasspathContainerInitializer
• Classpath containers can no longer contain variable entries
• JavaCore now persists its options (JavaCore#getOptions) using its plugin property store. Clients no longer need to save them.
• JavaCore now provides constants for all supported option IDs and values.
• JavaCore option added, to allow build to abort in presence of invalid classpath.
• Leveraged new encoding support from Platform/Core. The JavaCore option "org.eclipse.jdt.core.encoding" is now equivalent to ResourcesPlugin.getEncoding().

  	 * BUILDER / Abort if Invalid Classpath
  	 *    Allow to toggle the builder to abort if the classpath is invalid
  	 *     - option id:        "org.eclipse.jdt.core.builder.invalidClasspath"
  	 *     - possible values:  { "abort", "ignore" }
  	 *     - default:          "ignore"
  	

Problem Reports Fixed

Problem Reports Closed

Eclipse Platform Build Notes 
Java Development Tooling Core

What's new in this drop

• Priority of the background indexer has been lowered so that it doesn't interfer with other threads (e.g. when switching JRE the indexing will not start before the switch has completed)
• Revised Classpath Container proposal (also see notes):
  • classpathContainerChanged() got replaced with setter method JavaCore.setClasspathContainer(IPath containerPath, IJavaProject[] affectedProjects, IClasspathContainer respectiveContainers)
  • ClasspathContainerResolver got renamed into ClasspathContainerInitializer
  • Container can no longer contain any CPE_SOURCE entry.
  • added container interface IClasspathContainer in order to allow containers to be presented in a UI.
    • IClasspathEntry[] getClasspathEntries()
    • String getDescription()
    • int getKind()
    • Path getPath()
• If the completion is inside a super type in type declaration header then the relevance grow when the type have the correct nature :
  • After extends keyword of a class header the relevance grow if the type is a class.
  • After implements keyword of a class header the relevance grow if the type is an interface.
  • After extends keyword of an interface header the relevance grow if the type is an interface.
• If the completion is inside a type in a catch or throws clause the relevance grow when the type is an exception (if the name of the type contain exception or error).
• If the completion is inside a throw statement the relevance grow when the proposal is an exception.
• The background indexer now recovers from internal crash. If this happens, a new thread is created and a consistency check is done on all indexes.
• An internal buffer factory is now used to create buffers when clients don't provide one.
• Special handling in the formatter for //$NON-NLS- comments in the source. When a line contains such comments it is not formatted anymore. The user will need to manually format it. See 14387 and 12540.

Problem Reports Fixed

Problem Reports Closed

Eclipse Platform Build Notes 
Java Development Tooling Core

What's new in this drop

• Java builder is logging its internal errors

Problem Reports Fixed

Problem Reports Closed

Eclipse Platform Build Notes 
Java Development Tooling Core

What's new in this drop

• Java model API additions:
  • IJavaProject.findType(String)
  • IJavaProject.findType(String, String)
  • IMethod.isMainMethod()
  • IMethod.isSimilar(IMethod)
  • IType.getFullyQualifiedName(char)
  • IType.getTypeQualifiedName(char)
• API change: IWorkingCopy.findSharedWorkingCopy() is now taking an extra argument: the buffer factory it is associated with. This ensures that working copies can only be reused for the same buffer factories.
• JavaModelOperations now guarantee the JavaModel is up to date when notifying the Java model change listeners. In particular, a builder running after the Java builder will be able to query the Java model with respect to the changes introduced through Java model operations (except for index queries). This was never guaranteed in 1.0, but indirectly occurred due to the fact that the previous Java builder implementation did force to refresh the Java model while building.
• Classpath Container Enhancement (also see notes):
  Added new type of classpath entry (CPE_CONTAINER), (see proposal here) so as to better encapsulate client defined libraries. Typically, VM installs would use classpath containers instead of classpath variables (JRE_LIB) so as to better describe the corresponding set of libraries (including extension dirs) to be placed on the build path.

  New APIs added to reflect this addition:

  • JavaCore.newContainerEntry(IPath containerPath)
  • JavaCore.newContainerEntry(IPath containerPath, boolean isExported)
  • JavaCore.classpathContainerChanged(IPath containerPath, IJavaElement scope)
  • ClasspathContainerResolver
• DOM/AST:
  A new type of node has been added to handle properly the instanceof expression. So the new InstanceofExpression node replaced the usage of InfixExpression with the operator InfixExpression.Operator.INSTANCEOF. This operator has been deprecated and is expected to be removed for the next integration build. See bug 14453.

Problem Reports Fixed

Problem Reports Closed

Eclipse Platform Build Notes 
Java Development Tooling Core

What's new in this drop

• Changing the source attachement of a jar will now correctly fire source attachment java deltas. The flags of these deltas are:
  • IJavaElementDelta.F_SOURCEATTACHED if a source has been attached to a jar and no source previously existed.
  • IJavaElementDelta.F_SOURCEDETACHED if a source has been detached from a jar and no other source has been attached.
  • IJavaElementDelta.F_SOURCEDETACHED | JavaElementDelta.F_SOURCEATTACHED if an attached source has been changed.

Problem Reports Fixed

Problem Reports Closed

Eclipse Platform Build Notes 
Java Development Tooling Core

What's new in this drop

• Changed the package fragment caching policy so as to accomodate large workspaces. It used to be an overflowing LRU cache of size 1000 package fragments. It now is a simple table, which is never emptied implicitly any longer. Memory overhead looks negligeable, and it allows to deal much better with very large workspaces. Other similar improvements were made on the same front so as to improve JRE switching with such workspaces.
• ElementChangedEvent got added notion of type (similar to IResourceChangeEvent), so as to better allow clients to react to JavaModel changes:
  • ElementChangedEvent.POST_CHANGE :

    	/**
    	 * Event type constant (bit mask) indicating an after-the-fact 
    	 * report of creations, deletions, and modifications
    	 * to one or more Java element(s) expressed as a hierarchical
    	 * java element delta as returned by getDelta.
    	 *
    	 * Note: this notification occurs during the corresponding POST_CHANGE
    	 * resource change notification, and contains a full delta accounting for
    	 * any JavaModel operation  and/or resource change.
    	 *
    	 * @see IJavaElementDelta
    	 * @see IResourceChangeEvent
    	 * @see #getDelta
    	 * @since 2.0
    	 */
    	public static final int POST_CHANGE = 1;
    

  • ElementChangedEvent.PRE_AUTO_BUILD

    	/**
    	 * Event type constant (bit mask) indicating an after-the-fact 
    	 * report of creations, deletions, and modifications
    	 * to one or more Java element(s) expressed as a hierarchical
    	 * java element delta as returned by getDelta.
    	 *
    	 * Note: this notification occurs during the corresponding PRE_AUTO_BUILD
    	 * resource change notification. The delta which is notified here only contains
    	 * information relative to the previous JavaModel operations (i.e. ignores the
    	 * possible resources which have changed outside Java operations). In
    	 * particular, it is possible that the JavaModel be inconsistent with respect to
    	 * resources which got modified outside JavaModel operations (it will only be
    	 * fully consistent once the POST_CHANGE notification has occured).
    	 * 
    	 * @see IJavaElementDelta
    	 * @see IResourceChangeEvent
    	 * @see #getDelta
    	 * @since 2.0
    	 */
    	public static final int PRE_AUTO_BUILD = 2;
    

  • ElementChangedEvent.RECONCILE

    	/**
    	 * Event type constant (bit mask) indicating an after-the-fact 
    	 * report of creations, deletions, and modifications
    	 * to one or more Java element(s) expressed as a hierarchical
    	 * java element delta as returned by getDelta.
    	 *
    	 * Note: this notification occurs as a result of a working copy reconcile
    	 * operation.
    	 *
    	 * @see IJavaElementDelta
    	 * @see IResourceChangeEvent
    	 * @see #getDelta
    	 * @since 2.0
    	 */
    	public static final int POST_RECONCILE = 4;	
    

• Also added a corresponding API on JavaCore so as to allow registering a listener for a given type of event.

  	/**
  	 * Adds the given listener for changes to Java elements.
  	 * Has no effect if an identical listener is already registered.
  	 * After completion of this method, the given listener will be registered for exactly the
  	 * the specified events.  If they were previously registered for other events, they
  	 * will be deregistered.  
  	 *
  	 * Once registered, a listener starts receiving notification of changes to
  	 * java elements in the model. The listener continues to receive 
  	 * notifications until it is replaced or removed. 
  	 * 
  	 * Listeners can listen for several types of event as defined in ElementChangeEvent.
  	 * Clients are free to register for any number of event types however if they register
  	 * for more than one, it is their responsibility to ensure they correctly handle the
  	 * case where the same java element change shows up in multiple notifications.  
  	 * Clients are guaranteed to receive only the events for which they are registered.
  	 *
  	 * 
  	 * @param listener the listener
  	 * @param eventMask the bit-wise OR of all event types of interest to the listener
  	 * @see IElementChangeListener
  	 * @see ElementChangeEvent
  	 * @see #removeElementChangeListener
  	 *	@since 2.0
  	 */
  	public static void addElementChangedListener(IElementChangedListener listener, int eventMask)
  	

Problem Reports Fixed

Problem Reports Closed

Eclipse Platform Build Notes 
Java Development Tooling Core

What's new in this drop

• Added a first proposal for .class file reading APIs. This is still experimental and might change slightly. See new API in org.eclipse.jdt.core.util.
  • ByteCodeVisitorAdapter
  • ClassFormatException
  • DecodingFlag
  • IAttributeNamesConstants
  • IBytecodeVisitor
  • IClassFileAttribute
  • IClassFileDisassembler and ToolFactory#createDefaultClassFileDisassembler
  • IClassFileReader
  • ICodeAttribute
  • IConstantPool
  • IConstantPoolConstant
  • IConstantPoolEntry
  • IConstantValueAttribute
  • IExceptionAttribute
  • IExceptionTableEntry
  • IFieldInfo
  • IInnerClassesAttribute
  • IInnerClassesAttributeEntry
  • ILineNumberAttribute
  • ILocalVariableAttribute
  • ILocalVariableTableEntry
  • IMethodInfo
  • IModifierConstants
  • IOpcodeMnemonics
  • ISourceAttribute
  • OpcodeStringValues
  The default implementations are in org.eclipse.jdt.internal.core.util. Any comment is welcome and related bugs should be entered in JDT/Core.
• Added char array based APIs on Signature. This APIs avoid creating needless Strings and are thus much more performant than their String based equivalent.
  • createArraySignature(char[], int arrayCount)
  • createCharArrayTypeSignature(char[], boolean)
  • createMethodSignature(char[][], char[])
  • getArrayCount(char[])
  • getElementType(char[])
  • getParameterCount(char[])
  • getParameterTypes(char[])
  • getQualifier(char[])
  • getReturnType(char[])
  • getSimpleName(char[])
  • getSimpleNames(char[])
  • toCharArray(char[], char[], char[][], boolean, boolean)
  • toCharArray(char[])
  • toQualifiedName(char[][])
• Removed temporary 2.0 API which were deprecated in previous builds:
  • IWorkingCopy#getSharedWorkingCopy(IProgressMonitor, IBufferFactory), use API with extra IProblemRequestor
  • IWorkingCopy#getWorkingCopy(IProgressMonitor, IBufferFactory), use API with extra IProblemRequestor
  • IWorkingCopy#reconcile(IProblemRequestor), use API with no IProblemRequestor

Problem Reports Fixed

Problem Reports Closed

Eclipse Platform Build Notes 
Java Development Tooling Core

What's new in this drop

• Adding a new empty source folder no longer causes a full build. Only an incremental build is needed now.
• Java model API additions:
  • IJavaElement.getAncestor(int)
  • IJavaElement.getOpenable()
  • IJavaElement.getPath()
  • IJavaElement.getResource()
  • IJavaProject.isOnClasspath(IJavaElement)
  • IPackageFragmentRoot.getRawClasspathEntry()
  • IType.findMethods(IMethod)
  • IWorkingCopy.findElements(IJavaElement)
  • IWorkingCopy.findPrimaryType()
• ICompletionRequestor API change :
  • Added #beginReporting() and #endReporting() API on IProblemRequestor. #beginReporting is always called before restarting error detection. #endReporting is always called at the end of detection.
  • Added API for setting multiple classpath variables at once (JavaCore#setClasspathVariables, this allows to update all affected projects exactly once, instead of iterating multiple times on each project (if it references the variable). This can improve performance when setting JRE variables.
  • Added a new parameter relevance to be able to sort proposal by degree of relevance. relevance is a positive integer which are used for determine if this proposal is more relevant than another proposal. This value can only be used for compare relevance. A proposal is more relevant than another if his relevance value is higher.
    
    ICompletionRequestor{
      void acceptAnonymousType(..., int relevance);
      void acceptClass(..., int relevance);
      void acceptError(...);
      void acceptField(..., int relevance);
      void acceptInterface(..., int relevance);
      void acceptKeyword(..., int relevance);
      void acceptLabel(..., int relevance);
      void acceptLocalVariable(..., int relevance);
      void acceptMethod(..., int relevance);
      void acceptMethodDeclaration(..., int relevance);
      void acceptModifier(..., int relevance);
      void acceptPackage(..., int relevance);
      void acceptType(..., int relevance);
      void acceptVariableName(..., int relevance);
    }
    
    
  • If the completion identifier and proposal are equal and the case match then the proposal relevance grow. Note that this isn't a 1.0 breaking API change, it only affects the 2.0 new code assist API (i.e. still backward compatible with 1.0 clients) which hasn't yet reached stability, though it should be close to now.

Problem Reports Fixed

Problem Reports Closed

Eclipse Platform Build Notes 
Java Development Tooling Core

What's new in this drop

• Improved specification of IBuffer by saying that:
  • Java model operations that manipulate an IBuffer (e.g. IType.createMethod(...)) ensures that the same line delimiter (i.e. either "\n" or "\r" or "\r\n") is used accross the whole buffer. Thus these operations may change the line delimiter(s) included in the string to be append, or replaced. However implementors of this interface should be aware that other clients of IBuffer might not do such transformations beforehand.
  • addBufferChangedListener and removeBufferChangedListener have no effect if the buffer is already closed.
  • Other operations that manipulate the buffer (like setContent might throw a RuntimeException if called after the buffer has been closed.
• IScanner API :
  • added IScanner#getSource so as to retrieve the scanner original source
  • renamed IScanner#setSourceBuffer into IScanner#setSource

Problem Reports Fixed

Problem Reports Closed

Eclipse Platform Build Notes 
Java Development Tooling Core

What's new in this drop

• Reconciling with errors provide type errors in addition to syntax ones. This is still experimental, and can be disabled by unchecking the editor preference for transient problems.
• Performance improvement of index queries with the WaitUntilReady policy. The background indexer now takes all the CPU when another thread is waiting for it to finish indexing. User will notice this improvement when doing a search or opening a type and there are still files to index.
• Scanner API
  • defined scanner API (see org.eclipse.jdt.core.compiler.IScanner).
  • added tool factory API (see org.eclipse.jdt.core.ToolFactory#createScanner), allowing to obtain a scanner (implementing IScanner API).
• Code formatter API
  • defined code formatter API (see org.eclipse.jdt.core.ICodeFormatter).
  • added tool factory API (see org.eclipse.jdt.core.ToolFactory#createCodeFormatter), allowing to obtain a code formatter (implementing ICodeFormatter API). Note that an extension point was also added to allow client code to contribute a code formatter implementation. The code formatter extension point is named org.eclipse.jdt.core.codeFormatter, also see associate comment in plugin.xml.
  • added tool factory API (see org.eclipse.jdt.core.ToolFactory#createDefaultCodeFormatter), allowing to obtain a default code formatter (implementing ICodeFormatter API).
• Working Copy API : instead of passing a problem requestor (org.eclipse.jdt.core.IProblemRequestor) to working copy #reconcile(...) operation. The problem requestor is passed along at creation time.
  • added IWorkingCopy.getWorkingCopy(IProgressMonitor, IBufferFactory, IProblemRequestor)
  • added IWorkingCopy.getSharedWorkingCopy(IProgressMonitor, IBufferFactory, IProblemRequestor)
  Previous API taking IBufferFactory got deprecated, they will be removed in a subsequent build.
• Some internal classes got deprecated (as client code relies on them), since being surfaced:
  • org.eclipse.jdt.internal.core.parser.InvalidInputException
    ==> org.eclipse.jdt.core.compiler.InvalidInputException
  • org.eclipse.jdt.internal.core.parser.TerminalSymbols
    ==> org.eclipse.jdt.core.compiler.ITerminalSymbols
  They will be removed in a subsequent build.

Problem Reports Fixed

Problem Reports Closed

Eclipse Platform Build Notes 
Java Development Tooling Core

What's new in this drop

Problem Reports Fixed

Problem Reports Closed

Eclipse Platform Build Notes 
Java Development Tooling Core

What's new in this drop

• New API on IType for complete snippet in current type context. Code complete is performed against source (if available) or against type structure
        void codeComplete(
            char[] snippet,
            int insertion,
            int position,
            char[][] localVariableTypeNames,
            char[][] localVariableNames,
            int[] localVariableModifiers,
            boolean isStatic,
            ICompletionRequestor requestor) throws JavaModelException;
   

Problem Reports Fixed

Problem Reports Closed

Eclipse Platform Build Notes 
Java Development Tooling Core

What's new in this drop

• Added option to trace java search activity. To enable it, see the following line in the org.eclipse.jdt.core/.options file: org.eclipse.jdt.core/debug/search=true
• Added API CorrectionEngine#computeCorrections(IProblem, ICompilationUnit, ICorrectionRequestor), allowing. to compute replacement corrections for IProblem(s) detected while reconciling.
• Added API ISourceReference#exists(), allowing. to check existency before invoking ISourceReference behavior. All implementations did already provide an exists() method since they also are implementing IJavaElement.

Problem Reports Fixed

Problem Reports Closed

Eclipse Platform Build Notes 
Java Development Tooling Core

What's new in this drop

• Added API IDOMFactory.createInterface() and IDOMFactory.createClass(). See 10980 for details.

Problem Reports Fixed

Problem Reports Closed

Eclipse Platform Build Notes 
Java Development Tooling Core

What's new in this drop

• Performance improvement:
  • Search doesn't populate the Java Model any longer. Thus the memory used by a search operation can be reclaimed at the end.
  • Access to zip and jar files has been improved, which should result in better performance on a slow network.
• Added flag IJavaElementDelta.F_FINE_GRAINED that indicates that a fine-grained delta was computed for a given delta. Clients can use this flag to find out if a compilation unit that have a F_CONTENT change should assume that there are no finer grained changes (F_FINE_GRAINED is set) or if finer grained changes were not considered (F_FINE_GRAINED is not set).
• Surfacing IProblem (org.eclipse.jdt.core.compiler.IProblem)
  This allows some Java API to report failures in a lighter way than generating markers. Marker based API have been deprecated (note that due to some deadlock in client code, some of these API did not even produce markers, e.g. reconciling). In addition to surfacing problem descriptions, IProblem exposes all the IDs for the Java problem markers (attribute "id" on markers of type "org.eclipse.jdt.core.problem")
• Changed error reporting method for ICompletionRequestor to surface IProblems instead of IMarkers.

Problem Reports Fixed

Problem Reports Closed

Eclipse Platform Build Notes 
Java Development Tooling Core

What's new in this drop

• Added API IClassFile.getWorkingCopy(IProgressMonitor, IBufferFactory) for consistence with IWorkingCopy. The returned working copy is just a wrapper on the class file's buffer. Thus only the getBuffer() operation is valid on this working copy.
• Added the notion of shared working copies. This allows clients to always get the same IWorkingCopy instance when asking for a working copy. See IWorkingCopy.getSharedWorkingCopy(IProgressMonitor, IBufferFactory), IWorkingCopy.findSharedWorkingCopy() and IWorkingCopy.destroy() for more detail.
• Added option to trace use of shared working copies. To enable it, see the following line in the org.eclipse.jdt.core/.options file: org.eclipse.jdt.core/debug/sharedworkingcopy=true
• Added extension point to jdtcore so as to allow client plugins to register classpath variable initializers. Extension point is "org.eclipse.jdt.core.classpathVariableInitializer". (also see design notes) Note that each classpath variable, if unbound, will trigger its registered initializer exactly once per session. If unsuccessful, it will stay unbound.
• Added option to trace classpath variable initializations. To enable it, see the following line in the org.eclipse.jdt.core/.options file: org.eclipse.jdt.core/debug/cpvariable=true
• Added option to trace access to zip and jar files from the Java model. To enable it, see the following line in the org.eclipse.jdt.core/.options file: org.eclipse.jdt.core/debug/zipaccess=true
• Resurrect some code for backport 1.0 internal functionality
  • org.eclipse.jdt.internal.compiler.ConfigurableOption (all the class).
  • org.eclipse.jdt.internal.formatter.CodeFormatter (some methods) :
    • public CodeFormatter(ConfigurableOption[] settings)
    • private static Map convertConfigurableOptions(ConfigurableOption[] settings)
    • public static ConfigurableOption[] getDefaultOptions(Locale locale)
    • public static String format(String sourceString, int initialIndentationLevel, ConfigurableOption[] options)
  • org.eclipse.jdt.internal.formatter.Options.properties (all the file)

Problem Reports Fixed

Problem Reports Closed

Eclipse Platform Build Notes 
Java Development Tooling Core

What's new in this drop

• Java tooling now performs normally inside method bodies whose signature could not be resolved.
• Specified that when an IBuffer is created through an IBufferFactory, its content is set with the original element's content.

Problem Reports Fixed

Problem Reports Closed

Eclipse Platform Build Notes 
Java Development Tooling Core

What's new in this drop

Problem Reports Fixed

Problem Reports Closed

Eclipse Platform Build Notes 
Java Development Tooling Core

What's new in this drop

• Resource copy filters : A new setting allows to specify exclusion filters for resource being copied to the output folder..
  • option id: "org.eclipse.jdt.core.builder.resourceCopyExclusionFilters"
  • possible values: { "[,]* } where is a file name pattern (only * wild-cards allowed)
  • default: ""
• Encoding support : Batch compiler can be specified the source encoding format using '-encoding myEncoding' command line option. In case of necessity, each individual file specified on the command line can be associated with a custom encoding by suffixing its name with '[myEncoding]' (if applied to a folder, then all files in it will be sharing the custom encoding). When no encoding is specified, then the platform default is used (as before). Similarily, a JavaCore option got added to control the default encoding (no support yet for per file custom encoding).
  • option id: "org.eclipse.jdt.core.encoding"
  • possible values: { "" for platform default, or any of the supported encoding name }.
  • default: ""
• Fix for 9183 required to increment the index signature version so as to trigger automatic reindexing on workspace startup (and thus add somme type references that were previously missing from the binary index files). Subsequent startups will not reindex any further (only if inconsistency is detected, e.g. signature version is different).
• The IBufferFactory used when creating an IWorkingCopy (see ICompilationUnit.getWorkingCopy(IProgressMonitor monitor, IBufferFactory factory)) is now remembered and will be reused if the working copy is closed then reopen.
• Old Java builder implementation got removed
• Project dependency cycle detection reenabled
• Open on selection no longer need a non-empty selection to perform (when empty it will use the token in which the selection start position is located).
• Improved progress reporting while searching all types in the workspace.

Problem Reports Fixed

Problem Reports Closed

Eclipse Platform Build Notes 
Java Development Tooling Core

What's new in this drop

• The JavaModel no longer notifies changes for generated classfiles in the output folder, these were never supposed to be signaled.

Problem Reports Fixed

Problem Reports Closed

Eclipse Platform Build Notes 
Java Development Tooling Core

What's new in this drop

• Java compiler is JCK 1.4 compliant. When toggled in 1.4 mode (batch: -1.4 -source 1.4), the Java compiler is fully JCK 1.4 compliant as of JCK 1.4 2001-10-01 update. When in 1.3 mode (default), it is JCK 1.3a compliant.
• By default, when toggled into 1.4 mode, the batch compiler will enable assertion support (e.g. -source 1.4). It can still manually be toggled for 1.3 source level compatibility (-source 1.3).
• Added constructor SearchEngine(IWorkingCopy[]) which takes a list of working copies that will take precedence over their original compilation units in the subsequent search operations on this search engine.
  Note that this functionality is still under development and some parts may not work as expected. Feedback is welcome.
• New feature to achieve problems corrections : org.eclipse.jdt.core.CorrectionEngine. Correction results are answered through a requestor (org.eclipse.jdt.core.ICorrectionRequestor).
• JavaCore will no longer add indirectly prereq'ed project amongst project references.
• New JDOM AST API available (also see design note). This API has not yet reached full stability, and feedback is very welcome.

Problem Reports Fixed

Problem Reports Closed

Eclipse Platform Build Notes 
Java Development Tooling Core

What's new in this drop

Problem Reports Fixed

Problem Reports Closed

Eclipse Platform Build Notes 
Java Development Tooling Core

What's new in this drop

• Added workaround for 7764 UI Dead Lock - IDE frozen

Problem Reports Fixed

Problem Reports Closed

Eclipse Platform Build Notes 
Java Development Tooling Core

What's new in this drop

• The selection engine now only selects identifier between selection start and selection end. Previous behaviour was to select identifier between selection start and identifier end. (e.g. if you select File in FileInput, now the selection engine select the class File and not FileInput)
• Fix for 6839 required to increment the index signature version so as to trigger automatic reindexing on workspace startup (and thus get rid of undesired anonymous type entries in the index files). Subsequent startups will not reindex any further (only if inconsistency is detected, e.g. signature version is different).

Problem Reports Fixed

Problem Reports Closed

Eclipse Platform Build Notes 
Java Development Tooling Core

What's new in this drop

• The compiler will now follow JLS 8.6 with respect to anonymous class constructors (i.e. allow them to throw any exceptions).
• The compiler now enforces that interface methods be compatible with Object ones.
• The batch compiler will no longer create package directory structure anymore when the command line argument '-d' is omitted (compliant with standard batch compilers).
• A type hierarchy that misses a super type is not rooted at Object any longer, but the subtype (of the missing type) will be a root (this is the behavior of VA/Java and VAME.)
• Adding a type that was missing from a hierarchy will update the hierarchy correctly.
• New API on ICompletionRequestor for suggest anonymous type declaration:

      void acceptAnonymousType(
          char[] superTypePackageName,
          char[] superTypeName,
          char[][] parameterPackageNames,
          char[][] parameterNames,
          char[][] parameterNames,
          char[] completionName,
          int modifiers,
          int completionStart,
          int completionEnd);
 

Problem Reports Fixed

Problem Reports Closed

Eclipse Platform Build Notes 
Java Development Tooling Core

What's new in this drop

• Added new compiler option to toggle compliance level (can be either "1.3" or "1.4" - 1.3 being the default), and it will affect the behavior of the compiler with respect to JLS 8.1.5 (inherited member shadows enclosing one). Option is located on JavaCore#getOptions() and named "org.eclipse.jdt.core.compiler.compliance" Accordingly, the batch compiler accepts an extra command line argument "-1.3" or "-1.4" (1.3 compliance being the default).

Problem Reports Fixed

Problem Reports Closed

Eclipse Platform Build Notes 
Java Development Tooling Core

What's new in this drop

Problem Reports Fixed

Problem Reports Closed

Eclipse Platform Build Notes 
Java Development Tooling Core

What's new in this drop

• Java element deltas are batched. If the java model operation modifies a resource, then the java element deltas are merged and fired during the resource delta processing. If the java model operation doesn't modify any resource (e.g. IWorkingCopy.reconcile()), then the java element delta is fired right away.

Problem Reports Fixed

Problem Reports Closed

Eclipse Platform Build Notes 
Java Development Tooling Core

What's new in this drop

Problem Reports Fixed

Problem Reports Closed

Eclipse Platform Build Notes 
Java Development Tooling Core

What's new in this drop

• New incremental builder implementation enabled by default (can reenable the old implementation by changing the builder extension in the plugin.xml)
• Delta processing improvement:
  • No longer creates unnecessary Java elements when traversing the resource delta.
  • Handles changes in binary folder libraries.
  • Projects that share libraries are notified individually.
  • Doesn't notify empty deltas any longer.
• Source folder resource copying no longer perfom any copies as soon as one source folder coincidates with the output location.
• Open on selection is more fault-tolerant: will now try to locate a selected method for which argument types are incorrect.
• Compiler no longer rejects correct code with respect to access to protected members defined in enclosing types (was only accepting a subset of correct scenarii).

Problem Reports Fixed

Problem Reports Closed

Eclipse Platform Build Notes 
Java Development Tooling Core

What's new in this drop

• Better highlighting of multi-line message sending
• Code assist only qualifies implicit members when necessary
• New API for setting both classpath and output location at the same time (allowing to avoid classpath validation failures in case there is no way to change both independantly):

IJavaProject.setRawClasspath(IClasspathEntry[] newClasspath, IPath newOutputLocation, IProgressMonitor monitor)

Problem Reports Fixed

Problem Reports Closed

Eclipse Platform Build Notes 
Java Development Tooling Core

What's new in this drop

• CodeAssist no longer find synthetic completions.
• Reduced startup time of Java perspective
• CodeAssist option added to force full qualification of implicit field/method references (see JavaCore option: "org.eclipse.jdt.core.codeComplete.forceImplicitQualification").

Problem Reports Fixed

Problem Reports Closed

Eclipse Platform Build Notes 
Java Development Tooling Core

What's new in this drop

Problem Reports Fixed

Problem Reports Closed

Eclipse Platform Build Notes 
Java Development Tooling Core

What's new in this drop

• Project references are maintained by the JavaCore, in parallel with build path.
• Resurrected deprecated APIs from 0.9 which were discarded previously.
• ICodeCompletion reverted to 1.0 version, and got deprecated. Use ICompletionRequestor instead.
• Cross-project incremental recompilation in presence of structural changes in produced binaries.

Problem Reports Fixed

Problem Reports Closed

Eclipse Platform Build Notes 
Java Development Tooling Core

What's new in this drop

• JavaModel is no longer performing smart classpath updates when Java package fragment roots are either moved or removed.

Problem Reports Fixed

Problem Reports Closed

Eclipse Platform Build Notes 
Java Development Tooling Core

What's new in this drop

• CodeAssist provides variable name suggestions.

    (breaking) API Changes on ICompletionRequestor
    + Added API for suggest variable name:
      void acceptVariableName(
          char[] typePackageName,
          char[] typeName,
          char[] name,
          char[] completionName,
          int completionStart,
          int completionEnd);
 
• Helper method for computing a resolved and expanded path (all exports from prerequisites) which was introduced in 204, got removed. This is not an API change, it never made it out officially.

   - IJavaProject.getExpandedClasspath(boolean)

SearchEngine.createJavaSearchScope(IResource[]) has been deprecated. Use SearchEngine.createJavaSearchScope(IJavaElement[]) instead. The rational is that createJavaSearchScope(IResource[]) was not well defined for projects, and it could not define a search scope for java elements that didn't have a corresponding resource (e.g. external jars). This deprecated API's behavior has also reverted to the 1.0 state for backward compatibility. The specification of createJavaSearchScope(IJavaElement[]) is as follows:

• If an element is an IJavaProject, then the project's source folders, its jars (external and internal) and its references projects (with their source folders and jars, recursively) will be included.
• If an element is an IPackageFragmentRoot, then only the package fragments of this package fragment root will be included.
• If an element is an IPackageFragment, then only the compilation unit and class files of this package fragment will be included. Subpackages will NOT be included.

Problem Reports Fixed

Problem Reports Closed

Eclipse Platform Build Notes 
Java Development Tooling Core

What's new in this drop

• Classpath entries (except for source folders) can be tagged as exported upon creation. When exported, an entry is contributed to dependent projects along with its output location.
• Added APIs:

    Testing status of a given entry
     + IClasspathEntry.isExported()

            Helper method computing a resolved and expanded path (all exports from prerequisites)
             + IJavaProject.getExpandedClasspath(boolean)

• CodeAssist inserts qualification on field/method references in case of ambiguities.
• CodeAssist provides parameter names on method completions.

    API Changes on ICompletionRequestor
   + Added API for answering method declaration completions:
      void acceptMethodDeclaration(
          char[] declaringTypePackageName,
          char[] declaringTypeName,
          char[] selector,
          char[][] parameterPackageNames,
          char[][] parameterTypeNames,
          char[][] parameterNames,
          char[] returnTypePackageName,
          char[] returnTypeName,
          char[] completionName,
          int modifiers,
          int completionStart,
          int completionEnd);
    + Added parameterNames to normal method results API:
      void acceptMethod(
          char[] declaringTypePackageName,
          char[] declaringTypeName,
          char[] selector,
          char[][] parameterPackageNames,
          char[][] parameterTypeNames,
          char[][] parameterNames,<<<<<<<<<<<<<<<< ADDED
          char[] returnTypePackageName,
          char[] returnTypeName,
          char[] completionName,
          int modifiers,
          int completionStart,
          int completionEnd);
 
• CodeAssist optionally performs visibility checks (see JavaCore option: "org.eclipse.jdt.core.codeComplete.visibilityCheck").
• Search for field read and field write references. Two new constants have been added

    on IJavaSearchConstants to be used when creating a field reference search pattern:
    - READ_REFERENCES: the search results contain *only* read access to a field.
    - WRITE_REFERENCES: the search results contain *only* write access to a field.
    Note that if REFERENCES is used, then search results contain both read and write
    accesss to a field.
• OpenOnSelection can now locate selected declarations which have a corresponding

    Java element (i.e. no local declaration is found), and is more tolerant of
    incorrect code.

Problem Reports Fixed

Problem Reports Closed

Eclipse Platform Build Notes 
Java Development Tooling Core

What's new in this drop

• New AST node for empty statements (org.eclipse.jdt.internal.compiler.ast.EmptyStatement)

   i.e. 2 more APIs on the AST visitor. Note: this was not an official API
• ISourceElementRequestor notifies enter/exit initializers instead of just acceptInitializer. Note: this was not an official API
• Search in inner-classes now works. Indexes are recomputed automatically on start-up.
•   Removed CodeAssist option for hungry mode (org.eclipse.jdt.core.codeComplete.entireWordReplacement)

   Client code can decide whether using inferred end position (hungry behavior) or original cursor location (insert behavior)
   based on the keystroke (enter/insert?).
•   org.eclipse.jdt.core.search.IJavaSearchResultCollector now clearly states that

    the order of the search result is unspecified.

Problem reports fixed

Problem Reports Closed

Eclipse Platform Build Notes 
Java Development Tooling Core

What is new in this drop

• JCK1.3a compliant.
• Added 2 new APIs on JavaConventions for classpath validation.
• IJavaModelStatus validateClasspath(IJavaProject project, IClasspathEntry[] classpath, IPath outputLocation)
• IJavaModelStatus validateClasspathEntry(IJavaProject project, IClasspathEntry entry, boolean checkSourceAttachment)
• Ant Eclipse compiler task added (org.eclipse.jdt.core.ant.Jdtcom)
• Assertions support enabled: by default the compiler is 1.3 compliant, but it can optionally be turned into source 1.4 mode cf. JavaCore options.
• More options are surfaced on JavaCore. See JavaCore.getDefaultOptions() for description.
• ...internal...ConfigurableOption has disappeared.
• Evaluation in binaries is functional
• Search for references now finds results in binaries. Indexes in old workspaces are recomputed when restarted which may result in longer startup times.

Problem Reports Fixed