[
https://issues.apache.org/jira/browse/VELOCITY-894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16499360#comment-16499360
]
Michael Osipov commented on VELOCITY-894:
-----------------------------------------
bq. 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.
It's good that you raised this. {{<optiimze>}} is really pure non-sense because
Plexus Compiler translates to {{-O}} and there is no such option with
{{javac}}. See also: https://stackoverflow.com/q/20928320/696632
Do you mind to open an issue with MCOMPILER? I will deprecate it with the next
version.
bq. 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.
What do you expect to see? The ASF recommending to compile with debug symbols?
This is the default for {{javac}}. The guide is only about deployment and not
semantics of the binary artifact.
[~tmortagne], I am really certain that no one will really build the binaries
for a given artifact just because of debug information. This is such hassle
within an entire toolchain with a lot of dependencies.
I think, we need to make the use as easy as possible.
> 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 what happen exactly when you have
> something to debug.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
