Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-316

JavaDoc link causes http-500 error when no javadoc was built

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major Major
    • core
    • None
    • Platform: All, OS: All

      If I configure a hudson project to publish javadoc at the end of a build, Hudson
      then provides a view javadoc link. If I never generated javadoc clicking on the
      javadoc link will cause a stack trace. IMO the software should do one of the
      following:

      1. Declare the build a failure if the publish javadoc step can't find javadoc.
      2. Supress the view javadoc link if none was published.
      3. Replace the stack trace with a simple message that no javadoc was found.

          [JENKINS-316] JavaDoc link causes http-500 error when no javadoc was built

          pmendelson created issue -
          Kohsuke Kawaguchi made changes -
          Resolution New: Fixed [ 1 ]
          Status Original: Open [ 1 ] New: Resolved [ 5 ]
          pmendelson made changes -
          Resolution Original: Fixed [ 1 ]
          Status Original: Resolved [ 5 ] New: Reopened [ 4 ]
          Kohsuke Kawaguchi made changes -
          Resolution New: Fixed [ 1 ]
          Status Original: Reopened [ 4 ] New: Resolved [ 5 ]
          Andrew Bayer made changes -
          Status Original: Resolved [ 5 ] New: Closed [ 6 ]
          Jenkins IRC Bot made changes -
          Component/s New: core [ 15593 ]
          Component/s Original: www [ 15484 ]
          R. Tyler Croy made changes -
          Workflow Original: JNJira [ 130389 ] New: JNJira + In-Review [ 199769 ]

            Unassigned Unassigned
            pmendelson pmendelson
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: