From: ludo@gnu.org (Ludovic Courtès)
To: Julien Lepiller <julien@lepiller.eu>
Cc: 31212@debbugs.gnu.org
Subject: [bug#31212] Add apache ivy
Date: Sat, 28 Apr 2018 23:25:57 +0200 [thread overview]
Message-ID: <87vacb81lm.fsf@gnu.org> (raw)
In-Reply-To: <20180418210458.306490ed@lepiller.eu> (Julien Lepiller's message of "Wed, 18 Apr 2018 21:04:58 +0200")
Hi Julien,
Julien Lepiller <julien@lepiller.eu> skribis:
> this small patch series adds apache-ivy and dependencies. They are the
> next packages required for maven. After that, I have groovy, in 22
> packages, then 18 more various java library packages, and finally 25
> packages to complete maven. We're almost there!
From a cursory look at the patches and as someone oblivious to Java ;-),
it looks reasonable. I think you can go ahead and push since nobody
replied in 10 days.
Thank you!
Ludo’.
next prev parent reply other threads:[~2018-04-28 21:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-18 19:04 [bug#31212] Add apache ivy Julien Lepiller
2018-04-18 19:21 ` [bug#31212] [PATCH 1/9] gnu: Add java-bouncycastle Julien Lepiller
2018-04-18 19:21 ` [bug#31212] [PATCH 2/9] gnu: Add java-jsch-agentproxy-core Julien Lepiller
2018-04-18 19:21 ` [bug#31212] [PATCH 3/9] gnu: Add java-jsch-agentproxy-sshagent Julien Lepiller
2018-04-18 19:21 ` [bug#31212] [PATCH 4/9] gnu: Add java-jsch-agentproxy-usocket-jna Julien Lepiller
2018-04-18 19:21 ` [bug#31212] [PATCH 5/9] gnu: Add java-jsch-agentproxy-pageant Julien Lepiller
2018-04-18 19:21 ` [bug#31212] [PATCH 6/9] gnu: Add java-jsch-agentproxy-usocket-nc Julien Lepiller
2018-04-18 19:21 ` [bug#31212] [PATCH 7/9] gnu: Add java-jsch-agentproxy-connector-factory Julien Lepiller
2018-04-18 19:21 ` [bug#31212] [PATCH 8/9] gnu: Add java-jsch-agentproxy-jsch Julien Lepiller
2018-04-18 19:21 ` [bug#31212] [PATCH 9/9] gnu: Add java-apache-ivy Julien Lepiller
2018-04-28 21:25 ` Ludovic Courtès [this message]
2018-04-29 21:24 ` bug#31212: Add apache ivy Julien Lepiller
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87vacb81lm.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=31212@debbugs.gnu.org \
--cc=julien@lepiller.eu \
/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/guix.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).