Is there a way to exclude a folder that is located under a dynamic link in InstallShield?
So I have a dynamic link that starts at PATH A, and the following is a small example directory structure:
PATH A
--- PATH B
--- PATH C (which contains files)
--- PATH D (which contains files)
--- PATH E (which contains files)
--- PATH F
--- PATH G (which contains files)
Currently I have a dynamic link that starts at PATH A, includes sub directories, and uses a *.* wild card with some explicit file exclusions.
What I want to do now is to completely exclude a directory, for example completely exclude PATH F from the above example directory structure.
There is no - way.
I've been trying to do this since InstallShield 6. They're at InstallShield 15 now, and you still can't do it. If you use Subversion and are concerned about about .svn directories, you could solve the problem the way I did: have your build process do an svn export to an intermediate directory before building.
Related
I have files that i want to add to svn that are inside a number of nested sub folders. All the subfolder tree is still unversioned.
Say i want to version file1 and file2 (but not file 3) inside subsubfolder and no other file inside subfolder (i.e. file0).
The current filesystem is as follows
trunk
|--subfolder
|--file0
|--subsubfolder
|--file1
|--file2
|--file3
Trunk is versioned, subfolder and subsubfolder are not versioned.
svn add /subfolder/subsubfolder/file1
gives
svn: warning: W155010: The node 'trunk/subfolder/subsubfolder' was not found.
svn: E200009: Could not add all targets because some targets don't exist
svn: E200009: Illegal target for the requested operation
I wonder if there is a quick, potentially one-liner, command to add those files instead of going through adding all the subfolders along the way (without adding their content) and then finally adding the files.
Use the --parents option. Here is an example:
svn add --parents /subfolder/subsubfolder/file1
I have a placeholder which will be fed by a string value. The string value represents a path to some directory name. In that directory there are different ".jpg" files. How can I ask TensorFlow to list all of those files?
In other words, I want to add a node to my computation graph which will result in listing the directory, if I run it through my session. Is there a way to do that?
You can do this either using or not TensorFlow. I will only show you how you can list all files in a certain directory using TensorFlow, using tf.gfile.ListDirectory. You don't even need placeholders (in this case).
import tensorflow as tf
dir_path = "."
print(tf.gfile.ListDirectory(dir_path))
I have a Directory with many sub-directories in it including one named as OLD. This OLD folder could also be inside any of the sub directories and contains archived files.
Root Directory A
SUB-DIRECTORY A
file1.txt
file2.txt
SUB-DIRECTORY B
file1.txt
file2.txt
OLD
SUB-DIRECTORY C
file1.txt
file2.txt
SUB-DIRECTORY D
file1.txt
OLD
SUB-SUB-DIRECTORY E
file7.txt
OLD
I need to create a job in Talend which shall look for all OLD folders (in main and in sub directory both) and delete the files from that folder. I can use tFilelist to and mask the files to be deleted. But unable to figure out how to configure the job to look for OLD folder in all sub directories and delete those files also.
What you need to do is in the tFileList put your main folder choose check box include sub directories and in the FileList type drop down list choose Directories. Your file mask should be "OLD" or if it is anything more "OLD".
Iterate and use the parameter ((String)globalMap.get("tFileList_1_CURRENT_FILEPATH"))
to capture your sub directories. Now you can use this folder path in a tFileDelete Which can also delete folders
follow below approach..
Add tFileList and configure to Travers over all the directories.
now use if conndition connection from tFileList
Add tJava and connect with iterator connection
Add tFileDelete after tJava and connect with IF condition.
Add below condition inside if condition.
((String)globalMap.get("tFileList_2_CURRENT_FILEPATH")).contains("OLD")
Now you will get the all files from all the directories above code will give pass to the files which has the "OLD" in there file path.
I have not tested but you can try it.
I do not want the full path names to appear in the include dependency graphs generated by Doxygen. Thus, I set FULL_PATH_NAMES = NO in my *.doxyfile, and the labels of header files in the dependency graph changed from /really/long/path/to/source/tree/Directory 3/Directory 3B/File 3B-1.h to simply File 3B-1.h, which is what I want.
However, upon doing this, Doxygen changed the way it displays the File List. Instead of consisting of a graphical, collapsible directory tree with multiple display levels like the following...
+ Directory 1
+ Directory 2
- Directory 3
+ Directory 3A
- Directory 3B
File 3B-1.h
File 3B-2.h
File 3-1
File 3-2
+ Directory 4
... it switched to a completely flattened display with files listed like the following...
/Directory 3/File 3-1
/Directory 3/File 3-2
/Directory 3/Directory 3B/File 3B-1.h
/Directory 3/Directory 3B/File 3B-2.h
Is there a way to change the behavior so that files in the dependency graphs appear as described in the first paragraph, but the File List appears as a directory tree?
One way of partially achieving the functionality I'm looking for is to set FULL_PATH_NAMES = YES in the config file, and then set STRIP_FROM_PATH = /really/long/path/to/source/tree/.
This keeps the file list like I want it, but the header files in the dependency diagrams are now shown as Directory 3/Directory 3B/File 3B-1.h instead of just File 3B-1.h like I want.
I had the same problem and setting STRIP_FROM_INC_PATH = src/ with FULL_PATH_NAMES = YES achieves the same result without having to set STRIP_FROM_PATH to an absolute path.
I am using input as INPUT = ../src so files are listed this way:
- src
+ Directory 1
- Directory 2
File 1
File 2
Have follwong chunk from pom.xml:
<systemProperty>
<name>axis2.config</name>
<value>file:${project.build.directory}/../../axis2.properties</value>
</systemProperty>
what does syntax for value tag mean?
/../ - is id cd .. and forwards to parent directory?
short: ../ means parent direcory
long version:
file: specifies, that the following
content should be interpreted as a
file path.
${project.build.directory} is a
variable which will be replaced by
the runtime with the actual project
build directory
/ are folder separators
.. means parent folder
axis2.properties is the name of the
properties file
if you want to display the path for debugging purposes you might want to have a look at this:
http://www.avajava.com/tutorials/lessons/how-do-i-display-the-value-of-a-pom-xml-element.html
or
maven ant echoproperties task
Yes, it's a relative path to the project build directory, and go upper (in parent) two times.
In other words: it's the parent directory of the directory that contain your project build directory ;)
Source: Maven Properties Guide