Guiceberry 3.3.1 Maven

[Roy Arnon]

Hi,

I've been using guiceberry for a while now, saw a new version came out but the version in Maven Central repo is still 3.0.

Any plans of updating the version there as well?

[Luiz-Otavio Zorzella]

Not being a maven user myself, I need help to figure out how to do this, as per (see last comment):

https://code.google.com/p/guiceberry/issues/detail?id=6#makechanges

Z

--
You received this message because you are subscribed to the Google Groups "guiceberry-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to guiceberry-use...@googlegroups.com.
To post to this group, send email to guiceber...@googlegroups.com.
Visit this group at http://groups.google.com/group/guiceberry-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[Roy Arnon]

ah but I see that tl4j is not required anymore per 

https://code.google.com/p/guiceberry/issues/detail?id=18

So all is needed is adding maven ant tasks. 

Just a quick question - which version of servlet-api-2.5 do you use? 

Out of these: 

http://search.maven.org/#search%7Cga%7C1%7Cservlet-api

Otherwise I see that easymock and tl4j are not needed and can be removed from build.xml no? (as they are missing from the trunk/lib dir)

[Roy Arnon]

Oh well. TL4J is required to build the project - I changed all dependencies to use maven central, but build fails:

    [javac] import com.google.common.testing.junit3.TearDownTestCase;

    [javac]                                        ^

    [javac] C:\Projects\guiceberry-read-only\src\com\google\inject\testing\guiceberry\junit3\GuiceBerryJunit3TestCase.java:19: error: package com.google.common.testing.junit3 does not exist

And from what I read up, it seems that sometime in the future most of the tl4j features will be in Guava, but this library is missing.

If you don't care about the older junit tests, the build compiles fine, but I don't know if you can afford to remove the junit3 tests.

[Roy Arnon]

OK, looked at tl4j, seems simple enough to add it to maven. Problem is that the files need to be PGP signed, which I'm assuming you guys at google would want to sign it. I can send you a patch with most of the code for tl4j pom to upload to maven, but you'll need to create a PGP signature. How does that sound?