• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Eureka!!!
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Eureka!!!


  • Subject: Re: Eureka!!!
  • From: Hugi Thordarson via Webobjects-dev <email@hidden>
  • Date: Sun, 19 Jan 2025 12:12:31 +0000

Mornin'!

Just adding to the conversation; I didn’t know JVM arguments from a project's
build.properties were passed to JVMs launched by Eclipse. If it’s so, I
probably don’t benefit from it since it's probably be the responsibility of the
WOLips launcher to read and pass in those arguments (meaning the application is
launched using Run/Debug as -> WOApplication).

I’ve mentioned this before, but for years I’ve been running my applications as
plain java applications rather than WO applications, since the WOLips launcher
constructs a broken classpath for maven applications (which, IIRC, also results
in problems resolving workspace projects at runtime when debugging). I haven’t
encountered any problems using this method so I think I can safely recommend it.

https://github.com/wocommunity/wolips/issues/153

Regarding workarounds for the module system (—add-exports/- -add-opens), I keep
those in the global configuration for the JREs used by Eclipse to launch my
applications (same place where you’d usually put the hotswap-agent and DCEVM
config), so it’s a one time thing that I don’t have to worry about in the
context of individual projects.

Cheers,
- hugi



> On 18 Jan 2025, at 22:15, Paul Hoadley via Webobjects-dev
> <email@hidden> wrote:
>
> On 19 Jan 2025, at 6:43 am, Theodore Petrosky via Webobjects-dev
> <email@hidden> wrote:
>
>> Hugi had a link with instructions how to move old projects into maven. I
>> hope he would be kind enough to pass on those URLs again.
>
>
> Here's my slightly modified version of Hugi's instructions:
>
> https://gist.github.com/paulhoadley/cd15b90c94eb8c640fddd9ac3fbbc6dc
>
> I've used the approach to migrate a lot of projects, though not for a while.
>
>> But the first hurdle has been accomplished.
>
>
> The hurdle was getting the jvmOptions (--add-exports) required to launch an
> app under Java 21. Putting them in build.properties is sufficient for
> launching a Maven-built app from the command line. For me, it's also
> sufficient to launch within Eclipse. With some trial and error, we worked out
> that Ted's setup required those options to be added to the Argument > VM
> arguments tab of the launch configuration as well. I'm not sure what the
> relevant difference is here.
>
>
> --
> Paul Hoadley
> https://logicsquad.net/
> https://www.linkedin.com/company/logic-squad/
>
> _______________________________________________
> 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

 _______________________________________________
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

  • Follow-Ups:
    • Re: Eureka!!!
      • From: Paul Hoadley via Webobjects-dev <email@hidden>
References: 
 >Eureka!!! (From: Theodore Petrosky via Webobjects-dev <email@hidden>)
 >Re: Eureka!!! (From: Paul Hoadley via Webobjects-dev <email@hidden>)

  • Prev by Date: Re: Eureka!!!
  • Next by Date: Re: Eureka!!!
  • Previous by thread: Re: Eureka!!!
  • Next by thread: Re: Eureka!!!
  • Index(es):
    • Date
    • Thread