Create
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Products
See all
Community resources
Top groups
Explore all groups
Community resources
Learn
Community resources
Events
Community resources

JavaDoc error building JIRA 5.2 from source

Wayne Mabey
Wayne Mabey November 18, 2012

I've hit an odd Javadoc error while trying to build JIRA 5.2 from the source code. I've had the same error with both Java 1.6 and 1.7, so I don't think that's the problem. The file not found message seems to indicate a corrupted path name, but the path is fine in other messages in the stream. It occurs while building the JIRA Admin Helper plugin:

[INFO] Scanning for projects...
[INFO] ------------------------------------------------------------------------
[INFO] Building Atlassian JIRA - Admin Helper Plugin
[INFO]    task-segment: [clean, install]
[INFO] ------------------------------------------------------------------------
[INFO] [clean:clean]
[INFO] Deleting C:\atlassian-jira-5.2-source\jira-admin-helper-plugin\target
[INFO] [jira:copy-bundled-dependencies]
[INFO] [dependency:copy-dependencies]
[INFO] [jira:compress-resources]
[INFO] [yuicompressor:compress]
[INFO] IssuePicker.js (1491b) -> IssuePicker-min.js (645b)[43%]
[INFO] notification-helper-dialog.js (4163b) -> notification-helper-dialog-min.js (2334b)[56%]
[INFO] notification-helper-nav.js (2022b) -> notification-helper-nav-min.js (1029b)[50%]
[INFO] notification-helper-ui.js (12517b) -> notification-helper-ui-min.js (5190b)[41%]
[INFO] notification-helper.js (1800b) -> notification-helper-min.js (1126b)[62%]
[INFO] permission-helper-dialog.js (4228b) -> permission-helper-dialog-min.js (2331b)[55%]
[INFO] permission-helper-nav.js (1985b) -> permission-helper-nav-min.js (1008b)[50%]
[INFO] permission-helper-ui.js (12249b) -> permission-helper-ui-min.js (5005b)[40%]
[INFO] permission-helper.js (1697b) -> permission-helper-min.js (1034b)[60%]
[INFO] whereismycf-dialog.js (10274b) -> whereismycf-dialog-min.js (5023b)[48%]
[INFO] whereismycf.js (3201b) -> whereismycf-min.js (1637b)[51%]
[INFO] total input (55627b) -> output (26362b)[47%]
[INFO] nb warnings: 0, nb errors: 0
[INFO] [resources:resources]
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 22 resources
[INFO] [jira:filter-plugin-descriptor]
[INFO] [resources:copy-resources {execution: virtual-execution}]
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 1 resource
[INFO] [compiler:compile]
[INFO] Compiling 107 source files to C:\atlassian-jira-5.2-source\jira-admin-helper-plugin\target\classes
[INFO] [compiler:compile {execution: compile}]
[INFO] Nothing to compile - all classes are up to date
[INFO] [jira:generate-manifest]
[WARNING] Atlassian plugin detected as the organisation name includes the string 'Atlassian'.  If this is meant for production, you should a
dd bundle instructions specifically configuring what packages are imported and exported.  This helps catch manifest generation bugs during t
he build rather than upon install.  The bundle generation configuration can be specified via the <instructions> element in the maven-jira-pl
ugin configuration.  For example:
    <configuration>
        <Import-Package>
            com.atlassian.myplugin*,
            com.library.optional.*;resolution:=optional,
            *
        </Import-Package>
    </configuration>

See the Maven bundle plugin (which is used under the covers) for more info: http://felix.apache.org/site/apache-felix-maven-bundle-plugin-bn
d.html#ApacheFelixMavenBundlePlugin%28BND%29-Instructions
[INFO] [jira:generate-rest-docs]
[INFO] Setting property: classpath.resource.loader.class => 'org.codehaus.plexus.velocity.ContextClassLoaderResourceLoader'.
[INFO] Setting property: velocimacro.messages.on => 'false'.
[INFO] Setting property: resource.loader => 'classpath'.
[INFO] Setting property: resource.manager.logwhenfound => 'false'.
[INFO] **************************************************************
[INFO] Starting Jakarta Velocity v1.4
[INFO] RuntimeInstance initializing.
[INFO] Default Properties File: org\apache\velocity\runtime\defaults\velocity.properties
[INFO] Default ResourceManager initializing. (class org.apache.velocity.runtime.resource.ResourceManagerImpl)
[INFO] Resource Loader Instantiated: org.codehaus.plexus.velocity.ContextClassLoaderResourceLoader
[INFO] ClasspathResourceLoader : initialization starting.
[INFO] ClasspathResourceLoader : initialization complete.
[INFO] ResourceCache : initialized. (class org.apache.velocity.runtime.resource.ResourceCacheImpl)
[INFO] Default ResourceManager initialization complete.
[INFO] Loaded System Directive: org.apache.velocity.runtime.directive.Literal
[INFO] Loaded System Directive: org.apache.velocity.runtime.directive.Macro
[INFO] Loaded System Directive: org.apache.velocity.runtime.directive.Parse
[INFO] Loaded System Directive: org.apache.velocity.runtime.directive.Include
[INFO] Loaded System Directive: org.apache.velocity.runtime.directive.Foreach
[INFO] Created: 20 parsers.
[INFO] Velocimacro : initialization starting.
[INFO] Velocimacro : adding VMs from VM library template : VM_global_library.vm
[ERROR] ResourceManager : unable to find resource 'VM_global_library.vm' in any resource loader.
[INFO] Velocimacro : error using  VM library template VM_global_library.vm : org.apache.velocity.exception.ResourceNotFoundException: Unable
 to find resource 'VM_global_library.vm'
