Am 10/11/16 um 21:50 schrieb Karl Heinz Marbaise:
> Hi Guillaue,
>
> On 11/10/16 21:21, Guillaume Boué wrote:
>> Regarding this failure, I think it is caused by a capitalization
>> issue... The test is looking for
>> "missing-artifactid-pluginManagement.xml" (lowercase "i" at artifactid)
>> while
Hi Guillaue,
On 11/10/16 21:21, Guillaume Boué wrote:
Regarding this failure, I think it is caused by a capitalization
issue... The test is looking for
"missing-artifactid-pluginManagement.xml" (lowercase "i" at artifactid)
while the file on disk is called
"missing-artifactId-pluginManagement.xm
Regarding this failure, I think it is caused by a capitalization
issue... The test is looking for
"missing-artifactid-pluginManagement.xml" (lowercase "i" at artifactid)
while the file on disk is called
"missing-artifactId-pluginManagement.xml" (uppercase "i"). I don't have
the issue on Window
Hi,
interesting, cause I couldn't reproduce the issue on my system ..only
the build server shows an test failure...
I need to investigage the reason for that ...cause other tests from the
same folder working...
Are you running on Linux / Mac / Windows ? Java Version?
Kind regards
Karl Hein
Just updated current master and am getting test failures. Just my local
checkout?
$ env LC_ALL=C git branch
* master
maven-3.x-next
$ env LC_ALL=C git status
On branch master
Your branch is up-to-date with 'origin/master'.
nothing to commit, working directory clean
testInvalidArtifactIdInPlugi