Unable to execute Mojo: ResourceDocletJSON?

[Jake Joseph]

Has Anyone seen this before? I can't do atlas-run or atlas-debug, this error keeps popping up.

[INFO] Unable to execute mojo

Embedded error: An error has occurred in JavaDocs report generation:Exit code: 1 - javadoc: error - Cannot find doclet class com.sun.jersey.wadl.resourcedoc.ResourceDocletJSON

[Aseem Parikh · Accepted solution]

This error was killing me but I finally figured it out. Very little documentation on the web about this error.

You need to add a dependency on the atlassian-rest-doclet artifact:

<dependency>
            <groupId>com.atlassian.plugins.rest</groupId>
            <artifactId>atlassian-rest-doclet</artifactId>
            <version>2.0.1</version>
        </dependency>

[Nahn Yanootz]

I had the above error, then added the dependency you mentioned, and the error went away.

But other errors showed up, as I mentioned in my question: https://answers.atlassian.com/questions/203177/errors-building-packaging-jira-issue-nav-plugin-from-source-jira-6

To fix it, Joseph Clark's link to the bug report helped me out.

Instead, I added the following, and it worked:

<dependency>
    <groupId>com.atlassian.plugins.rest</groupId>
    <artifactId>atlassian-rest-doclet</artifactId>
    <version>2.5.0</version>
    <scope>provided</scope>
</dependency>

The thing that made the difference was:

<scope>provided</scope>

[tousifs]

Hi ,

please check your java it should be jdk 1.6 and also check the jre for the same version

if we are implementing the java higher than 1.6 then 32 dependancy are missing. if the same problem persist you can clean and run again it should work.

[Joe Clark]

This was reported as a bug a while back and is supposed to be fixed now... what version of the Plugin SDK are you using?

[Aseem Parikh]

Using the latest as far as I know. Version 3.11

[Joe Clark]

Here's the bug report - https://ecosystem.atlassian.net/browse/AMPS-663 It's supposed to be fixed in 3.7.3. :-(

[EddieW]

I had been build a project for days fine, and then I started working through the admin page - https://developer.atlassian.com/display/DOCS/Plugin+tutorial+-+Writing+an+Admin+Configuration+Screen and this issue cropped up - think sometime around adding the backend REST service, or the config object.

[Joe Clark]

Yes... I think it is related to having a <rest> module in your plugin.

[EddieW]

It seems it is related to using the <package> element in my rest component. The trouble is that I expose to rest services (one for anon. use, ther other for admin operations) and I need to be explicit about wich classes are tied to each. The documentation for the rest component doesnt really discuss.

[EddieW]

It seems it is related to using the <package> element in my rest component. The trouble is that I expose to rest services (one for anon. use, ther other for admin operations) and at first I tried to have multipel <rest modules with distinct <paclage elements.
That was foolish on my part, and after using a single rest modeul, no package delcartion and leaving indivudals packages to declare the approprioate /admin or /summary contexts evertyhgin is working again.