That was it, package get created w/o any error.
Thank you for your advice.
Matt
Am 05.12.2017 um 08:54 schrieb Benoit Tellier:
Hi. Could you please remove the -Dmaven.test.skip=true part of your command?
Le 05/12/2017 à 04:49, cryptearth a écrit :
Hey Benoit,
thanks for your reply.
Ok, so after looking through the files and logs and repos - I found the
issue:
https://repo.maven.apache.org/maven2/org/apache/james/james-server-util-java8/
error: there isn't a pack for current 3.1.0 of james - so I guess that's
why a wrong artifact gets downloaded into local repo and
Hey Benoit,
thanks for your reply.
Here're my current build specs:
host: win7 ulti sp1 x64
vm: virtualbox 5.1.26r117224
vm-os: opensuse tumbleweed x64 - snapshot 20171203
jdk: openjdk 1.8.0_151 x64
maven: 3.5.2 - additional repo at
Hi Matt.
- DskipTests skips tests execution, not test compilation. If you used
that option then your failure is not normal.
By the way, such "non compilable/non runnable" tests seems really weird
to me. Could you:
- Give me your environment settings: OS/OS version/ Java JDK +
version/maven
Hey there all,
as one of you told me long ago to skip tests to get a working package
fast the current build somewhat fails to "skip" the tests.
~/james-project/mpt/impl/smtp/core/src/main/java/org/apache/james/mpt/smtp
contains two test-classes: ForwardSmtpTest.java and
