Install of JVMMonitor via Eclipsen 3.7 "add new software fails"

[GoogleCodeExporter]

Attempted to add JVMMonitor to a fresh Eclipse 3.7 installtion. After accepting 
the license aggreement and waiting about 30s for the installation to begin I 
got an error dialog: 

"Installing Software" has encountered a problem.

An error occurred while collecting items to be installed
session context was:(profile=epp.package.java, 
phase=org.eclipse.equinox.internal.p2.engine.phases.Collect, operand=, action=).
Artifact not found: osgi.bundle,org.jvmmonitor.core,3.7.1.201108172315.
http://www.jvmmonitor.org/updates/3.7/plugins/org.jvmmonitor.core_3.7.1.20110817
2315.jar
Artifact not found: osgi.bundle,org.jvmmonitor.doc,3.7.1.201108172315.
http://www.jvmmonitor.org/updates/3.7/plugins/org.jvmmonitor.doc_3.7.1.201108172
315.jar
Artifact not found: 
org.eclipse.update.feature,org.jvmmonitor,3.7.1.201108172315.
http://www.jvmmonitor.org/updates/3.7/features/org.jvmmonitor_3.7.1.201108172315
.jar
Artifact not found: osgi.bundle,org.jvmmonitor.tools,3.7.1.201108172315.
http://www.jvmmonitor.org/updates/3.7/plugins/org.jvmmonitor.tools_3.7.1.2011081
72315.jar
Artifact not found: osgi.bundle,org.jvmmonitor.ui,3.7.1.201108172315.
http://www.jvmmonitor.org/updates/3.7/plugins/org.jvmmonitor.ui_3.7.1.2011081723
15.jar

Original issue reported on code.google.com by s...@stodge.org on 31 Aug 2011 at 11:21

[GoogleCodeExporter]

I believe it's quite urgent, Indigo is now the standard.
Tks

Original comment by tullio0...@gmail.com on 13 Sep 2011 at 12:26

[GoogleCodeExporter]

I've just noticed - this also fails in Eclipse 3.6. I'd be surprised if anybody 
can isntall JVMMointor by the usual means right now.

Original comment by s...@stodge.org on 15 Sep 2011 at 9:45

[GoogleCodeExporter]

I should add: This error was observed using Eclipse 3.6 & 3.7 running Java 6 
32bit on Windows XP. I've not tested any non-Windows or 64 bit platforms.

Original comment by s...@stodge.org on 15 Sep 2011 at 9:47

[GoogleCodeExporter]

The current Google Code downloads specify "to be manually dropped in dropins 
folder" in the comments. JVM Monitor (3.7.1) beta install was successful for me 
on Eclipse 3.7 by unzipping it to the Eclipse "dropins" folder.

Original comment by ews...@gmail.com on 15 Sep 2011 at 9:50

[GoogleCodeExporter]

Your p2 update site is broken... It specifies jars which aren't available -- in 
fact the jars all have the following timestamp:
   201108172328

You can fix this by CD'ing into the udpate site and doing:
eclipse -nosplash -application 
org.eclipse.equinox.p2.publisher.FeaturesAndBundlesPublisher 
-metadataRepository file:/`pwd` -artifactRepository  file:/`pwd` -source `pwd` 
-configs ALL

(or just regenerate using the site publisher within eclipse...)
http://wiki.eclipse.org/Equinox/p2/Publisher

Original comment by jamesbla...@gmail.com on 29 Nov 2011 at 1:35

[GoogleCodeExporter]

New release 3.7.2 is available, and the issue #63 with 3.7.1 should disappear.

Original comment by yoshitak...@gmail.com on 12 Feb 2012 at 1:31

• Changed state: Fixed