Release Plugin-Errors

488 views
Skip to first unread message

laks...@qualesce.com

unread,
Aug 18, 2016, 7:01:23 AM8/18/16
to Jenkins Developers
Hi,

I have developed one plugin and submitted in the github repository,the plugin was already forked , while trying to release the plugin i am getting the following error,any one help me to resolve this issue.

Thanks for helping.

    [ERROR] Failed to execute goal org.apache.maven.plugins:maven-javadoc-plugin
:2.10.1:javadoc (default) on project WorksoftCertifyDashBoardSummary: An error h
as occurred in JavaDocs report generation:
    [ERROR] Exit code: 1 - javadoc: warning - No source files for package org.je
nkinsci.plugins.WorksoftCertifyDashboardSummary
    [ERROR] javadoc: error - No public or protected classes found to document.
    [ERROR]
    [ERROR] Command line was: "C:\Program Files\Java\jdk1.8.0_91\jre\..\bin\java
doc.exe" @options @packages
    [ERROR]
    [ERROR] Refer to the generated Javadoc files in 'C:\Users\Susmitha007\Deskto
p\imp Plugins\release_1.0\WorksoftCertifyDashBoardSummary\target\site\apidocs' d
ir.
    [ERROR] -> [Help 1]
    [ERROR]
    [ERROR] To see the full stack trace of the errors, re-run Maven with the -e
switch.
    [ERROR] Re-run Maven using the -X switch to enable full debug logging.
    [ERROR]
    [ERROR] For more information about the errors and possible solutions, please
 read the following articles:
ionException
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 05:07 min
[INFO] Finished at: 2016-08-18T16:00:59+05:30
[INFO] Final Memory: 22M/248M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-release-plugin:2.5
.3:prepare (default-cli) on project WorksoftCertifyDashBoardSummary: Maven execu
tion failed, exit code: '1' -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e swit
ch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please rea
d the following articles:
xception

C:\Users\Susmitha007\Desktop\imp Plugins\release_1.0\WorksoftCertifyDashBoardSum
mary>cd C:\Users\Susmitha007\Desktop\imp Plugins\release_1.0\WorksoftCertifyDash
BoardSummay

Thanks,
Lakshmi
pom.xml

Robert Sandell

unread,
Aug 19, 2016, 5:01:44 AM8/19/16
to jenkin...@googlegroups.com
    [ERROR] javadoc: error - No public or protected classes found to document.

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/daa2e751-dad7-49f8-8de0-c15977e00e75%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.



--
Robert Sandell
Software Engineer
CloudBees Inc.

Robert Sandell

unread,
Aug 19, 2016, 5:02:42 AM8/19/16
to jenkin...@googlegroups.com
Could it be because you have no javadoc?


[ERROR] javadoc: error - No public or protected classes found to document.

?

laks...@qualesce.com

unread,
Oct 17, 2016, 5:52:12 AM10/17/16
to Jenkins Developers
Can you brief me in which way javadoc is used in this plugin release.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-de...@googlegroups.com.
--
Robert Sandell
Software Engineer
CloudBees Inc.

Daniel Beck

unread,
Oct 17, 2016, 7:25:32 AM10/17/16
to jenkin...@googlegroups.com

> On 17.10.2016, at 11:52, laks...@qualesce.com wrote:
>
> Can you brief me in which way javadoc is used in this plugin release.

Versions of the 2.x plugins parent POM include Javadoc generation that creates a Javadoc archive as build artifact.

laks...@qualesce.com

unread,
Oct 18, 2016, 5:46:47 AM10/18/16
to Jenkins Developers, m...@beckweb.net

Hi,

Can you please tell what is the process to follow for releasing the plugin after over plugin has forked in github?

Daniel Beck

unread,
Oct 18, 2016, 7:19:37 AM10/18/16
to jenkin...@googlegroups.com

> On 18.10.2016, at 11:46, laks...@qualesce.com wrote:
>
> Can you please tell what is the process to follow for releasing the plugin after over plugin has forked in github?
>

https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins#HostingPlugins-Releasingtojenkinsci.org

Jesse Glick

unread,
Oct 18, 2016, 11:18:46 AM10/18/16
to Jenkins Dev
On Fri, Aug 19, 2016 at 5:02 AM, Robert Sandell <rsan...@cloudbees.com> wrote:
> Could it be because you have no javadoc?
>
> [ERROR] javadoc: error - No public or protected classes found to document.

No, this error would mean there are no sources at all, or they are all
paclage-private. Either way, that seems an impossible situation since
a plugin with no `public` classes cannot do anything.

Ted Xiao

unread,
Oct 19, 2016, 11:26:44 AM10/19/16
to Jenkins Developers
1 - javadoc: warning - No source files for package org.je
nkinsci.plugins.WorksoftCertifyDashboardSummary

java package name should be all lowercase
Reply all
Reply to author
Forward
0 new messages