Looks interesting. It even has the issue tracker on github still enabled.
--
--
You received this message because you are subscribed to the Google
Groups Clojure group.
To post to this group, send email to clojure@googlegroups.com
Note that posts from new members are moderated - please be
On Fri, Nov 29, 2013 at 3:38 AM, Lars Rune Nøstdal
larsnost...@gmail.com wrote:
Looks interesting. It even has the issue tracker on github still enabled.
The reason contrib libraries (and Clojure itself) have the issue
tracker disabled on Github is because they use JIRA for tracking
issues - and
Andrey:
I am no lawyer, but the following answer on this QA page about the Eclipse
Public License suggests that if you take code from an EPL-licensed project
(which java.jdbc is), then the project in which you include it must also be
licensed under the EPL (whch clj.jdbc is currently not, as far
Hi Andy.
A lot of thanks for this information. I was also researching on this point.
Currently I have removed all taken code from the clojure.java.jdbc, license
problem should be solved.
Again, I in no way want to belittle the original work. It was big mistake
on my part not to mention from
To Michael: It is fairly up to date - there have only been a few small
changes to java.jdbc since the last updates to that part of
clojure-doc.org. Now that java.jdbc 0.3.0 has hit beta and has a
stable API for release, I feel more comfortable about updating the
clojure-doc.org pages to include
On Sun, Nov 17, 2013 at 1:57 AM, Andrey Antukh n...@niwi.be wrote:
Additionally I have
copied some useful functions like parsing dbspec to URI or a map of
protocol-cases
and the rest are written from scratch.
Looking through the source code, there are quite a few functions
copied directly
Because there is no patch for human stupidity?
On Tue, Nov 19, 2013 at 1:35 PM, Sean Corfield seancorfi...@gmail.comwrote:
On Sun, Nov 17, 2013 at 1:57 AM, Andrey Antukh n...@niwi.be wrote:
Additionally I have
copied some useful functions like parsing dbspec to URI or a map of
You have the typical profile of people who do not understand open source.
To you, open source is the same thing has a side hobby, ...
with lack of commitment and seriousness.
How do you expect open source software quality to improve if each of us
starts to spin off our own flavor of the same lib
Hi Sean.
2013/11/19 Sean Corfield seancorfi...@gmail.com
To Michael: It is fairly up to date - there have only been a few small
changes to java.jdbc since the last updates to that part of
clojure-doc.org. Now that java.jdbc 0.3.0 has hit beta and has a
stable API for release, I feel more
Gaz, excuse me if I misunderstood you, I reread your reply and it was not clear
to me to whom you were referring in your comment.
I still stand by what I said toward the op. Saying that if rewritten the code
would be the same as the original is a lame excuse, it's the same as all that
internet
2013/11/20 Softaddicts lprefonta...@softaddicts.ca
How do you expect open source software quality to improve if each of us
starts to spin off our own flavor of the same lib ?
Sometimes creating a new library is the right thing to do.
I'll give you one example.
When I started Langohr and
2013/11/20 Andrey Antukh n...@niwi.be
About license question: if these functions had not copied, but written
from scratch, them would be the same functions with minimal differences or
none...
Sorry but that's a ridiculous argument. You must respect and obey by the
license of the project you
Whoops, sorry looks like my intended light-hearted sarcasm based on one of
the email signatures in the thread got mis-interpreted. Hard to express in
an email, perhaps a cheeky :P after would have let you know I wasn't being
particularly serious!
No offense intended, or taken :)
On Tue, Nov 19,
Is not an excuse, is only a opinion, nothing more. This opinion can not
change that, mention the original author is right and I've done it. I have
no way intend to belittle anyone.
;)
Andrey
2013/11/19 Softaddicts lprefonta...@softaddicts.ca
Gaz, excuse me if I misunderstood you, I reread
Sean, for what it's worth many of us do appreciate the slow and careful
development of java.jdbc. When it's used so widely in production code
frequent breaking changes are very costly. The new 0.3.0 API is pretty
nice, though I have found documentation for it somewhat lacking. That said,
I
I'll address the java.jdbc.sql question in a separate thread (I've
actually addressed it before so I'll search the archives and elaborate
on my previous responses). Give me an hour or so...
On Tue, Nov 19, 2013 at 5:03 PM, Alexander Hudek
a...@diligenceengine.com wrote:
Sean, for what it's worth
On Tue, Nov 19, 2013 at 2:28 PM, Michael Klishin
michael.s.klis...@gmail.com wrote:
2013/11/20 Andrey Antukh n...@niwi.be
About license question: if these functions had not copied, but written
from scratch, them would be the same functions with minimal differences or
none...
Sorry but that's
Hi agai Soan.
Repeating now: as I said previously, copyright notice of taken code should
to be present. And is my mistake from the start not incluide it, I don't
have any problem for it. Now I have added a copyright notice.
Yo can explain me that is a current legal problem has my library. I
Hi Zach!
It is not based on any concrete version (is not a fork). Casually, it
has similarities with java.jdbc 0.2.x because uses same name for some
functions
(in my opinion 0.2 version has better api than 0.3). Additionally I have
copied some useful functions like parsing dbspec to URI or a map
Hi!
I have some frustration with current official jdbc wrapper for clojure and
I have worked in one alternative mainly because of:
- Lack of documentation.
- Philosophical differences of how things should be done.
Documentation page: http://cljjdbc.readthedocs.org/en/latest/
Github:
2013/11/16 Andrey Antukh n...@niwi.be
- Lack of documentation.
- Philosophical differences of how things should be done.
Documentation page: http://cljjdbc.readthedocs.org/en/latest/
+ ridiculous Clojure CA that keeps non-North America/EU contributors away.
Good job, Andrey. It's important
On Saturday, November 16, 2013 5:11:05 AM UTC-8, Michael Klishin wrote:
+ ridiculous Clojure CA that keeps non-North America/EU contributors away.
What is this? A link will do, if this has been discussed previously.
--
--
You received this message because you are subscribed to the Google
2013/11/16 Brian Craft craft.br...@gmail.com
What is this? A link will do, if this has been discussed previously.
https://groups.google.com/forum/#!searchin/clojure/CA$20/clojure/FlwqULYM7n0/x1-ArtQe1isJ
https://groups.google.com/d/topic/clojure/0gwjKtatf-0/discussion
--
MK
2013/11/16 Andrey Antukh n...@niwi.be
- Lack of documentation.
FTR, there is some documentation for java.jdbc, but it certainly
isn't being actively worked on (despite not being covered by the CA) and may
already be out of date.
http://clojure-doc.org/articles/ecosystem/java_jdbc/home.html
2013/11/16 Michael Klishin michael.s.klis...@gmail.com
2013/11/16 Andrey Antukh n...@niwi.be
- Lack of documentation.
FTR, there is some documentation for java.jdbc, but it certainly
isn't being actively worked on (despite not being covered by the CA) and
may
already be out of date.
Andrey, this looks interesting. It seems to be based on a really old
version of clojure.java.jdbc, though. Is there a reason for this? Since it
is a fork, it seems like it would be best to base it on a recent version,
to aid those who may want to try switching to it. Also, does it require JDK
26 matches
Mail list logo
