02-23-2010 10:10 AM
I have been looking at how to effectively share a RIM library across multiple applications. Everything works fine, but the main problem is that when another application is installed that uses the same shared library as an existing application, the installation process warns continuously about potential conflicting libraries even though they are the exact same shared library binary. While this works fine, these kinds of messages are extremely confusing to users and would create a significant amount of support requests. Am I missing something here or is this just the way it is?
Do any of you attempt to create and share libraries? Are there alternate approaches to accomplish the same effective goal of sharing code across applications?
02-23-2010 10:14 AM
some libs are shared, like ksoap2 for example. i don't get any warnings on installation though, the old lib just gets replaced.
other libs, like my UI libs, are only used in eclipse. in the jde i add the classes so that they are included in the main software. this allows non-interface compliant changes.