1.7.5 seems to have lagging 1.7.4 dependencies

[GoogleCodeExporter]

What steps will reproduce the problem?
1. delete the maven folder `rm ~/.m2`
2. update an appengine-maven-plugin project to appspot to trigger dependencies 
downloading `mvn appengine:update`

What is the expected output? What do you see instead?

Expected output is that maven only downloaded 1.7.5 artifacts.

Instead, the following hierarchy can be observed in the .m2 folder:

mog@becca:~/.m2/repository/com/google$ tree -L 2 appengine/
appengine/
├── appengine
│   ├── 1.7.4
│   └── 1.7.5
├── appengine-api-1.0-sdk
│   └── 1.7.5
├── appengine-api-stubs
│   └── 1.7.5
├── appengine-java-sdk
│   └── 1.7.5
├── appengine-maven-plugin
│   └── 1.7.5
├── appengine-testing
│   └── 1.7.5
└── appengine-tools-sdk
    └── 1.7.4

What version of the product are you using? On what operating system?
I do not have my original computer here to check but it's a debian 7 with 
default packaged maven installation.

Please provide any additional information below.

Here is a link to the original Stack Overflow question: 
http://stackoverflow.com/questions/15112319/appengine-maven-plugin-1-7-5-seems-t
o-have-incomplete-java7-support-because-of-l

The direct consequence of this dependencies problem seems to be a non complete 
java 7 support, although the original problem might have come from something 
else entirely.

Original issue reported on code.google.com by mog...@gmail.com on 5 Mar 2013 at 7:12

[GoogleCodeExporter]

Original comment by matts...@google.com on 6 Mar 2013 at 2:50

• Changed state: Accepted

[GoogleCodeExporter]

Pushing 1.7.6 today, will fix this issue for good.  Using the enforcer plugin 
to ensure it doesn't happen again.

Original comment by matts...@google.com on 19 Mar 2013 at 8:38

[GoogleCodeExporter]

Original comment by matts...@google.com on 19 Mar 2013 at 8:38

• Changed state: Fixed