Issue 7 in srmi: Check on the class out-of-date check, especially in case of jar files.

[codesite...@google.com]

Issue 7: Check on the class out-of-date check, especially in case of
jar files.
http://code.google.com/p/srmi/issues/detail?id=7

New issue report by mohammad.nabil.h:
Check that line (SRMI.RemotingServices.ClassGeneration.ClassGenerator.java)
String fullPathOfDependencyClassFile = destinationFolder +

package_.replace(".",java.lang.System.getProperty("file.separator")) +
java.lang.System.getProperty("file.separator") +
wrappedUnQualifiedClassName +
".class";

It results in a double // before the class name!
That also assumes class files are available, it doesn't consider if they
are in a jar file.

Issue attributes:
Status: Accepted
Owner: mohammad.nabil.h
Labels: Type-Defect Priority-Medium

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings

[codesite...@google.com]