Packe [[email protected]]: > > Hi again, > > I have now committed my Roland D50 and Emu Proteus/2 contributions. > > One thing that annoys me is the source code structure. I have seen in > previous threads in this mailing list some > people suggesting porting JSynthLib to the Maven folder structure. > > I think this would be a good idea as that would facilitate adding test cases > and possibly in the future modularize > the application. > > I am willing to do the changes but I would just like to know if you guys are > ok with it before I put any effort into > this. > > BR > /Pascal >
Hi Pascal, If you look at my "refactor" branch, I restructured most of the source code into a more conventional style. I also started to re-encapsulate the API and re-wrote the Ant scripts so that adding unit testing support would be trivial. Since JSynthLib doesn't have any real dependencies, I'd humbly suggest that Maven is more trouble than it's worth (I use Maven at work on a project with many dependencies, but strongly feel that Ant and Ivy are a better solution). Regards, Chris ------------------------------------------------------------------------------ October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register > http://pubads.g.doubleclick.net/gampad/clk?id=60135031&iu=/4140/ostg.clktrk _______________________________________________ Jsynthlib-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jsynthlib-devel
