Hi Ricardo, I'm guessing your decision is already made, but after migrating a few dozen projects to maven, I'd still like to sincerely recommend you fully embrace the Maven Stockholm Syndrome and migrate your projects to the standard maven layout. It might sound like a scary proposal for large projects but I don't think I'm lying when saying it will make your life easier in the long run (with the caveat that things may have changed for the better — my Fluffy Bunny maven experiences are over a decade old).
As for the actual issue you asked about (bundle resource locations) I think what you're looking for are probably the *.patternset files in your project's woproject folder, like these... https://github.com/wocommunity/wonder/tree/master/Frameworks/Core/ERExtensions/woproject ..."resources.include" being the one defining the location of application resources. Cheers, - hugi > On 3 Nov 2025, at 14:33, Ricardo Parada via Webobjects-dev > <[email protected]> wrote: > > I think I’m making progress. > > Does the plugin need to be told where the resources are when using fluffy > bunny layout or does it detect fluffy bunny layout and looks in the Resources > folder automatically? > > I looked at the pom.xml file in the ERPrototypes framework and the only > fluffy bunny related thing I see is: > > <sourceDirectory>Sources</sourceDirectory> > > I also checked parent pom.xml files. > > How does the plugin know where to look? > > Thank you > > >> >> On Nov 2, 2025, at 4:26 AM, Ramsey Gurley <[email protected]> wrote: >> >> Sorry, I didn't mean to derail your thread in my excitement. Yes, you >> should be getting a /Resources directory inside your framework jars. That's >> where NSBundle is going to look for an Info.plist. If it doesn't find one, >> it won't consider it a framework. >> On 11/2/25 4:18 AM, Ricardo Parada wrote: >>> Thank you Paul and Ramsey. >>> >>> That modular approach sounds interesting but I’m still struggling getting >>> my app to run after converting it to maven. >>> >>> I’ll summarize in a separate email. >>> >>> Thank you >>> >>>> On Oct 30, 2025, at 9:16 PM, Ramsey Gurley <[email protected]> wrote: >>>> >>>> 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, >>>>> >>>>> On 26 Oct 2025, at 00:07, Ricardo Parada via Webobjects-dev >>>>> <[email protected]> wrote: >>>>> >>>>>> 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: >>>>> >>>>> https://github.com/wocommunity/wolifecycle-maven-plugin >>>>> >>>>>> 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: >>>>> >>>>> https://gist.github.com/paulhoadley/cd15b90c94eb8c640fddd9ac3fbbc6dc >>>>> >>>>>> 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. >>>>> >>>>> >>>>> -- >>>>> Paul Hoadley >>>>> https://logicsquad.net/ >>>>> https://www.linkedin.com/company/logic-squad/ >>>>>
