|
Size: 2353
Comment:
|
← Revision 29 as of 2009-09-20 21:55:06 ⇥
Size: 2363
Comment: converted to 1.6 markup
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 5: | Line 5: |
| We have split the JSE class library into a number of 'modules'. You can see them laid out in [http://svn.apache.org/viewcvs.cgi/incubator/harmony/enhanced/classlib/trunk/modules/ the classlib area of the Subversion repository]. Modules contain discrete sets of functionality and have well-defined dependencies between one another. The module interface is defined by an [http://en.wikipedia.org/wiki/OSGi OSGi] manifest (here is [http://svn.apache.org/viewcvs.cgi/*checkout*/incubator/harmony/enhanced/classlib/trunk/modules/luni/META-INF/MANIFEST.MF an example] taken from the LUNI module). A separate page details the package-level ["componentization"] of the class library code. | We have split the JSE class library into a number of 'modules'. You can see them laid out in [[http://svn.apache.org/viewcvs.cgi/incubator/harmony/enhanced/classlib/trunk/modules/|the classlib area of the Subversion repository]]. Modules contain discrete sets of functionality and have well-defined dependencies between one another. The module interface is defined by an [[http://en.wikipedia.org/wiki/OSGi|OSGi]] manifest (here is [[http://svn.apache.org/viewcvs.cgi/*checkout*/incubator/harmony/enhanced/classlib/trunk/modules/luni/META-INF/MANIFEST.MF|an example]] taken from the LUNI module). A separate page details the package-level [[componentization]] of the class library code. |
| Line 10: | Line 10: |
| Each class library module has a status page describing the ["component development status"]. Development discussion is conducted on the [http://incubator.apache.org/harmony/mailing.html Harmony development mailing list]. | Each class library module has a status page describing the [[component_development_status]]. Development discussion is conducted on the [[http://incubator.apache.org/harmony/mailing.html|Harmony development mailing list]]. |
| Line 15: | Line 15: |
| The Harmony website describes [http://incubator.apache.org/harmony/documentation/build_classlib.html how to obtain and run the class library code]. | The Harmony website describes [[http://incubator.apache.org/harmony/documentation/build_classlib.html|how to obtain and run the class library code]]. |
| Line 22: | Line 22: |
| * ["Apache Ant"] build tool (tbd) * ["Azureus"] Java BitTorrent Client * ["Eclipse JDT batch compiler"] for Java (tbd) * ["Apache Velocity"] template tool (looks good) * ["Apache Derby"] database (partially working) * ["Apache Tomcat"] servlet container (works) * ["Apache Axis"] web services platform (partially working) * ["Apache Maven Continuum"] continuous integration server (fails) * ["Apache Geronimo"] J2EE server (fails) * ["Apache Commons"] reusable Java components * ["Apache Struts"] servlet framework (fails) * ["Apache Cocoon"] web development framework (fails) * ["Apache MINA"] network application framework (looks good) * ["ArgoUML"] UML modelling tool (fails) * ["Apache Log4j"] Apache logging tool for Java (looks good) |
* [[Apache_Ant]] build tool (tbd) * [[Azureus]] Java BitTorrent Client * [[Eclipse JDT batch compiler]] for Java (tbd) * [[Apache_Velocity]] template tool (looks good) * [[Apache_Derby]] database (partially working) * [[Apache_Tomcat]] servlet container (works) * [[Apache_Axis]] web services platform (partially working) * [[Apache_Maven_Continuum]] continuous integration server (fails) * [[Apache_Geronimo]] J2EE server (fails) * [[Apache_Commons]] reusable Java components * [[Apache_Struts]] servlet framework (fails) * [[Apache_Cocoon]] web development framework (fails) * [[Apache_MINA]] network application framework (looks good) * [[ArgoUML]] UML modelling tool (fails) * [[Apache_Log4j]] Apache logging tool for Java (looks good) |
| Line 40: | Line 40: |
| ["Coverage information"] | [[Coverage_information]] |
| Line 43: | Line 43: |
| ["Excluded tests"] | [[Excluded_tests]] |
Harmony class library code
Componentization
We have split the JSE class library into a number of 'modules'. You can see them laid out in the classlib area of the Subversion repository. Modules contain discrete sets of functionality and have well-defined dependencies between one another. The module interface is defined by an OSGi manifest (here is an example taken from the LUNI module). A separate page details the package-level componentization of the class library code.
Development status
Each class library module has a status page describing the component_development_status. Development discussion is conducted on the Harmony development mailing list.
Obtaining the code
The Harmony website describes how to obtain and run the class library code.
What can it do?
Here are some applications that have been tried with the class library code. Please download the code, try running some applications, and report your findings here. It will be helpful if you record the code revision you are using, any special steps to run the application, and the results of your experiments!
Apache_Ant build tool (tbd)
Azureus Java BitTorrent Client
Eclipse JDT batch compiler for Java (tbd)
Apache_Velocity template tool (looks good)
Apache_Derby database (partially working)
Apache_Tomcat servlet container (works)
Apache_Axis web services platform (partially working)
Apache_Maven_Continuum continuous integration server (fails)
Apache_Geronimo J2EE server (fails)
Apache_Commons reusable Java components
Apache_Struts servlet framework (fails)
Apache_Cocoon web development framework (fails)
Apache_MINA network application framework (looks good)
ArgoUML UML modelling tool (fails)
Apache_Log4j Apache logging tool for Java (looks good)