You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by ji...@codehaus.org on 2003/12/02 23:38:56 UTC

[jira] Deleted: (MAVEN-225) Missing xdoclet module results in silent failure in maven, but not in pure ant build

Message:

  The following issue has been deleted from JIRA.

---------------------------------------------------------------------

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: MAVEN-225
    Summary: Missing xdoclet module results in silent failure in maven, but not in pure ant build
       Type: Bug

     Status: Unassigned
   Priority: Major

 Original Estimate: Unknown
 Time Spent: Unknown
  Remaining: Unknown

    Project: maven

   Assignee: 
   Reporter: Colin Sampaleanu

    Created: Tue, 28 Jan 2003 5:34 PM
    Updated: Sun, 3 Aug 2003 11:43 PM
Environment: maven CVS HEAD 2003-1-28

Description:
There appears to be a silent failure and continue (instead of the appropriate build-breakage) happening when xdoclet is run and a needed module is not found on the classpath, and this would appear to be a maven problem.

Consider the following code in a pure ant based build, which uses xdoclet:
   <ejbdoclet>
     ...
     <jboss 
       xxx="ssss"
       yyy="ddd"
      />
     ...
   </ejbdoclet>

Now the JBossSubtask class which is a subtask of EjbDocletTask, also uses the JMXDocletTask, which is found in another xdoclet module entirely. When the ant based build is run, if the xdoclet jmx module is not found on the classpath, the build fails as follows:
---- excerpt
xdoclet:

BUILD FAILED
file:./proj/buildTargets.xml:153: Couldn't find the class xdoclet.modules.jmx.JM
XDocletTask on the classpath: D:\src\tira\cvs\core\data-access\lib\core\log4j.ja
r;D:\src\tira\cvs\core\data-access\lib\forbuild\ejb.jar;D:\src\tira\cvs\shared\l
ib\xdoclet\xdoclet-1.2\commons-collections.jar;D:\src\tira\cvs\shared\lib\xdocle
t\xdoclet-1.2\commons-logging.jar;D:\src\tira\cvs\shared\lib\xdoclet\xdoclet-1.2
\xdoclet-bea-module.jar;D:\src\tira\cvs\shared\lib\xdoclet\xdoclet-1.2\xdoclet-e
jb-module.jar;D:\src\tira\cvs\shared\lib\xdoclet\xdoclet-1.2\xdoclet-jboss-modul
e.jar;D:\src\tira\cvs\shared\lib\xdoclet\xdoclet-1.2\xdoclet-mvcsoft-module.jar;
D:\src\tira\cvs\shared\lib\xdoclet\xdoclet-1.2\xdoclet-web-module.jar;D:\src\tir
a\cvs\shared\lib\xdoclet\xdoclet-1.2\xdoclet-xjavadoc.jar;D:\src\tira\cvs\shared
\lib\xdoclet\xdoclet-1.2\xdoclet.jar
----

but when maven is run, with a goal using the exact same ejbdoclet task definition, there is no error printed, the build is not stopped, and there is no indication that there is a problem, except that xdoclet does not run at all. I do not believe that this is an xdoclet problem. As indicated in the pure ant case, xdoclet is trying to stop the build when it can't find a needed module, but in the maven environment, that is not happening.




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

If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa

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


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org