Files are not packed using wildcards if the filename starts with dot

Comments

2 comments

  • Avatar
    juanjo

    Could you try using the below?:

      <distributionDirectory  allowWildcards="1">
         <origin>/data/bitrock/demo/lib/{*,.*}</origin>
         <includeFiles>*/*</includeFiles>
      </distributionDirectory>
    
  • Avatar
    the7trumpets

    I tried this on a distribution file list as below:

    <folder>
        <description>Development Sources</description>
        <destination>${installdir}/Sources</destination>
        <name>sources</name>
        <platforms>all</platforms>
        <distributionFileList>
            <distributionFile>
                <allowWildcards>1</allowWildcards>
                <origin>${build_project_directory}/../../source/{*,.*}</origin>
            </distributionFile>
    </folder>
    

    This resulted in installBuilder packing files which were in siblings of the /source/ directory, which was not intended. Finally, I tried this, which seemed to work as intended:

    <origin>{${build_project_directory}/../../source/*,.*}</origin>
    

    Is this the correct method?

    It seems crazy that there is no obvious or at least documented way to include dot or hidden files in a folder or matched file filter, given that many times hidden files are used for configuration data, which must be installed by an installer.

Please sign in to leave a comment.