2.0.0.RC1 in Maven Repository? following

amy

/milestone/lt;/uclgt;
lt;/repositorygt;
And the following dependency descriptor for the webflow jars:Code:
lt;dependencygt;
lt;groupIdgt;org..webflowlt;/groupIdgt;
lt;artifactIdgt;spring-faceslt;/artifactIdgt;
lt;versiongt;2.0.0.RC1lt;/versiongt;
lt;/dependencygt;
lt;dependencygt;
lt;groupIdgt;org..webflowlt;/groupIdgt;
lt;artifactIdgt;spring-webflowlt;/artifactIdgt;
lt;versiongt;2.0.0.RC1lt;/versiongt;
lt;/dependencygt;
lt;dependencygt;
lt;groupIdgt;org..webflowlt;/groupIdgt;
lt;artifactIdgt;spring-bindinglt;/artifactIdgt;
lt;versiongt;2.0.0.RC1lt;/versiongt;
lt;/dependencygt;
lt;dependencygt;
lt;groupIdgt;org..webflowlt;/groupIdgt;
lt;artifactIdgt;spring-jslt;/artifactIdgt;
lt;versiongt;2.0.0.RC1lt;/versiongt;
lt;/dependencygt;
Thanks,
Pedro Casagrande de Campos

Yes, this is a known issue that will be addressed shortly for Maven users.  Thank you for the report.  Will let you know when the 2.0.0.RC1 poms are updated (will be today).

Keith

The updated maven poms have now been uploaded to the milestone repository.  Clear the previous version from your local maven cache and try building again.


Originally Posted by jeremyg484The updated maven poms have now been uploaded to the milestone repository.  Clear the previous version from your local maven cache and try building again.

I removed all the exclusion that I added. All worked except the following dependency:Code:
lt;exclusiongt;
lt;groupIdgt;org.apachelt;/groupIdgt;
lt;artifactIdgt;commons-logginglt;/artifactIdgt;
lt;/exclusiongt;
I've added the following dependency to replace the above exclusion:Code:
lt;dependencygt;
lt;groupIdgt;commons-logginglt;/groupIdgt;
lt;artifactIdgt;commons-logginglt;/artifactIdgt;
lt;versiongt;1.1.1lt;/versiongt;
lt;/dependencygtedro,

Any idea why this didn't work? We didn't have any problems in our tests, and there is no mention of org.apache anywhere in the POMs on-line I can find.  Can you send us a more detailed output of the error when it happens, if it is still happening?

Keith

Keith,Sorry Keith, everything seems to be working nice now, maybe it was some problem on the cache. I'm not sure.Thanks,
Pedro Casagrande de Campos