3.1 Automated Configuration for Component Set (Projects) Import

Eclipse configuration files (namely .project, .classpath, but also all files in the .settings folder) are often difficult to manage. While they should be most often part of a project and are intended to be shared between project developers it is sometimes uncertain whether they have to be under source control. It is particularly difficult to handle merge conflicts of these files. In order to address such problems Intershop Studio can now automatically generate these files upon project import.

These files still can be under source control, but they can be re-generated or newly created if they are absent. Additional configuration options are available to handle this process.

Note following additional configuration options:

Import options

• Run before: Select and enter gradle tasks that will be executed before the import process.
• Run after: Select and enter gradle tasks that will be executed after the import process.

Project configuration

• Configuration template: Select the configuration template to apply.

  Note

  This select box will not be shown if you have no custom generation templates configured!

• Clean existing Eclipse configuration: If selected, existing .project, .classpath and files in .settings will be removed and recreated based on the configuration template.
• Overwrite existing Eclipse configuration: If selected already existing files will be overridden.

3.2 Configuration Templates

The Eclipse configuration will be created based on templates that ship with Intershop Studio. In order to use other rules for you project setup, you can provide your own templates. In order to do so you configure them in the preference: Intershop Studio | Cartridge Creation Templates.

Configuration templates have to be present in the folder <templatesFolder>/eclipse_config. Intershop Studio normally uses the files located in /plugins/com.intershop.studio.cartridge_[studioVersion]/templates.zip. It is recommended to create your templates as an adapted version of the generation templates found in: templates.zip\7.6_7.7.

Intershop recommends to follow the steps below:

1. Copy the templates.zip\7.6_7.7.
2. Delete folder default if you only want to create a configuration template.
   The folder default contains the templates that are used to create a new cartridge.

3. Adapt the generator.properties file:

   generator.properties

   name=My Cartridge Project Configuration
   description=Configures my cartridges and projects in my own fine way 

4. Adapt or create your files.
   E.g. .project (This example has an adaption at line 26):

   .project

   <projectDescription>
       <name>${name}</name>
       <comment></comment>
       <projects>
       </projects>
       <buildSpec>
   ${if(isCartridge)}        <buildCommand>
   ${if(isCartridge)}            <name>com.intershop.enfinity.studio.core.beehiveElementBuilder</name>
   ${if(isCartridge)}            <arguments>
   ${if(isCartridge)}            </arguments>
   ${if(isCartridge)}        </buildCommand>
           <buildCommand>
               <name>org.eclipse.jdt.core.javabuilder</name>
               <arguments>
               </arguments>
           </buildCommand>
       </buildSpec>
       <natures>
   ${if(isCartridge)}        <nature>com.intershop.enfinity.studio.core.beehiveNature</nature>
           <nature>org.eclipse.jdt.core.javanature</nature>
   ${if(isAssembly)}        <nature>org.eclipse.jdt.groovy.core.groovyNature</nature>        
   ${if(isCartridge)}        <nature>org.eclipse.wst.common.project.facet.core.nature</nature>
           <nature>org.springsource.ide.eclipse.gradle.core.nature</nature>
   
   		<!-- My customization here: add e.g. a nature -->
   		<nature>aNature.for.my.projects</nature>
       </natures>
   </projectDescription>

5. Adjust the preference for Cartridge Generation Templates according to your modifications.
   Set the new preference in: Window | Preferences | Intershop Studio | Cartridge Generation Templates.

4.1 Gradle Operations View Shows Gradle Tasks

A new view is available that displays Gradle operations. The view displays tasks along with their duration. An icon indicates tasks with messages or errors. Also skipped tasks and JUnit tasks can easily be recognized. Junit task entries can be used to open affected test element as well as the created HTML test report. See the following usage scenario:

1. Open view Gradle Tasks and Gradle Operations.
2. Launch a task (bc_catalog:test).
   
3. Progress and results will be displayed in Console and Gradle Operations view.
   
4. Properties of a selected task:
   
5. Open the Junit view to review results:
   

5.1  Revised Classpath Handling for Cartridge JUnit Test Launcher

The classpath for cartridge JUnit test case launches can now be configured more easily. The launcher will configure different test type accordingly and automatically. Usually there is no customization needed.

Launch Dialog:

If  Add Intershop Suite Server entries is checked the classpath container Intershop Server Class Loader is added:

6.1 Javadoc for all Cartridges in Intershop Studio Help

The Intershop Suite Cartridge API Javadoc help topic now shows a dynamically created list of cartridges to open the Javadoc of cartridges.