Re: Maven deployment application resources

Ahh, that was the bit I was missing :) Thanks Fabian! On Mar 7, 2016, at 12:12 PM, lists.fab...@e-lumo.com wrote: > Well, that was a case of "Reading goes quickly when you don't slow down to > comprehend". > > Do you set the finalName in the pom? Something like: > > > ${p

Re: Maven deployment application resources

Well, that was a case of "Reading goes quickly when you don't slow down to comprehend". Do you set the finalName in the pom? Something like: ${project.artifactId} The default is ${artifactId}-${version}. I've got projects with the default and others without th

Re: Maven deployment application resources

The WOFrameworksBaseURL works fine for me. All my framework resources are loading okay. It’s just the resources from the application itself that get a path with pom version in it. I’m using an approximately year old version of Wonder, so I should be unaffected by recent changes to Wonder. On

Re: Maven deployment application resources

Hi Ramsey, I'm guessing you're seeing . Markus proposed a fix in , of which I tested a preliminary version. For now I just reverted the commits from #704. Fabian > Am 07.03

Maven deployment application resources

Hi all, I’m doing a split deployment with apache. When deploying a maven application, I’m able to get the proper WebServerResources for all the frameworks using WOFrameworksBaseURL. However, any resources in the application itself seem to generate urls like domain/WebObjects/AppName-1.0.0-SNAP