search

barbolo / kaptcha

Automatically exported from code.google.com/p/kaptcha
Other
0 stars 1 forks source link

Maven & The kaptcha project #12

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
How can I use the kaptcha jar if I'm using maven? 
Is there a POM.xml for the kapatha project?

Thanks.

Original issue reported on code.google.com by chava.t...@gmail.com on 30 Mar 2008 at 7:11

GoogleCodeExporter commented 9 years ago 
Don't use maven. I'm very much an anti-maven person and forcing projects to 
include a POM just so that you can 
use them is a great reason why you shouldn't use maven. There will never be a 
POM for kaptcha. Sorry.

Original comment by latch...@gmail.com on 30 Mar 2008 at 4:37

GoogleCodeExporter commented 9 years ago 
For those who need it, you can use

mvn install:install-file -Dfile=kaptcha-2.2.jar -DgroupId=com.google.code \
    -DartifactId=kaptcha -Dversion=2.2 -Dpackaging=jar

to install it in your local repository. 

Of course, it would be better if somebody go through the
http://maven.apache.org/guides/mini/guide-central-repository-upload.html 
process and
upload the kaptcha into the central maven repositories. Since the author does 
not
want to deal with maven, I think, there is a possibility that they accept 
library
from someone else.

Original comment by WFr...@gmail.com on 12 Jun 2008 at 8:15

GoogleCodeExporter commented 9 years ago 
Issue 41 has been merged into this issue.

Original comment by latch...@gmail.com on 23 Jun 2009 at 3:14

GoogleCodeExporter commented 9 years ago 
I am not a maven user (thank god - been there, done that, escaped running with 
my
feet set on fire) but there are other tools that make extensive use of maven
repositories such as ivy and gradle. These are nice tools, and anyway I wouldn't
expect people to drop maven because of a single library dependence, which means 
that
this is just making integration uncomfortable.

Original comment by icol...@gmail.com on 10 Aug 2009 at 11:32

GoogleCodeExporter commented 9 years ago 
This isn't really a discussion forum, but whatever.

I don't believe in using central repositories for jar files. I think it is a 
bad idea. If you 
want your project to build 5 years from now, the best solution is to check the 
jar files 
in with the project code. End of story. I've been doing it that way for many 
years now 
and I've come to the conclusion that that is the best way to manage things. As 
much 
as Ivy is a great dep management solution without the baggage of Maven, the 
reality 
is that you don't really need it either. For my larger projects, I have a 
'repo' which is a 
svn project that is aptly called 'alexandria'. I put all my jar files in there 
along with a 
jar.properties file. I can then import that properties file into ant and refer 
to the jars 
directly by property name. ${kaptcha.jar}. My build process just grabs the jar 
files 
from this repo (which is checked out locally). To ensure I have the latest 
version of 
that repo, I use my svntask to do a svn update before my build. This works 
*great* 
and in 3 years of doing it this way across many large projects, I haven't had a 
single 
problem.

Regardless of what you say here, this issue will remain as WontFix. I'm not 
convinced 
that there is anything that I need to do.

Original comment by latch...@gmail.com on 10 Aug 2009 at 3:35

GoogleCodeExporter commented 9 years ago 
Issue 50 has been merged into this issue.

Original comment by latch...@gmail.com on 15 Apr 2010 at 3:17

GoogleCodeExporter commented 9 years ago 
Not asking for this to be addressed, just wanted to let project maintainer know 
that this keeps us from using this software (and from donating money).  Sorry 
you don't like Maven, and even more sorry you have such a chip on your shoulder 
about it.

I know you said this is not a discussion forum, but we all get to make our own 
decisions about what is important.

Best of luck in the future.

Original comment by derf.cla...@gmail.com on 21 Mar 2011 at 11:26

GoogleCodeExporter commented 9 years ago 
I've gotten $0 in donations so far, yet 1700+ downloads. Why don't you petition 
the maven developers to create a system that doesn't require me to do more work.

Original comment by latch...@gmail.com on 21 Mar 2011 at 11:42

