Hello,
Yes, it is. I've found that putting the real path in the pom.xml
works fine, but I can't use a variable as the path. The problem I
have with putting it in the pom makes the pom very specific rather
then the settings.xml.
I'm open for other suggestions on how to accomplish the same thing.
Basically a profile which defines the build rules for NSIS installer
should only be run when a path to NSIS is defined in the settings.xml
file for the environment.
thanks,
-jr
On Nov 14, 2009, at 9:20 AM, Sony Antony wrote:
The <file>,exists> block was inside <activation> right ?
<profiles>
<profile>
...
<activation>
<file><exists>${nsis.path}</exists></file>
</activation>
...
<profile>
<profiles>
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
