The main difference is that 2.7 is available on maven central,
whereas 2.5 is on the wocommunity server.
2.7 is also built with other dependencies moved to maven central,
woenvironment and woproject-ant-tasks. You can see the pom.xml for
the 2.7 in the central branch for differences.
https://github.com/wocommunity/wolifecycle-maven-plugin/blob/central/pom.xml
They're basically the same thing, for now... :) I'm working on
jigsaw packaging and will likely need to update where it puts
resources in the future. Since original NSBundles all put a top
level /Resources directory in the jar, that is seen as a split
package. I'm planning to relocate them into
/META-INF/webobjects/Resources for a new release of webobjects and
wonder.
I have more work to do, but I have just successfully launched the
first fully modular webobjects application for the first time.
https://github.com/nullterminated/SimpleWOApp/tree/modular-webobjects
Happy Halloween from Japan,
Ramsey
On 10/30/25 9:28 AM, Paul Hoadley
wrote:
Hi Ricardo,
I’ve seen Wonder seems to use this plugin:
<plugin>
<groupId>org.wocommunity</groupI>
<artifactId>wolifecycle-maven-plugin</artifactId>
<version>2.5</version>
</plugin>
But I’ve also seen in the SimpleWOApp from Ramsey this
one:
<plugin>
<groupId>io.github.wocommunity</groupI>
<artifactId>wolifecycle-maven-plugin</artifactId>
<version>2.7</version>
</plugin>
This one the version is 2.7. Does anybody know the
differences between these two? Which one should we use?
The latest here is 2.5, and that's what we're using:
Also, our projects still use the Fluffy Bunny layout:
Sources/
Resources/
WebServerResources/
…
When the frameworks build I noticed that the .jar file is
not including the Resources folder which is causing some
exceptions. Should Resources be included inside the .jar
file?
Yes. You can get Maven to build from Fluffy Bunny layout
(Wonder is still organised this way—check out the POMs there
if you want to do this), but converting to standard Maven
layout is easy. This should still work:
Also, the application seems to be built with all
Frameworks embedded within the app. What determines
whether or not frameworks are embedded in the application?
There's no such option. The Maven-built bundle is
self-contained and ready to run.
