[
https://issues.apache.org/jira/browse/DIRSTUDIO-539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pierre-Arnaud Marcelot closed DIRSTUDIO-539.
--------------------------------------------
> studio-maven-plugin cannot be installed locally
> -----------------------------------------------
>
> Key: DIRSTUDIO-539
> URL: https://issues.apache.org/jira/browse/DIRSTUDIO-539
> Project: Directory Studio
> Issue Type: Bug
> Environment: N/A
> Reporter: Hasan Ceylan
> Priority: Minor
>
> Since maven-docck-plugin needs to talk to some
> http://vm094.oxylos.org/projects/studio-plugin/ it is impossible for an
> anonymous to work with the plugin
> I suggest maven-docck-plugin's lifecycle attachment to 'deploy'
> Here's the stack trace
> [INFO] [docck:check]
> [INFO] Checking project: Apache Directory Studio Plugin
> [INFO] Using 2 extractors.
> [INFO] Applying extractor for language: java
> [INFO] Extractor for language: java found 6 mojo descriptors.
> [INFO] Applying extractor for language: bsh
> [INFO] Extractor for language: bsh found 0 mojo descriptors.
> [ERROR] The following documentation problems were found:
> o Apache Directory Studio Plugin (1 error, 0 warnings)
> [ERROR] Cannot reach project site with URL:
> 'http://vm094.oxylos.org/projects/studio-plugin/'.
> Error: The host did not accept the connection within timeout of 5000 ms
>
> [ERROR]
> Documentation problems were found. Please see the console output above for
> more information.null
> Error stacktrace:
>
> org.apache.maven.ProjectBuildFailureException: Build for project:
> org.apache.directory.studio:studio-maven-plugin:maven-plugin:1.0.3-SNAPSHOT
> failed during execution of mojo:
> org.apache.maven.plugins:maven-docck-plugin:1.0:check
>
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmentForProject(DefaultLifecycleExecutor.java:287)
>
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:201)
>
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:164)
>
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:207)
>
> at
> org.apache.maven.embedder.MavenEmbedder.execute(MavenEmbedder.java:846)
>
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:160)
>
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:63)
>
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>
> at java.lang.reflect.Method.invoke(Method.java:616)
>
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
>
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
>
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:408)
>
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:351)
>
> Caused by: org.apache.maven.plugin.MojoFailureException: Documentation
> problems were found. Please see the console output above for more
> information.
> at
> org.apache.maven.plugin.docck.AbstractCheckDocumentationMojo.execute(AbstractCheckDocumentationMojo.java:200)
>
> at
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:629)
>
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:492)
>
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmentForProject(DefaultLifecycleExecutor.java:259)
>
> ... 14 more
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
