On 3/27/2014 5:12 PM, Wayne Fay wrote:
Off the top of my head, I could imagine 2 other approaches:
1. set up 2 separate project trees - one that produces the debug
output, and another that depends on the source of the first (use
dependency:unpack), and merely produces the non-debug output
2.
I wish we could just do a post-release step to strip out debugging
information and compress Javascript / CSS . . .
post-release?
I suppose you mean post-package
see the complete phase list[1]
there are a lot of phases after complie = the place where code with debug
symbols are generated, so a
Recently I received a requirement much like that covered in the
following thread:
Releasing artifacts with and without debug info (December 04, 2013)
I'm new to Maven, but I more or less followed the idea:
1. create a profile
2. in the profile, specify the plugins
3. in each plugin, specify
Off the top of my head, I could imagine 2 other approaches:
1. set up 2 separate project trees - one that produces the debug
output, and another that depends on the source of the first (use
dependency:unpack), and merely produces the non-debug output
2. if tooling exists to strip debug
