[
https://issues.apache.org/jira/browse/VELOCITY-894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16498461#comment-16498461
]
Claude Brisson commented on VELOCITY-894:
-----------------------------------------
I'm sorry if I didn't respect the standard practice here. It seemed natural to
me to optimize the size of binaries, and someone willing to have debug
information can still build binaries with it. Since it's meaningful to set to
true the <optimize> flag, anyhow, you won't always get a proper step by step
debugging even with debug symbols.
But again, if the standard practice is to always keep the debugging symbols,
then we shall ensure that the debug symbols are present for the next release.
There's enough feedback for a new release, should I or someone else find the
time to work on it.
What really looks like pure nonsense to me is that there isn't any related
notice in [http://www.apache.org/dev/publishing-maven-artifacts.html] or
elsewhere, if it looks so vital.
> Maven central JARs don't contains debug information
> ---------------------------------------------------
>
> Key: VELOCITY-894
> URL: https://issues.apache.org/jira/browse/VELOCITY-894
> Project: Velocity
> Issue Type: Bug
> Components: Build
> Affects Versions: 2.0
> Reporter: Thomas Mortagne
> Priority: Major
>
> As far as I can see the JAR published on velocity-engine-core-2.0.java
> published on Maven central has been built without the debug information.
> Makes is quite a pain to understand when happen exactly when you have
> something to debug.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@velocity.apache.org
For additional commands, e-mail: dev-h...@velocity.apache.org
