Project Dependencies

Project Dependencies seem to be a lot of work at the moment especially as your unit of work becomes smaller.
If project A is dependent to project B currently I have to set A's properties to include B and also any dependencies that B has.
If someone creates project C and includes A now that person who knows nothing about A or B has to go back to all other subproject's and check off dependencies.
It would seem to me that since this is stored in the properties of each project that at a minimum the list could be initially created when project C selects A to be included ???

It isnt working that way for us in our adf-swing apps. If it is more then one deep then the designer finds it but when you run the project it dosnt find it during the load stage. So in each project we have had to make sure all dependencies are checked so the project can run correctly.

Similar Messages

Project dependencies in a Workspace (10g)

When I try to deploy something from a project, the IDE tries to compile all projects in that workspace, even if there are no dependencies between the projects. This means that I have to either remove the offending project(s) from the workspace or resolve all issues in all projects before deploying from any one of them.
Is this by design? I don't want to have to make a workspace per project to avoid this.

John
Make sure that there really are no dependencies.
In JDeveloper 10g Preview you can do a "Full Text Search" in the help on "About Project Dependencies" and you 'll see this is a "Topic Title".
In that topic there are sections about "Project-to-Project Dependency" and "Project-to-Profile Dependency". I hope it can help you, it confused me.
My conclusion until now : dependencies are not implemented very intuitively
success
-Jan

Project Dependencies on Jdeveloper

Hi all,
I'm wondering what is the difference between choosing "Build Output" or any other profile File on the Project Dependencies on Jdeveloper.
These question came to me because i tried to rename some classes from my application and only when I checked the "Build Output" option the refactor worked for all my projects on the app.
Thanks,
LC

Specifying dependency indicates the project is dependent on the project to which the dependency is defined.
+"Build Output" or any other profile File+
Specify the file on which the project is dependent.

Business Components Project Dependencies Problem

Hi everyone,
I have a workspace on 9i that has four projects. All of them use the Entity Objects contained on the first project. If i tell the other projects they depend on the first one (on Project Settings -> Project Dependencies), even so the View Objects i create cannot see the Entities created on the first project. Shouldn't it be possible to create a separate project for them? do i have to put the entire model (VO, EO, VL, AO) in one single package? is there any way to only reference the other project's EOs?
Thanks very much in advance!
Thiago Souza

That's a feature in 10.1.3, you need to add them specifically to your project to access them.

BPEL Build and Project Dependencies

Hi,
We are developing set of BPEL processes using jDeveloper 10.1.3.1
As part of this development, we want to develop set of utility classes which will be used in one or more of the BPEL processes using java embedding. Also these utility java classes make use of libraries like Oracle content services FDK etc.
For this we have created a project called BPELCommon and are writing the common java classes in this project and also created various project level library setting against this project. Then made the other BPEL project depend on this BPELCommon project using Project dependency settings.
However, when we try to build and deploy the BPEL processes using the automatically generated build.xml xml, it is failing to access and compile the classes and the project library files from the BPELCommon project.
Tried creating a pre-build.xml file which explicitly compiles the files from the BPELCommon/src folder into the BPELProcess1/output folder using libraries. It creates the classes under the BPELProcess1/output but still “bpelc” fails to access them and to bundle the project libraries into the BPEL Suitcase.
I believe this is pretty generic requirement since anyone developing more than one bpel process would always look for some code reusability.
Is there a way to change the build.xml to take care of project dependencies? ie to compile the java files from BPELCommon project and bundle the compiled classes along with the library jars while building the BPEL Suitcase?
regards - rutwik

One of the key goals doing SOA BPEL/ESB projects is creating an automated build system. Oracle SOA is not delivering this, but it gives you the tool do do so; like all the ANT stuff. So if you have your developed reusable, you must create your own build system. I wrote an article on this on my blog
http://orasoa.blogspot.com/2006/08/using-ant-in-bpel-environment.html
Marc

Project dependencies & WAR deployment bug

