Re: [JPP-Devel] wiki on sourceforge

do you mean the email notification? i have checked out/in the attached file to the sourceforge cvsroot of jpp. But of course i previously had to register the email list. i hope this helps? stefan Larry Becker schrieb: I forgot about that. I couldn't get it to work on SkyJUMP. I suspect t

Re: [JPP-Devel] wiki on sourceforge

I forgot about that. I couldn't get it to work on SkyJUMP. I suspect that setting the script to execute will only work on linux. Any hints, Stefan? thanks, Larry On 5/16/07, Stefan Steiniger <[EMAIL PROTECTED]> wrote: > cool... thanx for pointing on that > but i wondered how they have done the

Re: [JPP-Devel] wiki on sourceforge

cool... thanx for pointing on that but i wondered how they have done the changelog on the vividsolutions cvs. But currently i am already quite happy to have the cvs email log ;) all the things mentioned by Sascha are very hepful and i really enjoy reading them for the wfs/printlayout plugin deve

Re: [JPP-Devel] wiki on sourceforge

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Handwritten ChangeLogs offer the opportunity to log some extra comments and backgrounds that do not make there way into the commit message. But this is of course a question of personal taste. - - Sascha Larry Becker schrieb: > A changeLog would be n

Re: [JPP-Devel] wiki on sourceforge

A changeLog would be nice. You can auto-generate one using the changelog Eclipse tool. Check the SkyJUMP release notes to see an example (scroll to the bottom). It basically concatenates all of the CVS commit notes in time order for you. Larry On

Re: [JPP-Devel] wiki on sourceforge

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, Stefan Steiniger schrieb: > i just have seen, that Sourceforge now also offers a wiki. > > It may offer the choice to move some development related pages to that > wiki. for instance changes on the cvs, needed and added new functions, Wikis ar

Re: [JPP-Devel] wiki on sourceforge

Stefan, Let me try out the SourceForge Wiki. I think it may be a good idea to move a lot of the development content over to this wiki. I think most, if not all, of the JPP Wiki content could go there. In this case I would delete the JPP Wiki and begin to use the SourceForge wiki exclusively. Let