Examples of IErlProject

• org.erlide.engine.model.root.IErlProject
  An Erlang project represents a view of a project resource in terms of Erlang elements such as applications, modules, attributes and functions. A project may contain several applications, which contain modules. An application corresponds to an underlying folder.

  Each Erlang project has a code path, defining which folders contain source code and where required libraries are located. Each Erlang project also has an output location, defining where the builder writes .beam files. A project that references modules in another project can access the modules by including the required project in a code path entry. The Erlang model will present the source elements in the required project; when building, the compiler will use the corresponding generated beam files from the required project's output location(s). The code path format is a sequence of code path entries describing the location and contents of applications.

  Erlang project elements need to be opened before they can be navigated or manipulated. The children of a Erlang project are the package fragment roots that are defined by the classpath and contained in this project (in other words, it does not include package fragment roots for other projects).

  @noimplement This interface is not intended to be implemented by clients. Aninstance of one of these handles can be created via ErlangCore.create(project).

  @see ErlangCore#createRoot(org.eclipse.core.resources.IProject)
• org.erlide.engine.new_model.IErlProject

Examples of org.erlide.engine.model.root.IErlProject

Examples of org.erlide.engine.new_model.IErlProject