Closed GoogleCodeExporter closed 9 years ago
I was able to get the jar from maven repos :
http://maven.objectify-appengine.googlecode.com/git/com/googlecode/objectify/obj
ectify/4.0a4/. But the build proccess with gradle should be fixed..
Original comment by sebastigurin
on 26 Sep 2012 at 4:19
Thanks for the report! I will get this fixed later today.
In the mean time just to get things going, you can create a
~/.gradle/gradle.properties with the following:
nexusUsername=anyrandomstring
nexusPassword=anyrandomstring
Original comment by lhori...@gmail.com
on 26 Sep 2012 at 4:31
Aja, I suspected a properties file should be filled. You should mention this on
file https://github.com/stickfigure/objectify/blob/master/README.mkd
also, I think It can be nice if you add a small section at
http://code.google.com/p/objectify-appengine/wiki/Setup indicating how to build
the jar from latest sources. Something like:
{{{
git clone git://github.com/stickfigure/objectify.git
cd objectify
cat > ~/.gradle/gradle.properties
nexusUsername=anyrandomstring
nexusPassword=anyrandomstring
Ctrl-D
gradle build
}}}
Original comment by sebastigurin
on 26 Sep 2012 at 4:39
Build now works out of the box. Also updated Setup/ContributingToObjectify.
Original comment by lhori...@gmail.com
on 20 Oct 2012 at 5:50
Sorry to be picky, but I don't think this is resolved.
I think new users will still make the same mistake I did: download 3.1 thinking
it is the current version, and then not understanding why it doesn't jive with
the documentation.
If download page will no longer have a download for the current version then I
think it would help to have a note there to that effect, or a prominent note on
the project's home page (or maybe the release page).
Original comment by t...@malcolmson.ca
on 20 Oct 2012 at 9:19
There will be a download for v4. It's not quite ready yet. It's coming.
The build problem described in this issue is, however, resolved. While it
might make sense to create a separate issue for "hurry up and get v4 released",
please don't.
Original comment by lhori...@gmail.com
on 21 Oct 2012 at 7:11
Very nice, thanks for the fix. Verified. You should close this issue.
Original comment by sebastigurin
on 21 Oct 2012 at 6:17
Original issue reported on code.google.com by
sebastigurin
on 26 Sep 2012 at 4:14