Is there any plan to rejoin these efforts into one development line?
I ask this to know where to send patches (currently I think I'll fork the branch with the most recent changes and will try to get my changes merged there).
Greetings
Matthias
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Unfortunately I can't spend much time developing the project right now.
I welcome everyone to make changes in my code; I can add anyone to the list of developers.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thanks for this info - I'll try to contact the 4 authors that made changes on github whether they are interested in joining the efforts into one version again. I think that could also mean creating a "release" branch on git hub from which at some point a real releases are pulled.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
JSQLParser is a very usefull tool. I am very interested in combining all these useful extentions and corrections into one release again.
@linuxfun: Maybe there are forks on other platforms (e.g. bitbucket) as well. Did you check that?
I forked on github because of the activity of this project "clone". So I had the same questions like linuxfun.
I would prefer github as the new jsqlparser - source repository. Are there any significant reasons to stay on sourceforge? I was suprised to see that git projects are hosted here as well. ;)
By the way, wumpz/JSqlParser is my fork on github.
Greetings
Tobias
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
my intent with this request was to use an established base. I see no benifit to move everything over to github. The foren, file distribution and homepage could stay on sourceforge. This could act as a stable anchor. What is more for google this place is the primary target and should not look dead (as the development is alive as we can see in you repository). So movements in the development should be documented here and results of the development (aka release :-)) can also be placed where.
Where the development happens is insofar important, that at some point in time the authors of the software need to be located, than the whole history of the repository is needed. (No I don't see a relicence comming, but there may be other reasons). I have no strong feeling towards one repository system (I can live with subversion, git, mercurial, whatever) and can see the benifits of using github as a base. When moving to github, there is a strong need to get one lead repository from which then releases are created. Your repository looks like the most active, so it would be a good candiate :-)
I'll try to do a more thorough search whether there are more code repositories out there.
Greetings
Matthias
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have no experience in using sourceforge, but keeping the entry point stable is surely necessary. So +1 for this. Is it possible to host a maven repository at sourceforge? So I could begin to deploy my snapshot artifacts here.
Are there any reactions from the other developers?
Greetings
Tobias
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
This essentially offeres free snapshot + release hosting and the opportunity to publish releases to maven central.
I did some reading and if git is the only reason to stay at github, sourceforge offers this also, but I see the benefit, that everybody can fork on github and more easily contribute back.
My take what is really important: Clear the situation on the webpage and make sure that everybody works on the same thing. Whether this is at sourceforge or at github I realy to see as to big differences.
Greetings
Matthias
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Its trivial to get a project into Maven Central with Sonatype's OSS repo. If someone can assign developer privilege for this project to me, I'll be happy to convert it to a proper maven build and cut a release in no time.
Rob
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
@manningr
If this repository upload is done, would it be possible to deploy from github forks as well to this location? We are discussion here the reunion of the forks of this projects and may be a relocation of the sourcecode.
Tobias
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
@Tobias:
I won't expect a problem. @work we use an internal nexus repository as proxy and hosting platform for internal modules. Publishing to this nexus instance is basicly a http-POST protected by http authentication. We hold our code in a subversion repository, but even if not I could publisch to the repository.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello,
I noticed that forks of jsqlparser on github received much more attention:
https://github.com/ig0774/JSqlParser
https://github.com/wumpz/JSqlParser
Is there any plan to rejoin these efforts into one development line?
I ask this to know where to send patches (currently I think I'll fork the branch with the most recent changes and will try to get my changes merged there).
Greetings
Matthias
Unfortunately I can't spend much time developing the project right now.
I welcome everyone to make changes in my code; I can add anyone to the list of developers.
Thanks for this info - I'll try to contact the 4 authors that made changes on github whether they are interested in joining the efforts into one version again. I think that could also mean creating a "release" branch on git hub from which at some point a real releases are pulled.
Hello,
JSQLParser is a very usefull tool. I am very interested in combining all these useful extentions and corrections into one release again.
@linuxfun: Maybe there are forks on other platforms (e.g. bitbucket) as well. Did you check that?
I forked on github because of the activity of this project "clone". So I had the same questions like linuxfun.
I would prefer github as the new jsqlparser - source repository. Are there any significant reasons to stay on sourceforge? I was suprised to see that git projects are hosted here as well. ;)
By the way, wumpz/JSqlParser is my fork on github.
Greetings
Tobias
Hey Tobias,
my intent with this request was to use an established base. I see no benifit to move everything over to github. The foren, file distribution and homepage could stay on sourceforge. This could act as a stable anchor. What is more for google this place is the primary target and should not look dead (as the development is alive as we can see in you repository). So movements in the development should be documented here and results of the development (aka release :-)) can also be placed where.
Where the development happens is insofar important, that at some point in time the authors of the software need to be located, than the whole history of the repository is needed. (No I don't see a relicence comming, but there may be other reasons). I have no strong feeling towards one repository system (I can live with subversion, git, mercurial, whatever) and can see the benifits of using github as a base. When moving to github, there is a strong need to get one lead repository from which then releases are created. Your repository looks like the most active, so it would be a good candiate :-)
I'll try to do a more thorough search whether there are more code repositories out there.
Greetings
Matthias
Hi Matthias,
I have no experience in using sourceforge, but keeping the entry point stable is surely necessary. So +1 for this. Is it possible to host a maven repository at sourceforge? So I could begin to deploy my snapshot artifacts here.
Are there any reactions from the other developers?
Greetings
Tobias
Hi Tobias,
sorry for the late reply. AFAIK sourceforge does not offer it's own maven repository. But take a look at this sonatype OSS offering:
https://docs.sonatype.org/display/Repository/Sonatype+OSS+Maven+Repository+Usage+Guide
This essentially offeres free snapshot + release hosting and the opportunity to publish releases to maven central.
I did some reading and if git is the only reason to stay at github, sourceforge offers this also, but I see the benefit, that everybody can fork on github and more easily contribute back.
My take what is really important: Clear the situation on the webpage and make sure that everybody works on the same thing. Whether this is at sourceforge or at github I realy to see as to big differences.
Greetings
Matthias
Its trivial to get a project into Maven Central with Sonatype's OSS repo. If someone can assign developer privilege for this project to me, I'll be happy to convert it to a proper maven build and cut a release in no time.
Rob
manningr,
I added you to the project. Let me know if you need other permissions.
@manningr
If this repository upload is done, would it be possible to deploy from github forks as well to this location? We are discussion here the reunion of the forks of this projects and may be a relocation of the sourcecode.
Tobias
@Tobias:
I won't expect a problem. @work we use an internal nexus repository as proxy and hosting platform for internal modules. Publishing to this nexus instance is basicly a http-POST protected by http authentication. We hold our code in a subversion repository, but even if not I could publisch to the repository.
Hello,
What is the status now? Did you bring the latest changes back to SourceForge?
I've started adding better support for some MySQL statements. Where can I send my patches?
Boris.
I don't know. Meanwhile I do my additions using my fork at github.
https://github.com/wumpz/JSqlParser
I would appreciate any pull requests. This fork started with JSqlParser 0.7.x.
Tobias