Re: java.util.logging and Maven builds
Re: java.util.logging and Maven builds
- Subject: Re: java.util.logging and Maven builds
- From: Hugi Thordarson <email@hidden>
- Date: Sat, 24 Jun 2017 01:25:42 +0000
Very true. Ironically, I think my couple of years away from WO, doing
java-only, probably improved me the most as a WO programmer. When I came back I
had a vastly different approach to WO—it was no longer the center of my
development universe, but rather just another framework to be integrated with
other best-of-breed tools. And using it like that makes it even better.
- hugi
> On 24 Jun 2017, at 01:05, Chuck Hill <email@hidden> wrote:
>
> As you use more modern Java tools and libraries, it become increasingly
> important to recognize the differences between “The WO Way” and “The Java
> Way”. Trying to force one to be the other is a recipe for pain. As you have
> experienced. :-) WOLifecyle needs to evolve.
>
> Chuck
>
> From: Paul Hoadley <email@hidden>
> Date: Friday, June 23, 2017 at 5:48 PM
> To: Hugi Thordarson <email@hidden>
> Cc: Chuck Hill <email@hidden>, WebObjects Development
> <email@hidden>
> Subject: Re: java.util.logging and Maven builds
>
> Hi Hugi,
>
> On 23 Jun 2017, at 6:17 pm, Hugi Thordarson <email@hidden
> <mailto:email@hidden>> wrote:
>
> I’m stumped—any Maven aficionados want to chime in?
>
> WOLifecycle modifies the maven standard behaviour by enlisting src/resources
> for WO bundle resources only (equivalent to /Resources in Fluffy Bunny).
> However, the Eclipse compiler doesn't know about WOLifecycle's eccentricities
> and will continue to behaves as if the project is a standard maven project
> and copy the resources in src/main to target/classes. That's why everything
> works during development and blows up in production.
>
> I've mentioned that we should really change this behaviour: Make WOLifecycle
> handle src/resources like a standard maven java project does and then add a
> separate folder for WO bundle resources (app-resources, wo-resources or
> something like that). You can see a bit of discussion in #maven on Slack on
> January 24th. Unfortunately I haven't had the time to actually *do* anything
> about that :).
>
> Ah, yes—I remember the discussion. I also remember not quite having a
> concrete understanding of the problem or how the solution would help. Now
> that this has bitten me, I know _exactly_ what you’re talking about!
>
> If you'd like, here's a workaround: You can force maven to copy the java
> resources (or certain resources). But of course, this is less than optimal.
>
> https://gist.github.com/hugith/a2ece8632ab33b994403ff9a04722fc1
> <https://gist.github.com/hugith/a2ece8632ab33b994403ff9a04722fc1>
>
> Thanks Hugi I’ll check that out.
>
>
> --
> Paul Hoadley
> http://logicsquad.net/ <http://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