Costin Manolache wrote:
Could you summarise what conflicts and why do we have to use JDT ?
As usual: version conflicts with people who would use JDT in their webapps.
My understanding was that the main reason is that it's better / faster / less leaky than javac - is this correct ? Is it still true for JDK1.5 ? Could we just use javac as default - and in case of 'conflicts' ?
More importantly, dependencies are read using a classloader, which is much faster.
Package rename kind of implies additional maintainance of a non-trivial piece of code, merging, etc. Of course - having it as a separate module ( and download ) might be the best solution IMO.
No, using it as a default is the best option by far (otherwise, people need the JDK, etc), as was done with 5.5. javac remains usable at any time.
Rémy --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
