Re: [wtp-dev] Status of M9 Candidate build -- we are not there yet, but

[Chuck Bridgham <cbridgha@xxxxxxxxxx>]

Hi Sachin,

Yes this could be a OS issue, and we
may need to change our code a bit...  Its trying to get the "JavaRuntime.getDefaultVMInstall();"
And thats null for you....

Can you set a default java vm?

- Chuck

Rational J2EE Tooling Team Lead
IBM Software Lab - Research Triangle Park, NC
Email:  cbridgha@xxxxxxxxxx
Phone: 919-254-1848 (T/L: 444)

Sachin Patel <sppatel2@xxxxxxxxx>
Sent by: wtp-dev-bounces@xxxxxxxxxxx

11/17/2005 09:11 AM

Please respond to
"General discussion of project-wide or architectural issues."

To	"General discussion of project-wide or architectural issues." <wtp-dev@xxxxxxxxxxx>
cc
Subject	Re: [wtp-dev] Status of M9 Candidate build -- we are not there yet,        but close -- ETA Thursday morning

Could this possibly be a platform specific issue?
I'm running and 
testing on MacOS X.  Here is the full stack trace and I am unable
to 
launch the project creation wizard due to this exception.

!ENTRY org.eclipse.ui 4 0 2005-11-17 08:54:57.229
!MESSAGE java.lang.NullPointerException
!STACK 0
java.lang.NullPointerException
    at 
org.eclipse.jst.common.project.facet.JavaFacetInstallDataModelProvider.getDefaultProperty(JavaFacetInstallDataModelProvider.java:40)
    at 
org.eclipse.wst.common.frameworks.internal.datamodel.DataModelImpl.getProperty(DataModelImpl.java:128)
    at 
org.eclipse.wst.common.componentcore.datamodel.FacetProjectCreationDataModelProvider.getValidPropertyDescriptors(FacetProjectCreationDataModelProvider.java:187)
    at 
org.eclipse.wst.common.frameworks.internal.datamodel.DataModelImpl.getValidPropertyDescriptors(DataModelImpl.java:318)
    at 
org.eclipse.wst.common.frameworks.internal.datamodel.ui.DataModelSynchHelper.setWidgetValue(DataModelSynchHelper.java:298)
    at 
org.eclipse.wst.common.frameworks.internal.datamodel.ui.DataModelSynchHelper$1.run(DataModelSynchHelper.java:221)
    at org.eclipse.swt.widgets.Synchronizer.syncExec(Synchronizer.java:152)
    at 
org.eclipse.ui.internal.UISynchronizer.syncExec(UISynchronizer.java:28)
    at org.eclipse.swt.widgets.Display.syncExec(Display.java:3510)
    at 
org.eclipse.wst.common.frameworks.internal.datamodel.ui.DataModelSynchHelper.synchUIWithModel(DataModelSynchHelper.java:212)
    at 
org.eclipse.wst.common.frameworks.internal.datamodel.ui.DataModelSynchHelper.synchComposite(DataModelSynchHelper.java:435)
    at 
org.eclipse.wst.common.frameworks.internal.datamodel.ui.DataModelSynchHelper.synchCombo(DataModelSynchHelper.java:472)
    at 
org.eclipse.wst.web.ui.internal.wizards.DataModelFacetCreationWizardPage.createServerTargetComposite(DataModelFacetCreationWizardPage.java:102)
    at 
org.eclipse.jst.j2ee.internal.wizard.J2EEComponentFacetCreationWizardPage.createTopLevelComposite(J2EEComponentFacetCreationWizardPage.java:47)
    at 
org.eclipse.wst.common.frameworks.internal.datamodel.ui.DataModelWizardPage.createControl(DataModelWizardPage.java:95)
    at org.eclipse.jface.wizard.Wizard.createPageControls(Wizard.java:179)
    at 
org.eclipse.wst.common.project.facet.ui.AddRemoveFacetsWizard.createPageControls(AddRemoveFacetsWizard.java:250)
    at 
org.eclipse.jface.wizard.WizardDialog.createPageControls(WizardDialog.java:611)
    at 
org.eclipse.jface.wizard.WizardDialog.setWizard(WizardDialog.java:965)
    at 
org.eclipse.jface.wizard.WizardDialog.updateForPage(WizardDialog.java:1016)
    at 
org.eclipse.jface.wizard.WizardDialog.access$2(WizardDialog.java:1013)
    at org.eclipse.jface.wizard.WizardDialog$4.run(WizardDialog.java:1003)
    at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:69)
    at 
