Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 363419 - Error in "File \ New \ Other \ Git \ Git Repository"
Summary: Error in "File \ New \ Other \ Git \ Git Repository"
Status: CLOSED DUPLICATE of bug 357951
Alias: None
Product: EGit
Classification: Technology
Component: UI (show other bugs)
Version: unspecified   Edit
Hardware: PC All
: P3 major (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-11-09 23:58 EST by Paul CLA
Modified: 2011-11-10 07:27 EST (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Paul CLA 2011-11-09 23:58:18 EST 
Build Identifier: 20110916-0149

The selected wizard could not be started.
Plug-in "org.eclipse.egit.ui" was unable to instantiate class "org.eclipse.egit.ui.internal.repository.NewRepositoryWizard".
org.eclipse.egit.ui.internal.repository.NewRepositoryWizard

\------
This is similar to https://bugs.eclipse.org/bugs/show_bug.cgi?id=357951, but not fixed...

Reproducible: Always

Steps to Reproduce:
info in summary
Comment 1 Remy Suen CLA 2011-11-10 06:46:33 EST 
Please provide the full stack trace.

What version of EGit are you using?
Comment 2 Paul CLA 2011-11-10 06:53:54 EST 
(In reply to comment #1)
> Please provide the full stack trace.
> 
> What version of EGit are you using?

Egit version: 1.1.0.201109151100-r.

This trace is all that shows Eclipse.
Comment 3 Remy Suen CLA 2011-11-10 07:01:08 EST 
(In reply to comment #2)
> Egit version: 1.1.0.201109151100-r.

The change was released after 1.1 was released so you are not going to have the fix.
Comment 4 Paul CLA 2011-11-10 07:27:40 EST 
(In reply to comment #3)
> (In reply to comment #2)
> > Egit version: 1.1.0.201109151100-r.
> 
> The change was released after 1.1 was released so you are not going to have the
> fix.

Ok

*** This bug has been marked as a duplicate of bug 357951 ***