Examples of IClasspathContainer

org.aspectj.org.eclipse.jdt.core.IClasspathContainer
Interface of a classpath container. A classpath container provides a way to indirectly reference a set of classpath entries through a classpath entry of kind CPE_CONTAINER. Typically, a classpath container can be used to describe a complex library composed of multiple JARs or projects, considering also that containers can map to different set of entries on each project, in other words, several projects can reference the same generic container path, but have each of them actually bound to a different container object.
The set of entries associated with a classpath container may contain any of the following:
- library entries (CPE_LIBRARY)
- project entries (CPE_PROJECT)
In particular, a classpath container can neither reference further classpath containers or classpath variables.
Classpath container values are persisted locally to the workspace, but are not preserved from a session to another. It is thus highly recommended to register a ClasspathContainerInitializer for each referenced container (through the extension point "org.aspectj.org.eclipse.jdt.core.ClasspathContainerInitializer").
@see IClasspathEntry @since 2.0
org.eclipse.jdt.core.IClasspathContainer
Interface of a classpath container. A classpath container provides a way to indirectly reference a set of classpath entries through a classpath entry of kind CPE_CONTAINER. Typically, a classpath container can be used to describe a complex library composed of multiple JARs or projects, considering also that containers can map to different set of entries on each project, in other words, several projects can reference the same generic container path, but have each of them actually bound to a different container object.
The set of entries associated with a classpath container may contain any of the following:
- library entries (CPE_LIBRARY)
- project entries (CPE_PROJECT)
In particular, a classpath container can neither reference further classpath containers or classpath variables.
A library entry can reference other libraries through the Class-Path section of the JAR's MANIFEST.MF file. If the container wants such referenced entries to be part of the classpath, the container must explicitly add them to the array returned from {@link #getClasspathEntries()}.
Classpath container values are persisted locally to the workspace, but are not preserved from a session to another. It is thus highly recommended to register a ClasspathContainerInitializer for each referenced container (through the extension point "org.eclipse.jdt.core.ClasspathContainerInitializer").
@see IClasspathEntry @since 2.0

Examples of org.eclipse.jdt.core.IClasspathContainer

      Set<IPath> sourceTargets = new HashSet<IPath>();
      for (int i = 0; i < entries.length; i++) {
        IClasspathEntry entry = entries[i];
        switch (entry.getEntryKind()) {
          case IClasspathEntry.CPE_CONTAINER:
            IClasspathContainer container = JavaCore.getClasspathContainer(entry.getPath(), project);
            if (container != null) {
              switch (container.getKind()) {
                case IClasspathContainer.K_DEFAULT_SYSTEM:
//                  classpathEntries.add(JavaRuntime.newRuntimeContainerClasspathEntry(container.getPath(), IRuntimeClasspathEntry.STANDARD_CLASSES, project));
                  break;
                default:
                  classpathEntries.add(JavaRuntime.newRuntimeContainerClasspathEntry(container.getPath(), IRuntimeClasspathEntry.USER_CLASSES, project));
                  break;
              }
            }
            break;
          case IClasspathEntry.CPE_LIBRARY:

View Full Code Here

0 1 2 3 4 5

TOP

All source code are property of their respective owners. Java is a trademark of Sun Microsystems, Inc and owned by ORACLE Inc. Contact coftware#gmail.com.