"pete.muir(a)jboss.org" wrote :
| But, I can see that this is more generally applicable in the area of tooling (both
prod via Jopr, and dev via JBoss Tools) - that if an accurate deployment exception(s) can
be reported back to the tool, it can start to suggest possible remedies...
How do you know what's accurate? :-)
I can see this being done in a test, but not in general, e.g. tooling.
As there can be so many layers in between the real cause and when the exception finally
that chance of having one framework wrapping it in useless wrapper is quite big.
And imho wrong/confusing info is worse than no info at all. :-)
View the original post :
Reply to the post :