According to the help/manual (Getting Started / About JDeveloper / About project dependencies):
This project-to-project compile-time dependency also has an impact on deploy-time behavior. The project dependency guarantees that when you deploy Project A's profile, JDeveloper will deploy everything specified in the profile for Project A, as well as the complete contents of Project B.
This seems to work fine when deploying to a jar. When deploying to a WAR however, things are different. All files from project B are included in the deployment, except the classes that are used in project A. I would rather prefer the opposite...(to put it mildly)
Is this a known bug? Maybe there's a workaround?
Cheers Hans

bump

Project dependencies issue

I am having a problem locating & removing a dll dependency within my project. When the dependencies area loads I have a single dll that appears.The project lists the dll's path as dll_name.dll which confuses me because the path doesn't start with C:/ or D:/ or something which makes it hard to locate on my hard drive. Searching for the dll's callers brings up several VI's but these VI's never call the dll that is loaded into the dependencies. I'm running LabView 2010 on XP and the VI's are third party VI's used for interfacing with some hardware. If anyone knows how I can remove or locate this dll please let me know.

Sorry for the confusion. There was one dll of interest with 2 instances/paths loading into the project. One was moved out of the dependencies area and the 3rd party VI's that are used in my program call this dll correctly. The other dll was in the dependencies area and its only caller was my main VI which does not actually call the dll, nor do any of its SubVI's. I was able to fix this by modifying the dll location in a 3rd party VI which contained all of the other 3rd party VI's. My guess was that there was a weird dependence between one of the 3rd party polymorphic VIs used in my program.
In 8.6 I only had to include the main VI and let the project locate all other dependencies. I then built and ran the 8.6 executable and was able to correctly operate the hardware cards the software interfaces with.
Back in 2010 after the dll dependecy issue was resolved I then had an issue with running the actual executable. Yesterday running the executable was returning an error originating from the call library node which called the dll that was giving me problems before. This issue was fixed after receiving some updated files from the vendor.
Now I have a new problem. Upon running the executable I received a slew of errors regarding class method calling errors within the dll I was having dependency problems with earlier. Tomorrow I will install an updated software package supplied by the vendor and see if the issue can be resolved.
I'm going to have to check out that dependency walker program, thanks for the info!

Re: Project Dependencies on Jdeveloper

Dears,
Dependencies is not working and I cannot see the output of the another Projects after choosing "Build Output" !!! Kindly help

What specifically doesn't work? What behavior do you see?

Project not picking up changes in external sources

I have a flex project that's using a couple of other Flex
library projects as external sources... i have everything setup and
working nicely.
Except... if i make a change to one of the library projects
the flex project doesn't seem to pick it up... for a while... if i
add a log comment to my library project and build it, then run the
flex project i don't see the log... if i close down Flex 3 and
leave it for a bit, then open it and run it again... there it is...
if i close and immediately reopen i don't see it... seems like
something is being held in memory... but not sure if this is a Flex
issue or local to my installation/machine etc.
Anyone else seen anything like this?

Sounds like you are seeing a problem with project
dependencies, and possibly also slow compilation times. Would you
mind entering a bug at
http://bugs.adobe.com/jira ?
If you could zip up and attach the projects that reproduce
the problem, that will greatly help us investigate. However only
attach them via the bug form if it is code you don't mind the
public seeing. If you want to keep it private (but don't mind
sharing it with us internally), you can file the bug and email the
code to [email protected], including the bug number.
If you can't submit the code as-is, I understand, but if you
are able to strip it down to something basic / non-sensitive that
still reproduces the problem and submit that, it would be immensely
helpful.
Thanks much,
Tom

Project explorer doesn't show callers for .rtm (run time menu) files (is this a confirmed bug?)

