On Aug 9, 2010, at 10:21 PM, Paul Hoadley wrote:
> On 10/08/2010, at 2:29 PM, Q wrote:
>
>> It is building it as a WO5.2 bundle, or whatever ancient version it is that
>> doesn't use WOBootstrap.jar.
>
> It may well be—is that what WOProject does when it can't find WOBootstrap.jar?
Yes.
>
On 10/08/2010, at 2:29 PM, Q wrote:
> It is building it as a WO5.2 bundle, or whatever ancient version it is that
> doesn't use WOBootstrap.jar.
It may well be—is that what WOProject does when it can't find WOBootstrap.jar?
In any case, the solution was...
> You should be able to just set wo.
On 10/08/2010, at 2:21 PM, Chuck Hill wrote:
>> I've hit a small snag with my Project Hudson: a built application I just
>> tried to deploy won't actually launch (JavaMonitor or command line). The
>> specific problem is that it can't find the Postgres JDBC JAR, which hasn't
>> moved from previ
It is building it as a WO5.2 bundle, or whatever ancient version it is that
doesn't use WOBootstrap.jar. You should be able to just set
wo.bootstrapjar=blah in wolips.properties and it will do the right thing.
I have attached a couple of build files I wrote for use with hudson.
build-hudson.x
On Aug 9, 2010, at 9:41 PM, Paul Hoadley wrote:
> Hello Hudson builders,
>
> I've hit a small snag with my Project Hudson: a built application I just
> tried to deploy won't actually launch (JavaMonitor or command line). The
> specific problem is that it can't find the Postgres JDBC JAR, whic
Hello Hudson builders,
I've hit a small snag with my Project Hudson: a built application I just tried
to deploy won't actually launch (JavaMonitor or command line). The specific
problem is that it can't find the Postgres JDBC JAR, which hasn't moved from
previous launch (with an Eclipse-built
