public inbox for kawa@sourceware.org
 help / color / mirror / Atom feed
From: Arvydas Silanskas <nma.arvydas.silanskas@gmail.com>
To: kawa mailing list <kawa@sourceware.org>
Subject: maven-like tooling for kawa
Date: Sat, 22 Aug 2020 23:45:52 +0300	[thread overview]
Message-ID: <CAPh7weCUmAh+wFbKq3m-y3d9nbE5U6BQuSyzJ93NSE6yNm9R3A@mail.gmail.com> (raw)

Good evening,

I guess no need for an introduction about what maven is, and why people in
the jvm world use it. I feel currently, kawa is missing an equivalent to
it. Sure, maven could be used now for getting ahold of java
dependencies' jars (using dependency:copy-dependencies), however what about
other niceties, such as

* running scheme files while including those dependency jars on classpath
* packaging (compiling scheme files first before bundling it all together)
* testing (automatically discovering and running scheme test files in some
known directory, what in java is src/testing/java)
* expanding dependencies gathering not only for java libs, but r7rs scheme
libs too (particularly thinking about snow), with configuration managed in
uniform or at least similar manner

I have a public facing example project of tackling these points using
combination of ant and maven at
https://github.com/arvyy/libGDX-Kawa-Starter
<https://github.com/arvyy/libGDX-Kawa-Starter/blob/master/build.xml> ,
however I'm not entirely happy with this, and I'd find a kawa-specialized
tool a cleaner approach.

Have you discussed a topic of maven-like tooling for kawa? Any general
thoughts -- ranging from general functionality to how the configuration
would look? I plan having a go at prototyping such tool, and before I start
I though gathering some thoughts about it.

Regards,
Arvydas

                 reply	other threads:[~2020-08-22 20:45 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=CAPh7weCUmAh+wFbKq3m-y3d9nbE5U6BQuSyzJ93NSE6yNm9R3A@mail.gmail.com \
    --to=nma.arvydas.silanskas@gmail.com \
    --cc=kawa@sourceware.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.
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).