]
Lucia Jelinkova closed JBIDE-11240.
-----------------------------------
Verified JBDS Beta2
getting NPE when cloning existing app that have been manully typed in
instead of selected via dialog
----------------------------------------------------------------------------------------------------
Key: JBIDE-11240
URL:
https://issues.jboss.org/browse/JBIDE-11240
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Reporter: Max Rydahl Andersen
Assignee: Andre Dietisheim
Priority: Blocker
Fix For: 3.3.0.Beta2
Attachments: JBIDE-11361b.patch,
set-existing-app-when-typing-existingappname-2.patch,
set-existing-app-when-typing-existingappname-3.patch,
set-existing-app-when-typing-existingappname.patch
Can't import existing app.
EXECUTE: Start openshift wizard (from central or the new wizards, DONT use express
console)
EXECUTE: Check *existing app*
EXECUTE: Type in (do NOT use browse) your existing app name
EXECUTE: Press Finish
ASSERT: no errors
Result:
Getting this:
java.lang.NullPointerException
at
org.jboss.tools.openshift.express.internal.ui.wizard.appimport.AbstractImportApplicationOperation.cloneRepository(AbstractImportApplicationOperation.java:86)
at
org.jboss.tools.openshift.express.internal.ui.wizard.appimport.ImportNewProject.execute(ImportNewProject.java:72)
at
org.jboss.tools.openshift.express.internal.ui.wizard.OpenShiftExpressApplicationWizardModel.importProject(OpenShiftExpressApplicationWizardModel.java:81)
at
org.jboss.tools.openshift.express.internal.ui.wizard.OpenShiftExpressApplicationWizard$ImportJob.runInWorkspace(OpenShiftExpressApplicationWizard.java:281)
at
org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
If I use browse it fixes it, if I use new app it works, if I click back/next a few times
it seem to also fix it self.
So my guess is that the wizard is *not* taking the content of the existing app into
account - only takes it account if pressed browse or next a few times
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: