Received-SPF: none
 receiver=post.selbstdenker.com; client-ip=185.112.145.70; envelope-from=hugi@karlmenn.is
From: Hugi Thordarson <hugi@karlmenn.is>
Content-Type: text/plain;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 15.0 \(3693.20.0.1.32\))
Subject: Re: [WO-DEV] Installation on osx Monterey - deployment
Date: Tue, 28 Dec 2021 11:10:18 +0000
References: <list-27030648@post.selbstdenker.com>
To: WebObjects & WOnder Development <webobjects-dev@wocommunity.org>
In-Reply-To: <list-27030648@post.selbstdenker.com>
Message-Id: <40F21A85-839A-4881-91D7-98028B115368@karlmenn.is>

Hi Stavros,
here's a quick "getting started guide:

https://gist.github.com/hugith/d2ba6da9e4942f4ece95d7a721159cd1

=E2=80=A6and here's a guide to converting an existing Fluffy Bunny =
application:

https://gist.github.com/hugith/3c269a3196d0c4f2da486f1109c16d42

Don't hesitate to ask if you hit any walls or get errors you have no =
idea what mean. Those of us that have made this switch have probably hit =
all the sharp corners :).

Cheers,
- hugi


> On 28 Dec 2021, at 11:03, Stavros Panidis <stavros.panidis@gmail.com> =
wrote:
>=20
> Dear Paul,
>=20
> Thank you very much for the info.
>=20
> I never used Maven before, but since it is the solution I have to do =
now. Are there any info / documentation /how to on this?
>=20
> Best regards
>=20
> Stavros
>=20
>=20
>> On 28 Dec 2021, at 8:29 AM, Paul Hoadley <paulh@logicsquad.net> =
wrote:
>>=20
>> Hi Stavros,
>>=20
>> On 28 Dec 2021, at 3:04 pm, Stavros Panidis =
<stavros.panidis@gmail.com> wrote:
>>=20
>>> Old applications run with no problems but when I deploy the new one, =
built in Java 17, application does not start, even after I add:
>>>=20
>>> --add-exports=3Djava.base/sun.security.action=3DALL-UNNAMED
>>>=20
>>> in JavaMonitor (Additional arguments).
>>=20
>> I ran into this issue a few months ago, and discussed it in #java on =
Slack. The problem is that the application launch script inside the WOA =
bundle does some magic on all the arguments to get them into the right =
place on the eventual command line invocation. There are two issues: (a) =
--add-exports needs to appear before the Java class name on the command =
line; but (b) the launch script pre-dates the existence of any arguments =
that look like that, and hence doesn't move it. So it's appearing on the =
command line after the class name, and has no effect.
>>=20
>> There's an easy fix, but you need to be using Maven to build: =
wolifecycle-maven-plugin 2.5 will add options like this to the =
*ClassPath.txt files, where they will be honoured on launch. You can =
specify them in build.properties.
>>=20
>> https://github.com/wocommunity/wolifecycle-maven-plugin/pull/15
>>=20
>>=20
>> --=20
>> Paul Hoadley
>> https://logicsquad.net/
>> https://www.linkedin.com/company/logic-squad/
>>=20
>=20