Citrus cannot be used with gradle about citrus

[christophd]

Relative paths in parent Maven pom is a usual thing to do and the paths are correct. Maven build is successful and Maven repositories can access the Citrus artifacts. I believe Gradle interprets the relative path when reading artifacts from the Maven repository which is not adequate

[holzerc]

Well, no other library or framework that I know has similar problems with Gradle. So it is obviously not a usual thing to do.

It is your decision to support or not support Gradle. However for the sake of other Gradle users it would be very helpful to point it out in the documentation.

[christophd]

Well, no other library or framework that you know uses relative Maven parent pom. Then all Maven projects using relative parent pom are not supported by Gradle. I think this should be pointed out.

[rhuss]

@holzerc, maybe you can provide a concrete example with error messages ? The relative path in the poms looks correct and of course gradle should support the resolution as the vast majority of maven modules (if not the vast majorit) use relative paths this way.

And even then, if the parent POM could not be found in the filesystem it is resolved via the maven coordinates in the repository.

So I guess, your problem has a different origin.

[holzerc]

It is very easy to reproduce the problem. Just use Citrus with Gradle. Christoph already saw the behavior twice with two different customer projects.

The only workaround he could provide was either not using Gradle or patching all Citrus pom.xml files in the local Maven repository.

[rhuss]

ok. I'm out, since I don't have a Gradle setup with Citrus at hand to reproduce it and without a concrete, stripped down example, I can't help much.

I'm pretty sure that it can be fixed, though.

Cheers ...