1) Do you have a build description how to build the CasEditor
artifact?
This is imported and we need to have that before we can ship it.
There is already a build script available which I wrote earlier, but
was never included in the Cas Editor repository.
I will check if I can fix that so we can include it. I will try it
tonight, if this does not work I will write a file with
build instructions.
2) The binary package contains a plugin like org.junit4_4.3.1 do we
really need that for the binary shipment?
Thats included in the MANIFEST.MF to make the junit plugin tests work.
So if I remove it, it will break the junit plugin
tests, but we can ship without it. So I think its not a big think to
ship it together with rest even it is not needed.
If I find a way to do the plugin tests without the junit plugin in the
manifest we can remove it.
3) The binary package for windows contains the CasEditor package with
src, target, docbook directories and some eclipse setting files. Do we
really need that all? I think the binary package should just contain
the
necessary compiled content to run the product.
Thats right I will have a look at it.
Jörn