Hi,
I have found a line of code which I might misunderstand...
https://gitbox.apache.org/repos/asf?p=maven-archiver.git;a=blob;f=src/main/java/org/apache/maven/archiver/MavenArchiver.java;h=66d93536d8c77fef66194841362cfca18a460e0c;hb=HEAD#l124
if ( hasManifestEntries )
{
Ok, after more tests i found that error exists when project was executed in
path with @ char that was encoded to %402 -
https://issues.apache.org/jira/browse/SUREFIRE-1312
Sylwester
śr., 27 gru 2017 o 13:31 użytkownik Karl Heinz Marbaise
napisał:
> Hi,
>
> On 27/12/17 13:01, Sylwester Lachiewic
Hi,
On 27/12/17 13:01, Sylwester Lachiewicz wrote:
Build fails with long directory name - also on windows.
Upgrade maven-surefire-plugin to 2.20.1 fixes test error.
Hm..this is a little bit confusing, cause the length for windows are
about 141 characters (already thought about something simil
Build fails with long directory name - also on windows.
Upgrade maven-surefire-plugin to 2.20.1 fixes test error.
śr., 27 gru 2017 o 08:49 użytkownik Plamen Totev
napisał:
> And if this could help (I know it's obvious but may safe time) it
> looks the reason for the failing tests is the same. T
And if this could help (I know it's obvious but may safe time) it
looks the reason for the failing tests is the same. The following code
fails with assertion error:
final Manifest manifest = getJarFileManifest( jarFile );
String classPath = manifest.getMainAttributes().getValue(
At
Hi,
On Tue, Dec 26, 2017 at 9:01 PM, Karl Heinz Marbaise wrote:
> Is someone out there who can check the current state of maven-archiver git
> repo on Windows and can reproduce the issue ?
I ran the build a couple of times(just in case) on Windows 10, Maven
3.5.2, JDK 9.0.1 and everything is ok
[6]:
https://builds.apache.org/job/maven-box/job/maven-archiver/job/master/6/testReport/
On Tue 26 Dec 2017 at 22:45, Stephen Connolly <
stephen.alan.conno...@gmail.com> wrote:
> Yes, I have set the command line to ignore failing tests, then the junit
> reporter marks the build as unstable based
Yes, I have set the command line to ignore failing tests, then the junit
reporter marks the build as unstable based on the test results
You should be able to see the 27 failing tests from [6]
On Tue 26 Dec 2017 at 21:59, Robert Scholte wrote:
> Interesting...
>
> The pipeline steps[1] say all s
Interesting...
The pipeline steps[1] say all succeeded, however #6 overview[2] complaints
about failing tests.
Robert
[1]
https://builds.apache.org/job/maven-box/job/maven-archiver/job/master/6/flowGraphTable/
[2]
https://builds.apache.org/job/maven-box/job/maven-archiver/job/master/6/
Hi Robert,
I will try and see the result..
Thanks.
Kind regards
Karl Heinz
On 26/12/17 20:27, Robert Scholte wrote:
The job starting quite some time ago. Maybe better to kill the it and
start over again.
I had trouble visiting builds.apache.org this afternoon, could be related.
thanks,
Rob
The job starting quite some time ago. Maybe better to kill the it and
start over again.
I had trouble visiting builds.apache.org this afternoon, could be related.
thanks,
Robert
On Tue, 26 Dec 2017 20:01:02 +0100, Karl Heinz Marbaise
wrote:
Hi,
currently I'm observing a strange thing..c
Hi,
currently I'm observing a strange thing..cause the build on Jenkins
produces test failure with JDK 9
https://builds.apache.org/job/maven-box/job/maven-archiver/job/master/5/consoleFull
The problem I'm currently having is that I can't reproduce this..
I have tested with Maven 3.5.2 and JD
12 matches
Mail list logo
