Description of problem:

When new snapshot kjar are deployed on a maven repo and the kiescanner is not enabled, a newly created kiecontainer referring to that snapshot releaseId actually uses the old kjar (cached in the KieRepository) instead of downloading the new one from the maven repo.

How reproducible:

Always

Steps to Reproduce:

A pull request reproducing this issue has been provided here:

https://github.com/droolsjbpm/drools/pull/248/files

Actual results:

The 2nd KieContainer uses the old kjar instead of downloading the new one deployed in the maven repository.

Expected results:

when creating a new KieContainer it should check if a new snapshot has been deployed in the maven repo and then use it.