Re: java.util.logging and Maven builds

[Chuck Hill]

It is all a nightmare which will be resolved by retirement.  :-P

On the bright side, you could be committing PHP all day long.



From: Paul Hoadley <pa...@logicsquad.net>
Date: Tuesday, June 27, 2017 at 4:42 PM
To: Chuck Hill <ch...@gevityinc.com>
Cc: WebObjects Development <webobjects-dev@lists.apple.com>, Hugi Thordarson 
<h...@karlmenn.is>
Subject: Re: java.util.logging and Maven builds

Hi Chuck,

On 28 Jun 2017, at 03:59, Chuck Hill 
<ch...@gevityinc.com<mailto:ch...@gevityinc.com>> wrote:

What you are describing seems to be the intent of this part of Java:

If "java.util.logging.config.class" property is not set, then the 
"java.util.logging.config.file" system property can be used to specify a 
properties file (in java.util.Properties format). The initial logging 
configuration will be read from this file.
If neither of these properties is defined then, as described above, the 
LogManager will read its initial configuration from a properties file 
"lib/logging.properties" in the JRE directory.

I did not see any mention of a default file name or location, other than the 
JRE one.

Thanks for doing my research for me! That would seem to explain everything. 
Well, everything except that Eclipse seems to pick up logging.properties from 
src/main/resources, which must be what set my expectation for how things would 
work in deployment. Unless I imagined even that. I’ve moved on. I’m putting 
this episode behind me…


