On Thu, Nov 20, 2014 at 8:21 AM, Jochen Kemnade <jochen.kemn...@eddyson.de> wrote:
> Am 20.11.2014 um 17:10 schrieb Kalle Korhonen: > >> Will try gradlew. mavenLocal() was absolutely not by accident and I tried >> > Same error with gradlew (gradle 1.0). > to highlight the reason for it in the comments. Since the underlying >> kaptcha lib doesn't exist in Maven central the build would fail without >> mavenLocal(). >> > > Yes, and so it will for everyone who doesn't have the library in their > local maven repository. And every user's webapp build that uses > tapestry-kaptcha and does not use a repository that provides > com.google.kaptcha:kaptcha:2.3. > I think it would be better to leave the old version in place and leave it > to users to override it with a newer version if they like. > Also, we could try to talk the creator of the library into publishing a > newer version to Maven Central oder JCenter. > Yes, I perfectly understand that and again tried to highlight that in the commit comments. The newer kaptcha library is built with jdk 1.6. Given how difficult it was to get even a decision on T5.4 to move to JDK 1.6, I thought it was best to avoid that. Kalle > > Jochen > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org > For additional commands, e-mail: dev-h...@tapestry.apache.org > >