Thanks for the reply Henrique. I just wanted to make sure I am not overlooking some special magic property to make it work or if there is some way to reference it from my dependency repo. I may see if I can figure out how to make the old woapp script properly escape the () in the path, since it appears to work (at least, on windows 10) otherwise. Then I just won’t need(?) WOBootstrap.jar.
I gather this is the desired way to go if I want to use WOInject at some point in the future, based on my reading of old threads from the mailing list. Referencing magic jars outside the dependency repo seems like a step backwards when trying to use maven. I notice on the rather dated roadmap that 3.0 was intended to merge/replace the woproject ant stuff. https://wiki.wocommunity.org/display/WOL/Roadmap Have you ever made a branch for that or had any progress in that direction? Are there any major hurdles blocking that goal? On Nov 18, 2015, at 7:40 AM, Henrique Prange <[email protected]> wrote: > Hi Ramsey, > > Theoretically, defining the wo.bootstrapjar variable in the build.properties > should work. Defining the full path as you did is another option too. > However, as soon as the Maven plugin uses an old version of > woproject-ant-tasks, it may not work as we expect it to work (considering the > current source code for this library). > > I’ll try to debug the plugin execution to understand what’s going on. > > Cheers, > > Henrique > >> On 17 de nov de 2015, at 22:25, Ramsey Gurley <[email protected]> >> wrote: >> >> Also, I’ve tried creating >> >> /System/Library/WebObjects/JavaApplications/wotaskd.woa/WOBootstrap.jar >> >> directly on the build server, as that appears to be the default location >> where WOVariables looks. Still getting the old and busted appstart.cmd file. >> >> On Nov 17, 2015, at 3:19 PM, Ramsey Gurley <[email protected]> wrote: >> >>> Hi maven people, >>> >>> I’m building a maven project with woapplication packaging. The >>> Application.CMD file for windows is coming from the woapp instead of the >>> woapp_52 directory in the woproject.jar. The woapp script is broken because >>> it does not gracefully handle directory paths like \ProgramFiles (x86)\ on >>> Windows the way woapp_52 script does. I’m getting it because >>> WOBootstrap.jar does not exist, and therefore, it assumes I’m using old n >>> busted WO 5 or 5.1. I tried adding >>> wo.bootstrapjar=/path/to/wotaskd/WOBootstrap.jar to build.properties, but >>> that did not work. I tried adding that as a property in the pom, but that >>> did not work either. >>> >>> Can anyone tell me how to build a maven project with woapplication >>> packaging such that one gets the launch scripts from woapp_52 instead of >>> woapp? >>> >>> Thanks, >>> >>> Ramsey >> >> >> _______________________________________________ >> Do not post admin requests to the list. They will be ignored. >> Webobjects-dev mailing list ([email protected]) >> Help/Unsubscribe/Update your Subscription: >> https://lists.apple.com/mailman/options/webobjects-dev/hprange%40gmail.com >> >> This email sent to [email protected] >
_______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to [email protected]
