/ CSS . . .
Thanks for the ideas.
/mde/
On Thu, Mar 27, 2014 at 2:22 PM, Mark Eggers its_toas...@yahoo.com 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
/
On Thu, Mar 27, 2014 at 2:22 PM, Mark Eggers its_toas...@yahoo.com
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
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
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
and it is
skipped in the release version.
Best regards,
Dimitar
From: cemalettin@gmail.com
Date: Thu, 5 Dec 2013 09:28:53 +0200
Subject: Releasing artifacts with and without debug info
To: users@maven.apache.org
Hi,
Jackson project is using this compiler parameters to reduce jar size
Well first off I think it would be better to have the full debug info in
the main artifact as you can always use tooling to strip debug info as
a consumer
the debug info will have no effect on the transitive dependencies, so from
that PoV having a -nodebug.jar makes sense
Classifier would
Classifier would seem to be appropriate for this case... but I would be
interested to see what others say.
I agree on this approach. It will require extra execution blocks for at
least the maven-compiler-plugin and maven-jar-plugin. You also have to
decide if you want the
Or writing a plugin that strips debug info from a .jar and attaches the
stripped artifact with the nodebug classifier...
/me wonders if shade offers this functionality...
On Thursday, 5 December 2013, Robert Scholte wrote:
Classifier would seem to be appropriate for this case... but I would be
Hi,
Jackson project is using this compiler parameters to reduce jar size.
debugtrue/debug
debuglevellines,source/debuglevel
However this is causing a lot pain to debug. Every single artifact has to
be compiled with necessary compiler flags again to be debugged. Before
