RocketHacker Posted September 4, 2013 Report Share Posted September 4, 2013 ok. lets see if i can explain this clearly... i am trying to build A.vi into package A.vip. A.vi has a dependency on B.vi B.vi is not in the same folder as A.vi or the .vipb file for A.vip B.vi has a dependency on C.vip In the .vipb for A.vi, when i click "scan for dependency changes", C.vip is not detected as a dependency when A.vip is built, NO files from C.vip are included The workaround is to manually include C.vip as a dependency, but then why am i buying the pro version... is this expected behavior? Link to comment Share on other sites More sharing options...
Michael Aivaliotis Posted September 6, 2013 Report Share Posted September 6, 2013 Thanks for bringing this up to the forefront. It's a known issue that we have not resolved yet. Also reported here: http://forums.jki.net/topic/1619-bug-secondary-dependencies-not-included-as-internal-dependencies Link to comment Share on other sites More sharing options...
RocketHacker Posted September 10, 2013 Author Report Share Posted September 10, 2013 Good to hear that you're familiar with the issue! We're starting to migrate our 3k++ VIs into VI packages. This bug is a near-blocker for us at the moment. We can work around it, but it is going to add extra steps to our package validation process and increase the likelihood of bad packages getting out into the wild (and make VIPM look bad ). We'd appreciate any efforts you could put toward getting this one resolved. let us know if you need any more information or need us to do any beta testing. Thanks! Link to comment Share on other sites More sharing options...
Michael Aivaliotis Posted September 20, 2013 Report Share Posted September 20, 2013 I looked closer at this issue reported by JGCode in the thread referenced. That specific issue is actually fixed, so I'm sorry for the confusion. Your issue might be slightly different. Could you attach some example code that reproduces this issue? Also describe your workflow. Link to comment Share on other sites More sharing options...
RocketHacker Posted September 24, 2013 Author Report Share Posted September 24, 2013 here is a set of files exhibiting the bug. steps: extract all files open package\.vipb goto "package dependencies" scan for dependency changes notice how no dependencies are detected this project has a package dependency on open g time library i'm using VIPM 2013.0.0.1893 my workflow would ideally not allow secondary dependencies like this, but since i am migrating 3k VIs into a hundred or so packages, it is something i'll have to transition through. my migration plan is: build every tool into a package. leaving all dependencies linked to source code switch over applications to use packages update all tools to point from dependency source code to dependency packages (this will take some time) NoDetectSecondDependency.zip Link to comment Share on other sites More sharing options...
Michael Aivaliotis Posted September 27, 2013 Report Share Posted September 27, 2013 RocketHacker, please submit a support ticket for this. I may have a fix for you: http://support.jki.net/anonymous_requests/new Link to comment Share on other sites More sharing options...
Michael Aivaliotis Posted October 4, 2013 Report Share Posted October 4, 2013 Just to follow up for others that may read this. We have now fixed this and a version of VIPM that contains this fix is available from the VIPM Labs. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.