[INFO] Velocimacro :  VM library template macro registration complete.
[INFO] Velocimacro : allowInline = true : VMs can be defined inline in templates
[INFO] Velocimacro : allowInlineToOverride = false : VMs defined inline may NOT replace previous VM definitions
[INFO] Velocimacro : allowInlineLocal = false : VMs defined inline will be  global in scope if allowed.
[INFO] Velocimacro : initialization complete.
[INFO] Velocity successfully started.
[INFO] [javadoc:javadoc]
Loading source file C:/atlassian-jira-5.2-source/jira-admin-helper-plugin/src/main/java/com/atlassian/jira/customfieldhelper/rest/DefaultFie
ldInfoRequestUserValidator.java...
Loading source file C:/atlassian-jira-5.2-source/jira-admin-helper-plugin/src/main/java/com/atlassian/jira/customfieldhelper/rest/DefaultFie
ldInspectionContextFactory.java...
Loading source file C:/atlassian-jira-5.2-source/jira-admin-helper-plugin/src/main/java/com/atlassian/jira/customfieldhelper/rest/DefaultIns
pectorFactory.java...
Loading source file C:/atlassian-jira-5.2-source/jira-admin-helper-plugin/src/main/java/com/atlassian/jira/customfieldhelper/rest/FieldInfoJ
son.java...
Loading source file C:/atlassian-jira-5.2-source/jira-admin-helper-plugin/src/main/java/com/atlassian/jira/customfieldhelper/rest/FieldInfoR
equestUserValidator.java...
Loading source file C:/atlassian-jira-5.2-source/jira-admin-helper-plugin/src/main/java/com/atlassian/jira/customfieldhelper/rest/FieldInfoR
esource.java...
Loading source file C:/atlassian-jira-5.2-source/jira-admin-helper-plugin/src/main/java/com/atlassian/jira/customfieldhelper/rest/FieldInspe
ctionContextFactory.java...
Loading source file C:/atlassian-jira-5.2-source/jira-admin-helper-plugin/src/main/java/com/atlassian/jira/customfieldhelper/rest/InspectorF
actory.java...
Loading source file C:/atlassian-jira-5.2-source/jira-admin-helper-plugin/src/main/java/com/atlassian/jira/customfieldhelper/rest/InvalidReq
uestException.java...
Loading source file C:/atlassian-jira-5.2-source/jira-admin-helper-plugin/src/main/java/com/atlassian/jira/customfieldhelper/rest/InvalidReq
uestExceptionFactory.java...
Loading source file C:/atlassian-jira-5.2-source/jira-admin-helper-plugin/src/main/java/com/atlassian/jira/customfieldhelper/rest/Notificati
onInfoJson.java...
Loading source file C:/atlassian-jira-5.2-source/jira-admin-helper-plugin/src/main/java/com/atlassian/jira/customfieldhelper/rest/Notificati
onInspectors.java...
Loading source file C:/atlassian-jira-5.2-source/jira-admin-helper-plugin/src/main/java/com/atlassian/jira/customfieldhelper/rest/Notificati
onsResource.java...
Loading source file C:/atlassian-jira-5.2-source/jira-admin-helper-plugin/src/main/java/com/atlassian/jira/customfieldhelper/rest/Permission
GroupRepresentation.java...
Loading source file C:/atlassian-jira-5.2-source/jira-admin-helper-plugin/src/main/java/com/atlassian/jira/customfieldhelper/rest/Permission
InfoJson.java...
Loading source file C:/atlassian-jira-5.2-source/jira-admin-helper-plugin/src/main/java/com/atlassian/jira/customfieldhelper/rest/Permission
Inspectors.java...
Loading source file C:/atlassian-jira-5.2-source/jira-admin-helper-plugin/src/main/java/com/atlassian/jira/customfieldhelper/rest/Permission
Representation.java...
Loading source file C:/atlassian-jira-5.2-source/jira-admin-helper-plugin/src/main/java/com/atlassian/jira/customfieldhelper/rest/Permission
sResource.java...
Loading source file C:/atlassian-jira-5.2-source/jira-admin-helper-plugin/src/main/java/com/atlassian/jira/customfieldhelper/rest/RestValida
tionHelper.java...
Loading source file C:/atlassian-jira-5.2-source/jira-admin-helper-plugin/src/main/java/com/atlassian/jira/customfieldhelper/rest/StatusProc
essor.java...
Constructing Javadoc information...
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Unable to execute mojo

