* class file java version check wrt maven config
* Recommiting the jars built with updated java version
* Updating encoding for demo as well for consistency
Normally it is not a good idea to place <version> constraints in the
definition of plugins in pom.xml unless a specific version really is
needed.
This patch removes the constraints.
There are various benefits to this, one of them is that it will always
build with the latest packaged version of the plugins on a Debian or
Ubuntu system.
Author: daniel@pocock.proR=jia.shao.peng@gmail.com
BUG=
Review URL: https://codereview.appspot.com/122480043
That lets the demo be part of the libphonenumber Maven project thus adds the following benefits:
- Automatically update the version of the demo and the libphonenumber artifact the demo depends on when performing a release.
- Let Maven handle the deployment of the demo to AppEngine without any need to install the AppEngine SDK.
- No need to push the dependency JARs (servlet, apache common fileupload/io) even if they are still here to let you use Ant if you prefer.
Note that this CL depends on CL 5395054.
Review URL: http://codereview.appspot.com/5405041