GoogleCodeExporter commented 9 years ago 
That stinks.  I'm sorry to hear that more people haven't given back.

Original comment by derf.cla...@gmail.com on 23 Mar 2011 at 3:24

GoogleCodeExporter commented 9 years ago 
Issue 66 has been merged into this issue.

Original comment by latch...@gmail.com on 10 Mar 2012 at 6:26

GoogleCodeExporter commented 9 years ago 
Issue 68 has been merged into this issue.

Original comment by latch...@gmail.com on 18 Apr 2012 at 4:18

GoogleCodeExporter commented 9 years ago 
So then, if you really think that maven sucks and you are better than everyone, 
I'll fork your code, made some optimizations, change it to a maven project, and 
then put it in maven repositories.

Also, you should try to not commit your eclipse preferences, since it is not 
part of your project code.

Hope you don't mind if I do that :)

Best regards,
Carlos

Original comment by caarlos0 on 13 Aug 2012 at 5:34

GoogleCodeExporter commented 9 years ago 
Sounds great Carlos! Have fun with that.

Not sure I understand your comment about Eclipse, but whatever.

Original comment by latch...@gmail.com on 13 Aug 2012 at 5:37

GoogleCodeExporter commented 9 years ago 
For those having problems with this try:
    <repositories>
        <repository>
            <id>google-maven-snapshot-repository</id>
            <name>Google Maven Snapshot Repository</name>
            <url>https://m2repos.googlecode.com/svn/nexus</url>
            <snapshots>
                <enabled>true</enabled>
            </snapshots>
        </repository>
    </repositories>

Original comment by tbarab...@gmail.com on 26 Sep 2012 at 2:19

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
To work with the Google Maven Snapshot Repository, use the following:

        <dependency>
            <groupId>com.google.code</groupId>
            <artifactId>kaptcha</artifactId>
            <version>2.3.2</version>
        </dependency>

Original comment by ejy...@gmail.com on 24 Apr 2013 at 11:03

GoogleCodeExporter commented 9 years ago 
Any chance of getting the 2.3 version added to this repo too?  It's required 
for the Tapestry-Kaptcha library and I have no choice but to use maven (not 
that that's a bad thing IMHO).

Original comment by bentitma...@gmail.com on 30 May 2013 at 1:36

GoogleCodeExporter commented 9 years ago 
Hi, I am stuck on this same kaptcha 2.3 issue when importing the 
tapestry5-hotel-booking project into Eclipse Juno.  Can someone point a way out 
of this?

Original comment by cenja...@gmail.com on 19 Jun 2013 at 8:45

GoogleCodeExporter commented 9 years ago 
For anyone else who runs into this pain, someone has finally uploaded the 2.3 
version to an m2 repo:

https://maven-us.nuxeo.org/nexus/content/repositories/public

Maven is awesome.

Original comment by bentitma...@gmail.com on 29 May 2014 at 9:10

GoogleCodeExporter commented 9 years ago 
I would not trust that version. I didn't build it and you have no idea what 
code is in it. For all you know it is sending any sensitive information on your 
server somewhere.

I've come around to the need and use of maven, but I still think it is a pile 
of shit.

Original comment by latch...@gmail.com on 29 May 2014 at 3:53

GoogleCodeExporter commented 9 years ago 
Yesterday, I did some work to put it maven central 
(repo here: https://github.com/codingtony/kaptcha)

I was about to release it to maven central when I have found another project 
that did almost the same work as I did : https://github.com/axet/kaptcha

The repo is already on maven central

    <dependency>
      <groupId>com.github.axet</groupId>
      <artifactId>kaptcha</artifactId>
      <version>0.0.9</version>
    </dependency>

I did not want to do a second fork for nothing. So I decided to put my release 
to maven central on hold. 

However my repo will stay there if the author of the original kaptcha project 
want to start from there to publish to maven central.

Thanks for your work on this project.

Original comment by t.bussie...@gmail.com on 3 Aug 2014 at 2:23