The following comment has been added to this issue:

     Author: Adrian Bigland
    Created: Thu, 4 Aug 2005 10:14 AM
       Body:
I would like to second this comment. It would probably be difficult, but if I 
say to XDoclet 'please generate JMX interfaces for simple MBeans under this 
directory' and XDoclet doesn't find any there, I would prefer an error rather 
than XDoclet just saying 'nothing to do then' and letting Ant carry on with the 
build process.

What is particularly annoying is when starting out with XDoclet, and not 
realising that you have to set your fileset directory to the top of your source 
directory i.e. with src/java/uk/... creating a fileset at src will do no good, 
it has to be src/java. If you get it wrong you just get silence by default.

I also find it incredibly difficult to figure out how to turn on debugging 
level logging in XDoclet classes. I have tried setting commons logging 
properties to use Log4J and to set up a log4j.properties file - I am 
experienced at using Log4j so that was no problem, but these settings have no 
effect. I can't get a clue as to why I get no logging. I appreciate that there 
may good reasons why logging is set up this way - but could we please have some 
documentation on how to set this up?
---------------------------------------------------------------------
View this comment:
  
http://opensource.atlassian.com/projects/xdoclet/browse/XDT-1409?page=comments#action_17102

---------------------------------------------------------------------
View the issue:
  http://opensource.atlassian.com/projects/xdoclet/browse/XDT-1409

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: XDT-1409
    Summary: Debug XDoclet errors in Ant
       Type: Improvement

     Status: Open
   Priority: Major

 Original Estimate: Unknown
 Time Spent: Unknown
  Remaining: Unknown

    Project: XDoclet
   Versions:
             1.2.3

   Assignee: xdoclet-devel (Use for new issues)
   Reporter: Roberto Nanamura

    Created: Thu, 19 May 2005 10:02 PM
    Updated: Thu, 4 Aug 2005 10:14 AM
Environment: any

Description:
There should be a better way to debug problems with XDoclet in the ant tasks 
even with verbose no log or message is given in some failures. 

If it does not find the class, it should log this. Instead the task is silent 
even in verbose mode (which does not add much, is it working?)

Every time I have to debug an issue in XDoclet is a hassle and I spend dyas to 
do this....

Nice tool but only if it works :-)



---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://opensource.atlassian.com/projects/xdoclet/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
xdoclet-devel mailing list
xdoclet-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/xdoclet-devel

Reply via email to