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
In 1.6.6 (commit 8ae84d5) the target directory of wr4j-generated runnable jar was changed from libsFolder to appFolder. 1.6.6 release message doesn't mention it. I know it's been 3 years, but is there a specific reason why that change was implemented? Is there a way to change this behavior in the latest version?
I am trying to upgrade an older maven project. I could edit ini.vtl to account for one more classpath, but it is still kind of odd that there is just this 1 jar that is being copied differently from all of the other jars that go into libs\ with copyDependencies.
The text was updated successfully, but these errors were encountered:
In 1.6.6 (commit 8ae84d5) the target directory of wr4j-generated runnable jar was changed from libsFolder to appFolder. 1.6.6 release message doesn't mention it. I know it's been 3 years, but is there a specific reason why that change was implemented? Is there a way to change this behavior in the latest version?
I am trying to upgrade an older maven project. I could edit ini.vtl to account for one more classpath, but it is still kind of odd that there is just this 1 jar that is being copied differently from all of the other jars that go into libs\ with copyDependencies.
The text was updated successfully, but these errors were encountered: