I am trying to set the property value to DirectorySearch result. It is working fine for absolute path like Path='C:\Program Files\SampleDir'.But it is failing if I use path like Path='[INSTALLDIR]'.
What I observed in case of path=[INSTALLDIR] it is searching for the file in C drive itself.But here [INSTALLDIR] original value is 'C:\Program Files\SampleDir'.If I change the Depth=2 then it is working fine. Whatever the property that I mention in Path attribute it is searching in C drive only.But it is working fine with absolute value of Path like Path='C:\Program Files\SampleDir'.
The code that I am using is
<Property Id='BACKUPFILESEXIST' Secure='yes' Value='ABC'>
<DirectorySearch Id='DirSearch' Path='[INSTALLDIR]' Depth='0' AssignToProperty='yes'>
<FileSearch Id='FileSearch' Name='EncodeDateAction.dll'/>
</DirectorySearch>
</Property>
Related
I try rewrite the source file path to ~/src/lib by using fdebug-prefix-map.
I can confirm DW_AT_decl_file is rewritten to something like ~/src/lib/path.
But the result is lldb can't find the source file. If I change to a absolute path, it works fine.
How can I solve this?
You can use the target.source-map setting to remap location of source files. From (lldb) apropos source-map:
Source path remappings are used to track the change of location between a source file when built, and where it exists on the current system. It consists of an array of duples, the first element of each duple is some part (starting at the root) of the path to the file when it was built, and the second is where the remainder of the original build hierarchy is rooted on the local system. Each element of the array is checked in order and the first one that results in a match wins.
The usage looks something like:
(lldb) settings append target.source-map /foo /bar
Note that you use append here instead of set, because otherwise you'd overwrite the mapping every time you add an entry. You can check the mapping with:
(lldb) settings show target.source-map
I am using nar-maven-plugin to build my c++ projects,everything is OK, the only problem is that the output is located at
..\target\nar\socketutility-1.0.0-SNAPSHOT-amd64-Windows-gpp-shared\lib\amd64-Windows-gpp\shared
This is a long path, I have two questions for this:
can this path be represented by one variable like ${project.xx}?
can I customize this path?
Sorry if it's a repeat question. I couldn't find the answer anywhere.
My java application expects a password through an environment variable.
My staging environment doesn't have any password setup. How can I send a null value to the java application through env variable?
export pass=
If I put the above ^ in my ~/.bash_rc file, it isn't working.
EDIT :
I'm using spring & hibernate and taking the value in the XML. Something like the below:
<bean id="myclass" class="mu.package.Myclass">
<constructor-arg index="0" value="${pass}"/>
</bean>
If I replace ${pass} with ${pass:#{null}} to handle null checks with spel, it always takes the null value because the value is not present as a property but as an env variable. Is it possible for ${pass:#{null}} to check both properties & env variable before assigning null value?
Make sure your configuration has defined a PropertyPlaceHolder element in the XML:
<context:property-placeholder />
Then you simply need to make sure that by setting up the system environment variable that it is named exactly the same as your XML configuration expects for it to be translated.
Whenever I use the -lpf parameter with the pmcmd command, the workflow runs perfectly fine but when I add the same path in the Parameter FileName under Workflow 'Properties' and try to execute the workflow from the Workflow Manager, I get an error saying that parameter file is not found.
Now, the path which I am giving for '-lpf' is :
/apps/config/informatica/param.txt.
I don't understand why it works when I am overriding the parameter file name, whereas it doesn't work when I add it in the workflow properties (the file is not found).
By default, is any Informatica Environment variable set which needs to be changed and what's the default path of the parameter file on server and can this be changed?
Could you provide the log file?
Assuming I did understand this:
when you run the workflow with the parameter file -lpf that has this path:
/apps/config/informatica/param.txt
it does work, instead when you run it manually does not.
it could be so simply that manually you have to put instead of the extended path the string $PMSourceFileDir\ in the Source file Directory or to put it better: Source file Directory = $PMSourceFileDir\.
That because $PMSourceFileDir refer to the Informatica server initialization, as it is a server variable.
Instead with a parameter file usually is used to override that "deafult" path.
I am invoking VSDBCMD.EXE in my build process template, there is a custom setvar parameter that requires a reference to the current source directory, passing this path has become an unexpected challenge.
I've tried using relative paths and $(SourceDirectory) to no avail (it remains as the literal string "$(SourceDirectory)" when I see the debug output), the parameter needs an absolute path.
Is there any way to get the absolute path for the current source directory when the script runs?
In the DefaultTemplate build workflow there is a variable called SourcesDirectory that contains the absolute path.
If you pass it to an InvokeProcess you just type the variable name in the activity property, no $() around it.
It might be worth checking out this resource, where author makes use of ConvertWorkspaceItem within his build in order to pass in a string the disk location of a know target in source control