Closed ingokegel closed 8 years ago
There is already a separate goal just for this. Configuration of which is fairly simple. Unsure the wrinkle about it calling system.exit() < 6.1 is worth it.
Ie:
<plugin>
<groupId>org.sonatype.install4j</groupId>
<artifactId>install4j-maven-plugin</artifactId>
<executions>
<execution>
<phase>package</phase>
<goals>
<goal>install-license</goal>
<goal>compile</goal>
</goals>
<configuration>
<projectFile>${project.basedir}/src/main/installer/whatever.install4j</projectFile>
<licenseKey>whatever</licenseKey>
</configuration>
</execution>
</executions>
</plugin>
vs:
<plugin>
<groupId>org.sonatype.install4j</groupId>
<artifactId>install4j-maven-plugin</artifactId>
<executions>
<execution>
<phase>package</phase>
<goals>
<goal>compile</goal>
</goals>
<configuration>
<projectFile>${project.basedir}/src/main/installer/whatever.install4j</projectFile>
<licenseKey>whatever</licenseKey>
</configuration>
</execution>
</executions>
</plugin>
Actually @ingokegel should ask, does this new behavior in 6.1 change now install4jc --license
works w/o any other arguments? Or in 6.1 does it now only work when trying to compile installer?
OK, I missed that this was already available. You can still specify only the --license argument and the command line compiler will exit after updating the licensing information.
In install4j 6.1, it will be possible to set the license key when invoking the command line compiler. The argument "--license" is recognized by earlier versions of install4j as well, where the compiler exits after updating the licensing information.