Hi, for examples you can open each example one by one or only the example module in your ide, no need to open the whole project if you just want a sample.
Here some info, hope it helps: 1) we do some (a lot regarding the conf) things by reflection and it can be missing in code coverage 2) some (a lot) things are tested through TCK which are not in the main build (not public) 3) if there are duplications in examples that's not an error or a bad practice, we want each sample to be runnable without needing any dependency on a parent or another module, the philosophy is "download only the sample and run it" - Romain 2012/5/14 Erhan Bagdemir <[email protected]> > I've checked out the openejb source code from the repository, > and had some wishes from the developers of the project. > There are lots of javadocs missing in the source codes and the workspace > is IMO extremly complex structured (My IDE (IDEA 10) is heavly > processing to resolve dependencies right now) > Do you mind if it would be better to setup a new branch for these > examples? instead to commit all into the single trunk to create a new > project like "openejb-examples/trunk" ? > It would also help the tools and analyze the production code better. > http://nemo.sonarsource.org/dashboard/index/108716?page_id=3 > I don't think that the source has really %18,3 code duplications, but > there must be duplications in examples and tests. > > Is there any plan in sight to refactor the project? > > PS-1: Lack of javadocs in classes like OpenEjbContainer is critical to > understand the source code i.e. how the whole thing works. > PS-2: Code Coverage %27.3 ? > > Erhan >
