Skip to main content

Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Search results

Page title matches

Page text matches

  • ...us of the [http://www.eclipse.org/linuxtools/ Linux Distros] project is on packaging and distributing Eclipse technology in Linux distributions. In the context Buckminster has four types of meta-data. Two that controls behavior (one for the resolver and one for
    9 KB (1,284 words) - 14:18, 1 October 2007
  • <td>Provide tooling for packaging SDD descriptors and artifacts</td> <td>Resolution should examine the model to check for previously resolved types</td>
    12 KB (1,949 words) - 10:03, 1 April 2009
  • * Packaging: JAR A list of types and the setting handler classes that support them:
    4 KB (545 words) - 10:35, 15 December 2008
  • ...er, components can be many things, but one of the most important component types is Eclipse projects. ...ource map contains a component index and location descriptions (repository types and addresses). Buckminster looks up the component index which points to a
    43 KB (7,063 words) - 10:24, 18 January 2008
  • ...along many dimensions - location, version, fastest mirror, version range, packaging type, deployment target, release cycle status, etc. At the most basic level ...er allows to introduce custom handling of physical or conceptual component types whereas the latter deals with ensuring correct access, retrieval and interp
    13 KB (1,925 words) - 09:30, 22 June 2007
  • ...er, components can be many things, but one of the most important component types is Eclipse projects. ...ource map contains a component index and location descriptions (repository types and addresses). Buckminster looks up the component index which points to a
    46 KB (7,380 words) - 21:48, 23 April 2011
  • ...along many dimensions - location, version, fastest mirror, version range, packaging type, deployment target, release cycle status, etc. At the most basic level ...er allows to introduce custom handling of physical or conceptual component types whereas the latter deals with ensuring correct access, retrieval and interp
    13 KB (1,925 words) - 20:39, 14 February 2009
  • *Use of the Eclipse Packaging Project to offer additional role-based packages (such as Web Development ki ##Public wrapper APIs for specific module types (e.g. IWebProject,IEnterpriseApplication, WebApp)[https://bugs.eclipse.org/
    31 KB (4,526 words) - 17:39, 25 June 2008
  • ...pport building from multiple repositories.</ref>, and there are three main types of build: nightly, release, and maint. The jobs for each build type are lin === EPP Eclipse Packaging Project ===
    9 KB (1,552 words) - 10:31, 10 November 2014
  • * How do we publish our packaging for the CMDBf Use Case? * What can we do to ensure that adopters of ALL types derive immediate value?
    8 KB (1,132 words) - 09:37, 28 January 2008
  • ...basic ways in which you can use EclipseLink, including the following usage types: ...Link to persist Java objects to relational databases that support SQL data types accessed using JDBC.
    110 KB (15,926 words) - 11:20, 18 July 2012
  • [[Special:Whatlinkshere/Packaging a EclipseLink Application (ELUG)|Related Topics]]</div>How you package the ...fic details applicable to the common packaging strategies used for various types of applications.
    9 KB (1,263 words) - 11:21, 18 July 2012
  • *[[Packaging a EclipseLink Application (ELUG)|Packaging an EclipseLink Application]] – explains how to package the deployment fil ...EclipseLink Application]] – provides procedures for deploying different types of EclipseLink applications in a variety of environments.
    1 KB (139 words) - 15:59, 21 December 2007
  • * [[Packaging%20a%20EclipseLink%20Application%20(ELUG)|Packaging a EclipseLink Application]] ...ommon operations. You need only grant certain permissions depending on the types of optional EclipseLink features you use.
    45 KB (6,382 words) - 11:21, 18 July 2012
  • ...eLink information that you need when creating deployment files for various types of applications. For more information on packaging and deployment, see the following:
    32 KB (4,766 words) - 11:21, 18 July 2012
  • ...ners and other non-EJB 3.0 Java EE containers. For more information, see [[Packaging%20and%20Deploying%20EclipseLink%20JPA%20Applications%20(ELUG)#Deploying an ...lass (usually made up of two or more primitive, JDK object types or Entity types) for an entity or MappedSuperclass.
    123 KB (17,768 words) - 17:30, 30 January 2015
  • ...requirements and data access strategies. You can combine different session types in the same application. ==Session Types==
    96 KB (14,065 words) - 16:57, 16 December 2013
  • ...open and you will need to fill in some basic maven metadata. The selected packaging will determine how the conversion will be performed : The projects types for which m2e-wtp provides conversion capabilities are :
    4 KB (553 words) - 06:52, 27 September 2012
  • [[Special:Whatlinkshere/Packaging and Deploying EclipseLink JPA Applications (ELUG)|Related Topics]]</div> ==Packaging an EclipseLink JPA Application==
    19 KB (2,873 words) - 11:23, 18 July 2012
  • == Types of Changes == ...atible with JPA 1.0. The scope of its work will involve changes of various types with different effects on EclipseLink.
    14 KB (1,945 words) - 14:54, 24 October 2011

View (previous 20 | next 20) (20 | 50 | 100 | 250 | 500)

Back to the top