Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP

Loading…

Kaptcha component conflicts with chenillekit-kaptcha when depending on only tapx-prototype #5

Closed
BuckOFive opened this Issue · 4 comments

3 participants

@BuckOFive

tapx-prototype depends on tapx-core which contains a kaptcha component which interferes with chenillekit-kaptcha.

Possible suggestions: move kaptcha component into its own library like the other tapx components or remove the dependencies on tapx-core from tapx-prototype.

Service id 'KaptchaProducer' has already been defined by org.chenillekit.image.ChenilleKitImageModule.buildKaptchaProducer(Map) (at ChenilleKitImageModule.java:38) and may not be redefined by com.howardlewisship.tapx.core.services.KaptchaProducerImpl(Map, boolean) (at KaptchaProducerImpl.java:39) via com.howardlewisship.tapx.core.services.CoreModule.bind(ServiceBinder) (at CoreModule.java:29). You should rename one of the service builder methods.

@hlship
Owner

Remove dependency from tapx-prototype to tapx-core

Closed by 484a05d

@hlship
Owner

I may spin the Kaptcha stuff into a seperate project; still a tapx component, though.

@jochenberger
Collaborator

The same happens for tapx-datefield.
I created a separate module for the Kaptcha parts in my fork. http://github.com/jochenberger/tapx/commit/87a6e6c70d83338b1dd001cff8c969ee98089584

@hlship
Owner

Fixed by 2ca6139 ... broke out a new tapestry-kaptcha module

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.