Embedded error: An error has occurred in JavaDocs report generation:Exit code: 1 - Nov 19, 2012 9:29:22 AM com.sun.jersey.wadl.resourcedoc.R
esourceDocletJSON start
SEVERE: Could not serialize ResourceDoc.
java.io.FileNotFoundException: C:tlassian-jira-5.2-sourcejira-admin-helper-plugin       argetclasses
esourcedoc.xml (The filename, directory name, or volume label syntax is incorrect)
        at java.io.FileOutputStream.open(Native Method)
        at java.io.FileOutputStream.<init>(FileOutputStream.java:194)
        at java.io.FileOutputStream.<init>(FileOutputStream.java:84)
        at com.sun.jersey.wadl.resourcedoc.ResourceDocletJSON.start(ResourceDocletJSON.java:199)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:597)
        at com.sun.tools.javadoc.DocletInvoker.invoke(DocletInvoker.java:269)
        at com.sun.tools.javadoc.DocletInvoker.start(DocletInvoker.java:143)
        at com.sun.tools.javadoc.Start.parseAndExecute(Start.java:340)
        at com.sun.tools.javadoc.Start.begin(Start.java:128)
        at com.sun.tools.javadoc.Main.execute(Main.java:41)
        at com.sun.tools.javadoc.Main.main(Main.java:31)

Command line was:"C:\Program Files (x86)\Java\jdk1.6.0_26\jre\..\bin\javadoc.exe" -J-Xmx1024m @options @argfile
[INFO] ------------------------------------------------------------------------
[INFO] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Unable to execute mojo
        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:703)
        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:540)
        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:519)
        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:371)
        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:332)
        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:181)
        at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:356)
        at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:137)
        at org.apache.maven.cli.MavenCli.main(MavenCli.java:356)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:597)
        at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
        at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
        at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
        at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: org.apache.maven.plugin.MojoExecutionException: Unable to execute mojo
        at org.twdata.maven.mojoexecutor.MojoExecutor.executeMojoImpl(MojoExecutor.java:122)
        at org.twdata.maven.mojoexecutor.MojoExecutor$ExecutionEnvironmentM2.executeMojo(MojoExecutor.java:403)
        at org.twdata.maven.mojoexecutor.MojoExecutor.executeMojo(MojoExecutor.java:74)
        at com.atlassian.maven.plugins.amps.MavenGoals.generateRestDocs(MavenGoals.java:1045)
        at com.atlassian.maven.plugins.amps.GenerateRestDocsMojo.execute(GenerateRestDocsMojo.java:20)
        at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:483)
        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:678)
        ... 16 more
Caused by: org.apache.maven.plugin.MojoExecutionException: An error has occurred in JavaDocs report generation:Exit code: 1 - Nov 19, 2012 9
:29:22 AM com.sun.jersey.wadl.resourcedoc.ResourceDocletJSON start
SEVERE: Could not serialize ResourceDoc.
java.io.FileNotFoundException: C:tlassian-jira-5.2-sourcejira-admin-helper-plugin       argetclasses
esourcedoc.xml (The filename, directory name, or volume label syntax is incorrect)
        at java.io.FileOutputStream.open(Native Method)
        at java.io.FileOutputStream.<init>(FileOutputStream.java:194)
        at java.io.FileOutputStream.<init>(FileOutputStream.java:84)
        at com.sun.jersey.wadl.resourcedoc.ResourceDocletJSON.start(ResourceDocletJSON.java:199)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:597)
        at com.sun.tools.javadoc.DocletInvoker.invoke(DocletInvoker.java:269)
        at com.sun.tools.javadoc.DocletInvoker.start(DocletInvoker.java:143)
        at com.sun.tools.javadoc.Start.parseAndExecute(Start.java:340)
        at com.sun.tools.javadoc.Start.begin(Start.java:128)
        at com.sun.tools.javadoc.Main.execute(Main.java:41)
        at com.sun.tools.javadoc.Main.main(Main.java:31)

