emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Tim Jones <tim.jones.001@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Org-babel Java imports
Date: Tue, 19 Sep 2017 09:51:18 +0000	[thread overview]
Message-ID: <CAAjD55gaRMMAwT4huU6fCqhM4UYpqFC9N-r1wmLcW04-7dY1FA@mail.gmail.com> (raw)
In-Reply-To: <87377jdpfx.fsf@pinto.chemeng.ucl.ac.uk>

[-- Attachment #1: Type: text/plain, Size: 1194 bytes --]

Eric

Thanks for your reply

No - that's exactly what I did first, but it did not work.

I then tried preceding it with a package statement, which did not work
either.

It got me thinking that I had now idea how it could resolve dependencies,
whether for java packages, which you would expect to be on the classpath by
default and therefore could be found, or for external libraries, which
would usually be downloaded and put on the classpath by a tool like gradle
or maven.

Have you any insight into this or could you suggest whom I might ask?

Regards,

Tim

On Tue, Sep 19, 2017 at 10:10 AM Eric S Fraga <esflists@gmail.com> wrote:

> On Friday, 15 Sep 2017 at 14:56, Tim Jones wrote:
> > Hi
> > Want to create org docs with embedded java blocks which will generate
> > testing data
> >
> > I have seen
> > http://ehneilsen.net/notebook/orgExamples/org-examples.html#sec-19
> > but have not been able to find an example where there are any import
> > statements e.g.
> > import java.time.*;
>
> Can you not simply put this line as the first line of the actual source
> block, i.e. after the #+begin_src?  (untested)
> --
> : Eric S Fraga via Emacs 26.0.50, Org release_9.0.10-729-gb792e2
>

[-- Attachment #2: Type: text/html, Size: 1799 bytes --]

  reply	other threads:[~2017-09-19  9:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-15 14:56 Org-babel Java imports Tim Jones
2017-09-19  9:10 ` Eric S Fraga
2017-09-19  9:51   ` Tim Jones [this message]
2017-09-19 15:52     ` Eric S Fraga

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

  List information: https://www.orgmode.org/

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

  git send-email \
    --in-reply-to=CAAjD55gaRMMAwT4huU6fCqhM4UYpqFC9N-r1wmLcW04-7dY1FA@mail.gmail.com \
    --to=tim.jones.001@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).