An improved project import and the new Gradle Operations view are the key features of the new Intershop Studio based on Eclipse 4.5.2.
2 Eclipse Platform
Intershop Studio 4.5.2 is based on Eclipse 4.5.2 (Mars).
3 Automated Project
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:
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:
4 Gradle Operations View
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:
5 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.
If Add Intershop Suite Server entries is checked the classpath container Intershop Server Class Loader is added:
6 Cartridge Javadoc
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.
Cartridges that do not provide any Javadoc are not listed.
The information provided in the Knowledge Base may not be applicable to all systems and situations. Intershop Communications will not be liable to any party for any direct or indirect damages resulting from the use of the Customer Support section of the Intershop Corporate Web site, including, without limitation, any lost profits, business interruption, loss of programs or other data on your information handling system.