Maybe I was to quick to report this as a bug... I was unable to find anything related to it at my normal sources of information. Does someone has exeperience with it?
I have a work-around and this is included in the description :
http://forums.ni.com/ni/board/message?board.id=BreakPoint&message.id=6776 (message 25)
** Original post **
When a library (.lvlib) that contains a file with a run-time-menu (.rtm) file is removed from the project, but there is still a file that uses this .rtm file, both the .lvlib and all of it's vis and the .rtm file are displayed in the project Dependencies.
For the Vi's the callers can be found by 'Find->calllers'. For the .rtm file this always results in 'No items found' but the .rtm file remains in the Dependencies (as it should since it is still used).
Finding the .rtm file can be hard since it is only loaded at run-time and not at edit time(?). If someone encounters this issue, a working method:
- rename the rtm file (so it cannot be found)
- open the vis that you suspect are using this file AND try to edit the run-time menu. When this vi uses the run-time menu a warning will appear (cannot load rtm file, using default menu instead)
Kind regards,
Mark

Dear Mr. Beuvink,
thank you for your reply. It seems that a while back this problem has been reported to our R&D group. The request (CAR) has ID; 41579. There is the following statement in this CAR: the caller vi is in memory or not. When a caller vi is in memory, rtm files will currently never report the vi as a caller. This confirms the behavior you are seeing.
I'm sorry to say I don't have a solution at this moment, at this moment they are busy fixing this problem. You can look this up in future release notes by searching on the CAR ID I mentioned.
If you haven any questions, please don't hesitate to contact me.
Best regards,
Martijn S
Applications Engineer
NI Netherlands

Saving Error in Project Server 2013, Need Help!

Hey All,
I am running into issues with a Projects saving from Project Pro 2013 to our Project Server 2013 Farm.
It is strange, when someone tries to save a project out of Project Pro 2013 to Project Server, it will run through the "Synchronizing Data to the Server", and then bombs out with error
Job Type: Save
Error ID:9000(0x2328)
The project could not be saved to the server, Etc..
My understanding is that this is a generic save error that could mean many things.
In the ULS logs under "Active Cache Save" , I am getting:
"Cancelling correlation 1339927b-e9e5-e311-941d-00155d2bc10d as save is an overwrite or resubmit"
What is strange at this point is if I check the project back in, and re-open/re-checkout the project, and try to save again, it is successful in saving.
Just a few details about the environment:
Project Server Version: 2013 RTM (In the process of upgrading)
SharePoint Version: 2013 RTM (In the process of upgrading)
Project Structure: One Master Project with all other projects being subprojects of the master
Published Status: All Published
SQL Version: SQL Server 2012 SP1
User Count: About 5 currently
Deployment: 1 WFE, 1 APP Server, 1 SQL Server
It is just odd, as it seems to be completely random. We have tried clearing caches out to see if that resolves it but it did not. It is just odd that it takes two saves for it to actually work correctly, and is problematic as the many times they are saving
from the master and it bombs out there.
I am not sure how it could be an issue as it is usually just a single user working on the individual subprojects.
Maybe it is an issue in the RTM? I couldn't find any info in any of the CU's or SP's that addresses this directly
Has anyone seen this, or have any suggestions?
MS Support has not been any help at all.
Thanks all

I have heard of issues with Master and Sub-Projects and both being published to Project Server, as a rule it is a feature I learnt to avoid as a result of bad experiences with earlier versions of Project Server.
Whilst this will not resolve the issue you have encountered the following suggestion may help you avoid pain in the future and leverages the potential of Project Server to represent common attributes for projects.
Typically a Master/Sub Project environment is intended to reflect projects that are commonly aligned - it is not unusual for a Master Project to represent a programme and for there to be multiple sub-projects forming the programme - there can be programme
level events that have multiple predecessors from multiple sub-projects.
Rather than create a master and sub-project situation I would suggest looking to define two Enterprise Custom Project fields to assist with such situations. The first being a Project Field called Programme that has a look up table with a list of current
programmes you can select from. The second Project Field would be a Programme Status Field with an associated lookup table with 3 values, Master, Sub-Project, Standalone.
You can have a project represent the Master (Programme) project and open it and all sub-projects in the programme (albeit this would have to be a one by one action to begin with). With all the projects open go and open a New Window in Project Professional
and elect to include all the open projects in the new window - this will create a new project with all the selected projects showing as
"embedded objects" and then create dependencies from sub-projects to programme level events in the Master Project (I would suggest what I call
"one way traffic" when creating "cross project dependencies" to avoid further headaches). Close the project, you will be prompted to save changes which you should do but do not save the new window
"container" project. The dependencies across the projects will persist - in each project you will be able to see external successors - tasks in the master project. In the master project you will be able to see external predecessors.
In PWA you can create Project Centre Programme views that filter to exclude projects that ARE Standalone and group them by Programme and sort by Programme Status Field - this will ensure that the "Master" sits at the top of the pile for each programme grouping.
Just a suggestion - I hope the issue you have encountered is resolved soon.
Dominic Moss | MAPM Microsoft Certified Technology Specialist | Our Newsletter:
PM News Project Server Specialists
Project Server PRIME | Twitter:
@Twitter | Facebook:
@Facebook | Linkedin:
Wellingtone

