Hi, we cant get rid of this error. This is due to the behaviour of maven site plugin. It transitively searches through all dependency poms. Some dependency jar, refers to this non-existing pom and therefor it gives this error.
proper solution would be maven exclusions. But to find the exact jar/pom that refers to this non-existing pom, is not an easy task. maven dependency:tree might give some clues. --Pradeep
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
