Ceylon maven improvements

[vietj]

there are a few issues with this code:

• it jarjar Arquillian / Aether code that can create classloading conflict issues
• it uses Arquillian facade and it could use directly Aether
• the Aether version is very old

[quintesse]

With "this code" I assume you refer to the maven-support JAR?

[quintesse]

The issue also doesn't make very clear what the proposed improvements are, I assume:

• get rid of Arquillian by using Aether directly
• update to a newer version of Aether in the process

Right?

But I'm not sure what the problem is with the class loader? And that problem would not be fixed by using Aether directly? So what would you propose to do about it?

[alesj]

it uses Arquillian facade and it could use directly Aether

Aether API must be one of the worst to work with, hence I chose the lesser evil -- ShrinkWarp over Aether. But feel free to change it.

[vietj]

@quintesse yes both : one stone two birds @alesj it may be horrible but once the code is written it's done

[vietj]

I won't change it myself :), it's an issue for improvement.

[vietj]

I mean it's not that I don't want to do it, it's just an issue to record what needs to be done.

[vietj]

the main problem is that the ceylon-maven-plugin cannot resolve maven module because the aether api is too old and conflicting with the recent maven aether apis creating classloading prb