You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are some problems with rebuilding the plugin.
First, if you have a custom versions of both the plugin and Launch4j and you upload it to your own repo, then try to build a simple demo on another machine it doesn't recognize Launch4j from custom repo. It's there on the disk, but gets ignored.
Second, the LocalArtifactResult.getFile() returns expanded versions, contrary to the comments. I assume it was a bug in Maven that got fixed in the meantime. It resulted in Launch4j being unable to locate one of the exe files.
Here are the quick fixes for both Lilianne-Blaze@7088cf4
The relevant parts are in Launch4jMojo unpackWorkDir lines 546-628
The tests were on Maven 3.9.1, Liberica JDK 21, Windows 11/10.
The text was updated successfully, but these errors were encountered:
There are some problems with rebuilding the plugin.
First, if you have a custom versions of both the plugin and Launch4j and you upload it to your own repo, then try to build a simple demo on another machine it doesn't recognize Launch4j from custom repo. It's there on the disk, but gets ignored.
Second, the LocalArtifactResult.getFile() returns expanded versions, contrary to the comments. I assume it was a bug in Maven that got fixed in the meantime. It resulted in Launch4j being unable to locate one of the exe files.
Here are the quick fixes for both
Lilianne-Blaze@7088cf4
The relevant parts are in Launch4jMojo unpackWorkDir lines 546-628
The tests were on Maven 3.9.1, Liberica JDK 21, Windows 11/10.
The text was updated successfully, but these errors were encountered: