Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 330780

Summary: Finish to create new SVN repository and share project in single operation fails
Product: [Technology] Subversive Reporter: Swati Koul <swati.koul>
Component: UIAssignee: Igor Burilo <igor.burilo>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: P3 CC: a.gurov, monaka, swati.koul
Version: unspecified   
Target Milestone: ---   
Hardware: PC   
OS: Windows XP   
Whiteboard:
Attachments:
Description Flags
The image describes the initial page where we set credentials
none
The error dailog none

Description Swati Koul CLA 2010-11-22 04:51:49 EST 
Build Identifier: 

Please make sure there are no current SVN locations in SVN Repository Exploring perspective.

And then follow Steps to reproduce, the operation fails with a null pointer exception.
Please take into consideration that it happens only when you are specifying a new SVN location which is not already there in SVN perspective.

Reproducible: Always

Steps to Reproduce:
Please make sure there are no current SVN locations in SVN Repository Exploring perspective.

1. Create any new Project. and then do Right Click Team -> Share Project.
2. Select SVN as the repository and press Next
3. In the Share Project Wizard, set SVN url, User and Password
4. Click Finish
5. Bug - Share Project fails with NullPointerException

Using Next to step through the wizard will correctly create the SVN location and add the project to source control.

If there is already an existing SVN location specified, specifying it and clicking Finish will correctly add the project to source control
Comment 1 Swati Koul CLA 2010-11-22 05:04:42 EST 
Created attachment 183555 [details]
The image describes the initial page where we set credentials
Comment 2 Swati Koul CLA 2010-11-22 05:05:14 EST 
Created attachment 183556 [details]
The error dailog
Comment 3 Alexander Gurov CLA 2010-12-08 15:03:57 EST 
Fixed.
Comment 4 Alexander Gurov CLA 2011-03-22 03:11:56 EDT 
*** Bug 315521 has been marked as a duplicate of this bug. ***