Post as a guest Name. It all works just dandy, but blows up in one obscure corner where we have a windows azure integration. When I switched the dependency to runtime scope, the error disappeared, but then our IDEs complains that the dependency isn't available, which is prohibitive. You will also see that the master branch of the Azure SDK project still has the explicit dependency on Jackson 1. Sign up using Facebook. Asked 4 years, 2 months ago. I used this pom. 
| Uploader: | Malkis |
| Date Added: | 6 June 2017 |
| File Size: | 58.2 Mb |
| Operating Systems: | Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X |
| Downloads: | 26842 |
| Price: | Free* [*Free Regsitration Required] |
I'm jackson-xc.9.9.jar to upgrade Jackson from 1. Email Required, but never shown. It seems the azure's dependency should just be automatically pulled in, as any other dependency is. How do we handle problem users?
Index of /repositories/central-m1/n/jars
Peter Pan Peter Pan Works fine for me. Any concerns, please feel free to let me know. It all works just dandy, but blows up in one obscure corner where we have a windows azure integration.
Sign up using Facebook. JavaJigs 10 10 bronze badges. Unicorn Meta Zoo 9: Can you compare with your POM to see if there is a mismatch somewhere? Though you need to use Jackson 2. When I switched the dependency to runtime scope, the error disappeared, but then our IDEs complains that the dependency isn't available, which is prohibitive. Jackaon-xc-1.9.9.jar Azure Service Bus has an explicit dependency on Jackson 1.
I'd understand the conflict if these were different versions of the same artifact, but my impression is that to maven these appear to be two different completely artifacts, so it should then be perfectly happy to pull both into the classpath simultaneously as I now have to do explicitly. I've tried including the old versions explicitly, and the error doesn't occur. When I tried to reproduce your failure with your first pom.
Active 4 years ago. This makes sense and meshes with what I've seen, but I guess my larger question still stands: Yep this still occurs with exclusions, unfortunately. This is the package list of my Eclipse project with maven. If you see my POM file, the 1. Using dependency management view of eclipse pom. Stack Overflow for Teams is a private, secure spot for you and your coworkers to find and share information.
Jackson-xc-1.9.9.jar as a guest Name.
Index of /nexus/content/repositories/central/org/codehaus/jackson/jackson-xc/1.9.9/
A big part of what I don't understand is why Maven doesn't simply pull in the right dependency for Azure jackson-xc-1.9.9.jr it's not technically a dependency convergence issue because the groupId and everything have changed from org. If you look at the source code for the class BrokerPropertiesMapper that throws the exception, you will see that it uses com. Sign up or log in Sign up using Google.
What's the best way to remedy it? jackson-xc-1.9.9jar
Index of /repositories/public/org/codehaus/jackson/jackson-xc/
No, sorry, I think I'm being unclear. Try to keep only fasterxml jackson version codehaus is an old version of Jackson. So to manage Java package dependency with maven, you just figure out azure package information, and maven will autoinstall azure dependency packages such as the old jacison-xc-1.9.9.jar packages of Jackson.
Upgrading Jackson maven jacoson-xc-1.9.9.jar issues Ask Question. Asked 4 years, 2 months ago. However, for the time being you are stuck with keeping Jackson 1. My question is why do both of these separate artifacts need to be explicitly specified?
No comments:
Post a Comment