Dependency on http extensions android2 and android3; predictable version dependency

Add dependency on http extensions android2 and android3 so the built zip assembly has those jars in it.

Revert back to specifying the HTTP project dependency explicitly.  This brings back the predictability in behavior.  It also ensures that if there is a built SNAPSHOT library, that it will still use the release library, not the snapshot.  It also speeds up the process of computing the dependency, because if you specify a version range it requires a check to all repositories for an updated version.

[aiuto, 2011-07-28 03:08:41]

http://codereview.appspot.com/4826047/diff/1/pom.xml
File pom.xml (right):

http://codereview.appspot.com/4826047/diff/1/pom.xml#newcode12
pom.xml:12: <version>1.5.0-beta-SNAPSHOT</version>
Don't you want to move this out of SNAPSHOT too.

http://codereview.appspot.com/4826047/diff/1/pom.xml#newcode103
pom.xml:103: </dependency>
Is there a better way to to do this, like depending on the whole assembly?

It seems strange that we can define them, but not depend on them.

[yanivi, 2011-07-28 12:58:32]

http://codereview.appspot.com/4826047/diff/1/pom.xml
File pom.xml (right):

http://codereview.appspot.com/4826047/diff/1/pom.xml#newcode12
pom.xml:12: <version>1.5.0-beta-SNAPSHOT</version>
On 2011/07/28 03:08:41, aiuto wrote:
> Don't you want to move this out of SNAPSHOT too.

No.  This is done automatically by Maven as part of the release process.

http://codereview.appspot.com/4826047/diff/1/pom.xml#newcode103
pom.xml:103: </dependency>
On 2011/07/28 03:08:41, aiuto wrote:
> Is there a better way to to do this, like depending on the whole assembly?
> 
> It seems strange that we can define them, but not depend on them.

Done.  Great idea, thanks!

[aiuto, 2011-07-28 13:44:34]

lgtm

http://codereview.appspot.com/4826047/diff/1/pom.xml
File pom.xml (right):

http://codereview.appspot.com/4826047/diff/1/pom.xml#newcode12
pom.xml:12: <version>1.5.0-beta-SNAPSHOT</version>
On 2011/07/28 12:58:32, yanivi wrote:
> On 2011/07/28 03:08:41, aiuto wrote:
> > Don't you want to move this out of SNAPSHOT too.
> 
> No.  This is done automatically by Maven as part of the release process.

OK. But huh? I can't believe they designed it backwards like that. Things should
be defined in terms of truth, and at push time we should be able to say if it is
a snapshot or release.

[yanivi, 2011-07-28 14:54:18]

On 2011/07/28 13:44:34, aiuto wrote:
> lgtm
> 
> http://codereview.appspot.com/4826047/diff/1/pom.xml
> File pom.xml (right):
> 
> http://codereview.appspot.com/4826047/diff/1/pom.xml#newcode12
> pom.xml:12: <version>1.5.0-beta-SNAPSHOT</version>
> On 2011/07/28 12:58:32, yanivi wrote:
> > On 2011/07/28 03:08:41, aiuto wrote:
> > > Don't you want to move this out of SNAPSHOT too.
> > 
> > No.  This is done automatically by Maven as part of the release process.
> 
> OK. But huh? I can't believe they designed it backwards like that. Things
should
> be defined in terms of truth, and at push time we should be able to say if it
is
> a snapshot or release.

mvn release:prepare removes the -SNAPSHOT from the top-level <version> from the
pom.xml files, hg commits it and creates a 1.5.0-beta Hg tag.   

Clearly this is only appropriate for a non-snapshot release. I would need to
investigate if there is a way to modify the script to do a snapshot release. 
But let's continue that aspect of the discussion in a separate e-mail thread.