--
Paul Hoadley
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  (Webobjects-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: java.util.logging and Maven builds

[Chuck Hill]

It is all a nightmare which will be resolved by retirement.  :-P

On the

From: Paul Hoadley <pa...@logicsquad.net>
Date: Tuesday, June 27, 2017 at 4:42 PM
To: Chuck Hill <ch...@gevityinc.com>
Cc: WebObjects Development <webobjects-dev@lists.apple.com>, Hugi Thordarson 
<h...@karlmenn.is>
Subject: Re: java.util.logging and Maven builds

Hi Chuck,

On 28 Jun 2017, at 03:59, Chuck Hill 
<ch...@gevityinc.com<mailto:ch...@gevityinc.com>> wrote:

What you are describing seems to be the intent of this part of Java:

If "java.util.logging.config.class" property is not set, then the 
"java.util.logging.config.file" system property can be used to specify a 
properties file (in java.util.Properties format). The initial logging 
configuration will be read from this file.
If neither of these properties is defined then, as described above, the 
LogManager will read its initial configuration from a properties file 
"lib/logging.properties" in the JRE directory.

I did not see any mention of a default file name or location, other than the 
JRE one.

Thanks for doing my research for me! That would seem to explain everything. 
Well, everything except that Eclipse seems to pick up logging.properties from 
src/main/resources, which must be what set my expectation for how things would 
work in deployment. Unless I imagined even that. I’ve moved on. I’m putting 
this episode behind me…


--
Paul Hoadley
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  (Webobjects-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: java.util.logging and Maven builds

[Paul Hoadley]

Hi Chuck,

On 28 Jun 2017, at 03:59, Chuck Hill  wrote:

> What you are describing seems to be the intent of this part of Java:
>  
> If "java.util.logging.config.class" property is not set, then the 
> "java.util.logging.config.file" system property can be used to specify a 
> properties file (in java.util.Properties format). The initial logging 
> configuration will be read from this file.
> If neither of these properties is defined then, as described above, the 
> LogManager will read its initial configuration from a properties file 
> "lib/logging.properties" in the JRE directory.
>  
> I did not see any mention of a default file name or location, other than the 
> JRE one.

Thanks for doing my research for me! That would seem to explain everything. 
Well, everything except that Eclipse seems to pick up logging.properties from 
src/main/resources, which must be what set my expectation for how things would 
work in deployment. Unless I imagined even that. I’ve moved on. I’m putting 
this episode behind me…


-- 
Paul Hoadley
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  (Webobjects-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: java.util.logging and Maven builds

[Chuck Hill]

Hi Paul,

What you are describing seems to be the intent of this part of Java:

If "java.util.logging.config.class" property is not set, then the 
"java.util.logging.config.file" system property can be used to specify a 
properties file (in java.util.Properties format). The initial logging 
configuration will be read from this file.
If neither of these properties is defined then, as described above, the 
LogManager will read its initial configuration from a properties file 
"lib/logging.properties" in the JRE directory.

I did not see any mention of a default file name or location, other than the 
JRE one.
Chuck

From: Paul Hoadley <pa...@logicsquad.net>
Date: Monday, June 26, 2017 at 8:32 PM
To: WebObjects Development <webobjects-dev@lists.apple.com>
Cc: Hugi Thordarson <h...@karlmenn.is>, Chuck Hill <ch...@gevityinc.com>
Subject: Re: java.util.logging and Maven builds

For the archives:

On 24 Jun 2017, at 10:18 am, Paul Hoadley 
<pa...@logicsquad.net<mailto:pa...@logicsquad.net>> wrote:

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

Thanks Hugi I’ll check that out.

Unbelievably, that’s not the complete fix. That copies logging.properties into 
the root of the application’s JAR, but java.util.logging _still_ doesn’t 
automatically find it. It allows me to change this startup parameter:

-Djava.util.logging.config.file="Contents/Resources/logging.properties”

to this:

-Djava.util.logging.config.file=logging.properties

at which point I think that's as good as we’re going to get. (I’ve never used 
java.util.logging before, and now I know why!)


--
Paul Hoadley
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  (Webobjects-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: java.util.logging and Maven builds

[Paul Hoadley]

For the archives:

On 24 Jun 2017, at 10:18 am, Paul Hoadley  wrote:

>> 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 
>> 
> Thanks Hugi I’ll check that out.

Unbelievably, that’s not the complete fix. That copies logging.properties into 
the root of the application’s JAR, but java.util.logging _still_ doesn’t 
automatically find it. It allows me to change this startup parameter:

-Djava.util.logging.config.file="Contents/Resources/logging.properties”

to this:

-Djava.util.logging.config.file=logging.properties

at which point I think that's as good as we’re going to get. (I’ve never used 
java.util.logging before, and now I know why!)


-- 
Paul Hoadley
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  (Webobjects-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: java.util.logging and Maven builds

[Hugi Thordarson]

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 <ch...@gevityinc.com> 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 <pa...@logicsquad.net>
> Date: Friday, June 23, 2017 at 5:48 PM
> To: Hugi Thordarson <h...@karlmenn.is>
> Cc: Chuck Hill <ch...@gevityinc.com>, WebObjects Development 
> <webobjects-dev@lists.apple.com>
> Subject: Re: java.util.logging and Maven builds
>  
> Hi Hugi,
>  
> On 23 Jun 2017, at 6:17 pm, Hugi Thordarson <h...@karlmenn.is 
> <mailto:h...@karlmenn.is>> 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  (Webobjects-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: java.util.logging and Maven builds

[Chuck Hill]

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 <pa...@logicsquad.net>
Date: Friday, June 23, 2017 at 5:48 PM
To: Hugi Thordarson <h...@karlmenn.is>
Cc: Chuck Hill <ch...@gevityinc.com>, WebObjects Development 
<webobjects-dev@lists.apple.com>
Subject: Re: java.util.logging and Maven builds

Hi Hugi,

On 23 Jun 2017, at 6:17 pm, Hugi Thordarson 
<h...@karlmenn.is<mailto:h...@karlmenn.is>> 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

Thanks Hugi I’ll check that out.


--
Paul Hoadley
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  (Webobjects-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: java.util.logging and Maven builds

[Paul Hoadley]

Hi Hugi,

On 23 Jun 2017, at 6:17 pm, Hugi Thordarson  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 
> 
Thanks Hugi I’ll check that out.


-- 
Paul Hoadley
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  (Webobjects-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: java.util.logging and Maven builds

[Chuck Hill]

Yes, that change to WOLifeCycle is The Right Thing To Do.

Chuck

From: Hugi Thordarson <h...@karlmenn.is>
Date: Friday, June 23, 2017 at 1:47 AM
To: Paul Hoadley <pa...@logicsquad.net>
Cc: Chuck Hill <ch...@gevityinc.com>, WebObjects Development 
<webobjects-dev@lists.apple.com>
Subject: Re: java.util.logging and Maven builds

src/main/resources is a path to a Java resource.  Contents/Resources is a path 
to a WebObjects resource.  Java knows Jacques Schmidt about these.  Only WO 
classes know about this.   Your Maven build needs to get this file into the top 
level directory that the class files are under (would normally go into a 
package, top level is the default package).

logging.properties _does_ get copied from src/main/resources into 
target/classes during build. But it _doesn’t_ make it into the app’s JAR (which 
ends up in Contents/Resources/Java), which I suspect is where it needs to be.

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 :).

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

Cheers,
- hugi
 ___
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list  (Webobjects-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: java.util.logging and Maven builds

[Hugi Thordarson]

>> src/main/resources is a path to a Java resource.  Contents/Resources is a 
>> path to a WebObjects resource.  Java knows Jacques Schmidt about these.  
>> Only WO classes know about this.   Your Maven build needs to get this file 
>> into the top level directory that the class files are under (would normally 
>> go into a package, top level is the default package).
> 
> logging.properties _does_ get copied from src/main/resources into 
> target/classes during build. But it _doesn’t_ make it into the app’s JAR 
> (which ends up in Contents/Resources/Java), which I suspect is where it needs 
> to be.
> 
> 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 :).

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 


Cheers,
- hugi ___
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list  (Webobjects-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: java.util.logging and Maven builds

[Paul Hoadley]

On 23 Jun 2017, at 14:49, Chuck Hill  wrote:

> src/main/resources is a path to a Java resource.  Contents/Resources is a 
> path to a WebObjects resource.  Java knows Jacques Schmidt about these.  Only 
> WO classes know about this.   Your Maven build needs to get this file into 
> the top level directory that the class files are under (would normally go 
> into a package, top level is the default package).

logging.properties _does_ get copied from src/main/resources into 
target/classes during build. But it _doesn’t_ make it into the app’s JAR (which 
ends up in Contents/Resources/Java), which I suspect is where it needs to be.

I’m stumped—any Maven aficionados want to chime in?


-- 
Paul Hoadley
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  (Webobjects-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: java.util.logging and Maven builds

[Chuck Hill]

Yes, that also works.

From: Paul Hoadley <pa...@logicsquad.net>
Date: Thursday, June 22, 2017 at 10:32 PM
To: Chuck Hill <ch...@gevityinc.com>
Cc: WebObjects Development <webobjects-dev@lists.apple.com>
Subject: Re: java.util.logging and Maven builds

Hi Chuck,

On 23 Jun 2017, at 14:49, Chuck Hill 
<ch...@gevityinc.com<mailto:ch...@gevityinc.com>> wrote:

src/main/resources is a path to a Java resource.  Contents/Resources is a path 
to a WebObjects resource.  Java knows Jacques Schmidt about these.  Only WO 
classes know about this.   Your Maven build needs to get this file into the top 
level directory that the class files are under (would normally go into a 
package, top level is the default package).

Ah, thanks. I’ll look into that. Meanwhile, a workaround is adding an argument 
in JavaMonitor:

-Djava.util.logging.config.file="Contents/Resources/logging.properties”


--
Paul Hoadley
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  (Webobjects-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: java.util.logging and Maven builds

[Paul Hoadley]

Hi Chuck,

On 23 Jun 2017, at 14:49, Chuck Hill  wrote:

> src/main/resources is a path to a Java resource.  Contents/Resources is a 
> path to a WebObjects resource.  Java knows Jacques Schmidt about these.  Only 
> WO classes know about this.   Your Maven build needs to get this file into 
> the top level directory that the class files are under (would normally go 
> into a package, top level is the default package).

Ah, thanks. I’ll look into that. Meanwhile, a workaround is adding an argument 
in JavaMonitor:

-Djava.util.logging.config.file="Contents/Resources/logging.properties”


-- 
Paul Hoadley
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  (Webobjects-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: java.util.logging and Maven builds

[Chuck Hill]

Hi Paul,

src/main/resources is a path to a Java resource.  Contents/Resources is a path 
to a WebObjects resource.  Java knows Jacques Schmidt about these.  Only WO 
classes know about this.   Your Maven build needs to get this file into the top 
level directory that the class files are under (would normally go into a 
package, top level is the default package).

Chuck


From: Webobjects-dev 
<webobjects-dev-bounces+chill=gevityinc@lists.apple.com> on behalf of Paul 
Hoadley <pa...@logicsquad.net>
Date: Thursday, June 22, 2017 at 10:07 PM
To: WebObjects Development <webobjects-dev@lists.apple.com>
Subject: java.util.logging and Maven builds

Hello,

This is admittedly rather obscure, but just in case…

I’m using Maven to build an app. It depends on a JAR that uses 
java.util.logging, and it’s also ridiculously chatty—I need to get it under 
control. I’ve got a logging.properties file in src/main/resources that does 
what I want in development. But once deployed, that’s _not_ getting picked up 
on application launch, though it is present in Contents/Resources.

Has anyone hit this before, or would anyone like to guess at a solution?


--
Paul Hoadley
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  (Webobjects-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

java.util.logging and Maven builds

[Paul Hoadley]

Hello,

This is admittedly rather obscure, but just in case…

I’m using Maven to build an app. It depends on a JAR that uses 
java.util.logging, and it’s also ridiculously chatty—I need to get it under 
control. I’ve got a logging.properties file in src/main/resources that does 
what I want in development. But once deployed, that’s _not_ getting picked up 
on application launch, though it is present in Contents/Resources.

Has anyone hit this before, or would anyone like to guess at a solution?


-- 
Paul Hoadley
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  (Webobjects-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com