|
From: | Hartmut Goebel |
Subject: | Re: State of maven build system, gradle and Apache commens |
Date: | Fri, 2 Sep 2016 12:44:08 +0200 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0 |
Am 02.09.2016 um 09:47 schrieb Ricardo
Wurmus:
This should not be on the CLASSPATH. The “ant-build-system” sets CLASSPATH to the result of running “generate-classpath” on all inputs. Currently, all this does it add any and all “.jar” files to the CLASSPATH. To keep “jar” itself out, the regular _expression_ should be changed from (find-files dir "\\.*jar$") to something like (find-files dir "\\.jar$") Thanks for this tip, it helped. (Will submit a patch later) Meantime I managed to build commons-io, commons-cli, commons-lang and commons-codec. 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. I failed building commons-logging, which requires e.g. javax.servelet, the avalon-frameweork and much more. --
Schönen Gruß Hartmut Goebel Dipl.-Informatiker (univ), CISSP, CSSLP, ISO 27001 Lead Implementer Information Security Management, Security Governance, Secure Software Development
Goebel Consult, Landshut
Blog:
http://www.goebel-consult.de/blog/warum-sie-nicht-perl-programmiern-sollten
|
commons-io.txt
Description: Text document
smime.p7s
Description: S/MIME Cryptographic Signature
[Prev in Thread] | Current Thread | [Next in Thread] |