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. if tooling exists to strip debug information, set up a second tree
of projects, each one depending on the primary artifact and running
the "strip debug" tool
Best of luck keeping the versions in sync etc.
Wayne
I'm thinking of a third alternative . . .
Set up a separate repository that handles the -DEBUG classifier artifacts.
Create a profile that generates the artifacts and overrides the
deployment information.
Create a Jenkins CI job that gets triggered after a release build. Pass
in the appropriate scm tag, and do a debug release with the appropriate
profile.
Developers should then be able to pick it up with the appropriate
classifier.
I'll probably have to look at the enforcer plugin to see if I can
prevent a classifier dependency from making it into a release . . .
I wish we could just do a post-release step to strip out debugging
information and compress Javascript / CSS . . .
Thanks for the ideas.
/mde/
On Thu, Mar 27, 2014 at 2:22 PM, Mark Eggers <[email protected]> wrote:
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 multiple execution blocks
a. one block is configured to generate debug info
b. another block is configured to omit debug info
c. add classifiers to the JAR or WAR plugin as needed
4. deploy plugin
a. add a configuration section
b. add a files section
c. list additional artifacts to be attached (?!)
Is this the gist of Dimitar Gospodinov's reply at the end of the thread?
It seems both hackish and verbose.
However, I'm not sure of any other way to provide both fully optimized
(compressed CSS, Javascript) and non-optimized WAR and JAR artifacts.
Any time I'm doing something like this, I feel that I'm not doing it the
"Maven way".
Other approaches?
/mde/
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
