Description of problem:

Customer is trying to access KieJar using "LATEST" key word via KieScanner but if jar is built today, it's working and if jar is old (not built today) than it's not working.

This is similar bug filed on community.

https://issues.jboss.org/browse/DROOLS-465

Version-Release number of selected component (if applicable):
BRMS 6.1.0 and BRMS 6.2.0

How reproducible:
try to access any old kie-jar (not built today) via KieScanner using LATEST key word.

For Example :
public class SampleRuleExecution {
	
	private  static KieServices ks = null;
	private static  KieContainer contnrExceptionLD = null;
	
	public static void main(String[] args){
		try{
	    	ks = KieServices.Factory.get();
	    	
	    	ReleaseId releaseId = ks.newReleaseId("example", "SampleProject", "LATEST"); //6.1.0
	    	System.out.println("releaseId : " + releaseId.getGroupId() + " : " + releaseId.getArtifactId() + " : " + releaseId.getVersion() );
			contnrExceptionLD = ks.newKieContainer(releaseId);
    	}catch(Exception e){
    		e.printStackTrace();
    	}
	}
}

Actual results:
SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
java.lang.RuntimeException: Cannot find KieModule: example:SampleProject:LATEST
	at org.drools.compiler.kie.builder.impl.KieServicesImpl.newKieContainer(KieServicesImpl.java:86)
	at com.sample.SampleRuleExecution.main(SampleRuleExecution.java:24)



Expected results:
Latest KieJar should be accessed from local maven repository.

Additional info:

Following are few more findings while working on this issue.

- If I am trying to access KieJar from sample java code via Kie-Scanner using "LATEST" key word and if the jar is built recently (today) than it is working properly where as if the project is not built today than kie-scanner is not considering the old jar (which is previously built and not built today) and facing this issue on BRMS 6.1.0 and 6.2.0.
 
- One more finding : If the "maven-metadata-loacl.xml" file is being updated manually by changing value of "lastUpdated" tag with latest value than it's working fine and in this scenario, it's not required to re-build the jar.
 
- While accessing jar from sample code (jar with old timestamp), than "maven-metadata-loacl.xml" is being removed from local repository and if you create new meta-data file than it's working fine.