From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ricardo Wurmus Subject: Re: State of maven build system, gradle and Apache commens Date: Fri, 2 Sep 2016 16:24:49 +0200 Message-ID: References: <57C812CE.1000308@goebel-consult.de> <57C85C78.5070800@goebel-consult.de> <57C957F8.1020005@goebel-consult.de> <57C973DE.8040704@goebel-consult.de> Mime-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:54695) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bfpOv-0000U2-86 for guix-devel@gnu.org; Fri, 02 Sep 2016 10:25:02 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bfpOq-00072e-PS for guix-devel@gnu.org; Fri, 02 Sep 2016 10:25:00 -0400 Received: from sinope02.bbbm.mdc-berlin.de ([141.80.25.24]:54802) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bfpOq-00072I-IF for guix-devel@gnu.org; Fri, 02 Sep 2016 10:24:56 -0400 In-Reply-To: <57C973DE.8040704@goebel-consult.de> List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: Hartmut Goebel Cc: guix-devel@gnu.org Hartmut Goebel writes: > Am 02.09.2016 um 13:48 schrieb Ricardo Wurmus: > > =20 > > I found all of these need intervention for building, as there= is no >> "install" target (maybe I missed something). Echo of the packages >> behaves a bit different (e.g. different directory names), while >> sharing some common patterns. I'll attach my WIP for your convenience. > > =E2=80=9Cant-build-system=E2=80=9D creates a =E2=80=9Cbuild.xml=E2=80= =9D with an install target when > =E2=80=9C#:jar-name=E2=80=9D is provided. This is useful in case there= =E2=80=99s only a > =E2=80=9Cpom.xml=E2=80=9D and the package provides a single jar. > > Yes, this is what you wrote earlier today. But most of these (four) > commons packages habe a build.xml, But they behave differently. Some > build into "target", some into "dist/", some put docs in "apidocs/" > others into "docs/api/". > > Or do you suggest to use a build.xml created be ant-build-system? This depends on the package and the expected output (e.g. one jar file to be installed). The build.xml generated by the ant-build-system does not build docs because it=E2=80=99s supposed to work for most Java packag= es. We could change the ant-build-system such that a smarter =E2=80=9Cbuild.x= ml=E2=80=9D would be generated, but I think if a project provides a =E2=80=9Cbuild.xm= l=E2=80=9D we should be using it, unless it=E2=80=99s really defective or close to usel= ess. Another option is to write procedures to parse the =E2=80=9Cbuild.xml=E2=80= =9D and add custom targets, but since I don=E2=80=99t know what to expect in the buil= d files I cannot think of a general approach that would be useful here. ~~ Ricardo