unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Julien Lepiller <julien@lepiller.eu>
To: 31943@debbugs.gnu.org
Subject: bug#31943: Some Maven bugs
Date: Wed, 4 Jul 2018 22:06:08 +0200	[thread overview]
Message-ID: <20180704220558.0efc9e0f@lepiller.eu> (raw)
In-Reply-To: <20180623003935.21f7da0b@alma-ubu>

Le Sat, 23 Jun 2018 00:39:35 +0200,
Björn Höfling <bjoern.hoefling@bjoernhoefling.de> a écrit :

> Maven is now part of Guix, yeah! I gave it a try and found some bugs
> which I post collectively here. I don't know yet where exactly they
> come from and if they are trivial or not to fix. So if you think they
> should better go each into a separate bug report, please separate
> them.
> 
> [...]
> 
> 6) Maven does not compile Java 1.8 code.
> 

This should be fixed in 892a5647debc7fe8eafac4f725c46134eb085b63.

I was cramming the whole set of dependencies for maven in the
classpath, but it seems it doesn't play well with downloaded plugins.
Now I generated a m2.conf file with multiple "load" lines to tell
plexus-classworlds where to find the required jar files.

> 
> 
> 7) I have some trouble executing the tests. This is indeterministic
> (!), sometimes is is successful, sometimes I get an error:
> 

So I've tested this, and it turns out it's not our package's fault: it
fails undeterministically also when using the system's maven. I fixed
it by downgrading maven-surefire-plugin version to 2.20 instead of
2.20.1.

Thank you for your reports! Do you think we can close this report now?

  parent reply	other threads:[~2018-07-04 20:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-22 22:39 bug#31943: Some Maven bugs Björn Höfling
2018-06-23 10:20 ` Julien Lepiller
2018-06-25 10:13   ` Björn Höfling
2018-07-04 20:06 ` Julien Lepiller [this message]
2018-07-05  4:42   ` Björn Höfling

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=20180704220558.0efc9e0f@lepiller.eu \
    --to=julien@lepiller.eu \
    --cc=31943@debbugs.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).