Command line was:"C:\Program Files (x86)\Java\jdk1.6.0_26\jre\..\bin\javadoc.exe" -J-Xmx1024m @options @argfile
        at org.apache.maven.plugin.javadoc.JavadocReport.execute(JavadocReport.java:238)
        at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:483)
        at org.twdata.maven.mojoexecutor.MojoExecutor.executeMojoImpl(MojoExecutor.java:120)
        ... 22 more
Caused by: org.apache.maven.reporting.MavenReportException: Exit code: 1 - Nov 19, 2012 9:29:22 AM com.sun.jersey.wadl.resourcedoc.ResourceD
ocletJSON start
SEVERE: Could not serialize ResourceDoc.
java.io.FileNotFoundException: C:tlassian-jira-5.2-sourcejira-admin-helper-plugin       argetclasses
esourcedoc.xml (The filename, directory name, or volume label syntax is incorrect)
        at java.io.FileOutputStream.open(Native Method)
        at java.io.FileOutputStream.<init>(FileOutputStream.java:194)
        at java.io.FileOutputStream.<init>(FileOutputStream.java:84)
        at com.sun.jersey.wadl.resourcedoc.ResourceDocletJSON.start(ResourceDocletJSON.java:199)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:597)
        at com.sun.tools.javadoc.DocletInvoker.invoke(DocletInvoker.java:269)
        at com.sun.tools.javadoc.DocletInvoker.start(DocletInvoker.java:143)
        at com.sun.tools.javadoc.Start.parseAndExecute(Start.java:340)
        at com.sun.tools.javadoc.Start.begin(Start.java:128)
        at com.sun.tools.javadoc.Main.execute(Main.java:41)
        at com.sun.tools.javadoc.Main.main(Main.java:31)

Command line was:"C:\Program Files (x86)\Java\jdk1.6.0_26\jre\..\bin\javadoc.exe" -J-Xmx1024m @options @argfile
        at org.apache.maven.plugin.javadoc.AbstractJavadocMojo.executeReport(AbstractJavadocMojo.java:1580)
        at org.apache.maven.plugin.javadoc.JavadocReport.generate(JavadocReport.java:136)
        at org.apache.maven.plugin.javadoc.JavadocReport.execute(JavadocReport.java:224)
        ... 24 more
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 19 seconds
[INFO] Finished at: Mon Nov 19 09:29:22 AST 2012
[INFO] Final Memory: 95M/227M
[INFO] ------------------------------------------------------------------------

Has anyone else come across this error?

Watch
Like Andrej Gregorka likes this
695 views

5 answers

1 accepted

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

Post a new question

0 votes
Answer accepted
Wayne Mabey
Wayne Mabey November 19, 2012

I've commented out the lines referring to the jira-admin-helper plugin (and the jira-welcome-plugin, which has the same problem) in the build.bat file. I'm running the build now. It will mean that these plugins aren't included, of course, but it doesn't look like they provide core functionality.

Reply
0 votes
Raquel Moracho
Raquel Moracho Sánchez February 11, 2013

Is there another way of solving this issue?, I'm not able to build the source code with the jira welcome plugin

Thank you in advance

View More Comments
Wayne Mabey
Wayne Mabey February 11, 2013

I've just left them commented out in the build.bat file.

The plugins can be downloaded from the Atlassian Marketplace once your JIRA build is deployed. It doesn't seem like they need to be built from source.

Like
Reply
0 votes
Raquel Moracho
Raquel Moracho Sánchez January 21, 2013

I have the same problem with jira-welwome-plugin when I try to build jira source, have you found a solution for this?. I wouldn't like to comment the line because I would like to have this plugin in the project

Thank you

Reply
0 votes
Andrej Gregorka
Andrej Gregorka November 19, 2012

I'm having the exact same problem when building Jira 5.2. Did you manage to find the solution yet?

View More Comments
Andrej Gregorka
Andrej Gregorka November 19, 2012

Thank you, the Jira has built successfully now.

Like
Reply
0 votes
Ramesh Udari1
Ramesh Udari1 November 18, 2012

Hi Wayne,

I am also facing the same problem. did you find any solution to this?.

Reply

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

Post a new question

Atlassian logo
Answers Developer Questions
TAGS
AUG Leaders

Atlassian Community Events

    See all events