Initial Maven Setup Sample Clauses

Initial Maven Setup. The first thing to do is to create the POM file for your project. This will allow Xxxxx to build it. A complete POM example (the POG) can be found in Sec- tion A.1. The main elements of a POM are: parent group: this identifies the super package where your plugin will go. artifactID: this identifies the main package of your plugin dependencies: one of the more important groups. You will typically want the core COMPASS libraries and possibly the Overture ones as well. You should also add anything else that your plugin may require. See Listing 1 for an example build: this entry allows you to fine-tune how maven builds your project. For example, you can configure it to ignore test failures and keep building. <dependency> <!-- the group id of the dependency, from its own POM --> <groupId> </groupId> <!-- the id of the dependency as specified in its own POM --> <artifactId> </artifactId> <!-- the specific version of the dependency; variables such as ${project.version} are allowed --> <version> </version> </dependency> , \z r Listing 1: A maven dependency entry. If you want your plugin to be usable in the COMPASS Eclipse IDE you have to register it with the IDE core. In order to do this, you must edit the POM for eu.compass.research.ide.cml.core and add the following entry inside <artifactItems>: <artifactItem> <groupId> </groupId> <artifactId> </artifactId> <version>${project.version}</version> <type>jar</type> <overWrite>true</overWrite> <!-- <destFileName>optional-new-name.jar</destFileName> --> </artifactItem> , \z r Listing 2: Registering a plugin in the ide core The groupId and artifactId identify your plugin. Once this has been done, the next time you build with maven, a jar for your plugin should be in the lib folder of eu.compass.research.ide.cml.core. As always, add it to the build path.
Sample 1
AutoNDA by SimpleDocs

Related to Initial Maven Setup

  • FTTP Loop A Loop consisting entirely of fiber optic cable, whether dark or lit, that extends from the main distribution frame (or its equivalent) in an end user’s serving End Office to the demarcation point at the end user’s customer premises or to a serving area interface at which the fiber optic cable connects to copper or coaxial distribution facilities that extend to the end user's customer premises demarcation point, provided that all copper or coaxial distribution facilities extending from such serving area interface are not more than 500 feet from the demarcation point at the respective end users' customer premises; provided, however, that in the case of predominantly residential multiple dwelling units (MDUs), an FTTP Loop is a Loop consisting entirely of fiber optic cable, whether dark or lit, that extends from the main distribution frame (or its equivalent) in the End Office that serves the multiunit premises: (a) to or beyond the multiunit premises’ minimum point of entry (MPOE), as defined in 47 C.F.R. § 68.105; or

  • Shipping must be Freight On Board Destination to the delivery location designated on the Customer purchase order The Contractor will retain title and control of all goods until delivery is completed and the Customer has accepted the delivery. All risk of transportation and all related charges are the responsibility of the Contractor. The Customer will notify the Contractor and H-GAC promptly of any damaged goods and will assist the Contractor in arranging for inspection. The Contractor must file all claims for visible or concealed damage. Unless otherwise stated in the Agreement, deliveries must consist only of new and unused merchandise.

  • Post-Stabilization Services The PH-MCO must cover Post-Stabilization Services, as defined in 42 C.F.R. §438.114. The PH-MCO must limit charges to Members for Post-Stabilization Services to an amount no greater than what the PH-MCO would charge the Member if he or she had obtained the services through a Network Provider. The PH-MCO must cover Post-Stabilization Services without authorization, and regardless of whether the Member obtains the services within or outside its Provider Network if any of the following situations exist:

  • OVATIONS FOOD SERVICES, L.P. dba SPECTRA All food and beverage service must be discussed with and approved by Spectra, the OCFEC Master Concessionaire. FORM F-31 AGREEMENT NO. R-026-18 DATE May 16, 2018 REVIEWED APPROVED RENTAL AGREEMENT FAIRTIME INTERIM XX THIS AGREEMENT by and between the 32nd District Agricultural Association dba OC Fair & Event Center, hereinafter called the Association, and B & L Productions, Inc. hereinafter, called the Rentor

  • Provision of Interconnection Financial Security The Interconnection Customer is obligated to provide all necessary Interconnection Financial Security required under Section 11 of the GIDAP in a manner acceptable under Section 11 of the GIDAP. Failure by the Interconnection Customer to timely satisfy the GIDAP’s requirements for the provision of Interconnection Financial Security shall be deemed a breach of this Agreement and a condition of Default of this Agreement.

  • Energy Resource Interconnection Service (ER Interconnection Service).

  • Network Resource Interconnection Service (check if selected)

  • Supervisory Control and Data Acquisition (SCADA) Capability The wind plant shall provide SCADA capability to transmit data and receive instructions from the ISO and/or the Connecting Transmission Owner for the Transmission District to which the wind generating plant will be interconnected, as applicable, to protect system reliability. The Connecting Transmission Owner for the Transmission District to which the wind generating plant will be interconnected and the wind plant Developer shall determine what SCADA information is essential for the proposed wind plant, taking into account the size of the plant and its characteristics, location, and importance in maintaining generation resource adequacy and transmission system reliability in its area.

  • CLEC to CLEC Conversions for Unbundled Loops 2.1.11.1 The CLEC to CLEC conversion process for Loops may be used by ITC^DeltaCom when converting an existing Loop from another CLEC for the same End User. The Loop type being converted must be included in ITC^DeltaCom’s Agreement before requesting a conversion.

  • Scope of Interconnection Service 1.3.1 The NYISO will provide Energy Resource Interconnection Service to Interconnection Customer at the Point of Interconnection.

Time is Money Join Law Insider Premium to draft better contracts faster.