I've been spending time trying to update as many dependencies to the 
latest version available via the upstream repositories. I'm having 
troubles tracking down where some older versions of a dependency gets 
pulled in. I am using the "makerpm.sh" script. At compile time, it seems 
everything is using the correct dependency, but when the rpm's are 
built, older versions of libraries are added in. They also exist in the 
tar.gz file built in target/rpm/BUILD/opennms*/target/.

1. There are different versions of the same library in 
/opt/opennms/lib/  and /opt/opennms/system/...
2. There are different versions of the same library in /opt/opennms/lib/ 
and /opt/opennms/jetty-webapps/opennms-remoting/webstart/.

Running a "./compile.pl dependency:tree" and "./assemble.pl 
dependency:tree" does not show me why these older versions get picked 
up. Any suggestions on how to track these down?

Ron




------------------------------------------------------------------------------
AlienVault Unified Security Management (USM) platform delivers complete
security visibility with the essential security capabilities. Easily and
efficiently configure, manage, and operate all of your security controls
from a single console and one unified framework. Download a free trial.
http://p.sf.net/sfu/alienvault_d2d
_______________________________________________
Please read the OpenNMS Mailing List FAQ:
http://www.opennms.org/index.php/Mailing_List_FAQ

opennms-devel mailing list

To *unsubscribe* or change your subscription options, see the bottom of this 
page:
https://lists.sourceforge.net/lists/listinfo/opennms-devel

Reply via email to