[jboss-dev] com.sun.tools.javac.code.Symbol$CompletionFailure

Anil Saldhana Anil.Saldhana at redhat.com
Thu Nov 29 11:29:30 EST 2007


I did figure out that it is a CNFE.  What intrigues me is what did Sun 
fix in the following bug:
http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6180021

Rather than throw a CNFE, they just handled that one case?

Scott, where are our javaxb classes located?
   <path refid="sun.jaxb.classpath"/>


Scott Stark wrote:
> When I have seen this error it is because of missing classpath items 
> referenced by the indicated class. javaxb classes typically. It should 
> be reported as a CNFE, I guess that is the bug.
>
> On Nov 28, 2007, at 10:51 PM, Anil Saldhana wrote:
>
>> Removal of the metadata classpath made the build to go through.....
>>
>> Anil Saldhana wrote:
>>> Any clue what is happening here:
>>>
>>> ====================
>>> compile-classes:
>>>   [javac] Compiling 57 source files to 
>>> C:\cygwin\home\asaldhana\jboss-5.0\jboss-head\security\output\classes
>>>   [javac] 
>>> C:\cygwin\home\asaldhana\jboss-5.0\jboss-head\security\src\main\org\
>>> jboss\security\auth\login\DynamicLoginConfig.java:36: warning: 
>>> [deprecation] org
>>> .jboss.deployment.DeploymentException in org.jboss.deployment has 
>>> been deprecate
>>> d
>>>   [javac] import org.jboss.deployment.DeploymentException;
>>>   [javac]                             ^
>>>   [javac] An exception has occurred in the compiler (1.5.0_14). 
>>> Please file a
>>> bug at the Java Developer Connection 
>>> (http://java.sun.com/webapps/bugreport)  af
>>> ter checking the Bug Parade for duplicates. Include your program and 
>>> the followi
>>> ng diagnostic in your report.  Thank you.
>>>   [javac] com.sun.tools.javac.code.Symbol$CompletionFailure: file 
>>> javax\xml\bi
>>> nd\annotation\XmlType.class not found
>>>
>>> BUILD FAILED
>>> C:\cygwin\home\asaldhana\jboss-5.0\jboss-head\security\build.xml:194: 
>>> Compile fa
>>> iled; see the compiler error output for details.
>>> =====================================
>>>
>>> All I did was import metadata classpath into the security workspace 
>>> in AS trunk.



More information about the jboss-development mailing list