Article - CS259867
ThingWorx Eclipse Plugin SDK Location within team development process
Modified: 01-Mar-2018
Applies To
- ThingWorx Platform 7.2
Description
- To create a ThingWorx extension in eclipseWorkspace (File -> New ThingWorx Extension Project), the extension SDK path has to be added in order to press the Finish button, and then a folder is created
- Checking the code for extension.properties in the created folder, the code line sdk_location equals the location of the path mentioned above
- If some of these files are missing and are imported in Eclipse, the properties in Eclipse can't be changed
- Each team member having its own path and setups, and different OS (operating systems) (e.g. Linux, Windows), the absolute path in directories like .settings or files like metadata.xml or extensions.properties or com.thingworx.exlipse.extension.ui.prefs are not checked with regularity
- If more developers work on the same project, but from different OS machines, one of the OS wouldn't understand reading a path format from another type of OS
- Is it possible to include the extension SDK zip file, within the project workspace, in order to not need to add an absolute path in the field SDK Location of Properties for Server Extension? (example: .\<folder_name>.zip)
This is a printer-friendly version of Article 259867 and may be out of date. For the latest version click CS259867