Get rid of CPEs

[GoogleCodeExporter]

We should get rid of all our CPEs and replace them with Java classes.
They're constantly out of date as it is, and the CPE approach is going away
in the near future anyway. Plus, if we had them as simple Java classes with
main methods, it would be really simple to run them from the command line.

Original issue reported on code.google.com by steven.b...@gmail.com on 28 Apr 2009 at 8:31

[GoogleCodeExporter]

I totally agree.  I recently removed a cpe in favor of a java class that did 
the same
thing with a main method.  See
/ClearTK/test/src/org/cleartk/chunk/BuildTestTokenChunkModel.java (I just 
noticed
this class is in the wrong package - look in token/chunk if it has been moved.)

Original comment by pvogren@gmail.com on 28 Apr 2009 at 8:38

[GoogleCodeExporter]

For two more examples, I replaced the CPEs for building the example pos model 
and
running the example pos tagger with the classes:

/ClearTK/src/org/cleartk/example/pos/BuildTestExamplePosModel.java
/ClearTK/src/org/cleartk/example/pos/RunExamplePOSAnnotator.java

I don't know that we should start polluting our code with a bunch of misc. main
methods.  But I figured it was ok here since it is example code.  

Original comment by pvogren@gmail.com on 30 Apr 2009 at 4:58

[GoogleCodeExporter]

The remaining two cpes that lingered on did not survive the project re-org 
(moving to
framework and toolkit projects).  If you want to see them, checkout ClearTK at
revision 896.

Original comment by pvogren@gmail.com on 13 Aug 2009 at 7:33

• Changed state: Fixed