You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
The dependencies jndi:jndi:1.2.1 and jta:jta:1.0.1 are not available within the central maven or the atlassian repos. Those missing libraries are available within a regular Confluence/Jira where the plugin might be deployed to but not within the development instance which is created using Maven during the build. Those missing dependencies can cause debugging-problems.
To Reproduce
Steps to reproduce the behavior:
Start the maven goal jira:run in IntelliJ
Within the Run tab wait until the run step shows error messages about not finding those deps
Expected behavior
No missing dependencies.
Screenshots
The text was updated successfully, but these errors were encountered:
@sjahreis I just created a fresh project from the new archetype version 3.3.0.
I imported it into IntelliJ and started the jira:debug run configuration.
I don't get these errors anymore. Maybe this problem is resolved by now? We had some Jira upgrades and also AMPS upgrade.
Describe the bug
The dependencies
jndi:jndi:1.2.1
andjta:jta:1.0.1
are not available within the central maven or the atlassian repos. Those missing libraries are available within a regular Confluence/Jira where the plugin might be deployed to but not within the development instance which is created using Maven during the build. Those missing dependencies can cause debugging-problems.To Reproduce
Steps to reproduce the behavior:
Expected behavior
No missing dependencies.
Screenshots
The text was updated successfully, but these errors were encountered: