Hi Ricardo,
you need to set a configuration parameter on the wolifecycle plugin in your
pom to have it flatten the component folder structure on build.
I have no idea why this isn't the default.
<configuration>
<flattenComponents>true</flattenComponents>
</configuration>
Cheers,
- huig
> On 5 Nov 2025, at 20:04, Ricardo Parada via Webobjects-dev
> <[email protected]> wrote:
>
> Hello all,
>
> I’m trying to figure out why some components render no html.
>
> The component lives in the project folder under
> Components/ClaimsProfessional/ClaimHome/ClaimHome.wo
>
> Prior to maven conversion I can see the component is copied to a build
> folder, something like this
> …/build/ClaimComponents.framework/Resources/ClaimHome.wo
>
> And when I debug in Eclipse I see the WOComponentDefinition constructor gets
> called with the path to that file.
>
> In other words it seems like *all* components have been put together under
> Resources folder after it builds the framework which is okay with me.
>
> Now, when I build with maven and look inside the jar file for the framework
> where the component resides I noticed that the components are not flattened.
> The hierarchy of folders is preserved, e.g.
> Resources/ClaimsProfessional/ClaimHome/ClaimHome.wo.
>
> Anyways, I’m not sure if that is the reason why some components render no
> html but my guess is that it is because otherwise WebObjects would have to do
> a recursive search.
>
> If anyone knows whether it is okay for maven to preserve the hierarchy of
> folders under Components or whether it is supposed to copy all components and
> put them together under Resources please let me know.
>
> Thank you
> Ricardo Parada
