unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Hartmut Goebel <h.goebel@goebel-consult.de>
To: guix-devel@gnu.org
Subject: Re: State of maven build system, gradle and Apache commens
Date: Tue, 6 Sep 2016 09:32:53 +0200	[thread overview]
Message-ID: <57CE7125.9080106@goebel-consult.de> (raw)
In-Reply-To: <20160906001553.25365b2a@alma-ubu>


[-- Attachment #1.1: Type: text/plain, Size: 2062 bytes --]

Am 06.09.2016 um 00:15 schrieb Björn Höfling:
> I'm interested in which version of maven do you start to create? Which
> version(s) of the dependencies/plugins are you rebuilding?

I started building the current version of maven, since the others are
outdated and I did not want to rely on unmaintained software.

> How do you proceed? Do you have an issue raised where we can share
> knowledge/coordinate next steps?

I'll convert my intermediate results into patches and some "report" to
the mailinglist later this week.


I gave up on packaging further Java packages. It's a abottomless pit of
recursive dependencies.

"Bootstrapping" maven requires some pre-built .jar files (some of which
are included in maven's "source"). But building these .jar files
requires maven to find it's way through all the build-steps. There is
some "maven-ant-plugin" which is said to "Generates an Ant build file
from a POM." but (since it is a maven-plugin), it again requires maven.

Debian has some "maven-ant-helper" which contains some default
"maven-build.xml", but again requires maven.


Later this week I'll prepare my work and some ides so others can pick up
and then Java can see my backside.

Side note;: I always had a bad feeling about Java software, but now I
have a informed position, why Java software is of bad quality. One must
only look at these cyclic build-dependencies and the sheer amount of
packages from so many different sources required to package even
"common" stuff. Example: some "easymock" package requires a "dexmaker"
package from google (which seems to be for access in android .dex
files). Such a crap!

-- 
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
http://www.goebel-consult.de

Blog: http://www.goebel-consult.de/blog/ehrlichkeit-made-in-germany
Kolumne: http://www.cissp-gefluester.de/2010-06-adobe-und-der-maiszunsler


[-- Attachment #1.2: Type: text/html, Size: 3573 bytes --]

[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 2430 bytes --]

  parent reply	other threads:[~2016-09-06  7:33 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-01 11:36 State of maven build system, gradle and Apache commens Hartmut Goebel
2016-09-01 12:03 ` Ricardo Wurmus
2016-09-01 16:51   ` Hartmut Goebel
2016-09-02  7:47     ` Ricardo Wurmus
2016-09-02 10:44       ` Hartmut Goebel
2016-09-02 11:48         ` Ricardo Wurmus
2016-09-02 12:43           ` Hartmut Goebel
2016-09-02 14:24             ` Ricardo Wurmus
2016-09-05 22:15   ` Björn Höfling
2016-09-06  6:54     ` Ricardo Wurmus
2016-09-06  7:32     ` Hartmut Goebel [this message]
2016-09-06 20:43       ` Björn Höfling
2016-09-12 11:26       ` Java hand-over (was: State of maven build system, gradle and Apache commens) Hartmut Goebel

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=57CE7125.9080106@goebel-consult.de \
    --to=h.goebel@goebel-consult.de \
    --cc=guix-devel@gnu.org \
    /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).