1:20 p.m.
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
Reporter: Rob Stryker
Fix For: 2.0.1
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
1:20 p.m.
New subject: [JBoss JIRA] Updated: (JBIDE-1657) Imported Project's classpath container assuming server exists
[ http://jira.jboss.com/jira/browse/JBIDE-1657?page=all ]
Rob Stryker updated JBIDE-1657:
-------------------------------
Component/s: JBossAS
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
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
1:20 p.m.
New subject: [JBoss JIRA] Assigned: (JBIDE-1657) Imported Project's classpath container assuming server exists
[ http://jira.jboss.com/jira/browse/JBIDE-1657?page=all ]
Rob Stryker reassigned JBIDE-1657:
----------------------------------
Assignee: Rob Stryker
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
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
4:12 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-1657) Imported Project's classpath container assuming server exists
[ http://jira.jboss.com/jira/browse/JBIDE-1657?page=comments#action_12395829 ]
Max Andersen commented on JBIDE-1657:
-------------------------------------
It should say "this case when one is importing/creating an existing project"
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
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
9:29 p.m.
New subject: [JBoss JIRA] Commented: (JBIDE-1657) Imported Project's classpath container assuming server exists
[ http://jira.jboss.com/jira/browse/JBIDE-1657?page=comments#action_12396108 ]
Rob Stryker commented on JBIDE-1657:
------------------------------------
Throwing a CoreException on initialization of that container instead. This should display
the error at the proper time and in teh proper location.
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
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
9:31 p.m.
New subject: [JBoss JIRA] Resolved: (JBIDE-1657) Imported Project's classpath container assuming server exists
[ http://jira.jboss.com/jira/browse/JBIDE-1657?page=all ]
Rob Stryker resolved JBIDE-1657.
--------------------------------
Resolution: Done
Requesting QA verify this bug as fixed. I cannot replicate.
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
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
4:59 a.m.
New subject: [JBoss JIRA] Reopened: (JBIDE-1657) Imported Project's classpath container assuming server exists
[ http://jira.jboss.com/jira/browse/JBIDE-1657?page=all ]
Max Andersen reopened JBIDE-1657:
---------------------------------
reopening since the user still does not have anyway to really fix it.
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
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
5:01 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-1657) Imported Project's classpath container assuming server exists
[ http://jira.jboss.com/jira/browse/JBIDE-1657?page=comments#action_12396534 ]
Max Andersen commented on JBIDE-1657:
-------------------------------------
The user should at least be able to select the runtime they want to use instead.
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
5:01 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-1657) Imported Project's classpath container assuming server exists
[ http://jira.jboss.com/jira/browse/JBIDE-1657?page=comments#action_12396535 ]
Max Andersen commented on JBIDE-1657:
-------------------------------------
p.s. the user still gets "page contains invalid values"
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
5:01 a.m.
New subject: [JBoss JIRA] Updated: (JBIDE-1657) Imported Project's classpath container assuming server exists
[ http://jira.jboss.com/jira/browse/JBIDE-1657?page=all ]
Max Andersen updated JBIDE-1657:
--------------------------------
Attachment: runtimecontainerbug.png
see screenshot what happens for the user.
the error log also has entries for the runtime to not be there.
it is extremely easy to reproduce:
Create project with runtime
delete the project (without deleting the files)
rename the runtime
reimport the project
bug is there
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
4:31 p.m.
New subject: [JBoss JIRA] Resolved: (JBIDE-1657) Imported Project's classpath container assuming server exists
[ http://jira.jboss.com/jira/browse/JBIDE-1657?page=all ]
Rob Stryker resolved JBIDE-1657.
--------------------------------
Resolution: Done
With the small change to use a friendlier wtp-related classpath container path, and the UI
method to accomplish the use case described, I'm closing this issue.
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
4:31 p.m.
New subject: [JBoss JIRA] Commented: (JBIDE-1657) Imported Project's classpath container assuming server exists
[ 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
3:42 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-1657) Imported Project's classpath container assuming server exists
[ http://jira.jboss.com/jira/browse/JBIDE-1657?page=comments#action_12396990 ]
Max Andersen commented on JBIDE-1657:
-------------------------------------
cool - what does WTP-related classpath container path mean ? Did we change the format of
the path or how ?
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
3:46 a.m.
New subject: [JBoss JIRA] Reopened: (JBIDE-1657) Imported Project's classpath container assuming server exists
[ http://jira.jboss.com/jira/browse/JBIDE-1657?page=all ]
Max Andersen reopened JBIDE-1657:
---------------------------------
looking at the commits it seem we changed to init the classpath to use the WTP runtime
ones instead ?
What does that mean for the existing classpath containers ? Are they deprecated ? Which
one are deprecated and could we please add a unittest to ensure we don't accidently
remove the support for them.
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
9:56 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-1657) Imported Project's classpath container assuming server exists
[ http://jira.jboss.com/jira/browse/JBIDE-1657?page=comments#action_12397202 ]
Rob Stryker commented on JBIDE-1657:
------------------------------------
The previous container still exists and has not been deprecated. It is actually the
delegate that is used when the WTP runtime classpath container path is used. It will
remain in existence. There was no change to plugin.xml here so support for the container
is in no way removed. If you insist, though, a unit test can be made.
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
11:56 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-1657) Imported Project's classpath container assuming server exists
[ http://jira.jboss.com/jira/browse/JBIDE-1657?page=comments#action_12397224 ]
Max Andersen commented on JBIDE-1657:
-------------------------------------
I insist.
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
6:42 p.m.
New subject: [JBoss JIRA] Closed: (JBIDE-1657) Imported Project's classpath container assuming server exists
[ http://jira.jboss.com/jira/browse/JBIDE-1657?page=all ]
Rob Stryker closed JBIDE-1657.
------------------------------
Resolution: Done
unit test making sure the old path still works has been added.
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
6636
days inactive
6650
days old
jbosstools-issues@lists.jboss.org
16 comments
2 participants
participants (2)
-
Max Andersen (JIRA) -
Rob Stryker (JIRA)