You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ant.apache.org by bu...@apache.org on 2007/07/18 14:25:50 UTC
DO NOT REPLY [Bug 42928] New: - when we wrap an Error in a BuildException, we should include the stack trace
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=42928>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND�
INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=42928
Summary: when we wrap an Error in a BuildException, we should
include the stack trace
Product: Ant
Version: 1.7Alpha (nightly)
Platform: Other
OS/Version: other
Status: NEW
Severity: normal
Priority: P2
Component: Core
AssignedTo: dev@ant.apache.org
ReportedBy: stevel@apache.org
I have a gump build failing:
maybe-ivy-resolve:
[ivy:resolve] :: loading settings :: file =
/srv/gump/public/workspace/smartfrog/antbuild/ivy/ivyconf.xml
[ivy:resolve] DEPRECATED: 'ivyconf' element is deprecated, use 'ivysettings'
instead (file:/srv/gump/public/workspace/smartfrog/antbuild/ivy/ivyconf.xml)
[ivy:resolve] :: resolving dependencies :: [ org.smartfrog | sf-tasks |
working@vmgump ]
[ivy:resolve] confs: [default, build, compile, daemon, test, master, redist,
runtime, documentation]
[ivy:resolve] found [ org.smartfrog | smartfrog | 18072007 ] in local
[ivy:resolve] [18072007] [ org.smartfrog | smartfrog | latest.integration ]
BUILD FAILED
/srv/gump/public/workspace/smartfrog/common.xml:1776:
java.lang.NoClassDefFoundError: org/apache/commons/codec/DecoderException
We can see there is an error, but no line in the ivy lib where it is surfacing.
Should we perhaps report stack traces when any error gets wrapped, on the
assumption that this is pretty low level.
alternatively, make this an option we can somehow enable
--
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org
DO NOT REPLY [Bug 42928] - when we wrap an Error in a BuildException, we should include the stack trace
Posted by bu...@apache.org.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=42928>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND�
INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=42928
stevel@apache.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |DUPLICATE
------- Additional Comments From stevel@apache.org 2007-09-18 01:22 -------
this is the same problem we've been discussing: loss of stack trace
*** This bug has been marked as a duplicate of 43398 ***
--
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org