Its pointless to parse human text as a precondition for a bug report. Create
the bug report with the example and it will either be determined to be an issue
to be fixed or it won't.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3865306#3865306
Reply to the
I have no problem filing a bug report (and trying to build a small test case)
BUT
I need to get some confirmation from JBOSS technicians as to whether this SEEMS
to be a bug? OR... based on what you read of my configuration, that I have
CLEARLY not configured something correctly?...
So p
As a side benefit of developing the simplest possible test case to post along
with a bug report, one often finds the problem becomes clear. This is why I've
never filed a bug report.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3865078#3865078
Reply to the
The ideal condition for a bug report is a reproducible testcase and a
description of why its a bug. The timeframe for resolution of the bug is a
function how far from the ideal the report is.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3865062#3865062
Rep
So Scott,
Are you saying that based on everything you see in my problem description, that
it SHOULD work, and that because it doesn't, I should file a bug? If so, I can
do it. Not sure what you mean by "example of the classes not being picked up"
note. Would not the initial description of the
A Class-Path manifest entry is the only way APP-INF content has any meaning as
there is no standard for an APP-INF directory. Create a bug report with an
example of the classes not being picked up when referenced by a Class-Path
manifest entry.
http://jira.jboss.com/jira/browse/JBAS
View the
