From: "Björn Höfling" <bjoern.hoefling@bjoernhoefling.de>
To: Julien Lepiller <julien@lepiller.eu>
Cc: 30606@debbugs.gnu.org
Subject: [bug#30606] maven resolver packages
Date: Wed, 14 Mar 2018 07:36:38 +0100 [thread overview]
Message-ID: <20180314073638.385d73c8@alma-ubu> (raw)
In-Reply-To: <20180225164822.60ae5c2a@lepiller.eu>
[-- Attachment #1: Type: text/plain, Size: 712 bytes --]
Hi Julien,
sorry I was slower reviewing than you commiting this one.
On Sun, 25 Feb 2018 16:48:22 +0100
Julien Lepiller <julien@lepiller.eu> wrote:
> Hi,
>
> here are the first few packages needed by maven. I created a new
> maven.scm file for them.
All 5 look good, besides maybe this remark:
These packages are used to bootstrap Maven. Once we have Maven and a
maven-build-system, we eventually want to rebuild them with Maven and
have them in some (to be defined) Guix-Maven-Layout, for example with
pom.xml included and in the usual .m2/repository directory-structure.
Should we thus rename them to maven-*-bootstrap and just (define them
instead of (define-public?
Björn
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2018-03-14 6:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-25 15:48 [bug#30606] maven resolver packages Julien Lepiller
2018-02-25 15:56 ` [bug#30606] [PATCH 1/5] gnu: Add maven-resolver-api Julien Lepiller
2018-02-25 15:56 ` [bug#30606] [PATCH 2/5] gnu: Add maven-resolver-spi Julien Lepiller
2018-02-25 15:56 ` [bug#30606] [PATCH 3/5] gnu: Add maven-resolver-test-util Julien Lepiller
2018-02-25 15:56 ` [bug#30606] [PATCH 4/5] gnu: Add maven-resolver-util Julien Lepiller
2018-02-25 15:56 ` [bug#30606] [PATCH 5/5] gnu: Add maven-resolver-connector-basic Julien Lepiller
2018-03-14 6:36 ` Björn Höfling [this message]
2018-03-14 13:15 ` [bug#30606] maven resolver packages julien lepiller
2018-03-16 11:53 ` bug#30606: " Björn Höfling
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=20180314073638.385d73c8@alma-ubu \
--to=bjoern.hoefling@bjoernhoefling.de \
--cc=30606@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 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.