all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Igor Gajsin <igor@gajsin.name>
To: Michael Rohleder <mike@rohleder.de>
Cc: 53934@debbugs.gnu.org
Subject: bug#53934: OpenJDK doesn't have a doclet
Date: Mon, 14 Feb 2022 22:26:27 +0100	[thread overview]
Message-ID: <874k51f894.fsf@gajsin.name> (raw)
In-Reply-To: <87zgmumjxv.fsf@rohleder.de>

I narrowed down where the problem arise and found the exact bugreport:
https://github.com/clojure-emacs/orchard/issues/117#issuecomment-859987280

Unfortunately, I didn't get the solution 'one has to use ONLY the
package "openjdk:jdk"'. What does it mean?

Also, why openjdk removes javadoc, is it a bug or a correct behaviour?

Michael Rohleder <mike@rohleder.de> writes:

> [[PGP Signed Part:Undecided]]
> Igor Gajsin <igor@gajsin.name> writes:
>> There is a problem with openjdk (all versions 10 to 17). When I run
>> cider (emacs mode for clojure) it complains about:
>> java.lang.ClassNotFoundException: jdk.javadoc.doclet.Doclet
>>
>> when I try to set icedtea there is no such problem. If I understand well
>> doclet is a part of JDK so it shoulb be part of a modern openjdk
>> installation.
>
> I haven't tried, but maybe adding a file "module-info.java" with the
> content "requires jdk.javadoc" to your project might help. [1]
>
> [1]
> https://stackoverflow.com/questions/65683365/why-cant-i-import-the-jdk-javadoc-doclet-package


-- 
With best regards,
Igor Gajsin




  reply	other threads:[~2022-02-14 21:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-10 23:26 bug#53934: OpenJDK doesn't have a doclet Igor Gajsin
2022-02-13 23:21 ` Michael Rohleder
2022-02-14 21:26   ` Igor Gajsin [this message]
2022-02-14 21:35     ` Julien Lepiller
2022-02-14 22:49       ` Igor Gajsin
2022-02-15 22:45       ` Igor Gajsin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=874k51f894.fsf@gajsin.name \
    --to=igor@gajsin.name \
    --cc=53934@debbugs.gnu.org \
    --cc=mike@rohleder.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.