Hi Ramsey,
I solved this situation by adding this line to build.properties file in each
project:
jvmOptions=--add-exports\=java.base/sun.security.action\=ALL-UNNAMED
for multiple arguments:
jvmOptions=--add-exports\=java.base/sun.security.action\=ALL-UNNAMED
--add-exports java.base/jdk.interna
Add something like this in the plugins section of your pom file. You
probably want to make sure your wolifecycle plugin is using the latest
version too (2.5).
org.apache.maven.plugins
maven-compiler-plugin
3.8.1
21
OK I’m almost there…. I picked up a settings.xml from an old machine that was
almost working… now I can create new WO Apps but they fail to launch with:
SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See http:
In order to use the wocommunity archetypes, you need to edit your
~/.m2/settings.xml and add the wocommunity repo before they'll work.
You can follow the instructions here,
https://github.com/wocommunity/webobjects-maven-archetypes
I'm going to try them out myself, I haven't used them since ve
OK I think I've almost got it but I’m missing something :(
How do I tell Eclipse-WOLips to use the archetype
I have the newest version of eclipse installed and I've used the WOLips update
URL:
http://wocommunity.github.io/wolips/repository/
My Java version
java -version
Hello everyone,
If the wobootstrap-maven-plugin and the WOInstall.jar got married and
had a baby, it would be the woinstall-maven-plugin. I'm pleased to
inform you that installing webobjects is now as easy as pasting the
following into your terminal,
mvn io.github.wocommunity:woinstall-maven
