Folks, I'm planning to investigate a fix for NPANDAY-411 that would allow us to specify versions as properties and successfully resolve the dependency transitively.
o https://issues.apache.org/jira/browse/NPANDAY-411 Based on previous discussions about the issue when it was originally reported, I understand that this behavioral difference occurs because we are approximating Maven dependency behavior in NPanday and that there is a longer-term perfect solution for this. I'd like to understand what might be involved in updating our diverged implementation to be more compliant, as well as better understanding what is involved in a complete uptake of full compatibility with Maven dependency management. Can anyone shed some light on this to help me understand where in the code I should be focusing attention? tc, -john. -- >|< Kaazing Corporation >|< John Fallows | CTO | +1.650.960.8148 444 Castro St, Suite 1100 | Mountain View, CA 94041, USA