org.eclipse.jface.wizard.WizardDialog.showPage(WizardDialog.java:1001)
    at 
org.eclipse.jface.wizard.WizardDialog.nextPressed(WizardDialog.java:753)
    at 
org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:345)
    at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:556)
    at 
org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:90)
    at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66)
    at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1380)
    at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1404)
    at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1389)
    at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1237)
    at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3060)
    at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2712)
    at org.eclipse.jface.window.Window.runEventLoop(Window.java:809)
    at org.eclipse.jface.window.Window.open(Window.java:787)
    at 
org.eclipse.ui.actions.NewProjectAction.run(NewProjectAction.java:114)
    at org.eclipse.jface.action.Action.runWithEvent(Action.java:996)
    at 
org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:538)
    at 
org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:488)
    at 
org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:400)
    at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66)
    at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1380)
    at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1404)
    at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1389)
    at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1237)
    at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3060)
    at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2712)
    at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1699)
    at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1663)
    at 
org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:367)
    at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:143)
    at 
org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplication.java:103)
    at 
org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:226)
    at 
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:376)
    at 
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:163)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:324)
    at org.eclipse.core.launcher.Main.invokeFramework(Main.java:334)
    at org.eclipse.core.launcher.Main.basicRun(Main.java:278)
    at org.eclipse.core.launcher.Main.run(Main.java:973)
    at org.eclipse.core.launcher.Main.main(Main.java:948)

Sachin Patel wrote:
> I picked this driver up as well.  Is no one else hitting the
NPE when 
> hitting next after selecting a project creation wizard?  Is there
some 
> workaround I'm not aware of?
>
> -1 from me.
>
>
> Chuck Bridgham wrote:
>>
>> I picked up this build: 
>>  http://download.eclipse.org/webtools/committers/drops/I-I200511162235-200511162235/
>>
>>
>> Previous blocking problems are solved -    +1 for declaring
this build
>>
>> - Chuck
>>
>> Rational J2EE Tooling Team Lead
>> IBM Software Lab - Research Triangle Park, NC
>> Email:  cbridgha@xxxxxxxxxx
>> Phone: 919-254-1848 (T/L: 444)
>>
>>
>>
>> *David M Williams/Raleigh/IBM@IBMUS*
>> Sent by: wtp-dev-bounces@xxxxxxxxxxx
>>
>> 11/16/2005 05:06 PM
>> Please respond to
>> "General discussion of project-wide or architectural issues."
>>
>>
>>     
>> To
>>     wtp-dev@xxxxxxxxxxx
>> cc
>>     
>> Subject
>>     [wtp-dev] Status of M9 Candidate build -- we are
not there yet, 
>> but close -- ETA Thursday morning
>>
>>
>>
>>     
>>
>>
>>
>>
>>
>>
>> While we wait to confirm _116700_ 
>> <https://bugs.eclipse.org/bugs/show_bug.cgi?id=116700>
>> (both by the bug owners, and for a respin with Chuck's best guess
at 
>> a fix),
>> other teams should prepare for their more in-depth testing, be
sure 
>> test plans
>> are up to date, API document prepared (not to mention all that
facet 
>> documentation :)
>> etc.
>>
>> Chuck, will you be able to give a quick sanity check to be sure
the 
>> bug 116700
>> is fixed in a "built driver", as well as your local
fixes? (I had to 
>> "unjar" the websphere.core plugin too,
>> I don't think it was ever meant to be jarred?). The next I-build
>> candidate will be ready about 7 PM (Eastern).
>>
>> Lastly, I think we are still waiting for confirmation of I-build
>> suitability from Server Team?
>> (And .. I think Gorkem is "on call" this week for that
team?).
>>
>> Bottom line: I expect I-build to be officially promoted Thursday
>> morning.
>>
>> We will, though, still begin "lock down" mode ... auto
I-builds 
>> turned off, I-build only on request, with bugs listed in mail
to 
>> mailing list.
>> _______________________________________________
>> wtp-dev mailing list
>> wtp-dev@xxxxxxxxxxx
>> https://dev.eclipse.org/mailman/listinfo/wtp-dev
>>
>> ------------------------------------------------------------------------
>>
>> _______________________________________________
>> wtp-dev mailing list
>> wtp-dev@xxxxxxxxxxx
>> https://dev.eclipse.org/mailman/listinfo/wtp-dev
>>   
>
> _______________________________________________
> wtp-dev mailing list
> wtp-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/wtp-dev
>

_______________________________________________
wtp-dev mailing list
wtp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/wtp-dev