This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
NB: 6.7.1 FCS OS: Ubuntu 9.04 JDK: 1.6.0_13 1. Invoke Team>Kenai>New Kenai Project 2. Fill in the first step of the wizard 3. Select external bugtracking and fill in following address (incorrect): http://kenai.com/bugzilla/buglist.cgi?product=brumlatex&order=Importance&limit=25 4. Click the Finish button -> The process starts, but it does not finish due to invalid path, the wizard stays on the screen -> The check should be performed immediately after the user presses the Finish button
Are you sure that process didn't finish because of invalid ext. repo. path? I just created a project with exactly the same path as external repo, see testkenai project 'kenaiproject989898'. There was probably some different problem than invalid path or was it in error message?
Oh, I wrote "repo" instead the "bugtracking" in the summary field... shame on me - the problem is with bug tracking... description is correct... In trunk, the error message that is in the dialog is: "Issue Tracking creation failed: Name is invalid" - the wizard remains on the screen, Finish button is disabled, you can click the Back button though. But otherwise, the project is created. IMO information about unsuccessfully created features should be displayed in a dialog that shows up after the wizard closes, so that you cannot navigate there and back... (Maybe they could be displayed together with instruction about what has to be fixed?)
Well, it's general problem coming from the fact that project creation is not atomic operation but series of steps - creating project, creating repo, creating issue tracking, chat, ... and each step can fail independently on others. We must somehow divide to failures that can be fixed in the wizard (then leave the wizard open and Back enabled) and failures that can be fixed afterward on web site (because the project has been already created, but some feature not).
*** Issue 165711 has been marked as a duplicate of this issue. ***
WAD. Would need a UI spec to do it differently ...