Thank you for your comments Steve. Your input is always appreciated. You have an excellent idea about placing plug-in code into the CVS. I will give that some more serious thought.
I think there are some advantages to Subversion. Its main appeal to me is the ease with which the directory structure can be modified. There are a lot of administrative tasks that I can do directly with a Subversion Repository on SourceForge that I would have to request through SourceForge staff if I was using CVS. I'm not planning to replace the CVS Repository at this time, I'd just like to get Subversion up and running. I think more and more developers will be using Subversion in the future. I don't think there are a great deal of developers that are contributing to our OpenJUMP CVS Repository. Perhaps 3 or 4 at the most? I think I will place the current OpenJUMP code in the SVN Repository at the SurveyOS Project. That way I don't derail the developers using the JPP CVS, but I can see how OpenJUMP code works in Subversion. The Sunburned Surveyor On 8/22/06, Steve Tanner <[EMAIL PROTECTED]> wrote: > Hello, > Although I am not that much involved any more, I would however make some > comments: > - A new wiki? The existing one is good. Why to change? > - Going from CVS to Subversion? Why? CVS is more than sufficient, and is > working since May 2005. Why all these efforts to change? You may loose > in the process the motivation of the members who contribute to CVS if > you change the system... CVS is working equally good with Eclipse and > other IDE, the only difficulty is to configure your client, but the > difficulty is absolutely the same with Subversion. > - About preventing Plugin Chaos, this is a very good idea... I had > proposed a long time ago to host the plugin code on the same CVS. I > created new modules, but only Stefan (to my knowledge) used that > possibility. I think that you should try again to motivate people to > port their plugin code to the CVS, this is the easiest solution. > Everything already exists. > > In the CVS, there exists NOW the following structure: > > /openjump (module) > > /ExtensionManagerPlugin (module) > > /MapGenToolboxPlugin (module) > /lib > /src > > /PostGISDriverPlugin (module) > > /PrintLayoutPlugin (module) > > /RasterImagePlugin (module) > /src > > These modules can be used to host the plugin code. Easy! > > > NOTE: Sourceforge have changed in July the policy to access CVS. Now, > the jump-pilot CVS can be accessed with these parameters: > :ssh:[EMAIL PROTECTED]:/cvsroot/jump-pilot > > If you were working with a client and cannot find the way to change the > settings (mainly the root parameter) you need to edit your "root" file > in the CVS (hidden) folder, and replace: > :ssh:[EMAIL PROTECTED]:/cvsroot/jump-pilot > by > ssh:[EMAIL PROTECTED]:/cvsroot/jump-pilot > > Best regards, > Steve > > > Sunburned Surveyor a écrit : > > I've given everyone a couple of days to respond to my post about > > reactivating the Development Committee. I was disappointed that I > > didn't get any responses. I'm afraid the current situation is due in > > large part to my neglect, and the fact that I have left Stefan to > > carry most of the administrative load. > > > > I am going to take a more active role in the JPP and OpenJUMP starting > > today. I think the project has been suffering because of a lack of > > coordination between the different teams developing there own versions > > of OpenJUMP. I really think that OpenJUMP and the JUMP Pilot Project > > need to have an administrator that isn't directly tied to the other > > JUMP projects, and for the time being I will be that person. > > > > I think that most of the developers are concerned with improving and > > maintaining there own versions of OpenJUMP. I understand this, but > > hope we can all work together more in the near future. In the meantime > > I will be making some significant changes to OpenJUMP, mostly > > administrative in nature. Here is the agenda I will be working to > > implement in the next couple of weeks: > > > > (1) Migrating to a new wiki: Our existing wiki is somewhat cluttered, > > and we still have Jon Acquino hosting. I have started a new wiki for > > the JPP here: > > > > http://thejumppilotproject.pbwiki.com/ > > > > This wiki host is free, there is no size restriction, I can use a > > password mechanism to prevent spamming, and I can generate a back-up > > zip file of the wiki with a single mouse click. I will leave the > > OpenJUMP wiki up at Jon's site until use of the new wiki picks up. > > > > (2) Subversion Repository: I will be creating a Subversion repository > > for OpenJUMP source code at the SourceForge site. I believe the CVS > > repository can remain in place. However, I am using Subversion as my > > main source code repository for other projects, I think it has > > definite advantages over CVS, and I know it works well with Eclipse on > > both Windows and Linux operating systems. I will also be creating some > > standards for those developers that want to commit to the subversion > > repository. > > > > (3) Preventing Plug-In Chaos: I've got a link on the new wiki site for > > a plug-in catalog. I hope to start tracking information about plug-ins > > that can be used in OpenJUMP without modification, and that aren't > > tied to a specific "brand" of JUMP. I have heard a lot of discussion > > and confusion on the mailing list about raster support. One of my main > > development goals will be an "official" version of a raster plug-in > > for OpenJUMP. I also plan on creating a simple solution to the memory > > limit for large data files. > > > > Please remember that I am always open to changing my policies and > > plans when it comes to OpenJUMP and the JUMP Pilot Project. If you > > have concerns about my changes and want to become involved in the > > decision process you just have to let me know. In the meantime, I'm > > going to get to work. > > > > The Sunburned Surveyor > > > > ------------------------------------------------------------------------- > > Using Tomcat but need to do more? Need to support web services, security? > > Get stuff done quickly with pre-integrated technology to make your job > > easier > > Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo > > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 > > _______________________________________________ > > Jump-pilot-devel mailing list > > Jump-pilot-devel@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel > > > > > > > > ------------------------------------------------------------------------- > Using Tomcat but need to do more? Need to support web services, security? > Get stuff done quickly with pre-integrated technology to make your job easier > Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 > _______________________________________________ > Jump-pilot-devel mailing list > Jump-pilot-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel > ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
