From: Edward D. <eld...@tr...> - 2012-02-24 06:48:21
|
It would be most helpful if the jEdit SVN source code repository URL were put somewhere easy to find on the jEdit developer page at http://www.jedit.org/index.php?page=devel. As it is it is almost impossible to find amidst the other information there. Even if one were not interested in doing work as a jedit developer it would be most helpful to many jedit users to be able to access the source code through its SVN repository. Thanks ! |
From: Jarek C. <jar...@po...> - 2012-02-24 07:31:35
|
Handy Links. Almost at the top of the page you linked. Another link: Development links on the right side of the page. Sourceforge project. Then Code. What's the problem in finding these links? Jarek W dniu 2012-02-24 07:48, Edward Diener pisze: > It would be most helpful if the jEdit SVN source code repository URL > were put somewhere easy to find on the jEdit developer page at > http://www.jedit.org/index.php?page=devel. As it is it is almost > impossible to find amidst the other information there. Even if one were > not interested in doing work as a jedit developer it would be most > helpful to many jedit users to be able to access the source code through > its SVN repository. Thanks ! > > > ------------------------------------------------------------------------------ > Virtualization& Cloud Management Using Capacity Planning > Cloud computing makes use of virtualization - but cloud computing > also focuses on allowing computing to be delivered as a service. > http://www.accelacomm.com/jaw/sfnl/114/51521223/ |
From: Edward D. <eld...@tr...> - 2012-02-24 12:46:45
|
On 2/24/2012 2:31 AM, Jarek Czekalski wrote: > Handy Links. Almost at the top of the page you linked. > > Another link: Development links on the right side of the page. The latest source code is mirrored in 3 different repositories, SVN, CVS, and Git ? Wow ! I hope developers do not have to update 3 different repository systems whenever changes are made. That seems a bit of work to do. > Sourceforge project. Then Code. > > What's the problem in finding these links? > > Jarek > > W dniu 2012-02-24 07:48, Edward Diener pisze: >> It would be most helpful if the jEdit SVN source code repository URL >> were put somewhere easy to find on the jEdit developer page at >> http://www.jedit.org/index.php?page=devel. As it is it is almost >> impossible to find amidst the other information there. Even if one were >> not interested in doing work as a jedit developer it would be most >> helpful to many jedit users to be able to access the source code through >> its SVN repository. Thanks ! |
From: Edward D. <eld...@tr...> - 2012-02-24 12:52:18
|
On 2/24/2012 2:31 AM, Jarek Czekalski wrote: > Handy Links. Almost at the top of the page you linked. None of the browse links give a URL. It is only when going to Sourceforge, then Code, then each of the 3 different repository types that I finally see some URLs. That's the problem IMO. > > Another link: Development links on the right side of the page. > Sourceforge project. Then Code. > > What's the problem in finding these links? > > Jarek > > W dniu 2012-02-24 07:48, Edward Diener pisze: >> It would be most helpful if the jEdit SVN source code repository URL >> were put somewhere easy to find on the jEdit developer page at >> http://www.jedit.org/index.php?page=devel. As it is it is almost >> impossible to find amidst the other information there. Even if one were >> not interested in doing work as a jedit developer it would be most >> helpful to many jedit users to be able to access the source code through >> its SVN repository. Thanks ! |
From: Jarek C. <jar...@po...> - 2012-02-24 13:07:08
|
W dniu 2012-02-24 13:51, Edward Diener pisze: > On 2/24/2012 2:31 AM, Jarek Czekalski wrote: >> Handy Links. Almost at the top of the page you linked. > None of the browse links give a URL. It is only when going to > Sourceforge, then Code, then each of the 3 different repository types > that I finally see some URLs. That's the problem IMO. That's how Sourceforge works. One need to get familiar with Sourceforge projects. When you start developing jedit you'll find more problems. This one is a piece of cake and after all anyone can find this post and get to know where to look for the repository urls. Problem solved imo. Jarek |
From: Edward D. <eld...@tr...> - 2012-02-25 03:52:07
|
On 2/24/2012 8:06 AM, Jarek Czekalski wrote: > > > W dniu 2012-02-24 13:51, Edward Diener pisze: >> On 2/24/2012 2:31 AM, Jarek Czekalski wrote: >>> Handy Links. Almost at the top of the page you linked. >> None of the browse links give a URL. It is only when going to >> Sourceforge, then Code, then each of the 3 different repository types >> that I finally see some URLs. That's the problem IMO. > That's how Sourceforge works. One need to get familiar with Sourceforge > projects. When you start developing jedit you'll find more problems. > This one is a piece of cake and after all anyone can find this post and > get to know where to look for the repository urls. Problem solved imo. The problem is solved if you feel that it is not necessary to give a simple SVN URL link to the jedit source code repository on the developer's web page. I think it would be helpful to put it there, that's all. It was not a criticism, just a suggestion to make it easier for those interested in getting the jedit source to do so very easily. I assume jedit does try to get programmers help in its development or the development of a plug-in, if it can. When I looked at the developers page, because I am interested in adding my idea(s) to ProjectViewer, my first thought was "from what SCCS repository can I get the source code." It took a good while to find that info. I did see that the latest ProjectViewer code is in a Git repository, which I have already cloned locally. I will take a look at that as I have the time to see how I can add my own ideas. |
From: Matthieu C. <cho...@gm...> - 2012-02-24 13:58:26
|
Hi, to summarize : ignore CVS, it contains only old unmaintained plugins. If you want jEdit's sources, get them from SVN, this is the only valid repository. If you want plugins sources, most of them are on SVN, and if they are not on SVN, it is on git. 2012/2/24 Edward Diener <eld...@tr...> > On 2/24/2012 2:31 AM, Jarek Czekalski wrote: > > Handy Links. Almost at the top of the page you linked. > > > > Another link: Development links on the right side of the page. > > The latest source code is mirrored in 3 different repositories, SVN, > CVS, and Git ? Wow ! > > I hope developers do not have to update 3 different repository systems > whenever changes are made. That seems a bit of work to do. > > > Sourceforge project. Then Code. > > > > What's the problem in finding these links? > > > > Jarek > > > > W dniu 2012-02-24 07:48, Edward Diener pisze: > >> It would be most helpful if the jEdit SVN source code repository URL > >> were put somewhere easy to find on the jEdit developer page at > >> http://www.jedit.org/index.php?page=devel. As it is it is almost > >> impossible to find amidst the other information there. Even if one were > >> not interested in doing work as a jedit developer it would be most > >> helpful to many jedit users to be able to access the source code through > >> its SVN repository. Thanks ! > > > > ------------------------------------------------------------------------------ > Virtualization & Cloud Management Using Capacity Planning > Cloud computing makes use of virtualization - but cloud computing > also focuses on allowing computing to be delivered as a service. > http://www.accelacomm.com/jaw/sfnl/114/51521223/ > -- > ----------------------------------------------- > jEdit Users' List > jEd...@li... > https://lists.sourceforge.net/lists/listinfo/jedit-users > |
From: Jarek C. <jar...@po...> - 2012-02-24 14:06:55
|
W dniu 2012-02-24 14:57, Matthieu Casanova pisze: > > If you want plugins sources, most of them are on SVN, and if they are > not on SVN, it is on git. And one more unusual scenario: sometimes there are sources in both svn and git and only one repository is up-to-date. Jarek |
From: Matthieu C. <cho...@gm...> - 2012-02-24 15:31:25
|
2012/2/24 Jarek Czekalski <jar...@po...> > W dniu 2012-02-24 14:57, Matthieu Casanova pisze: > > > > If you want plugins sources, most of them are on SVN, and if they are > > not on SVN, it is on git. > > And one more unusual scenario: sometimes there are sources in both svn > and git and only one repository is up-to-date. I think the only case is jEdit's core, Alan tried to create a git repository and merged commits in it, but this was abandonned. I don't know why it still exist on git and I think it should be removed. Are there plugins that are in that case too ? |
From: Alan E. <ala...@gm...> - 2012-02-24 16:13:00
|
Yes, the jEdit GIT clone should be removed. I am not sure how to do that. And the CVS copy is old too. So only use the SVN version for jEdit core. No plugins should be in both SVN and GIT. 2012/2/24 Matthieu Casanova <cho...@gm...> > 2012/2/24 Jarek Czekalski <jar...@po...> > >> W dniu 2012-02-24 14:57, Matthieu Casanova pisze: >> > >> > If you want plugins sources, most of them are on SVN, and if they are >> > not on SVN, it is on git. >> >> And one more unusual scenario: sometimes there are sources in both svn >> and git and only one repository is up-to-date. > > > I think the only case is jEdit's core, Alan tried to create a git > repository and merged commits in it, but this was abandonned. > I don't know why it still exist on git and I think it should be removed. > > |
From: Shlomy R. <sre...@gm...> - 2012-02-24 20:08:31
|
There are a few plugins that I moved from SVN to Git, and by the request of some other developers, I left the directories in SVN with a readme file that says that these plugins were moved to Git (so that developers who update their SVN working directory will understand what happened). Shlomy 2012/2/24 Alan Ezust <ala...@gm...> > Yes, the jEdit GIT clone should be removed. I am not sure how to do that. > And the CVS copy is old too. So only use the SVN version for jEdit core. > No plugins should be in both SVN and GIT. > > > 2012/2/24 Matthieu Casanova <cho...@gm...> > >> 2012/2/24 Jarek Czekalski <jar...@po...> >> >>> W dniu 2012-02-24 14:57, Matthieu Casanova pisze: >>> > >>> > If you want plugins sources, most of them are on SVN, and if they are >>> > not on SVN, it is on git. >>> >>> And one more unusual scenario: sometimes there are sources in both svn >>> and git and only one repository is up-to-date. >> >> >> I think the only case is jEdit's core, Alan tried to create a git >> repository and merged commits in it, but this was abandonned. >> I don't know why it still exist on git and I think it should be removed. >> >> > > ------------------------------------------------------------------------------ > Virtualization & Cloud Management Using Capacity Planning > Cloud computing makes use of virtualization - but cloud computing > also focuses on allowing computing to be delivered as a service. > http://www.accelacomm.com/jaw/sfnl/114/51521223/ > -- > ----------------------------------------------- > jEdit Users' List > jEd...@li... > https://lists.sourceforge.net/lists/listinfo/jedit-users > > |
From: Jarek C. <jar...@po...> - 2012-02-24 22:07:19
|
W dniu 02/24/2012 09:08 PM, Shlomy Reinstein pisze: > There are a few plugins that I moved from SVN to Git, and by the > request of some other developers, I left the directories in SVN with a > readme file that says that these plugins were moved to Git (so that > developers who update their SVN working directory will understand what > happened). > > Shlomy And this is ok. In worst case one will check out the wrong repository and quickly learn to go to the other. I don't see any problems with repository contents. In case of deletion there is always risk of losing something important. Like with jedit build.xml, where we are unable to analyze its full history. Jarek > > 2012/2/24 Alan Ezust <ala...@gm... <mailto:ala...@gm...>> > > Yes, the jEdit GIT clone should be removed. I am not sure how to > do that. > And the CVS copy is old too. So only use the SVN version for jEdit > core. > No plugins should be in both SVN and GIT. > > > 2012/2/24 Matthieu Casanova <cho...@gm... > <mailto:cho...@gm...>> > > 2012/2/24 Jarek Czekalski <jar...@po... > <mailto:jar...@po...>> > > W dniu 2012-02-24 14:57, Matthieu Casanova pisze: > > > > If you want plugins sources, most of them are on SVN, > and if they are > > not on SVN, it is on git. > > And one more unusual scenario: sometimes there are sources > in both svn > and git and only one repository is up-to-date. > > > I think the only case is jEdit's core, Alan tried to create a > git repository and merged commits in it, but this was abandonned. > I don't know why it still exist on git and I think it should > be removed. > > > ------------------------------------------------------------------------------ > Virtualization & Cloud Management Using Capacity Planning > Cloud computing makes use of virtualization - but cloud computing > also focuses on allowing computing to be delivered as a service. > http://www.accelacomm.com/jaw/sfnl/114/51521223/ > -- > ----------------------------------------------- > jEdit Users' List > jEd...@li... > <mailto:jEd...@li...> > https://lists.sourceforge.net/lists/listinfo/jedit-users > > > > > ------------------------------------------------------------------------------ > Virtualization& Cloud Management Using Capacity Planning > Cloud computing makes use of virtualization - but cloud computing > also focuses on allowing computing to be delivered as a service. > http://www.accelacomm.com/jaw/sfnl/114/51521223/ > > |
From: Alan E. <ala...@gm...> - 2012-02-24 22:10:36
|
I just uploaded the CVS dump of jEdit from before it was migrated to SVN. You can see it in the "oldfiles" section of jEdit, and it's simply called "jEdit.tar.gz" On Fri, Feb 24, 2012 at 2:08 PM, Jarek Czekalski <jar...@po...>wrote: > W dniu 02/24/2012 09:08 PM, Shlomy Reinstein pisze: > > to the other. I don't see any problems with repository contents. In case > of deletion there is always risk of losing something important. Like with > jedit build.xml, where we are unable to analyze its full history. > |
From: Edward D. <eld...@tr...> - 2012-02-25 03:57:43
|
On 2/24/2012 3:08 PM, Shlomy Reinstein wrote: > There are a few plugins that I moved from SVN to Git, and by the request > of some other developers, I left the directories in SVN with a readme > file that says that these plugins were moved to Git (so that developers > who update their SVN working directory will understand what happened). I would like to suggest that it be made more transparent to programmers who might be willing to work on some things in jedit where the latest version of jedit resides and where the latest version of the various jedit plugins reside. Maybe i am being picky but I found it difficult to ascertain this from the website. |
From: Matthieu C. <cho...@gm...> - 2012-02-26 13:16:28
|
2012/2/25 Edward Diener <eld...@tr...> > On 2/24/2012 3:08 PM, Shlomy Reinstein wrote: > > There are a few plugins that I moved from SVN to Git, and by the request > > of some other developers, I left the directories in SVN with a readme > > file that says that these plugins were moved to Git (so that developers > > who update their SVN working directory will understand what happened). > > I would like to suggest that it be made more transparent to programmers > who might be willing to work on some things in jedit where the latest > version of jedit resides and where the latest version of the various > jedit plugins reside. Maybe i am being picky but I found it difficult to > ascertain this from the website. > > But you can browse the repositories. It's simple, if it is on git, it is the latest version, if it is not on git it is on svn. |
From: Edward D. <eld...@tr...> - 2012-02-27 03:53:28
|
On 2/26/2012 8:16 AM, Matthieu Casanova wrote: > 2012/2/25 Edward Diener <eld...@tr... > <mailto:eld...@tr...>> > > On 2/24/2012 3:08 PM, Shlomy Reinstein wrote: > > There are a few plugins that I moved from SVN to Git, and by the > request > > of some other developers, I left the directories in SVN with a readme > > file that says that these plugins were moved to Git (so that > developers > > who update their SVN working directory will understand what > happened). > > I would like to suggest that it be made more transparent to programmers > who might be willing to work on some things in jedit where the latest > version of jedit resides and where the latest version of the various > jedit plugins reside. Maybe i am being picky but I found it difficult to > ascertain this from the website. > > > But you can browse the repositories. > It's simple, if it is on git, it is the latest version, if it is not on > git it is on svn. Thanks ! Appreciate the info. |