[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[bug#28841] [PATCH 03/24] gnu: Add java-eclipse-jetty-test-helper.
From: |
Julien Lepiller |
Subject: |
[bug#28841] [PATCH 03/24] gnu: Add java-eclipse-jetty-test-helper. |
Date: |
Sun, 22 Oct 2017 14:11:40 +0200 |
Le Thu, 19 Oct 2017 11:57:07 +0200,
julien lepiller <address@hidden> a écrit :
> Le 2017-10-18 22:50, Ricardo Wurmus a écrit :
> > Hi Julien,
> >
> >> From: Julien Lepiller <address@hidden>
> >>
> >> * gnu/packages/java.scm (java-eclipse-jetty-test-helper): New
> >> variable.
> >
> > […]
> >
> > I wonder: is there a better place for this than java.scm? The same
> > question applies to all other patches in this series. Let’s try to
> > avoid a second python.scm situation :)
>
> eclipse.scm? Or maybe maven.scm, with all other maven bootstrap
> dependencies (and maven itself)? Or maven-bootstrap.scm, maven.scm
> being for the complete maven built with maven-bootstrap, and all the
> plugins of maven?
So, I've corrected all your comments, except this one, and I don't want
to push without some sort of a consensus. Do I add these packages to
java.scm, eclipse.scm, maven.scm, maven-bootstrap.scm?
>
>
>
[bug#28841] [PATCH 07/24] gnu: Add java-eclipse-jetty-io., julien, 2017/10/14
[bug#28841] [PATCH 11/24] gnu: Add java-eclipse-jetty-jmx., julien, 2017/10/14
[bug#28841] [PATCH 20/24] gnu: Add java-javax-inject., julien, 2017/10/14
[bug#28841] [PATCH 08/24] gnu: Add java-eclipse-jetty-io-9.2., julien, 2017/10/14
[bug#28841] [PATCH 06/24] gnu: Add java-eclipse-jetty-util-9.2., julien, 2017/10/14
[bug#28841] [PATCH 10/24] gnu: Add java-eclipse-jetty-http-9.2., julien, 2017/10/14
[bug#28841] [PATCH 13/24] gnu: Add java-eclipse-jetty-server., julien, 2017/10/14
[bug#28841] [PATCH 09/24] gnu: Add java-eclipse-jetty-http., julien, 2017/10/14