Adrian,
I wouldn't recommend to use both p2 and classic update manager at the
same time. It is possible that your issue caused by this mix. Of course
there is still a chance that there is something wrong in m2eclipse
update site, but we test every release and verify that migration from
the previously installed version works properly. We only test updating
with new p2 update manager and it been working ok in our tests. From
your description the only difference is that you are using classic
update manager, so I would suggest to try without it.
By the way, you can see list of installed and not activated plugins in
PDE plugin registry view
regards,
Eugene
adrians wrote:
I just wanted to give some additional information on the installation
failure. At the point the error dialog appears, the plugin jars are already
copied under the Eclipse install directory (under features and plugins), but
checking the configuration with the option "Manage Configuration..." reveals
some problems with each feature - I've enabled the older update manager to
be able to see the status of misconfigured plugins, but the failed install
was attempted using p2 of Eclipse 3.4. The status for each feature indicates
that the corresponding plugins are not found, but as I said, the jars were
copied to the plugins directory.
Adrian
adrians wrote:
For the last few dev releases I've been having a hard time installing the
plugin under Eclipse 3.4. I uninstall the old version and then try to
install a newer one. Partway through the update process a I get a dialog
telling me:
"An error occurred during provisioning.
Error reading signed content.
The file
"C:\dev\eclipse\plugins\org.eclipse.zest.core_1.0.0.v20080115.jar" does
not exist"
The last time I finally managed to install the dev build by starting with
a fresh Eclipse install and somehow I got m2eclipse to install. Looks like
I'm going to have to do that again since I've now uninstalled the previous
version. Any clue as to what might be causing this?
Just for reference, I install the WTP plugins (latest M build of 3.0.1
prior to actual release) under dropings by manually unzipping there. I'm
not sure if these plugins are related to the problem, but maybe the zest
stuff is installed as part of that plugin set and is interfering somehow.
In any case, even with this WTP install, I managed to get m2eclipse to
install somehow - just not sure why it failed in the first place. I'm also
using the latest working M build of Eclipse 3.4.1 for Windows (Build id:
M20080716-0800).
Cheers,
Adrian
Eugene Kuleshov wrote:
We have published stable development build 0.9.6.20080822-1053. You
can install it from the dev update site at
http://m2eclipse.sonatype.org/update-dev/
This build is focused on bug fixes and
This build includes number of bug fixes for the Form-based POM editor.
See full list of fixed issues at http://tinyurl.com/6rhdwr
There only new feature added since previous dev build is option to
focus Dependency graph and Hierarchy viewers in Maven POM editor on
selected dependency scope. See mode details on New and Noteworthy
features for this and previous builds on the wiki at
http://docs.codehaus.org/display/M2ECLIPSE/New+and+Noteworthy
As always, we would like to hear your feedback. Please don't hesitate
to share your thoughts in the news group and mailing lists, submit bug
reports to the project issue tracker [1] and contribute to project
documentation on the wiki [2].
Thanks
m2eclipse team
[1] http://jira.codehaus.org/browse/MNGECLIPSE
[2] http://docs.codehaus.org/display/M2ECLIPSE
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