Find xctl in VI's dependencies

Hello everybody,
I am trying to find programatically all the subVI's used in a VI and save them together in the same folder.
I did that using Get VI Dependencies Invoke Method. It works with VIs, ctl, llb and lvlib (I can get their names and paths).
But if the VI contains an xctl, it doesn't appear in the Dependency Names and Dependency Paths.
Do you know how can I get programatically the path to an xctl used in a VI?
Thank's
Solved!
Go to Solution.

Hi,
Even i have tried this with the invoke node. Didn't work for me as well. I am not sure what is the correct solution for this question. But what I did was, I made a project with the VI containing the x-control and then i took the Project Dependencies using the invoke node. This returns the x-control name and path. I hope this helps you in some way.
Regards,
NitzZ
(Give Kudos to good Answers, Mark it as a Solution if your problem is Solved)

Can't replace a stale dependency in a LV project with correct dependency?

I have a LV project which contains a VI called "Main_Panel.vi". there is a typedef which it is depends on (let's call it typedefAversion1). I had to move the file which defines typedefAversion1 to another location in the file system. Let's call the moved typedef "typedefAversion2".
Everytime I open the project, it complains that it can't find typedefAversion1. I tell it where to find typedefAversion2 and then it is happy - until the next time that I open the project. Then it complains again.
I've tried locating typedefAversion1 in the "dependencies" tree in the LV project and right-clicking and selecting "replace with", then pointing it to typedefAversion2. All that happens is that typedefAversion1 disappears from the project dependencies for an instant, then re-appears. Why is it still in the dependency tree when I just told it to get replaced?
Note that I cannot simply update "Main_Panel.vi" by manually replacing the typedef in the VI with the new one - this typedef is found in hundreds of locations throughout my project, and in many VIs.
what is a quick and simple way to tell labview to stop looking for typedefVersion1 and instead look for trpedefVersion2?

Did you add the type def to the project? Not just the dependencies. But part of the actual project. I would imagine that should cause a conflict if VIs are still looking for a type def of the same name in a different location. You then just have to resolve the conflicts. There is a nice little button in the project toolbar to do that.
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines

Cant specify the Java Build Path in the Web Module Project

hi,
I have a problem while specify the project dependencies in the Web Module Project.While opening the properties of the web module project i cant choose the Java Build Path.The only two options i have are design root path and web service consistency check builder.Does anybody know why its like that?do i hav to reinstall the SAP developer studio?
With regards,
Jaisamma Varghese

Hi Jaisamma,
I just tested this, and for me it works as expected, within all explorer/navigator views.
Before reinstalling NWDS, check if the project itself may have some problem. Just create a new clean web module project and right-click on the project and try to access the BuildPath properties now. If it works, try to set up your project content again within this new project. Otherwise reinstalling NWDS may help.
Hope it helps
Detlev
PS: Please consider rewarding points for helpful answers on SDN. Thanks in advance!

Labview 8.5 project crashes when searching for callers of missing lvlib

I have done a search and reviewed previously reported crashes with LV8.5, but did not find a match to what I'm seeing.
SYNOPSIS: When selecting Find > Callers, under the project Dependencies, LV crashes as shown in the image below.
I created a new project and "borrowed" some vi's from another project. Disconnected all vi's from previous libraries and proceeded to develop code last night. All seemed well.
This morning, as I opened the project to continue coding, it complained about a missing lvlib, the one items were "borrowed" from. No big deal, I'll just look at the dependencies and find out which one I missed. When doing the search, the program crashes immediately. Repeated a number of times with the same result. Verified system performance and memory useage, minimal change when opening the project or attempting to do the search.
I will attempt a workaround, but I am curious if others have seen this as well.
I'll wait before reporting this as a "bug", until more info is gathered on this..
By the way, the original lvlib was NOT deleted, removed, moved, renamed as the error suggests.. LV actually knows where it is because it finds the directory when doing the search..
I know the routine, "simply re-install LV8.5", but I'm trying to understand more of what's gooing on and how we can avoid this.. I remember LV8.2 was crashing a lot at the beginning, then for no apparent reason, it became stable, and now I can't remember the last time it crashed.. Do others observe the same thing? LV gets more stable with time?? LOL! A program with personality. Will LV turn into HAL? LOL!!
Here's the picture:
Message Edited by JoeLabView on 02-13-2008 08:35 AM
Attachments:
LV8.5ProjectCrash.PNG ‏38 KB

Good morning Jennifer,
I'll try to re-create the events from memory.
OS: Win-XP Pro - SP2
1. Opened library of VI's from Agilent E4440A drivers. Opened the "Tree.vi" to look at available vi's. Copied (pasted) some of the vi's into a new folder.   This may be important: I deleted the folder that contained the original library. (Actually, the zipped file was moved to a storage location). This means LV has no idea where to find the original library.
2. Opened all freshly copied VI at the new folder location. They all complained about not finding the .lvlib file. Ignored the error and disconnected every vi from the library and saved them. All except for one which was polymorphic and I didn't need it. I forgot to delete it at this time.
3. Created a new folder (real) within the directory structure of an existing project which uses an lvlib. Moved the disconnected vi's into this folder.
4. Opened the project and added the folder to the project, thus creating the virtual folder and files that were in the folder. All this was added to the library.
Note.. I can't remember the exact steps below, but they were something close to what I describe.
5. Cannot remember if I closed the project then opened it, but I do remember seeing a message complaining that one VI could not find the lvlib (the one from Agilent).
6. Looked into the folder and examined the saved date, which quickly led to the polymorphic VI that was still part of the original library. Since I was not sure if I wanted to use it later, I simply changed the extention from .vi to ._vi_.
7. Did some work, saved everything. Closed the project..
8. Opened the project and got an error message about a missing .lvlib. Again looking for the original Agilent lib. Remember that I had deleted the original library, it's folder, etc. (step 1).
9. Everytime I would open the project, I would get the error message. I ignore it and continue working. Since I don't like errors , I looked at the dependencies to find out what I missed. At this time, the file with the ._vi_ extension was still in the folder. I had forgotten about it and didn't realize that LV would pick it up.
10. In the dependencies tree, I right-clicked the error message and selected "Find>Callers", as shown in the attached image of the original post. Got the crash message. I repeated this 4 times. Rebooted the PC, and repeated it twice. All the same result >> Crash.   I may have saved a copy of the "crash" report, although I doubt it... I didn't bother sending the report to MS; because, well, I don't have much credibility over what those guys do at MS.
11. Looked at the folder to go through every VI to find out which one was still connected to the library. None of them were.
12. Noticed the ._vi_, and figured there would be no harm to delete it. Deleted it. It resolved the dependencies, thus no more error, no more crash.
I am actually surprised that LV project also looks into non-DOTvi files for dependencies. I imagined that it would ignore anything non-Labview known extentions. This is definitely good to know. However, the crash was a bit unexpected.
I will look for error logs. If I have time, I may try to repeat this on my PC and send logs. It will have to wait until I finish my surrent project (client / revenue)
Hope the above helps.
RayR

Project Dependencies

Similar Messages

Maybe you are looking for