Commons weaver seems to have an issue with its pom module settings. One symptom is that the following fails:
$ mvn dependency:list with Could not resolve dependencies for project org.apache.commons:commons-weaver-maven-plugin:maven-plugin:2.1-SNAPSHOT: Failure to find org.apache.commons:commons-weaver-processor:jar:2.1-SNAPSHOT in https://repository.apache.org/snapshots was cached in the local repository, resolution will not be reattempted until the update interval of apache.snapshots has elapsed or updates are forced This can be fixed using 'mvn install', but surely that should not be necessary? Is there some bootstrapping issue here? Much the same problem occurs when using japicmp in the maven-plugin module. [So it was temporarily disabled to allow builds to complete] Can anyone provide any assistance here? Sebb --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
