So ... Work (Huge PKI infrastructure migration) take me a lot of time and energy last months!
I felt in a sort of spacetime continuum hole ;)
I Correct lots of bugs and problems :
I also add some new key features :
I will now focus (again) on testing for releasing v0.1 ASAP.
Maven integration is now finished.
It's based on the Apache directory studio work.
One small side effect is that the console log is empty for the moment.
A continuous integration server is also up and running.
Nightly builds are now generated everyday.
With all that, we won't loose time and energy on publishing pre release (Beta, Release Candidate,..). Code will be automaticly compiled and packaged from the subversion repository, for testing next morning, and without any effort! that will also enhance testing iterations.
Work on releasing v0.1 will now restart...
Adding visible signature for PDF files (still beta). Adding certificate selection in signature wizards.
Many new stuff :
I added Hardware token support and fix developments for the 0.1 release.
The team will now focus on BugFixes, documentation and code quality (logs, ...).
I add configuration and correct default settings for Passphrase/PIN Policy.
A small BugFix on PDF Signing operation : it show the error message now.
Next and last step before first release will be :
I just correct an annoying bug on windows while mapping directly a drive.
Note that it could be quite slow while refreshing big folders (with lots of files and sub folders).
I'm proud to release the first beta release of eParapher.
After many discussions with friends (other PKI experts), i went to some conclusions :
So i decide to release it as an opensource software, to let grow a community of contributors, and sell consulting services (packaging, deployment) if it's successfull.
This software is a gift to the community. It's a kind of big "merci" to life for some personal recent event that finally finished quite well.
Arnault MICHEL