Making the version99 repo work with Nexus is particularly important because you don't really want to expose a repo like veersion99 without some sort of management in front. The version99 repo is deployed over several machines but not dimensioned to handle millions of requests (not that version99 repo is anywhere near saturation).
So, I am quite interested to see this fixed. On 23.12.2011 03:19, jsw wrote:
Provided scope works correctly on command-line, but eclipse includes it in the classpath at compile time, according to this: http://www.slf4j.org/faq.html#maven2 jeff On Thu, Dec 22, 2011 at 6:14 PM, Rusty Wright <[email protected] <mailto:[email protected]>> wrote: Is version99 still needed? I thought you could avoid that hack by using the provided scope. This is what I have in my pom.xml: <dependency> <groupId>commons-logging</groupId> <artifactId>commons-logging</artifactId> <version>1.1.1</version> <scope>provided</scope> </dependency> <dependency> <groupId>commons-logging</groupId> <artifactId>commons-logging-api</artifactId> <version>1.1</version> <scope>provided</scope> </dependency> http://lumpynose.wordpress.com/ On 2011-12-12 09:04, jsw wrote:Hi, Has anyone has gotten the version99 repository setup with nexus? I am unable to pull dependencies from this repo via nexus. From the nexus console I can browse remote, but nothing shows up in browse storage or browse index. Repository ID: version99 Repository Name: Version99 Repository Type: proxy Repository Policy: Release Repository Format: maven2 Contained in groups: Remote URL: http://version99.qos.ch/ thanks, jeff
-- Ceki http://twitter.com/#!/ceki _______________________________________________ slf4j-user mailing list [email protected] http://mailman.qos.ch/mailman/listinfo/slf4j-user
