Closed GoogleCodeExporter closed 8 years ago
Looking at the dependencies I see the following are in Ivy Roundup:
- servletapi
- junit
- svnkit
but Pixels Core isn't and would need to be added:
- http://java.net/projects/pixels
Not sure the best way to make this work properly. I can't seem to find it in
Maven, though that might be me looking in the wrong place?
I also see the latest release of Kaptcha is 2.3.2, but it has not yet been
tagged in svn repository of the project.
Original comment by aj...@sympatico.ca
on 4 Apr 2011 at 1:43
I just got an e-mail from the developer indicating that he would rather the
project not be added to Ivy, since he would like to see the download count on
Google Code. Unless there is a way to accommodate that or convince the
developer otherwise, it looks like we will have to put off adding this to Ivy
Roundup.
Original comment by aj...@sympatico.ca
on 4 Apr 2011 at 12:26
it's not really the developer's choice what we put on ivy roundup; however, if
you want it added please follow the instructions at
http://code.google.com/p/ivyroundup/wiki/HowToContribute
Original comment by spatialguru.net@gmail.com
on 4 Apr 2011 at 1:19
The download count will still work. Ivy RoundUp does not host archives, it only
hosts meta-data. Each user will still be downloading from the original source.
Original comment by archie.c...@gmail.com
on 4 Apr 2011 at 1:44
Let me know if you want to proceed with this. If so, please provide a patch
(see wiki page for instructions).
Original comment by archie.c...@gmail.com
on 7 Oct 2011 at 1:22
I want to continue, but with the Pixels issue I had got a bit stuck and I
haven't had much time to deal with this.
Unless someone else takes the initiative, I will do what I can when I have a
few spare cycles.
Original comment by andrejoh...@gmail.com
on 10 Oct 2011 at 2:39
No problem, we'll leave the bug open for now.
Original comment by archie.c...@gmail.com
on 10 Oct 2011 at 2:42
This issue should be set to state 'won´t fix'.
First, the maintainer of Kaptcha doesn't believe in using central repositories:
See discussion under http://code.google.com/p/kaptcha/issues/detail?id=12#c5
Second, the Kaptcha jar is incorporating lots of classes from com.jhlabs, so
not all sources are available. Those incorporated classes might introduce
licencing issues, at least it is waisteing disk space (The jar contains 232Kb
classes from com.google.code.kaptcha in contrast to 1,2Mb of 'borrowed' class
files from com.jhlabs). And Jerry Huxtable would not like to see his work
distributed without having his name mentioned.
Original comment by fifteenk...@gmail.com
on 31 Mar 2012 at 1:15
That works for me. It makes more sense to use projects where source is easily
accessible and that the project owner is interested in making life easy for
people. I had hoped to go back and address this, but I lost the motivation.
Original comment by andrejoh...@gmail.com
on 31 Mar 2012 at 2:42
Looks like Kaptcha is maintained in Amy-Winehose-mode:
NO, NO, NO!
http://code.google.com/p/kaptcha/issues/detail?id=41
http://code.google.com/p/kaptcha/issues/detail?id=50
http://code.google.com/p/kaptcha/issues/detail?id=66
Original comment by fifteenk...@gmail.com
on 31 Mar 2012 at 7:09
Resolving WON'T FIX.
Original comment by archie.c...@gmail.com
on 2 Apr 2012 at 2:19
Original issue reported on code.google.com by
aj...@sympatico.ca
on 4 Apr 2011 at 1:11