[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-1657) Imported Project's classpath container assuming server exists

[Rob Stryker (JIRA)]

    [ http://jira.jboss.com/jira/browse/JBIDE-1657?page=comments#action_12396952 ] 
            
Rob Stryker commented on JBIDE-1657:
------------------------------------

I made a slight change which made it friendlier. The user can now "edit" the incorrect classpath container and have a list of runtimes to select from.

HOWEVER:

This is *NOT* the approved UI for the user's use case.   Simply changing which runtime the classpath targets does NOT change the other files in the project that are runtime-specific... specifically   $project/.settings/org.eclipse.jst.common.project.facet.core.prefs and $project/.settings/org.eclipse.wst.common.project.facet.core.xml.

For the user's use case, the proper thing to do is:

1) import the project
2) observe the errors
3) right-click on the project, select properties
4) Go to the "targeted runtimes" section
5) check the box next to the runtime the user would like to target.

This changes both files AND the classpath container. 

> Imported Project's classpath container assuming server exists
> -------------------------------------------------------------
>
>                 Key: JBIDE-1657
>                 URL: http://jira.jboss.com/jira/browse/JBIDE-1657
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: JBossAS
>            Reporter: Rob Stryker
>         Assigned To: Rob Stryker
>             Fix For: 2.0.1
>
>         Attachments: runtimecontainerbug.png
>
>
> java.lang.NullPointerException
> 	at org.jboss.ide.eclipse.as.classpath.core.runtime.ProjectRuntimeClasspathProvider$RuntimeClasspathContainer.getDescription(ProjectRuntimeClasspathProvider.java:120)
> 	at org.eclipse.jdt.internal.ui.wizards.buildpaths.CPListLabelProvider.getCPListElementText(CPListLabelProvider.java:261)
> 	at org.eclipse.jdt.internal.ui.wizards.buildpaths.CPListLabelProvider.getText(CPListLabelProvider.java:78)
> 	at org.eclipse.jface.viewers.WrappedViewerLabelProvider.getText(WrappedViewerLabelProvider.java:108)
> 	at org.eclipse.jface.viewers.WrappedViewerLabelProvider.update(WrappedViewerLabelProvider.java:164)
> 	at org.eclipse.jface.viewers.ViewerColumn.refresh(ViewerColumn.java:135)
> 	at org.eclipse.jface.viewers.AbstractTableViewer.doUpdateItem(AbstractTableViewer.java:386)
> My guess is that your classpath container thinks the server exists...which it wont do in this case when he is creating a new project.
> That should be fixed in .0.1
> Workaround for user: delete the classpath entry about JBoss 4 server in classpath.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira