Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Variable replacement at compile time or run time? #16

Open
DavidPerezIngeniero opened this issue Feb 4, 2015 · 1 comment
Open

Variable replacement at compile time or run time? #16

DavidPerezIngeniero opened this issue Feb 4, 2015 · 1 comment

Comments

@DavidPerezIngeniero
Copy link

The doc states the following:

You can define any number of variables. If the plugin logic encounters a variable that isn’t defined, 
it simply replaces the variable reference with an empty string (like bash does).

But some variables like $INSTALL_PATH, aren't handled this way.

I have some variables that are entered by the user, like some custom destination directories:

        <fileset dir="tmp" targetdir="$dirWeb" override="true">
            <include name="js/**"/>
            <exclude name="js/**/*uncompressed*"/>
            <exclude name="js/build-report.txt"/>
            <exclude name="**/README"/>
        </fileset>

In this example, I don't want the variable $dirWeb to be replaced by a blank, but let IzPack do the substitution at run time. I need to be handled exactly like INSTALL_PATH.

How can this be done?

@DavidPerezIngeniero DavidPerezIngeniero changed the title Variable replacement Variable replacement at compile time or run time? Feb 4, 2015
@DavidPerezIngeniero
Copy link
Author

Byt playing a little, I've discovered the needed syntax:

fileset:
     includes: \$dirWeb

The dollar sign must be escaped with a backslash.

This SHOULD be documented.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant