Wrong version displayed on monitoring page and desktop (jnlp) app

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Include javamelody 1.56.0 in your project. In my case maven dependency
2. Start the application and open the monitoring page 
3. Scroll down to page - Just before Debugging logs

What is the expected output? What do you see instead?
Expected: JavaMelody 1.56.0 and also under debugging logs it should show DEBUG  
   JavaMelody version: 1.56.0.
Current Behavior: Just above Debugging logs, it shows JavaMelody 1.55.0 and 
under Debugging logs, it shows  DEBUG     JavaMelody version: 1.55.0

What version of the product are you using? On what application server, JDK,
operating system?
JavaMelody 1.56.0
Server: Tomcat 7.0.35
JDK: 1.7.0_51
OS: OS X - 10.10.3

Please provide any additional information below.

Original issue reported on code.google.com by jay.khimani on 27 Jun 2015 at 11:59

Attachments:

• [Screen Shot 2015-06-27 at 13.56.56.png](https://storage.googleapis.com/google-code-attachments/javamelody/issue-480/comment-0/Screen Shot 2015-06-27 at 13.56.56.png)
• [Screen Shot 2015-06-27 at 13.58.15.png](https://storage.googleapis.com/google-code-attachments/javamelody/issue-480/comment-0/Screen Shot 2015-06-27 at 13.58.15.png)
• [Screen Shot 2015-06-27 at 13.58.49.png](https://storage.googleapis.com/google-code-attachments/javamelody/issue-480/comment-0/Screen Shot 2015-06-27 at 13.58.49.png)

[GoogleCodeExporter]

For the desktop (jnlp), that's normal for now. The jar file is still downloaded 
from googlecode and is v1.49.0, but compatible with the latest versions, like 
in your project.
I will need to move that to github probably.

For the monitoring page, I think that the issue is on your side. Because when 
you download the following file and open it in a zip manager, the 
VERSION.properties contains 1.56.0.
So I suggest to look in the "Debugging logs" the line: "JavaMelody classes 
loaded from ...", to check if you still have in fact 1.55.0.

Original comment by evernat@free.fr on 27 Jun 2015 at 2:47

[GoogleCodeExporter]

Forgotten the Maven file which is 
http://search.maven.org/remotecontent?filepath=net/bull/javamelody/javamelody-co
re/1.56.0/javamelody-core-1.56.0.jar

Original comment by evernat@free.fr on 27 Jun 2015 at 3:24

[GoogleCodeExporter]

Ah right, mvn clean is what I was missing and intellij idea was still pickingup 
1.55.0. Thanks

Original comment by jay.khimani on 27 Jun 2015 at 3:37

[GoogleCodeExporter]

ok pour mvn clean

javamelody-swing jar file will be upgraded (to 1.56.0) in the next release 
(1.57.0)

Original comment by evernat@free.fr on 5 Jul 2015 at 6:40

• Changed state: Invalid