[JBoss JIRA] Created: (JBIDE-4719) JBoss Tools folder not displaying when I try to create new project in JBDS
6:37 p.m.
JBoss Tools folder not displaying when I try to create new project in JBDS
--------------------------------------------------------------------------
Key: JBIDE-4719
URL: https://jira.jboss.org/jira/browse/JBIDE-4719
Project: Tools (JBoss Tools)
Issue Type: Bug
Affects Versions: 3.0.0.GA
Environment: Windows
Sun HotSpot JDK 1.5
JBDS 2.0.0.GA
JBoss Tools 3.0.0.GA
Reporter: asookazian
In JBDS, I try to create a new project by right-clicking in Package Explorer, select new
--> other, and there is no JBoss Tools folder. Then I go to Help --> about JBDS and
click the JBoss Tools icon, select Project Examples, click plug-in details, then
close/ok.
Then I am able to see the JBoss Tools folder when I try to create a new project. Very
strange bug/behavior and I reproduced it by closing/opening a different/new workspace in
JBDS.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:48 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-4719) JBoss Tools folder not displaying when I try to create new project in JBDS
[
https://jira.jboss.org/jira/browse/JBIDE-4719?page=com.atlassian.jira.plu...
]
Denis Golovin commented on JBIDE-4719:
--------------------------------------
I cannot replicate this issue.
Could you provide some details about your workspaces? Anything would be good for start.
For instance, are those workspaces created with the same version of JBDS or pure eclipse?
Have you installed additional software?
Are there exceptions in Error Log View?
JBoss Tools folder not displaying when I try to create new project in
JBDS
--------------------------------------------------------------------------
Key: JBIDE-4719
URL: https://jira.jboss.org/jira/browse/JBIDE-4719
Project: Tools (JBoss Tools)
Issue Type: Bug
Affects Versions: 3.0.0.GA
Environment: Windows
Sun HotSpot JDK 1.5
JBDS 2.0.0.GA
JBoss Tools 3.0.0.GA
Reporter: asookazian
In JBDS, I try to create a new project by right-clicking in Package Explorer, select new
--> other, and there is no JBoss Tools folder. Then I go to Help --> about JBDS and
click the JBoss Tools icon, select Project Examples, click plug-in details, then
close/ok.
Then I am able to see the JBoss Tools folder when I try to create a new project. Very
strange bug/behavior and I reproduced it by closing/opening a different/new workspace in
JBDS.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:48 a.m.
New subject: [JBoss JIRA] Updated: (JBIDE-4719) JBoss Tools Category is not displaying when I try to create new project in JBDS
[
https://jira.jboss.org/jira/browse/JBIDE-4719?page=com.atlassian.jira.plu...
]
Denis Golovin updated JBIDE-4719:
---------------------------------
Summary: JBoss Tools Category is not displaying when I try to create new project in
JBDS (was: JBoss Tools folder not displaying when I try to create new project in JBDS)
Summary was updated
JBoss Tools Category is not displaying when I try to create new
project in JBDS
-------------------------------------------------------------------------------
Key: JBIDE-4719
URL: https://jira.jboss.org/jira/browse/JBIDE-4719
Project: Tools (JBoss Tools)
Issue Type: Bug
Affects Versions: 3.0.0.GA
Environment: Windows
Sun HotSpot JDK 1.5
JBDS 2.0.0.GA
JBoss Tools 3.0.0.GA
Reporter: asookazian
In JBDS, I try to create a new project by right-clicking in Package Explorer, select new
--> other, and there is no JBoss Tools folder. Then I go to Help --> about JBDS and
click the JBoss Tools icon, select Project Examples, click plug-in details, then
close/ok.
Then I am able to see the JBoss Tools folder when I try to create a new project. Very
strange bug/behavior and I reproduced it by closing/opening a different/new workspace in
JBDS.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:50 a.m.
New subject: [JBoss JIRA] Issue Comment Edited: (JBIDE-4719) JBoss Tools Category is not displaying when I try to create new project in JBDS
[
https://jira.jboss.org/jira/browse/JBIDE-4719?page=com.atlassian.jira.plu...
]
Denis Golovin edited comment on JBIDE-4719 at 8/6/09 2:49 AM:
--------------------------------------------------------------
I cannot replicate this issue.
Could you provide some details about your workspaces? Anything would be good for start.
For instance,
are those workspaces created with the same version of JBDS or pure eclipse?
Have you installed additional software?
Do you have JBoss Tools Web category in New Wizards Dialog?
Is there any JBoss Tools category in preferences dialog?
Are there exceptions in Error Log View?
was (Author: dgolovin):
I cannot replicate this issue.
Could you provide some details about your workspaces? Anything would be good for start.
For instance, are those workspaces created with the same version of JBDS or pure eclipse?
Have you installed additional software?
Are there exceptions in Error Log View?
JBoss Tools Category is not displaying when I try to create new
project in JBDS
-------------------------------------------------------------------------------
Key: JBIDE-4719
URL: https://jira.jboss.org/jira/browse/JBIDE-4719
Project: Tools (JBoss Tools)
Issue Type: Bug
Affects Versions: 3.0.0.GA
Environment: Windows
Sun HotSpot JDK 1.5
JBDS 2.0.0.GA
JBoss Tools 3.0.0.GA
Reporter: asookazian
In JBDS, I try to create a new project by right-clicking in Package Explorer, select new
--> other, and there is no JBoss Tools folder. Then I go to Help --> about JBDS and
click the JBoss Tools icon, select Project Examples, click plug-in details, then
close/ok.
Then I am able to see the JBoss Tools folder when I try to create a new project. Very
strange bug/behavior and I reproduced it by closing/opening a different/new workspace in
JBDS.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:14 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-4719) JBoss Tools Category is not displaying when I try to create new project in JBDS
[
https://jira.jboss.org/jira/browse/JBIDE-4719?page=com.atlassian.jira.plu...
]
asookazian commented on JBIDE-4719:
-----------------------------------
***********POSSIBLY CRITICAL: I SEE THE JBOSS TOOLS CATEGORY IN SEAM PERSPECTIVE OR JAVA
PERSPECTIVE WHEN I GO TO CREATE A NEW PROJECT BUT *NOT* IN DEBUG PERSPECTIVE OR JBOSS AS
PERSPECTIVE.**************
Workspace was created using JBDS 2.0.0.CR2
Be more specific about "additonal software"? If you mean Eclipse plug-ins, I
have installed subclipse and m2eclipse in JBDS 2.0.0.GA, which is what I'm currently
using.
Currently (I just launched JBDS with the same workspace), I do *not* see JBoss Tools
category in new project wizards dialog but I *do* see JBoss Tools Web category.
I *do* see a JBoss Tools category in preferences dialog (with JBoss ESB Runtimes, JBoss
Portlet and Web nested inside).
There are some exceptions in Error Log view from yesterday and today, but I'm not sure
which ones are applicable to this bug/problem.
/**************************************************************************************************************************************************/
eclipse.buildId=M20090211-1700
java.version=1.5.0_17
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US
Command-line arguments: -os win32 -ws win32 -arch x86
Error
Thu Aug 06 08:05:41 PDT 2009
Invalid preference page path: Integrated Agent Controller
/**************************************************************************************************************************************************/
eclipse.buildId=M20090211-1700
java.version=1.5.0_17
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US
Command-line arguments: -os win32 -ws win32 -arch x86 -data C:\Documents and
Settings\asookazi\BETS
Error
Wed Aug 05 16:53:23 PDT 2009
Problems occurred when invoking code from plug-in: "org.eclipse.ui.console".
org.eclipse.swt.SWTException: Device is disposed
at org.eclipse.swt.SWT.error(SWT.java:3777)
at org.eclipse.swt.SWT.error(SWT.java:3695)
at org.eclipse.swt.SWT.error(SWT.java:3666)
at org.eclipse.swt.widgets.Display.error(Display.java:1180)
at org.eclipse.swt.widgets.Display.asyncExec(Display.java:648)
at
org.eclipse.ui.internal.console.ConsoleDropDownAction.consolesRemoved(ConsoleDropDownAction.java:150)
at
org.eclipse.ui.internal.console.ConsoleManager$ConsoleNotifier.run(ConsoleManager.java:154)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37)
at
org.eclipse.ui.internal.console.ConsoleManager$ConsoleNotifier.notify(ConsoleManager.java:174)
at org.eclipse.ui.internal.console.ConsoleManager.fireUpdate(ConsoleManager.java:262)
at org.eclipse.ui.internal.console.ConsoleManager.removeConsoles(ConsoleManager.java:244)
at
org.eclipse.debug.internal.ui.views.console.ProcessConsoleManager.removeProcess(ProcessConsoleManager.java:98)
at
org.eclipse.debug.internal.ui.views.console.ProcessConsoleManager.removeLaunch(ProcessConsoleManager.java:81)
at
org.eclipse.debug.internal.ui.views.console.ProcessConsoleManager.shutdown(ProcessConsoleManager.java:198)
at org.eclipse.debug.internal.ui.DebugUIPlugin.stop(DebugUIPlugin.java:388)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl$3.run(BundleContextImpl.java:1050)
at java.security.AccessController.doPrivileged(Native Method)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl.stop(BundleContextImpl.java:1046)
at org.eclipse.osgi.framework.internal.core.BundleHost.stopWorker(BundleHost.java:457)
at
org.eclipse.osgi.framework.internal.core.AbstractBundle.suspend(AbstractBundle.java:531)
at org.eclipse.osgi.framework.internal.core.Framework.suspendBundle(Framework.java:1104)
at
org.eclipse.osgi.framework.internal.core.StartLevelManager.decFWSL(StartLevelManager.java:655)
at
org.eclipse.osgi.framework.internal.core.StartLevelManager.doSetStartLevel(StartLevelManager.java:312)
at
org.eclipse.osgi.framework.internal.core.StartLevelManager.shutdown(StartLevelManager.java:257)
at org.eclipse.osgi.framework.internal.core.SystemBundle.suspend(SystemBundle.java:236)
at org.eclipse.osgi.framework.internal.core.Framework.shutdown(Framework.java:678)
at org.eclipse.osgi.framework.internal.core.Framework.close(Framework.java:576)
at org.eclipse.osgi.framework.internal.core.OSGi.close(OSGi.java:41)
at org.eclipse.core.runtime.adaptor.EclipseStarter.shutdown(EclipseStarter.java:424)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:200)
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:585)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:549)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:504)
at org.eclipse.equinox.launcher.Main.run(Main.java:1236)
/**************************************************************************************************************************************************/
eclipse.buildId=M20090211-1700
java.version=1.5.0_17
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US
Command-line arguments: -os win32 -ws win32 -arch x86 -data C:\Documents and
Settings\asookazi\BETS
Error
Wed Aug 05 16:53:23 PDT 2009
An exception occurred during console notification
org.eclipse.swt.SWTException: Device is disposed
at org.eclipse.swt.SWT.error(SWT.java:3777)
at org.eclipse.swt.SWT.error(SWT.java:3695)
at org.eclipse.swt.SWT.error(SWT.java:3666)
at org.eclipse.swt.widgets.Display.error(Display.java:1180)
at org.eclipse.swt.widgets.Display.asyncExec(Display.java:648)
at
org.eclipse.ui.internal.console.ConsoleDropDownAction.consolesRemoved(ConsoleDropDownAction.java:150)
at
org.eclipse.ui.internal.console.ConsoleManager$ConsoleNotifier.run(ConsoleManager.java:154)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37)
at
org.eclipse.ui.internal.console.ConsoleManager$ConsoleNotifier.notify(ConsoleManager.java:174)
at org.eclipse.ui.internal.console.ConsoleManager.fireUpdate(ConsoleManager.java:262)
at org.eclipse.ui.internal.console.ConsoleManager.removeConsoles(ConsoleManager.java:244)
at
org.eclipse.debug.internal.ui.views.console.ProcessConsoleManager.removeProcess(ProcessConsoleManager.java:98)
at
org.eclipse.debug.internal.ui.views.console.ProcessConsoleManager.removeLaunch(ProcessConsoleManager.java:81)
at
org.eclipse.debug.internal.ui.views.console.ProcessConsoleManager.shutdown(ProcessConsoleManager.java:198)
at org.eclipse.debug.internal.ui.DebugUIPlugin.stop(DebugUIPlugin.java:388)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl$3.run(BundleContextImpl.java:1050)
at java.security.AccessController.doPrivileged(Native Method)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl.stop(BundleContextImpl.java:1046)
at org.eclipse.osgi.framework.internal.core.BundleHost.stopWorker(BundleHost.java:457)
at
org.eclipse.osgi.framework.internal.core.AbstractBundle.suspend(AbstractBundle.java:531)
at org.eclipse.osgi.framework.internal.core.Framework.suspendBundle(Framework.java:1104)
at
org.eclipse.osgi.framework.internal.core.StartLevelManager.decFWSL(StartLevelManager.java:655)
at
org.eclipse.osgi.framework.internal.core.StartLevelManager.doSetStartLevel(StartLevelManager.java:312)
at
org.eclipse.osgi.framework.internal.core.StartLevelManager.shutdown(StartLevelManager.java:257)
at org.eclipse.osgi.framework.internal.core.SystemBundle.suspend(SystemBundle.java:236)
at org.eclipse.osgi.framework.internal.core.Framework.shutdown(Framework.java:678)
at org.eclipse.osgi.framework.internal.core.Framework.close(Framework.java:576)
at org.eclipse.osgi.framework.internal.core.OSGi.close(OSGi.java:41)
at org.eclipse.core.runtime.adaptor.EclipseStarter.shutdown(EclipseStarter.java:424)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:200)
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:585)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:549)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:504)
at org.eclipse.equinox.launcher.Main.run(Main.java:1236)
/**************************************************************************************************************************************************/
eclipse.buildId=M20090211-1700
java.version=1.5.0_17
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US
Command-line arguments: -os win32 -ws win32 -arch x86 -data C:\Documents and
Settings\asookazi\BETS
Error
Wed Aug 05 14:12:09 PDT 2009
Problems occurred when invoking code from plug-in:
"org.eclipse.core.resources".
java.lang.NullPointerException
at
org.guvnor.tools.ResourceChangeListener.resourceChanged(ResourceChangeListener.java:59)
at
org.eclipse.core.internal.events.NotificationManager$2.run(NotificationManager.java:288)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37)
at
org.eclipse.core.internal.events.NotificationManager.notify(NotificationManager.java:282)
at
org.eclipse.core.internal.events.NotificationManager.broadcastChanges(NotificationManager.java:148)
at org.eclipse.core.internal.resources.Workspace.broadcastPostChange(Workspace.java:313)
at org.eclipse.core.internal.resources.Workspace.endOperation(Workspace.java:1022)
at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1809)
at org.eclipse.debug.core.model.Breakpoint.setAttribute(Breakpoint.java:190)
at
org.eclipse.jdt.internal.debug.core.breakpoints.JavaBreakpoint.decrementInstallCount(JavaBreakpoint.java:760)
at
org.eclipse.jdt.internal.debug.core.breakpoints.JavaBreakpoint.deregisterRequest(JavaBreakpoint.java:244)
at
org.eclipse.jdt.internal.debug.core.breakpoints.JavaBreakpoint.removeRequests(JavaBreakpoint.java:678)
at
org.eclipse.jdt.internal.debug.core.breakpoints.JavaBreakpoint.removeFromTarget(JavaBreakpoint.java:621)
at
org.eclipse.jdt.internal.debug.core.breakpoints.JavaLineBreakpoint.removeFromTarget(JavaLineBreakpoint.java:177)
at
org.eclipse.jdt.internal.debug.core.model.JDIDebugTarget.removeAllBreakpoints(JDIDebugTarget.java:1444)
at
org.eclipse.jdt.internal.debug.core.model.JDIDebugTarget.cleanup(JDIDebugTarget.java:1402)
at
org.eclipse.jdt.internal.debug.core.model.JDIDebugTarget.shutdown(JDIDebugTarget.java:1535)
at org.eclipse.jdt.internal.debug.core.JDIDebugPlugin.stop(JDIDebugPlugin.java:280)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl$3.run(BundleContextImpl.java:1050)
at java.security.AccessController.doPrivileged(Native Method)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl.stop(BundleContextImpl.java:1046)
at org.eclipse.osgi.framework.internal.core.BundleHost.stopWorker(BundleHost.java:457)
at
org.eclipse.osgi.framework.internal.core.AbstractBundle.suspend(AbstractBundle.java:531)
at org.eclipse.osgi.framework.internal.core.Framework.suspendBundle(Framework.java:1104)
at
org.eclipse.osgi.framework.internal.core.StartLevelManager.decFWSL(StartLevelManager.java:655)
at
org.eclipse.osgi.framework.internal.core.StartLevelManager.doSetStartLevel(StartLevelManager.java:312)
at
org.eclipse.osgi.framework.internal.core.StartLevelManager.shutdown(StartLevelManager.java:257)
at org.eclipse.osgi.framework.internal.core.SystemBundle.suspend(SystemBundle.java:236)
at org.eclipse.osgi.framework.internal.core.Framework.shutdown(Framework.java:678)
at org.eclipse.osgi.framework.internal.core.Framework.close(Framework.java:576)
at org.eclipse.osgi.framework.internal.core.OSGi.close(OSGi.java:41)
at org.eclipse.core.runtime.adaptor.EclipseStarter.shutdown(EclipseStarter.java:424)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:200)
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:585)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:549)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:504)
at org.eclipse.equinox.launcher.Main.run(Main.java:1236)
JBoss Tools Category is not displaying when I try to create new
project in JBDS
-------------------------------------------------------------------------------
Key: JBIDE-4719
URL: https://jira.jboss.org/jira/browse/JBIDE-4719
Project: JBoss Tools
Issue Type: Bug
Affects Versions: 3.0.0.GA
Environment: Windows
Sun HotSpot JDK 1.5
JBDS 2.0.0.GA
JBoss Tools 3.0.0.GA
Reporter: asookazian
In JBDS, I try to create a new project by right-clicking in Package Explorer, select new
--> other, and there is no JBoss Tools folder. Then I go to Help --> about JBDS and
click the JBoss Tools icon, select Project Examples, click plug-in details, then
close/ok.
Then I am able to see the JBoss Tools folder when I try to create a new project. Very
strange bug/behavior and I reproduced it by closing/opening a different/new workspace in
JBDS.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:37 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-4719) JBoss Tools Category is not displaying when I try to create new project in JBDS
[
https://jira.jboss.org/jira/browse/JBIDE-4719?page=com.atlassian.jira.plu...
]
Max Rydahl Andersen commented on JBIDE-4719:
--------------------------------------------
I have hard time following what is the problem ? Isn't this not just expected behavior
since Eclipse does not show all categories in all perspectives ?
If you could use jing or wink to record what you actually do I could better help.
JBoss Tools Category is not displaying when I try to create new
project in JBDS
-------------------------------------------------------------------------------
Key: JBIDE-4719
URL: https://jira.jboss.org/jira/browse/JBIDE-4719
Project: JBoss Tools
Issue Type: Bug
Affects Versions: 3.0.0.GA
Environment: Windows
Sun HotSpot JDK 1.5
JBDS 2.0.0.GA
JBoss Tools 3.0.0.GA
Reporter: asookazian
In JBDS, I try to create a new project by right-clicking in Package Explorer, select new
--> other, and there is no JBoss Tools folder. Then I go to Help --> about JBDS and
click the JBoss Tools icon, select Project Examples, click plug-in details, then
close/ok.
Then I am able to see the JBoss Tools folder when I try to create a new project. Very
strange bug/behavior and I reproduced it by closing/opening a different/new workspace in
JBDS.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:46 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-4719) JBoss Tools Category is not displaying when I try to create new project in JBDS
[
https://jira.jboss.org/jira/browse/JBIDE-4719?page=com.atlassian.jira.plu...
]
asookazian commented on JBIDE-4719:
-----------------------------------
So the steps to reproduce are indeed incorrect. I tried the steps again and it does not
show the JBoss Tools category if I'm in the debug perspective (which now I'm
assuming I was in yesterday when I first noticed it was missing). Most likely I did the
steps, then coincidentally switched perspective to Seam perspective, and voila.
So if that's the way Eclipse behaves, then I guess it's not a bug. Although it
seems strange that the JBoss Tools category is visible from some perspectives and not from
others, seemingly randomly... Somewhat suspect. So then why is the JBoss Tools Web
category visible from seemingly any perspective?
Feel free to close out this JIRA issue.
JBoss Tools Category is not displaying when I try to create new
project in JBDS
-------------------------------------------------------------------------------
Key: JBIDE-4719
URL: https://jira.jboss.org/jira/browse/JBIDE-4719
Project: JBoss Tools
Issue Type: Bug
Affects Versions: 3.0.0.GA
Environment: Windows
Sun HotSpot JDK 1.5
JBDS 2.0.0.GA
JBoss Tools 3.0.0.GA
Reporter: asookazian
In JBDS, I try to create a new project by right-clicking in Package Explorer, select new
--> other, and there is no JBoss Tools folder. Then I go to Help --> about JBDS and
click the JBoss Tools icon, select Project Examples, click plug-in details, then
close/ok.
Then I am able to see the JBoss Tools folder when I try to create a new project. Very
strange bug/behavior and I reproduced it by closing/opening a different/new workspace in
JBDS.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:26 p.m.
New subject: [JBoss JIRA] Commented: (JBIDE-4719) JBoss Tools Category is not displaying when I try to create new project in JBDS
[
https://jira.jboss.org/jira/browse/JBIDE-4719?page=com.atlassian.jira.plu...
]
Denis Golovin commented on JBIDE-4719:
--------------------------------------
I cannot reproduce it anyway. I have JBossTools Category no matter what perspective is
open.
JBoss Tools Category is not displaying when I try to create new
project in JBDS
-------------------------------------------------------------------------------
Key: JBIDE-4719
URL: https://jira.jboss.org/jira/browse/JBIDE-4719
Project: JBoss Tools
Issue Type: Bug
Affects Versions: 3.0.0.GA
Environment: Windows
Sun HotSpot JDK 1.5
JBDS 2.0.0.GA
JBoss Tools 3.0.0.GA
Reporter: asookazian
In JBDS, I try to create a new project by right-clicking in Package Explorer, select new
--> other, and there is no JBoss Tools folder. Then I go to Help --> about JBDS and
click the JBoss Tools icon, select Project Examples, click plug-in details, then
close/ok.
Then I am able to see the JBoss Tools folder when I try to create a new project. Very
strange bug/behavior and I reproduced it by closing/opening a different/new workspace in
JBDS.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:13 p.m.
New subject: [JBoss JIRA] Updated: (JBIDE-4719) JBoss Tools Category is not displaying when I try to create new project in JBDS
[
https://jira.jboss.org/jira/browse/JBIDE-4719?page=com.atlassian.jira.plu...
]
Denis Golovin updated JBIDE-4719:
---------------------------------
Component/s: common
JBoss Tools Category is not displaying when I try to create new
project in JBDS
-------------------------------------------------------------------------------
Key: JBIDE-4719
URL: https://jira.jboss.org/jira/browse/JBIDE-4719
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: common
Affects Versions: 3.0.0.GA
Environment: Windows
Sun HotSpot JDK 1.5
JBDS 2.0.0.GA
JBoss Tools 3.0.0.GA
Reporter: asookazian
In JBDS, I try to create a new project by right-clicking in Package Explorer, select new
--> other, and there is no JBoss Tools folder. Then I go to Help --> about JBDS and
click the JBoss Tools icon, select Project Examples, click plug-in details, then
close/ok.
Then I am able to see the JBoss Tools folder when I try to create a new project. Very
strange bug/behavior and I reproduced it by closing/opening a different/new workspace in
JBDS.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:02 a.m.
New subject: [JBoss JIRA] Resolved: (JBIDE-4719) JBoss Tools Category is not displaying when I try to create new project in JBDS
[
https://jira.jboss.org/jira/browse/JBIDE-4719?page=com.atlassian.jira.plu...
]
Max Rydahl Andersen resolved JBIDE-4719.
----------------------------------------
Resolution: Cannot Reproduce Bug
I can't follow the bug nor reproduce it - just as Denis says, category shows up
everywhere.
If you got screenshots or screencast to illustrate it then please attach/comment and
reopen it.
JBoss Tools Category is not displaying when I try to create new
project in JBDS
-------------------------------------------------------------------------------
Key: JBIDE-4719
URL: https://jira.jboss.org/jira/browse/JBIDE-4719
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: common
Affects Versions: 3.0.0.GA
Environment: Windows
Sun HotSpot JDK 1.5
JBDS 2.0.0.GA
JBoss Tools 3.0.0.GA
Reporter: asookazian
In JBDS, I try to create a new project by right-clicking in Package Explorer, select new
--> other, and there is no JBoss Tools folder. Then I go to Help --> about JBDS and
click the JBoss Tools icon, select Project Examples, click plug-in details, then
close/ok.
Then I am able to see the JBoss Tools folder when I try to create a new project. Very
strange bug/behavior and I reproduced it by closing/opening a different/new workspace in
JBDS.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5316
days inactive
5448
days old
jbosstools-issues@lists.jboss.org
9 comments
3 participants
participants (3)
-
asookazian (JIRA) -
Denis Golovin (JIRA)
-
Max Rydahl Andersen (JIRA)