Bug 1213 - Link compiler's used by Javac and EJBJar tasks
Link compiler's used by Javac and EJBJar tasks
Status: RESOLVED FIXED
Product: Ant
Classification: Unclassified
Component: Optional Tasks
1.3
PC All
: P1 enhancement (vote)
: ---
Assigned To: Ant Notifications List
:
Depends on:
Blocks:
  Show dependency tree
 
Reported: 2001-04-04 09:42 UTC by david.ventimiglia
Modified: 2004-11-16 19:05 UTC (History)
0 users



Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description david.ventimiglia 2001-04-04 09:42:35 UTC
The Javac task makes use of the build.compiler property to determine the 
compiler it should use (javac, jikes, etc.).  The EJBJar task uses an attribute 
in the nested Weblogic element to do the same thing (the attribute 
is 'compiler').  It would be nice if either 

1) EJBJar used the build.compiler property just as Javac does.  This would 
effectively link the two tasks ensuring they use the same compiler.  I've had 
UnmarshallingExceptions galore when using EJBs where container classes are 
generated using Javac but the bean classes are compiled using Jikes.  This 
option is a little less flexible.

2) Javac used an attribute to control the compiler, the same way that EJBJar 
does.  This way, they could be linked by a property if that's what you want, 
but it's flexible enough to have them use seperate compilers if THAT's what you 
want (for whatever reason).

Not a high priority, since I'm sure there's a workaround right now.
Thanks,
David
Comment 1 Conor MacNeill 2001-07-18 07:05:21 UTC
Done by having the ejbjar task pick up build.compiler value. Only jikes value 
is recognized.