<commit_before>grails-akka - TODO
==================

TODO
----

- fix docs and write the 2 Changelog (or similar) ... with 0.5, and 1.0, then remove this line

- for release 0.5 (first public release):
	+ tag sources in git
	+ put in downloads a zipped version of the plugin
		* add by hand README.md, NOTICE, LICENSE, and RELEASE-NOTES and README if present ...


- for release 1.0:
	+ verify the info put in readme.md
		* and then, create another test webapp (but not inline here) where to install it, following only readme info, to ensure they are right ...
	+ add some long-running actor, for example giving it the delay ...
		* ok, but up to now it doesn't seem to block execution for the given delay ... verify better, to make it work
	+ test the right behaviour (to be sure that Thread suspend/resume in done the right way), with a stress test ...
	+ make an akkaService, and test it
		* do it in the test webapp, because probably in the plugin it would be hard to have it so much generalized ...
	+ fix TODO in code ...
	+ exclude the transitivity of scala, to avoid dependency errors in the grails dependency-report ...
		* put exclusions for this in the BuildConfig of the plugin, until I get 0 evicted (in build, compile, and runtime)... ok
		* I commented all the exclusions for now otherwise a compile error will happen ...
		  just for reference, but could be the wrong way to do this, so let's see later if/how to fix this


- for release 1.0 or later:
	+ use some remote actor ... 
		* grails-akka-test webapp integration tests: 
		  call some remote actors (before start its server, maybe with a microkernel application under integration tests, as this) ...
	+ make it load a config file from the classpath, 
	  maybe with a dedicated key under Config.grails (in the webapp or in the plugin ? or in both ?), or using grails.config.locations ...
		* use sample conf files for Java and put under integration tests root folder, then try to use them
	+ update package creation, to add even README.md, NOTICE, LICENSE files in root, and RELEASE-NOTES and README if present ...
		* add by hand CHANGES.md with inside the full history of changes ... no, better: put this in plugin docs, in gdoc format
<commit_msg>small updates<commit_after>grails-akka - TODO
==================

TODO
----

- fix docs and write the 2 Changelog (or similar) ... with 0.5, and 1.0, then remove this line

- for release 0.5 (first public release):
	+ tag sources in git
	+ put in downloads a zipped version of the plugin
		* add by hand README.md, NOTICE, LICENSE, and RELEASE-NOTES and README if present ...


- for release 1.0:
	+ verify the info put in readme.md
		* and then, create another test webapp (but not inline here) where to install it, following only readme info, to ensure they are right ...
	+ add some long-running actor, for example giving it the delay ...
		* ok, but up to now it doesn't seem to block execution for the given delay ... verify better, to make it work
	+ test the right behaviour (to be sure that Thread suspend/resume in done the right way), with a stress test ...
	+ make an akkaService, and test it
		* do it in the test webapp, because probably in the plugin it would be hard to have it so much generalized ...
	+ fix TODO in code ...
    + sample usage of akka poison pill messages:
http://doc.akka.io/docs/akka/2.0.3/java/untyped-actors.html
    + sample usage of akka typed actors:
http://doc.akka.io/docs/akka/2.0.3/java/typed-actors.html
	+ verify if/how to exclude the transitivity of scala, to avoid dependency errors in the grails dependency-report ...
		* put exclusions for this in the BuildConfig of the plugin, until I get 0 evicted (in build, compile, and runtime)... ok
		* I commented all the exclusions for now otherwise a compile error will happen ...
		  just for reference, but could be the wrong way to do this, so let's see later if/how to fix this


- for release 1.0 or later:
	+ use some remote actor ... 
		* grails-akka-test webapp integration tests: 
		  call some remote actors (before start its server, maybe with a microkernel application under integration tests, as this) ...
	+ make it load a config file from the classpath, 
	  maybe with a dedicated key under Config.grails (in the webapp or in the plugin ? or in both ?), or using grails.config.locations ...
		* use sample conf files for Java and put under integration tests root folder, then try to use them
	+ update package creation, to add even README.md, NOTICE, LICENSE files in root, and RELEASE-NOTES and README if present ...
		* add by hand CHANGES.md with inside the full history of changes ... no, better: put this in plugin docs, in gdoc format

{'fraction_non_alphanumeric': 0.08106951871657754, 'fraction_numerical': 0.006417112299465241, 'mean_word_length': 3.2625341841385596, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 2, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '2583092', 'n_tokens_mistral': 1337, 'n_tokens_neox': 1264, 'n_words': 715}