maven-install-plugin 3.0 Aether impact

[Robert Scholte <rf...@apache.org>]

Hi

I've started a branch for the maven-install-plugin in order to move to a  
pure Maven3 solution, see
https://svn.apache.org/repos/asf/maven/plugins/branches/m-install-p-3.0

Now I'm facing 2 kind of issues due to the switch to Aether:

[ERROR] *  attach-jar-checksum\pom.xml
[ERROR] *  generate-pom-auto-1\pom.xml
[ERROR] *  jar-sources-javadoc\pom.xml
[ERROR] *  pom-checksum\pom.xml

Cause: missing maven-metadata-local.xml.md5
Aether is now responsible for generating the maven-metadata-local.xml, but  
it doesn't seem to generate the checksum(s). Should we consider this as an  
issue?


---
[ERROR] *  gav-validation\pom.xml

Cause: ModelValidator has been moved to maven-compat. However, I don't  
think that Aether will do this check. What to do here?

thanks,
Robert

ps. Right now I'm only testing with Maven 3.0, haven't verified other  
versions yet.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org