Silk4J project fails to compile when executed from Silk Central Connect
When attempting to execute my Silk4J project from Silk Central Connect, the status message "Not Executed" is displayed almost immediately, as shown below:
To determine why the Silk4J project failed to execute, click the magnifying icon:
Then click the browser icon with the warning icon to view the reason why the Silk4J project failed to execute:
Which then reveals the following failures:
When we look at the [javac] messages in the above screenshot, we can see a number of "cannot be resolved" errors were thrown when attempting to build the Silk4J project. Errors such as these indicate that the Silk4J project in question uses additional or 3rd party libraries, that have likely been added to the "Build Path" within Eclipse which allows Eclipse to build the project successfully.
When using additional libraries with a Silk4J project that is integrated with Silk Central Connect, we must import the additional libraries to the "lib" project folder. To do this:
- Right click on the lib folder and select "Import..."
- On the "Import" dialog, select General -> File System
- Click the "Browse" button and navigate to the directory that contains your additional libraries
- Check the additional libraries that must be imported for your project to build successfully
- Press Finish and confirm that the lib folder of your project now contains the additional library
- Commit the changes to Silk Central Connect
- Right Click on your Silk4J project
- Select Team -> Commit
If we now execute our Silk4J project from Silk Central Connect no further build errors will be received.