Hello Tetiana,

That helped, at least i get no more errors by resolving dependencies. But in the IntelliJ Community Edition editor i get the following message:

"can not resolve symbol". The words "BasicIssueKey" and "exalate" are highligted in the following code snippet:

static BasicIssueKey execute(
//entities
com.exalate.basic.domain.hubobject.v1.BasicHubIssue replica,
com.exalate.basic.domain.hubobject.v1.BasicHubIssue issue,
//helpers
.....

Is this a problem of IntelliJ settings ?

Cheers
Adrian Suter

----------------------------------------------------------------------------------------------------

Hey, 
using jiranode 4.6.10-j7 should fix a problem.

<dependency>
 <groupId>com.exalate</groupId>
 <artifactId>jiranode</artifactId>
 <version>4.6.10-j7</version>
 <scope>provided</scope>
</dependency>

Let me know if it helps. I'll ask to update a doc page.

Best regards, 

Tetiana

----------------------------------------------------------------------------------------------------

I tried to setup an environment according the article https://docs.idalko.com/exalate/display/ED/How+to+set+up+advanced+scripting+environment.I always get dependency errors even i changed some version values in the pom.xml file.
Unforutnately i'm not a real software develeoper and it would help if you had an example wich workswith the version im working with: Jira Server 8.13 and Exalate 5.0.4-j8 .
Enclosing you find the error message and the pom.xml file.

Thanks for help
Adrian Suter

pom.xml

[ERROR] Failed to execute goal on project externalized-scripts-example: Could not resolve dependencies for project com.exalate:externalized-scripts-example:jar:0.1.0: Failure to find com.
exalate:jiranode:jar:4.2.5-j7 in https://maven.atlassian.com/repository/public was cached in the local repository, resolution will not be reattempted until the update interval of atlassia
n-public has elapsed or updates are forced -> [Help 1]
[ERROR]