| 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.
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@hidden> 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,
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
|