[SLING-1451] Clean up compiler API and use classloading infrastructure

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: Commons Compiler 1.0.0
• Fix Version/s: Commons Compiler 2.0.0
• Component/s: Commons
• Assignee: Carsten Ziegeler
• Reporter: Carsten Ziegeler
• Created: 19/Mar/10 09:46
• Updated: 20/Dec/10 14:52
• Resolved: 24/Mar/10 07:56

Description

The current interface of the commons compiler is unnecessary complicated and does not use all of the features of the commons classloading infrastructure.

We can:

• remove the CompilerEnvironment interface - this can be handled internally
• remove the ClassWriter interface - we have the ClassLoaderWriter interface in the commons classloader
• change the options interface to extend a map - this allows us to add new options without changing interfaces/api
• the compile unit interface can be changed to
  CompileUnit {
  InputStream getSource();
  String getMainTypeName();
  }
  This simplifies the integration with the rest of sling which is resource based.
  The JavaCompiler interface then just takes an array of compile units, an error handler and the options