From: Remco van 't Veer <remco@remworks.net>
To: Julien Lepiller <julien@lepiller.eu>
Cc: "Dr. Arne Babenhauserheide" <arne_bab@web.de>, 55776@debbugs.gnu.org
Subject: bug#55776: maven-core fails to build
Date: Sat, 04 Jun 2022 16:25:23 +0200 [thread overview]
Message-ID: <87ilpgmros.fsf@remworks.net> (raw)
In-Reply-To: <20220604154707.099a3679@sybil.lepiller.eu>
2022/06/04 15:47, Julien Lepiller:
> So I figured I could fix java-plexus-component-metadata that we use to
> generate some xml files during the build of maven. jdom is one of its
> inputs. Adding another jdom to the native inputs would probably not fix
> the issue.
Reverting the jdom upgrade patch, I did get mave-core to build. I admit
I did not try running it. My interest in maven is as a dependency to
clojure-tools, I don't really know how to test maven is actually working
by itself.
> What I did instead is, since jdom wants to set more features than
> supported in the driver, to add dummy support for all these additional
> features by just not throwing the exception. It's not very satisfying,
> but it works and we don't keep a vulnerable jdom around. With the
> attached patch, I built up to maven.
Smart! I look forward to seeing your patch land in the main branch.
Cheers,
Remco
next prev parent reply other threads:[~2022-06-04 14:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-03 6:05 bug#55776: maven-core fails to build Dr. Arne Babenhauserheide
2022-06-04 10:25 ` Remco van 't Veer
2022-06-04 13:47 ` Julien Lepiller
2022-06-04 14:25 ` Remco van 't Veer [this message]
2022-06-04 15:00 ` Dr. Arne Babenhauserheide
2022-06-08 18:36 ` Julien Lepiller
2022-06-08 15:35 ` Andrew Tropin
2022-06-07 10:32 ` Steve George
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=87ilpgmros.fsf@remworks.net \
--to=remco@remworks.net \
--cc=55776@debbugs.gnu.org \
--cc=arne_bab@web.de \
--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 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).