Re: Maven build - webserver resources in frameworks
Re: Maven build - webserver resources in frameworks
- Subject: Re: Maven build - webserver resources in frameworks
- From: Paul Hoadley via Webobjects-dev <email@hidden>
- Date: Fri, 6 Mar 2020 09:28:37 +1030
Hi Steven,
On 6 Mar 2020, at 02:14, Steven Meyer via Webobjects-dev
<email@hidden> wrote:
> The wolifecycle-maven-plugin doesn’t seem to do that, so the web server
> resources portion of the split artifact looks like this
>
> MyApp.woa
> Contents
> WebserverResources
> <application WS resources>
> Frameworks
> MyFramework.framework
> WebserverResources
> <framework WS resources>
>
> The app is still generating resource URLs like
> "/WebObjects/MyApp.woa/Frameworks/MyFramework.framework/WebServerResources/images/myImage.png”
> which are unsurprisingly failing.
>
> I don’t see any way of configuring wolifecycle-maven-plugin, so I’m looking
> at how to change how those generated URLs look. Was hoping our old friend
> frameworksBaseURL() might help, but it doesn’t seem to.
What have you tried with respect to frameworksBaseURL() that doesn't work? It
should be sufficient to set the WOFrameworksBaseURL property:
WOFrameworksBaseURL=/WebObjects/YourApp.woa/Contents/Frameworks
I agree that this is annoying, though. I don't know the history behind those
subtle differences in bundle layout from the two build processes. It would be
nice if they did the same thing, or if the difference could be detected and
worked around.
--
Paul Hoadley
https://logicsquad.net/
https://www.linkedin.com/company/logic-squad/
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden