[JBoss JIRA] (JBDS-1983) JBDS Welcome screen should accept contributions from 3rd party extras like JRebel, Spring, FindBugs, PMD
12:37 p.m.
JBDS Welcome screen should accept contributions from 3rd party extras like JRebel, Spring,
FindBugs, PMD
--------------------------------------------------------------------------------------------------------
Key: JBDS-1983
URL: https://issues.jboss.org/browse/JBDS-1983
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: 3rdPartyCertification, 3rdPartyDependencies, Welcome
Affects Versions: 5.0.0.M5
Reporter: Nick Boldt
Assignee: Nick Boldt
Fix For: 5.0.0.Beta2
We're currently patching SpringIDE's broken plugin (JBDS-1838) which contributes a
new Welcome screen, leading to this issue:
!https://issues.jboss.org/secure/attachment/12349923/2011-12-15_0052.png!
However, it's been revealed that in addition to Spring, PMD, FindBugs, and now JRebel
also have this failing.
Therefore we ought to find a new way to suppress the effect across all of JBT/JBDS instead
of per-plugin, or get it fixed upstream.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:39 p.m.
[
https://issues.jboss.org/browse/JBDS-1983?page=com.atlassian.jira.plugin....
]
Nick Boldt updated JBDS-1983:
-----------------------------
Description:
We're currently patching SpringIDE's broken plugin (JBDS-1838) which contributes a
new Welcome screen, leading to this issue if unpatched:
!https://issues.jboss.org/secure/attachment/12349923/2011-12-15_0052.png!
However, it's been revealed that in addition to Spring, PMD, FindBugs, and now JRebel
also have this failing.
Therefore we ought to find a new way to suppress the effect across all of JBT/JBDS instead
of per-plugin, or get it fixed upstream.
was:
We're currently patching SpringIDE's broken plugin (JBDS-1838) which contributes a
new Welcome screen, leading to this issue:
!https://issues.jboss.org/secure/attachment/12349923/2011-12-15_0052.png!
However, it's been revealed that in addition to Spring, PMD, FindBugs, and now JRebel
also have this failing.
Therefore we ought to find a new way to suppress the effect across all of JBT/JBDS instead
of per-plugin, or get it fixed upstream.
JBDS Welcome screen should accept contributions from 3rd party extras
like JRebel, Spring, FindBugs, PMD
--------------------------------------------------------------------------------------------------------
Key: JBDS-1983
URL: https://issues.jboss.org/browse/JBDS-1983
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: 3rdPartyCertification, 3rdPartyDependencies, Welcome
Affects Versions: 5.0.0.M5
Reporter: Nick Boldt
Assignee: Nick Boldt
Fix For: 5.0.0.Beta2
We're currently patching SpringIDE's broken plugin (JBDS-1838) which contributes
a new Welcome screen, leading to this issue if unpatched:
!https://issues.jboss.org/secure/attachment/12349923/2011-12-15_0052.png!
However, it's been revealed that in addition to Spring, PMD, FindBugs, and now JRebel
also have this failing.
Therefore we ought to find a new way to suppress the effect across all of JBT/JBDS
instead of per-plugin, or get it fixed upstream.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:39 p.m.
[
https://issues.jboss.org/browse/JBDS-1983?page=com.atlassian.jira.plugin....
]
Nick Boldt updated JBDS-1983:
-----------------------------
Description:
We're currently patching SpringIDE's broken plugin (JBDS-1838) which contributes a
new Welcome screen, leading to this issue if unpatched:
!https://issues.jboss.org/secure/attachment/12346976/2011-09-09-105303.png!
However, it's been revealed that in addition to Spring, PMD, FindBugs, and now JRebel
also have this failing.
!https://issues.jboss.org/secure/attachment/12349923/2011-12-15_0052.png!
Therefore we ought to find a new way to suppress the effect across all of JBT/JBDS instead
of per-plugin, or get it fixed upstream.
was:
We're currently patching SpringIDE's broken plugin (JBDS-1838) which contributes a
new Welcome screen, leading to this issue if unpatched:
!https://issues.jboss.org/secure/attachment/12349923/2011-12-15_0052.png!
However, it's been revealed that in addition to Spring, PMD, FindBugs, and now JRebel
also have this failing.
Therefore we ought to find a new way to suppress the effect across all of JBT/JBDS instead
of per-plugin, or get it fixed upstream.
JBDS Welcome screen should accept contributions from 3rd party extras
like JRebel, Spring, FindBugs, PMD
--------------------------------------------------------------------------------------------------------
Key: JBDS-1983
URL: https://issues.jboss.org/browse/JBDS-1983
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: 3rdPartyCertification, 3rdPartyDependencies, Welcome
Affects Versions: 5.0.0.M5
Reporter: Nick Boldt
Assignee: Nick Boldt
Fix For: 5.0.0.Beta2
We're currently patching SpringIDE's broken plugin (JBDS-1838) which contributes
a new Welcome screen, leading to this issue if unpatched:
!https://issues.jboss.org/secure/attachment/12346976/2011-09-09-105303.png!
However, it's been revealed that in addition to Spring, PMD, FindBugs, and now JRebel
also have this failing.
!https://issues.jboss.org/secure/attachment/12349923/2011-12-15_0052.png!
Therefore we ought to find a new way to suppress the effect across all of JBT/JBDS
instead of per-plugin, or get it fixed upstream.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:33 p.m.
[
https://issues.jboss.org/browse/JBDS-1983?page=com.atlassian.jira.plugin....
]
mark yarborough updated JBDS-1983:
----------------------------------
Fix Version/s: 5.0.0.Beta1
(was: 5.0.0.Beta2)
Affects the code/build, so needs to be in Beta1 else will not make it.
JBDS Welcome screen should accept contributions from 3rd party extras
like JRebel, Spring, FindBugs, PMD
--------------------------------------------------------------------------------------------------------
Key: JBDS-1983
URL: https://issues.jboss.org/browse/JBDS-1983
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: 3rdPartyCertification, 3rdPartyDependencies, Welcome
Affects Versions: 5.0.0.M5
Reporter: Nick Boldt
Assignee: Nick Boldt
Fix For: 5.0.0.Beta1
We're currently patching SpringIDE's broken plugin (JBDS-1838) which contributes
a new Welcome screen, leading to this issue if unpatched:
!https://issues.jboss.org/secure/attachment/12346976/2011-09-09-105303.png!
However, it's been revealed that in addition to Spring, PMD, FindBugs, and now JRebel
also have this failing.
!https://issues.jboss.org/secure/attachment/12349923/2011-12-15_0052.png!
Therefore we ought to find a new way to suppress the effect across all of JBT/JBDS
instead of per-plugin, or get it fixed upstream.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:13 p.m.
[
https://issues.jboss.org/browse/JBDS-1983?page=com.atlassian.jira.plugin....
]
Nick Boldt updated JBDS-1983:
-----------------------------
Priority: Blocker (was: Major)
bump to blocker.
JBDS Welcome screen should accept contributions from 3rd party extras
like JRebel, Spring, FindBugs, PMD
--------------------------------------------------------------------------------------------------------
Key: JBDS-1983
URL: https://issues.jboss.org/browse/JBDS-1983
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: 3rdPartyCertification, 3rdPartyDependencies, Welcome
Affects Versions: 5.0.0.M5
Reporter: Nick Boldt
Assignee: Nick Boldt
Priority: Blocker
Fix For: 5.0.0.Beta1
We're currently patching SpringIDE's broken plugin (JBDS-1838) which contributes
a new Welcome screen, leading to this issue if unpatched:
!https://issues.jboss.org/secure/attachment/12346976/2011-09-09-105303.png!
However, it's been revealed that in addition to Spring, PMD, FindBugs, and now JRebel
also have this failing.
!https://issues.jboss.org/secure/attachment/12349923/2011-12-15_0052.png!
Therefore we ought to find a new way to suppress the effect across all of JBT/JBDS
instead of per-plugin, or get it fixed upstream.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:45 p.m.
[
https://issues.jboss.org/browse/JBDS-1983?page=com.atlassian.jira.plugin....
]
Nick Boldt reassigned JBDS-1983:
--------------------------------
Assignee: Snjezana Peco (was: Nick Boldt)
Do you have time to look at how to fix the Welcome screen so it doesn't break when we
install 3rd party tools like JRebel or Findbugs?
JBDS Welcome screen should accept contributions from 3rd party extras
like JRebel, Spring, FindBugs, PMD
--------------------------------------------------------------------------------------------------------
Key: JBDS-1983
URL: https://issues.jboss.org/browse/JBDS-1983
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: 3rdPartyCertification, 3rdPartyDependencies, Welcome
Affects Versions: 5.0.0.M5
Reporter: Nick Boldt
Assignee: Snjezana Peco
Priority: Blocker
Fix For: 5.0.0.Beta1
We're currently patching SpringIDE's broken plugin (JBDS-1838) which contributes
a new Welcome screen, leading to this issue if unpatched:
!https://issues.jboss.org/secure/attachment/12346976/2011-09-09-105303.png!
However, it's been revealed that in addition to Spring, PMD, FindBugs, and now JRebel
also have this failing.
!https://issues.jboss.org/secure/attachment/12349923/2011-12-15_0052.png!
Therefore we ought to find a new way to suppress the effect across all of JBT/JBDS
instead of per-plugin, or get it fixed upstream.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:24 p.m.
[
https://issues.jboss.org/browse/JBDS-1983?page=com.atlassian.jira.plugin....
]
Snjezana Peco commented on JBDS-1983:
-------------------------------------
We can do the following:
- patch the mentioned features (probably not possible for JRebel that is commercial)
- bring Eclipse Transforms back - JBDS-533
- enter an upstream bug
I propose introducing Eclipse Transforms.
JBDS Welcome screen should accept contributions from 3rd party extras
like JRebel, Spring, FindBugs, PMD
--------------------------------------------------------------------------------------------------------
Key: JBDS-1983
URL: https://issues.jboss.org/browse/JBDS-1983
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: 3rdPartyCertification, 3rdPartyDependencies, Welcome
Affects Versions: 5.0.0.M5
Reporter: Nick Boldt
Assignee: Snjezana Peco
Priority: Blocker
Fix For: 5.0.0.Beta1
We're currently patching SpringIDE's broken plugin (JBDS-1838) which contributes
a new Welcome screen, leading to this issue if unpatched:
!https://issues.jboss.org/secure/attachment/12346976/2011-09-09-105303.png!
However, it's been revealed that in addition to Spring, PMD, FindBugs, and now JRebel
also have this failing.
!https://issues.jboss.org/secure/attachment/12349923/2011-12-15_0052.png!
Therefore we ought to find a new way to suppress the effect across all of JBT/JBDS
instead of per-plugin, or get it fixed upstream.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:55 a.m.
[
https://issues.jboss.org/browse/JBDS-1983?page=com.atlassian.jira.plugin....
]
Nick Boldt updated JBDS-1983:
-----------------------------
Attachment: install-all-of-central-welcome-screen-breaks.png
Since we'd have to patch at least three 3rd party features, I agree w/ an overall
solution that works for everything and scales up w/o extra work.
+1 for Transforms.
As to an upstream bug... I just installed everything in JBoss Central into Eclipse Indigo
SR1 JEE and the resulting welcome screen WAS fine, until I closed it and opened the 3rd
party welcome screens. After that the default Eclipse one (with egit, dtp, wtp, and other
contributions in it) was blank.
!install-all-of-central-welcome-screen-breaks.png!
JBDS Welcome screen should accept contributions from 3rd party extras
like JRebel, Spring, FindBugs, PMD
--------------------------------------------------------------------------------------------------------
Key: JBDS-1983
URL: https://issues.jboss.org/browse/JBDS-1983
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: 3rdPartyCertification, 3rdPartyDependencies, Welcome
Affects Versions: 5.0.0.M5
Reporter: Nick Boldt
Assignee: Snjezana Peco
Priority: Blocker
Fix For: 5.0.0.Beta1
Attachments: install-all-of-central-welcome-screen-breaks.png
We're currently patching SpringIDE's broken plugin (JBDS-1838) which contributes
a new Welcome screen, leading to this issue if unpatched:
!https://issues.jboss.org/secure/attachment/12346976/2011-09-09-105303.png!
However, it's been revealed that in addition to Spring, PMD, FindBugs, and now JRebel
also have this failing.
!https://issues.jboss.org/secure/attachment/12349923/2011-12-15_0052.png!
Therefore we ought to find a new way to suppress the effect across all of JBT/JBDS
instead of per-plugin, or get it fixed upstream.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:59 a.m.
[
https://issues.jboss.org/browse/JBDS-1983?page=com.atlassian.jira.plugin....
]
Nick Boldt edited comment on JBDS-1983 at 2/17/12 10:58 AM:
------------------------------------------------------------
Since we'd have to patch at least three 3rd party features, I agree w/ an overall
solution that works for everything and scales up w/o extra work.
+1 for Transforms.
As to an upstream bug... I just installed everything in JBoss Central into Eclipse Indigo
SR1 JEE and the resulting welcome screen WAS fine, until I closed it and opened the 3rd
party welcome screens. After that the default Eclipse one (with egit, dtp, wtp, and other
contributions in it) was blank.
!install-all-of-central-welcome-screen-breaks.png!
So, yes, it's upstream in Eclipse AND in PMD, FindBugs, and JRebel.
was (Author: nickboldt):
Since we'd have to patch at least three 3rd party features, I agree w/ an overall
solution that works for everything and scales up w/o extra work.
+1 for Transforms.
As to an upstream bug... I just installed everything in JBoss Central into Eclipse Indigo
SR1 JEE and the resulting welcome screen WAS fine, until I closed it and opened the 3rd
party welcome screens. After that the default Eclipse one (with egit, dtp, wtp, and other
contributions in it) was blank.
!install-all-of-central-welcome-screen-breaks.png!
JBDS Welcome screen should accept contributions from 3rd party extras
like JRebel, Spring, FindBugs, PMD
--------------------------------------------------------------------------------------------------------
Key: JBDS-1983
URL: https://issues.jboss.org/browse/JBDS-1983
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: 3rdPartyCertification, 3rdPartyDependencies, Welcome
Affects Versions: 5.0.0.M5
Reporter: Nick Boldt
Assignee: Snjezana Peco
Priority: Blocker
Fix For: 5.0.0.Beta1
Attachments: install-all-of-central-welcome-screen-breaks.png
We're currently patching SpringIDE's broken plugin (JBDS-1838) which contributes
a new Welcome screen, leading to this issue if unpatched:
!https://issues.jboss.org/secure/attachment/12346976/2011-09-09-105303.png!
However, it's been revealed that in addition to Spring, PMD, FindBugs, and now JRebel
also have this failing.
!https://issues.jboss.org/secure/attachment/12349923/2011-12-15_0052.png!
Therefore we ought to find a new way to suppress the effect across all of JBT/JBDS
instead of per-plugin, or get it fixed upstream.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:08 a.m.
[
https://issues.jboss.org/browse/JBDS-1983?page=com.atlassian.jira.plugin....
]
Nick Boldt commented on JBDS-1983:
----------------------------------
!SESSION 2012-02-17 10:49:37.042 -----------------------------------------------
eclipse.buildId=M20110909-1335
java.version=1.6.0_25
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
Framework arguments: -product org.eclipse.epp.package.jee.product -showLocation
Command-line arguments: -os linux -ws gtk -arch x86_64 -product
org.eclipse.epp.package.jee.product -clean -showLocation -data
/home/nboldt/eclipse/workspace-clean37 -consolelog -console
!ENTRY org.eclipse.ui.ide 4 4 2012-02-17 10:51:43.784
!MESSAGE Error in WelcomeParser.parse
!ENTRY org.eclipse.ui.ide 4 1 2012-02-17 10:51:43.795
!MESSAGE An exception occurred when parsing the welcome page
!STACK 0
org.xml.sax.SAXParseException: The entity "trade" was referenced, but not
declared.
at
com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:195)
at
com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.fatalError(ErrorHandlerWrapper.java:174)
at
com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:388)
at
com.sun.org.apache.xerces.internal.impl.XMLScanner.reportFatalError(XMLScanner.java:1414)
at
com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanEntityReference(XMLDocumentFragmentScannerImpl.java:1900)
at
com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDriver.next(XMLDocumentFragmentScannerImpl.java:3032)
at
com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:648)
at
com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.next(XMLNSDocumentScannerImpl.java:140)
at
com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:511)
at
com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:808)
at
com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:737)
at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:119)
at
com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1205)
at
com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(SAXParserImpl.java:522)
at javax.xml.parsers.SAXParser.parse(SAXParser.java:395)
at
org.eclipse.ui.internal.ide.dialogs.WelcomeParser.parse(WelcomeParser.java:354)
at org.eclipse.ui.internal.ide.dialogs.WelcomeEditor.read(WelcomeEditor.java:962)
at
org.eclipse.ui.internal.ide.dialogs.WelcomeEditor.readFile(WelcomeEditor.java:980)
at
org.eclipse.ui.internal.ide.dialogs.WelcomeEditor.createPartControl(WelcomeEditor.java:686)
at
org.eclipse.ui.internal.EditorReference.createPartHelper(EditorReference.java:670)
at org.eclipse.ui.internal.EditorReference.createPart(EditorReference.java:465)
at
org.eclipse.ui.internal.WorkbenchPartReference.getPart(WorkbenchPartReference.java:595)
at org.eclipse.ui.internal.PartPane.setVisible(PartPane.java:313)
at
org.eclipse.ui.internal.presentations.PresentablePart.setVisible(PresentablePart.java:180)
at
org.eclipse.ui.internal.presentations.util.PresentablePartFolder.select(PresentablePartFolder.java:270)
at
org.eclipse.ui.internal.presentations.util.LeftToRightTabOrder.select(LeftToRightTabOrder.java:65)
at
org.eclipse.ui.internal.presentations.util.TabbedStackPresentation.selectPart(TabbedStackPresentation.java:473)
at
org.eclipse.ui.internal.PartStack.refreshPresentationSelection(PartStack.java:1245)
at org.eclipse.ui.internal.PartStack.setSelection(PartStack.java:1198)
at org.eclipse.ui.internal.PartStack.showPart(PartStack.java:1597)
at org.eclipse.ui.internal.PartStack.add(PartStack.java:493)
at org.eclipse.ui.internal.EditorStack.add(EditorStack.java:103)
at org.eclipse.ui.internal.EditorManager.openEditor(EditorManager.java:666)
at
org.eclipse.ui.internal.WorkbenchPage.busyOpenEditorBatched(WorkbenchPage.java:2942)
at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditor(WorkbenchPage.java:2850)
at org.eclipse.ui.internal.WorkbenchPage.access$11(WorkbenchPage.java:2842)
at org.eclipse.ui.internal.WorkbenchPage$10.run(WorkbenchPage.java:2793)
at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2789)
at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2773)
at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2756)
at
org.eclipse.ui.actions.QuickStartAction.openWelcomePage(QuickStartAction.java:239)
at org.eclipse.ui.actions.QuickStartAction.run(QuickStartAction.java:98)
at org.eclipse.jface.action.Action.runWithEvent(Action.java:498)
at org.eclipse.jface.commands.ActionHandler.execute(ActionHandler.java:119)
at org.eclipse.core.commands.Command.executeWithChecks(Command.java:476)
at
org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:508)
at
org.eclipse.ui.internal.handlers.HandlerService.executeCommand(HandlerService.java:169)
at
org.eclipse.ui.internal.handlers.SlaveHandlerService.executeCommand(SlaveHandlerService.java:241)
at
org.eclipse.ui.internal.actions.CommandAction.runWithEvent(CommandAction.java:157)
at
org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:584)
at
org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:501)
at
org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:411)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1258)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3588)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3209)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2696)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2660)
at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2494)
at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:674)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:667)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
at
org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:123)
at
org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:344)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
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:597)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:622)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:577)
at org.eclipse.equinox.launcher.Main.run(Main.java:1410)
at org.eclipse.equinox.launcher.Main.main(Main.java:1386)
JBDS Welcome screen should accept contributions from 3rd party extras
like JRebel, Spring, FindBugs, PMD
--------------------------------------------------------------------------------------------------------
Key: JBDS-1983
URL: https://issues.jboss.org/browse/JBDS-1983
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: 3rdPartyCertification, 3rdPartyDependencies, Welcome
Affects Versions: 5.0.0.M5
Reporter: Nick Boldt
Assignee: Snjezana Peco
Priority: Blocker
Fix For: 5.0.0.Beta1
Attachments: install-all-of-central-welcome-screen-breaks.png
We're currently patching SpringIDE's broken plugin (JBDS-1838) which contributes
a new Welcome screen, leading to this issue if unpatched:
!https://issues.jboss.org/secure/attachment/12346976/2011-09-09-105303.png!
However, it's been revealed that in addition to Spring, PMD, FindBugs, and now JRebel
also have this failing.
!https://issues.jboss.org/secure/attachment/12349923/2011-12-15_0052.png!
Therefore we ought to find a new way to suppress the effect across all of JBT/JBDS
instead of per-plugin, or get it fixed upstream.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:10 a.m.
[
https://issues.jboss.org/browse/JBDS-1983?page=com.atlassian.jira.plugin....
]
Nick Boldt edited comment on JBDS-1983 at 2/17/12 11:09 AM:
------------------------------------------------------------
Console error showing the welcome page parser error:
{code}
!SESSION 2012-02-17 10:49:37.042 -----------------------------------------------
eclipse.buildId=M20110909-1335
java.version=1.6.0_25
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
Framework arguments: -product org.eclipse.epp.package.jee.product -showLocation
Command-line arguments: -os linux -ws gtk -arch x86_64 -product
org.eclipse.epp.package.jee.product -clean -showLocation -data
/home/nboldt/eclipse/workspace-clean37 -consolelog -console
!ENTRY org.eclipse.ui.ide 4 4 2012-02-17 10:51:43.784
!MESSAGE Error in WelcomeParser.parse
!ENTRY org.eclipse.ui.ide 4 1 2012-02-17 10:51:43.795
!MESSAGE An exception occurred when parsing the welcome page
!STACK 0
org.xml.sax.SAXParseException: The entity "trade" was referenced, but not
declared.
at
com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:195)
at
com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.fatalError(ErrorHandlerWrapper.java:174)
at
com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:388)
at
com.sun.org.apache.xerces.internal.impl.XMLScanner.reportFatalError(XMLScanner.java:1414)
at
com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanEntityReference(XMLDocumentFragmentScannerImpl.java:1900)
at
com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDriver.next(XMLDocumentFragmentScannerImpl.java:3032)
at
com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:648)
at
com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.next(XMLNSDocumentScannerImpl.java:140)
at
com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:511)
at
com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:808)
at
com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:737)
at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:119)
at
com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1205)
at
com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(SAXParserImpl.java:522)
at javax.xml.parsers.SAXParser.parse(SAXParser.java:395)
at
org.eclipse.ui.internal.ide.dialogs.WelcomeParser.parse(WelcomeParser.java:354)
at org.eclipse.ui.internal.ide.dialogs.WelcomeEditor.read(WelcomeEditor.java:962)
at
org.eclipse.ui.internal.ide.dialogs.WelcomeEditor.readFile(WelcomeEditor.java:980)
at
org.eclipse.ui.internal.ide.dialogs.WelcomeEditor.createPartControl(WelcomeEditor.java:686)
at
org.eclipse.ui.internal.EditorReference.createPartHelper(EditorReference.java:670)
at org.eclipse.ui.internal.EditorReference.createPart(EditorReference.java:465)
at
org.eclipse.ui.internal.WorkbenchPartReference.getPart(WorkbenchPartReference.java:595)
at org.eclipse.ui.internal.PartPane.setVisible(PartPane.java:313)
at
org.eclipse.ui.internal.presentations.PresentablePart.setVisible(PresentablePart.java:180)
at
org.eclipse.ui.internal.presentations.util.PresentablePartFolder.select(PresentablePartFolder.java:270)
at
org.eclipse.ui.internal.presentations.util.LeftToRightTabOrder.select(LeftToRightTabOrder.java:65)
at
org.eclipse.ui.internal.presentations.util.TabbedStackPresentation.selectPart(TabbedStackPresentation.java:473)
at
org.eclipse.ui.internal.PartStack.refreshPresentationSelection(PartStack.java:1245)
at org.eclipse.ui.internal.PartStack.setSelection(PartStack.java:1198)
at org.eclipse.ui.internal.PartStack.showPart(PartStack.java:1597)
at org.eclipse.ui.internal.PartStack.add(PartStack.java:493)
at org.eclipse.ui.internal.EditorStack.add(EditorStack.java:103)
at org.eclipse.ui.internal.PartStack.add(PartStack.java:479)
at org.eclipse.ui.internal.EditorStack.add(EditorStack.java:112)
at
org.eclipse.ui.internal.EditorSashContainer.addEditor(EditorSashContainer.java:63)
at
org.eclipse.ui.internal.EditorAreaHelper.addToLayout(EditorAreaHelper.java:225)
at org.eclipse.ui.internal.EditorAreaHelper.addEditor(EditorAreaHelper.java:213)
at org.eclipse.ui.internal.EditorManager.createEditorTab(EditorManager.java:808)
at
org.eclipse.ui.internal.EditorManager.openEditorFromDescriptor(EditorManager.java:707)
at org.eclipse.ui.internal.EditorManager.openEditor(EditorManager.java:666)
at
org.eclipse.ui.internal.WorkbenchPage.busyOpenEditorBatched(WorkbenchPage.java:2942)
at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditor(WorkbenchPage.java:2850)
at org.eclipse.ui.internal.WorkbenchPage.access$11(WorkbenchPage.java:2842)
at org.eclipse.ui.internal.WorkbenchPage$10.run(WorkbenchPage.java:2793)
at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2789)
at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2773)
at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2756)
at
org.eclipse.ui.actions.QuickStartAction.openWelcomePage(QuickStartAction.java:239)
at org.eclipse.ui.actions.QuickStartAction.run(QuickStartAction.java:98)
at org.eclipse.jface.action.Action.runWithEvent(Action.java:498)
at org.eclipse.jface.commands.ActionHandler.execute(ActionHandler.java:119)
at org.eclipse.core.commands.Command.executeWithChecks(Command.java:476)
at
org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:508)
at
org.eclipse.ui.internal.handlers.HandlerService.executeCommand(HandlerService.java:169)
at
org.eclipse.ui.internal.handlers.SlaveHandlerService.executeCommand(SlaveHandlerService.java:241)
at
org.eclipse.ui.internal.actions.CommandAction.runWithEvent(CommandAction.java:157)
at
org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:584)
at
org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:501)
at
org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:411)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1258)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3588)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3209)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2696)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2660)
at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2494)
at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:674)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:667)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
at
org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:123)
at
org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:344)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
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:597)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:622)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:577)
at org.eclipse.equinox.launcher.Main.run(Main.java:1410)
at org.eclipse.equinox.launcher.Main.main(Main.java:1386)
{code}
was (Author: nickboldt):
!SESSION 2012-02-17 10:49:37.042 -----------------------------------------------
eclipse.buildId=M20110909-1335
java.version=1.6.0_25
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
Framework arguments: -product org.eclipse.epp.package.jee.product -showLocation
Command-line arguments: -os linux -ws gtk -arch x86_64 -product
org.eclipse.epp.package.jee.product -clean -showLocation -data
/home/nboldt/eclipse/workspace-clean37 -consolelog -console
!ENTRY org.eclipse.ui.ide 4 4 2012-02-17 10:51:43.784
!MESSAGE Error in WelcomeParser.parse
!ENTRY org.eclipse.ui.ide 4 1 2012-02-17 10:51:43.795
!MESSAGE An exception occurred when parsing the welcome page
!STACK 0
org.xml.sax.SAXParseException: The entity "trade" was referenced, but not
declared.
at
com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:195)
at
com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.fatalError(ErrorHandlerWrapper.java:174)
at
com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:388)
at
com.sun.org.apache.xerces.internal.impl.XMLScanner.reportFatalError(XMLScanner.java:1414)
at
com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanEntityReference(XMLDocumentFragmentScannerImpl.java:1900)
at
com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDriver.next(XMLDocumentFragmentScannerImpl.java:3032)
at
com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:648)
at
com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.next(XMLNSDocumentScannerImpl.java:140)
at
com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:511)
at
com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:808)
at
com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:737)
at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:119)
at
com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1205)
at
com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(SAXParserImpl.java:522)
at javax.xml.parsers.SAXParser.parse(SAXParser.java:395)
at
org.eclipse.ui.internal.ide.dialogs.WelcomeParser.parse(WelcomeParser.java:354)
at org.eclipse.ui.internal.ide.dialogs.WelcomeEditor.read(WelcomeEditor.java:962)
at
org.eclipse.ui.internal.ide.dialogs.WelcomeEditor.readFile(WelcomeEditor.java:980)
at
org.eclipse.ui.internal.ide.dialogs.WelcomeEditor.createPartControl(WelcomeEditor.java:686)
at
org.eclipse.ui.internal.EditorReference.createPartHelper(EditorReference.java:670)
at org.eclipse.ui.internal.EditorReference.createPart(EditorReference.java:465)
at
org.eclipse.ui.internal.WorkbenchPartReference.getPart(WorkbenchPartReference.java:595)
at org.eclipse.ui.internal.PartPane.setVisible(PartPane.java:313)
at
org.eclipse.ui.internal.presentations.PresentablePart.setVisible(PresentablePart.java:180)
at
org.eclipse.ui.internal.presentations.util.PresentablePartFolder.select(PresentablePartFolder.java:270)
at
org.eclipse.ui.internal.presentations.util.LeftToRightTabOrder.select(LeftToRightTabOrder.java:65)
at
org.eclipse.ui.internal.presentations.util.TabbedStackPresentation.selectPart(TabbedStackPresentation.java:473)
at
org.eclipse.ui.internal.PartStack.refreshPresentationSelection(PartStack.java:1245)
at org.eclipse.ui.internal.PartStack.setSelection(PartStack.java:1198)
at org.eclipse.ui.internal.PartStack.showPart(PartStack.java:1597)
at org.eclipse.ui.internal.PartStack.add(PartStack.java:493)
at org.eclipse.ui.internal.EditorStack.add(EditorStack.java:103)
at org.eclipse.ui.internal.EditorManager.openEditor(EditorManager.java:666)
at
org.eclipse.ui.internal.WorkbenchPage.busyOpenEditorBatched(WorkbenchPage.java:2942)
at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditor(WorkbenchPage.java:2850)
at org.eclipse.ui.internal.WorkbenchPage.access$11(WorkbenchPage.java:2842)
at org.eclipse.ui.internal.WorkbenchPage$10.run(WorkbenchPage.java:2793)
at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2789)
at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2773)
at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2756)
at
org.eclipse.ui.actions.QuickStartAction.openWelcomePage(QuickStartAction.java:239)
at org.eclipse.ui.actions.QuickStartAction.run(QuickStartAction.java:98)
at org.eclipse.jface.action.Action.runWithEvent(Action.java:498)
at org.eclipse.jface.commands.ActionHandler.execute(ActionHandler.java:119)
at org.eclipse.core.commands.Command.executeWithChecks(Command.java:476)
at
org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:508)
at
org.eclipse.ui.internal.handlers.HandlerService.executeCommand(HandlerService.java:169)
at
org.eclipse.ui.internal.handlers.SlaveHandlerService.executeCommand(SlaveHandlerService.java:241)
at
org.eclipse.ui.internal.actions.CommandAction.runWithEvent(CommandAction.java:157)
at
org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:584)
at
org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:501)
at
org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:411)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1258)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3588)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3209)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2696)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2660)
at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2494)
at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:674)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:667)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
at
org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:123)
at
org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:344)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
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:597)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:622)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:577)
at org.eclipse.equinox.launcher.Main.run(Main.java:1410)
at org.eclipse.equinox.launcher.Main.main(Main.java:1386)
JBDS Welcome screen should accept contributions from 3rd party extras
like JRebel, Spring, FindBugs, PMD
--------------------------------------------------------------------------------------------------------
Key: JBDS-1983
URL: https://issues.jboss.org/browse/JBDS-1983
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: 3rdPartyCertification, 3rdPartyDependencies, Welcome
Affects Versions: 5.0.0.M5
Reporter: Nick Boldt
Assignee: Snjezana Peco
Priority: Blocker
Fix For: 5.0.0.Beta1
Attachments: install-all-of-central-welcome-screen-breaks.png
We're currently patching SpringIDE's broken plugin (JBDS-1838) which contributes
a new Welcome screen, leading to this issue if unpatched:
!https://issues.jboss.org/secure/attachment/12346976/2011-09-09-105303.png!
However, it's been revealed that in addition to Spring, PMD, FindBugs, and now JRebel
also have this failing.
!https://issues.jboss.org/secure/attachment/12349923/2011-12-15_0052.png!
Therefore we ought to find a new way to suppress the effect across all of JBT/JBDS
instead of per-plugin, or get it fixed upstream.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:26 a.m.
[
https://issues.jboss.org/browse/JBDS-1983?page=com.atlassian.jira.plugin....
]
Max Rydahl Andersen commented on JBDS-1983:
-------------------------------------------
Firstly, we should *never* suggest patching/redistributing features as the first thing to
do - that is the *last* option.
Secondly, don't we control the welcome screen setup completely in JBDS at this time ?
surely these can be hidden/controlled or is this just as broken in plain eclipse?
Thirdly - this sounds like something that needs reported and fixing in eclipse itself also
so a bug would report would be relevant....
JBDS Welcome screen should accept contributions from 3rd party extras
like JRebel, Spring, FindBugs, PMD
--------------------------------------------------------------------------------------------------------
Key: JBDS-1983
URL: https://issues.jboss.org/browse/JBDS-1983
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: 3rdPartyCertification, 3rdPartyDependencies, Welcome
Affects Versions: 5.0.0.M5
Reporter: Nick Boldt
Assignee: Snjezana Peco
Priority: Blocker
Fix For: 5.0.0.Beta1
Attachments: install-all-of-central-welcome-screen-breaks.png
We're currently patching SpringIDE's broken plugin (JBDS-1838) which contributes
a new Welcome screen, leading to this issue if unpatched:
!https://issues.jboss.org/secure/attachment/12346976/2011-09-09-105303.png!
However, it's been revealed that in addition to Spring, PMD, FindBugs, and now JRebel
also have this failing.
!https://issues.jboss.org/secure/attachment/12349923/2011-12-15_0052.png!
Therefore we ought to find a new way to suppress the effect across all of JBT/JBDS
instead of per-plugin, or get it fixed upstream.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:06 p.m.
[
https://issues.jboss.org/browse/JBDS-1983?page=com.atlassian.jira.plugin....
]
Max Rydahl Andersen updated JBDS-1983:
--------------------------------------
Fix Version/s: 5.0.0.Beta2
(was: 5.0.0.Beta1)
JBDS Welcome screen should accept contributions from 3rd party extras
like JRebel, Spring, FindBugs, PMD
--------------------------------------------------------------------------------------------------------
Key: JBDS-1983
URL: https://issues.jboss.org/browse/JBDS-1983
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: 3rdPartyCertification, 3rdPartyDependencies, Welcome
Affects Versions: 5.0.0.M5
Reporter: Nick Boldt
Assignee: Snjezana Peco
Priority: Blocker
Fix For: 5.0.0.Beta2
Attachments: install-all-of-central-welcome-screen-breaks.png
We're currently patching SpringIDE's broken plugin (JBDS-1838) which contributes
a new Welcome screen, leading to this issue if unpatched:
!https://issues.jboss.org/secure/attachment/12346976/2011-09-09-105303.png!
However, it's been revealed that in addition to Spring, PMD, FindBugs, and now JRebel
also have this failing.
!https://issues.jboss.org/secure/attachment/12349923/2011-12-15_0052.png!
Therefore we ought to find a new way to suppress the effect across all of JBT/JBDS
instead of per-plugin, or get it fixed upstream.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:13 p.m.
[
https://issues.jboss.org/browse/JBDS-1983?page=com.atlassian.jira.plugin....
]
Denis Golovin reassigned JBDS-1983:
-----------------------------------
Assignee: Victor Rubezhny (was: Snjezana Peco)
Victor, could you check "if we can't prevent 3rd party welcome page contributions
from loading in jbds since we control the welcome screen anyway?" Max means other
options except transformation Snjezana suggested here.
JBDS Welcome screen should accept contributions from 3rd party extras
like JRebel, Spring, FindBugs, PMD
--------------------------------------------------------------------------------------------------------
Key: JBDS-1983
URL: https://issues.jboss.org/browse/JBDS-1983
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: 3rdPartyCertification, 3rdPartyDependencies, Welcome
Affects Versions: 5.0.0.M5
Reporter: Nick Boldt
Assignee: Victor Rubezhny
Priority: Blocker
Fix For: 5.0.0.Beta2
Attachments: install-all-of-central-welcome-screen-breaks.png
We're currently patching SpringIDE's broken plugin (JBDS-1838) which contributes
a new Welcome screen, leading to this issue if unpatched:
!https://issues.jboss.org/secure/attachment/12346976/2011-09-09-105303.png!
However, it's been revealed that in addition to Spring, PMD, FindBugs, and now JRebel
also have this failing.
!https://issues.jboss.org/secure/attachment/12349923/2011-12-15_0052.png!
Therefore we ought to find a new way to suppress the effect across all of JBT/JBDS
instead of per-plugin, or get it fixed upstream.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:15 a.m.
[
https://issues.jboss.org/browse/JBDS-1983?page=com.atlassian.jira.plugin....
]
Victor Rubezhny commented on JBDS-1983:
---------------------------------------
The problem described above, probably, is related to Eclipse 3.7.1 issue
https://bugs.eclipse.org/bugs/show_bug.cgi?id=370119 "Selecting Help/Welcome invokes
depricated QuickStartAction class and opens WelcomeEditor instead of
UniversalIntroPage".
Anyway, I have never saw a possibility to tell eclipse to use only 'our' Welcome
Intro and not to use all the other 'Welcome' screens from 3rd party products
(which are possibly installed later into JBDS).
Also, it's strange to me that 3rd party product Welcomes may be shown since the JBDS
has "-product
com.jboss.jbds.product.product" option defined in jbdevstudio.ini configuration file
and at the same time we have "com.jboss.jbds.intro.universal" Intro (JBDS
Welcome) associated with this product in product's plugin.xml.
If the Intro (Welcome) is replaced by a new one after some 3rd party product installation,
then anyway after the Eclipse is restarted it should show JBDS Welcome page (If is is not
configured to show Welcome at start, it should show JBDS Welcome when a user selectes
"Help->Welcome" menu item. If any other Welcome page is shown, then it's
a Eclipse's bug IMHO. Having WelcomeEditor to be invoked instead of UniversalIntroPage
(which is configured to be "com.jboss.jbds.intro.universal") is a bug also (see
https://bugs.eclipse.org/bugs/show_bug.cgi?id=370119).
If some cashing is playing here, then it should be fixable by using "-clean"
option at start.
JBDS Welcome screen should accept contributions from 3rd party extras
like JRebel, Spring, FindBugs, PMD
--------------------------------------------------------------------------------------------------------
Key: JBDS-1983
URL: https://issues.jboss.org/browse/JBDS-1983
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: 3rdPartyCertification, 3rdPartyDependencies, Welcome
Affects Versions: 5.0.0.M5
Reporter: Nick Boldt
Assignee: Victor Rubezhny
Priority: Blocker
Fix For: 5.0.0.Beta2
Attachments: install-all-of-central-welcome-screen-breaks.png
We're currently patching SpringIDE's broken plugin (JBDS-1838) which contributes
a new Welcome screen, leading to this issue if unpatched:
!https://issues.jboss.org/secure/attachment/12346976/2011-09-09-105303.png!
However, it's been revealed that in addition to Spring, PMD, FindBugs, and now JRebel
also have this failing.
!https://issues.jboss.org/secure/attachment/12349923/2011-12-15_0052.png!
Therefore we ought to find a new way to suppress the effect across all of JBT/JBDS
instead of per-plugin, or get it fixed upstream.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:33 a.m.
[
https://issues.jboss.org/browse/JBDS-1983?page=com.atlassian.jira.plugin....
]
Nick Boldt commented on JBDS-1983:
----------------------------------
Curiously, I can't seem to get the "which Welcome screen would you like"
editor to appear anymore, and the JBDS Welcome screen appears to always work (while other
3rd party ones like JRebel never appear).
Tested with this:
1. JBDS 5beta1 (Build id: v20120308-2315-H106-Beta1)
2. install findbugs, jslint, pmd, jrebel and springide from JBDS Central
3. restart. welcome screen works.
JBDS Welcome screen should accept contributions from 3rd party extras
like JRebel, Spring, FindBugs, PMD
--------------------------------------------------------------------------------------------------------
Key: JBDS-1983
URL: https://issues.jboss.org/browse/JBDS-1983
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: 3rdPartyCertification, 3rdPartyDependencies, Welcome
Affects Versions: 5.0.0.M5
Reporter: Nick Boldt
Assignee: Victor Rubezhny
Priority: Blocker
Fix For: 5.0.0.Beta3
Attachments: install-all-of-central-welcome-screen-breaks.png
We're currently patching SpringIDE's broken plugin (JBDS-1838) which contributes
a new Welcome screen, leading to this issue if unpatched:
!https://issues.jboss.org/secure/attachment/12346976/2011-09-09-105303.png!
However, it's been revealed that in addition to Spring, PMD, FindBugs, and now JRebel
also have this failing.
!https://issues.jboss.org/secure/attachment/12349923/2011-12-15_0052.png!
Therefore we ought to find a new way to suppress the effect across all of JBT/JBDS
instead of per-plugin, or get it fixed upstream.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:54 p.m.
[
https://issues.jboss.org/browse/JBDS-1983?page=com.atlassian.jira.plugin....
]
Victor Rubezhny commented on JBDS-1983:
---------------------------------------
Cannot reproduce it too on JBDS 5.0.0.beta2 (v20120323-1627-H119-Beta2).
Probably, some changes were made on other issues (like JBDS-2030 or JBDS-2058) that caused
Welcome Screen to work well.
Snjezana, Denis, could you verify if this issue is still can be reproduced?
JBDS Welcome screen should accept contributions from 3rd party extras
like JRebel, Spring, FindBugs, PMD
--------------------------------------------------------------------------------------------------------
Key: JBDS-1983
URL: https://issues.jboss.org/browse/JBDS-1983
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: 3rdPartyCertification, 3rdPartyDependencies, Welcome
Affects Versions: 5.0.0.M5
Reporter: Nick Boldt
Assignee: Victor Rubezhny
Priority: Blocker
Fix For: 5.0.0.Beta3
Attachments: install-all-of-central-welcome-screen-breaks.png
We're currently patching SpringIDE's broken plugin (JBDS-1838) which contributes
a new Welcome screen, leading to this issue if unpatched:
!https://issues.jboss.org/secure/attachment/12346976/2011-09-09-105303.png!
However, it's been revealed that in addition to Spring, PMD, FindBugs, and now JRebel
also have this failing.
!https://issues.jboss.org/secure/attachment/12349923/2011-12-15_0052.png!
Therefore we ought to find a new way to suppress the effect across all of JBT/JBDS
instead of per-plugin, or get it fixed upstream.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:32 p.m.
[
https://issues.jboss.org/browse/JBDS-1983?page=com.atlassian.jira.plugin....
]
Victor Rubezhny edited comment on JBDS-1983 at 3/30/12 6:32 PM:
----------------------------------------------------------------
Cannot reproduce it too on JBDS 5.0.0.beta2 (v20120323-1627-H119-Beta2) on Ubuntu x86-64
as well as on Win7 x86.
For both OS, I've installed all the features proposed by the Central, restarted the
Studio, then tried to reproduce the issue by openning/closing repeatedly the Welcome
Screen using Help->Welcome menu item. The issue is not reproducible for me in both
environments regardless of the fact that at least three installed plugins
(net.sourceforge.pmd.eclipse, net.sourceforge.pmd.ui and
edu.umd.cs.findbugs.plugin.eclipse) contain file welcome.xml (which is supposed to be an
old-style Welcome Page that caused WelcomeScreen editor to be opened instead of Universal
Intro page by selecting Help->Welcome as stated in
https://bugs.eclipse.org/bugs/show_bug.cgi?id=370119).
Probably, some changes were made on other issues (like JBDS-2030 or JBDS-2058) that caused
Welcome Screen to work well. So, it seems that the issue is fixed by some outstanding
changes.
Snjezana, Denis, could you verify if this issue is still can be reproduced?
was (Author: vrubezhny):
Cannot reproduce it too on JBDS 5.0.0.beta2 (v20120323-1627-H119-Beta2).
Probably, some changes were made on other issues (like JBDS-2030 or JBDS-2058) that caused
Welcome Screen to work well.
Snjezana, Denis, could you verify if this issue is still can be reproduced?
JBDS Welcome screen should accept contributions from 3rd party extras
like JRebel, Spring, FindBugs, PMD
--------------------------------------------------------------------------------------------------------
Key: JBDS-1983
URL: https://issues.jboss.org/browse/JBDS-1983
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: 3rdPartyCertification, 3rdPartyDependencies, Welcome
Affects Versions: 5.0.0.M5
Reporter: Nick Boldt
Assignee: Victor Rubezhny
Priority: Blocker
Fix For: 5.0.0.Beta3
Attachments: install-all-of-central-welcome-screen-breaks.png
We're currently patching SpringIDE's broken plugin (JBDS-1838) which contributes
a new Welcome screen, leading to this issue if unpatched:
!https://issues.jboss.org/secure/attachment/12346976/2011-09-09-105303.png!
However, it's been revealed that in addition to Spring, PMD, FindBugs, and now JRebel
also have this failing.
!https://issues.jboss.org/secure/attachment/12349923/2011-12-15_0052.png!
Therefore we ought to find a new way to suppress the effect across all of JBT/JBDS
instead of per-plugin, or get it fixed upstream.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:13 a.m.
[
https://issues.jboss.org/browse/JBDS-1983?page=com.atlassian.jira.plugin....
]
Snjezana Peco commented on JBDS-1983:
-------------------------------------
The issue can't be reproduced using JBDS 5.0.0.Beta2a.
The fix isn't related either to JBDS-2058 or to JBDS-2030.
JBDS-2058 hasn't been fixed yet.
JBDS-2030 isn't related to this issue. The fix is included in the trunk only.
The Spring IDE has been fixed by using the patched org.springframework.ide.eclipse plugin
(JBDS-1838)
The PMD, FindBugs have been fixed by introducing com.jbds.* feature and there is no
branding plugin for those features.
The JRebel plugin contains the welcomePage property, but doesn't contain the
welcome.xml file. The JRebel uses the org.eclipse.ui.intro.configExtension extension point
and I believe the welcomePage property is deprecated.
The JSLint feature isn't branded.
In my opinion, this issue can be marked as fixed.
JBDS Welcome screen should accept contributions from 3rd party extras
like JRebel, Spring, FindBugs, PMD
--------------------------------------------------------------------------------------------------------
Key: JBDS-1983
URL: https://issues.jboss.org/browse/JBDS-1983
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: 3rdPartyCertification, 3rdPartyDependencies, Welcome
Affects Versions: 5.0.0.M5
Reporter: Nick Boldt
Assignee: Victor Rubezhny
Priority: Blocker
Fix For: 5.0.0.Beta3
Attachments: install-all-of-central-welcome-screen-breaks.png
We're currently patching SpringIDE's broken plugin (JBDS-1838) which contributes
a new Welcome screen, leading to this issue if unpatched:
!https://issues.jboss.org/secure/attachment/12346976/2011-09-09-105303.png!
However, it's been revealed that in addition to Spring, PMD, FindBugs, and now JRebel
also have this failing.
!https://issues.jboss.org/secure/attachment/12349923/2011-12-15_0052.png!
Therefore we ought to find a new way to suppress the effect across all of JBT/JBDS
instead of per-plugin, or get it fixed upstream.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:25 a.m.
[
https://issues.jboss.org/browse/JBDS-1983?page=com.atlassian.jira.plugin....
]
Max Rydahl Andersen commented on JBDS-1983:
-------------------------------------------
No it cannot be closed IMO - we should not be "fixing" these by introducing
patched features nor introducing custom feature names if can be avoided.
This means JBDS still doesn't accept third party contributions, similar to what EPP
packages like JEE does.
JBDS Welcome screen should accept contributions from 3rd party extras
like JRebel, Spring, FindBugs, PMD
--------------------------------------------------------------------------------------------------------
Key: JBDS-1983
URL: https://issues.jboss.org/browse/JBDS-1983
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: 3rdPartyCertification, 3rdPartyDependencies, Welcome
Affects Versions: 5.0.0.M5
Reporter: Nick Boldt
Assignee: Victor Rubezhny
Priority: Blocker
Fix For: 5.0.0.Beta3
Attachments: install-all-of-central-welcome-screen-breaks.png
We're currently patching SpringIDE's broken plugin (JBDS-1838) which contributes
a new Welcome screen, leading to this issue if unpatched:
!https://issues.jboss.org/secure/attachment/12346976/2011-09-09-105303.png!
However, it's been revealed that in addition to Spring, PMD, FindBugs, and now JRebel
also have this failing.
!https://issues.jboss.org/secure/attachment/12349923/2011-12-15_0052.png!
Therefore we ought to find a new way to suppress the effect across all of JBT/JBDS
instead of per-plugin, or get it fixed upstream.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:03 a.m.
[
https://issues.jboss.org/browse/JBDS-1983?page=com.atlassian.jira.plugin....
]
Victor Rubezhny commented on JBDS-1983:
---------------------------------------
The patch provided for https://bugs.eclipse.org/bugs/show_bug.cgi?id=370119 issue in
BugZilla. The patch, if applied, fixes JBDS-1983 issue.
JBDS Welcome screen should accept contributions from 3rd party extras
like JRebel, Spring, FindBugs, PMD
--------------------------------------------------------------------------------------------------------
Key: JBDS-1983
URL: https://issues.jboss.org/browse/JBDS-1983
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: 3rdPartyCertification, 3rdPartyDependencies, Upstream, Welcome
Affects Versions: 5.0.0.M5
Reporter: Nick Boldt
Assignee: Victor Rubezhny
Priority: Blocker
Fix For: 5.0.0.Beta3
Attachments: install-all-of-central-welcome-screen-breaks.png
We're currently patching SpringIDE's broken plugin (JBDS-1838) which contributes
a new Welcome screen, leading to this issue if unpatched:
!https://issues.jboss.org/secure/attachment/12346976/2011-09-09-105303.png!
However, it's been revealed that in addition to Spring, PMD, FindBugs, and now JRebel
also have this failing.
!https://issues.jboss.org/secure/attachment/12349923/2011-12-15_0052.png!
Therefore we ought to find a new way to suppress the effect across all of JBT/JBDS
instead of per-plugin, or get it fixed upstream.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:03 a.m.
[
https://issues.jboss.org/browse/JBDS-1983?page=com.atlassian.jira.plugin....
]
Victor Rubezhny updated JBDS-1983:
----------------------------------
Component/s: Upstream
JBDS Welcome screen should accept contributions from 3rd party extras
like JRebel, Spring, FindBugs, PMD
--------------------------------------------------------------------------------------------------------
Key: JBDS-1983
URL: https://issues.jboss.org/browse/JBDS-1983
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: 3rdPartyCertification, 3rdPartyDependencies, Upstream, Welcome
Affects Versions: 5.0.0.M5
Reporter: Nick Boldt
Assignee: Victor Rubezhny
Priority: Blocker
Fix For: 5.0.0.Beta3
Attachments: install-all-of-central-welcome-screen-breaks.png
We're currently patching SpringIDE's broken plugin (JBDS-1838) which contributes
a new Welcome screen, leading to this issue if unpatched:
!https://issues.jboss.org/secure/attachment/12346976/2011-09-09-105303.png!
However, it's been revealed that in addition to Spring, PMD, FindBugs, and now JRebel
also have this failing.
!https://issues.jboss.org/secure/attachment/12349923/2011-12-15_0052.png!
Therefore we ought to find a new way to suppress the effect across all of JBT/JBDS
instead of per-plugin, or get it fixed upstream.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:02 a.m.
[
https://issues.jboss.org/browse/JBDS-1983?page=com.atlassian.jira.plugin....
]
Nick Boldt commented on JBDS-1983:
----------------------------------
Victor: this will never be fixed upstream as there will never be another 3.7.x build after
they finished 3.7.2 in February 2012.
So either *WE* patch our copy of the Eclipse.org bits, or we accept this won't be
fixed until we have a Juno-based release (eg., JBDS 6?).
JBDS Welcome screen should accept contributions from 3rd party extras
like JRebel, Spring, FindBugs, PMD
--------------------------------------------------------------------------------------------------------
Key: JBDS-1983
URL: https://issues.jboss.org/browse/JBDS-1983
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: 3rdPartyCertification, 3rdPartyDependencies, Upstream, Welcome
Affects Versions: 5.0.0.M5
Reporter: Nick Boldt
Assignee: Victor Rubezhny
Priority: Blocker
Fix For: 5.0.0.Beta3
Attachments: install-all-of-central-welcome-screen-breaks.png
We're currently patching SpringIDE's broken plugin (JBDS-1838) which contributes
a new Welcome screen, leading to this issue if unpatched:
!https://issues.jboss.org/secure/attachment/12346976/2011-09-09-105303.png!
However, it's been revealed that in addition to Spring, PMD, FindBugs, and now JRebel
also have this failing.
!https://issues.jboss.org/secure/attachment/12349923/2011-12-15_0052.png!
Therefore we ought to find a new way to suppress the effect across all of JBT/JBDS
instead of per-plugin, or get it fixed upstream.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:22 p.m.
[
https://issues.jboss.org/browse/JBDS-1983?page=com.atlassian.jira.plugin....
]
Victor Rubezhny commented on JBDS-1983:
---------------------------------------
I have a workaround for our product pluging for beta3 version. It needs to be tested, but
if succeded, it will solve the problem for Eclipse 3.7.x builds.
Hope, we can remove this workaround for JBDS 6 when Eclipse 3.8 (?) will be published (if
they will apply my patch /or will fix their issue by themselves)
JBDS Welcome screen should accept contributions from 3rd party extras
like JRebel, Spring, FindBugs, PMD
--------------------------------------------------------------------------------------------------------
Key: JBDS-1983
URL: https://issues.jboss.org/browse/JBDS-1983
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: 3rdPartyCertification, 3rdPartyDependencies, Upstream, Welcome
Affects Versions: 5.0.0.M5
Reporter: Nick Boldt
Assignee: Victor Rubezhny
Priority: Blocker
Fix For: 5.0.0.Beta3
Attachments: install-all-of-central-welcome-screen-breaks.png
We're currently patching SpringIDE's broken plugin (JBDS-1838) which contributes
a new Welcome screen, leading to this issue if unpatched:
!https://issues.jboss.org/secure/attachment/12346976/2011-09-09-105303.png!
However, it's been revealed that in addition to Spring, PMD, FindBugs, and now JRebel
also have this failing.
!https://issues.jboss.org/secure/attachment/12349923/2011-12-15_0052.png!
Therefore we ought to find a new way to suppress the effect across all of JBT/JBDS
instead of per-plugin, or get it fixed upstream.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:22 p.m.
[
https://issues.jboss.org/browse/JBDS-1983?page=com.atlassian.jira.plugin....
]
Victor Rubezhny edited comment on JBDS-1983 at 4/3/12 1:21 PM:
---------------------------------------------------------------
I have a workaround for our product pluging for beta3 version. It needs to be tested, but
if succeded, it will solve the problem for JBDS 5 (Eclipse 3.7.x builds).
Hope, we can remove this workaround for JBDS 6 when Eclipse 3.8 (?) will be published (if
they will apply my patch /or will fix their issue by themselves)
was (Author: vrubezhny):
I have a workaround for our product pluging for beta3 version. It needs to be tested,
but if succeded, it will solve the problem for Eclipse 3.7.x builds.
Hope, we can remove this workaround for JBDS 6 when Eclipse 3.8 (?) will be published (if
they will apply my patch /or will fix their issue by themselves)
JBDS Welcome screen should accept contributions from 3rd party extras
like JRebel, Spring, FindBugs, PMD
--------------------------------------------------------------------------------------------------------
Key: JBDS-1983
URL: https://issues.jboss.org/browse/JBDS-1983
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: 3rdPartyCertification, 3rdPartyDependencies, Upstream, Welcome
Affects Versions: 5.0.0.M5
Reporter: Nick Boldt
Assignee: Victor Rubezhny
Priority: Blocker
Fix For: 5.0.0.Beta3
Attachments: install-all-of-central-welcome-screen-breaks.png
We're currently patching SpringIDE's broken plugin (JBDS-1838) which contributes
a new Welcome screen, leading to this issue if unpatched:
!https://issues.jboss.org/secure/attachment/12346976/2011-09-09-105303.png!
However, it's been revealed that in addition to Spring, PMD, FindBugs, and now JRebel
also have this failing.
!https://issues.jboss.org/secure/attachment/12349923/2011-12-15_0052.png!
Therefore we ought to find a new way to suppress the effect across all of JBT/JBDS
instead of per-plugin, or get it fixed upstream.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:22 p.m.
[
https://issues.jboss.org/browse/JBDS-1983?page=com.atlassian.jira.plugin....
]
Victor Rubezhny edited comment on JBDS-1983 at 4/3/12 1:22 PM:
---------------------------------------------------------------
I have a workaround for our product pluging for beta3 version. It needs to be tested, but
if succeded, it will solve the problem for JBDS 5 (Eclipse 3.7.x builds). So, probably we
don't need to patch any eclipse's bits for JBDS 5.
Hope, we can remove this workaround for JBDS 6 when Eclipse 3.8 (?) will be published (if
they will apply my patch /or will fix their issue by themselves)
was (Author: vrubezhny):
I have a workaround for our product pluging for beta3 version. It needs to be tested,
but if succeded, it will solve the problem for JBDS 5 (Eclipse 3.7.x builds).
Hope, we can remove this workaround for JBDS 6 when Eclipse 3.8 (?) will be published (if
they will apply my patch /or will fix their issue by themselves)
JBDS Welcome screen should accept contributions from 3rd party extras
like JRebel, Spring, FindBugs, PMD
--------------------------------------------------------------------------------------------------------
Key: JBDS-1983
URL: https://issues.jboss.org/browse/JBDS-1983
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: 3rdPartyCertification, 3rdPartyDependencies, Upstream, Welcome
Affects Versions: 5.0.0.M5
Reporter: Nick Boldt
Assignee: Victor Rubezhny
Priority: Blocker
Fix For: 5.0.0.Beta3
Attachments: install-all-of-central-welcome-screen-breaks.png
We're currently patching SpringIDE's broken plugin (JBDS-1838) which contributes
a new Welcome screen, leading to this issue if unpatched:
!https://issues.jboss.org/secure/attachment/12346976/2011-09-09-105303.png!
However, it's been revealed that in addition to Spring, PMD, FindBugs, and now JRebel
also have this failing.
!https://issues.jboss.org/secure/attachment/12349923/2011-12-15_0052.png!
Therefore we ought to find a new way to suppress the effect across all of JBT/JBDS
instead of per-plugin, or get it fixed upstream.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:41 p.m.
[
https://issues.jboss.org/browse/JBDS-1983?page=com.atlassian.jira.plugin....
]
Victor Rubezhny updated JBDS-1983:
----------------------------------
Attachment: jbds-1983-workaround.patch
The jbds-1983-workaround.patch is a workaround for
https://bugs.eclipse.org/bugs/show_bug.cgi?id=370119 BugZilla issue. If applied, it should
be removed when UpStream issue is fixed.
JBDS Welcome screen should accept contributions from 3rd party extras
like JRebel, Spring, FindBugs, PMD
--------------------------------------------------------------------------------------------------------
Key: JBDS-1983
URL: https://issues.jboss.org/browse/JBDS-1983
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: 3rdPartyCertification, 3rdPartyDependencies, Upstream, Welcome
Affects Versions: 5.0.0.M5
Reporter: Nick Boldt
Assignee: Victor Rubezhny
Priority: Blocker
Fix For: 5.0.0.Beta3
Attachments: install-all-of-central-welcome-screen-breaks.png,
jbds-1983-workaround.patch
We're currently patching SpringIDE's broken plugin (JBDS-1838) which contributes
a new Welcome screen, leading to this issue if unpatched:
!https://issues.jboss.org/secure/attachment/12346976/2011-09-09-105303.png!
However, it's been revealed that in addition to Spring, PMD, FindBugs, and now JRebel
also have this failing.
!https://issues.jboss.org/secure/attachment/12349923/2011-12-15_0052.png!
Therefore we ought to find a new way to suppress the effect across all of JBT/JBDS
instead of per-plugin, or get it fixed upstream.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:56 p.m.
[
https://issues.jboss.org/browse/JBDS-1983?page=com.atlassian.jira.plugin....
]
Snjezana Peco commented on JBDS-1983:
-------------------------------------
This means JBDS still doesn't accept third party contributions,
similar to what EPP packages like JEE does.
If we want JBDS to accept the third party contributions, the JBDS intro page would have to
include the following standard pages:
overview (JRebel, WTP, DTP, M2E, a newer Spring IDE contributes its extensions to this
page)
tutorials
samples
whatsnew
The JRebel's contribution is included in the org.zeroturnaround.eclipse.remoting
plugin that isn't included in the JBT/JBDS discovery plugin.
Spring IDE 2.7.2 doesn't contribute anything to the welcome page. Spring IDE 2.9.1
contributes to the overview page.
PMD and FindBugs don't contribute anything to the welcome page.
FindBugs 1.3.9/PMD 3.2.4 (JBT/JBDS uses this version) contains an invalid welcome.xml file
that suppresses opening of the Welcome page in JBT.
This file has been removed from FindBugs 2.0.0.
PMD 3.2.6 hasn't been branded correctly and there is no problem with opening the
welcome page.
JBDS Welcome screen should accept contributions from 3rd party extras
like JRebel, Spring, FindBugs, PMD
--------------------------------------------------------------------------------------------------------
Key: JBDS-1983
URL: https://issues.jboss.org/browse/JBDS-1983
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: 3rdPartyCertification, 3rdPartyDependencies, Upstream, Welcome
Affects Versions: 5.0.0.M5
Reporter: Nick Boldt
Assignee: Victor Rubezhny
Priority: Blocker
Fix For: 5.0.0.Beta3
Attachments: install-all-of-central-welcome-screen-breaks.png,
jbds-1983-workaround.patch
We're currently patching SpringIDE's broken plugin (JBDS-1838) which contributes
a new Welcome screen, leading to this issue if unpatched:
!https://issues.jboss.org/secure/attachment/12346976/2011-09-09-105303.png!
However, it's been revealed that in addition to Spring, PMD, FindBugs, and now JRebel
also have this failing.
!https://issues.jboss.org/secure/attachment/12349923/2011-12-15_0052.png!
Therefore we ought to find a new way to suppress the effect across all of JBT/JBDS
instead of per-plugin, or get it fixed upstream.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:03 a.m.
New subject: [JBoss JIRA] (JBDS-1983) Handle issues concerning multiple welcome screens in Eclipse product
[
https://issues.jboss.org/browse/JBDS-1983?page=com.atlassian.jira.plugin....
]
Max Rydahl Andersen updated JBDS-1983:
--------------------------------------
Summary: Handle issues concerning multiple welcome screens in Eclipse product (was:
JBDS Welcome screen should accept contributions from 3rd party extras like JRebel, Spring,
FindBugs, PMD)
splitting this issue in to the two separate issues that is being discussed.
Handle issues concerning multiple welcome screens in Eclipse product
--------------------------------------------------------------------
Key: JBDS-1983
URL: https://issues.jboss.org/browse/JBDS-1983
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: 3rdPartyCertification, 3rdPartyDependencies, Upstream, Welcome
Affects Versions: 5.0.0.M5
Reporter: Nick Boldt
Assignee: Victor Rubezhny
Priority: Blocker
Fix For: 5.0.0.Beta3
Attachments: install-all-of-central-welcome-screen-breaks.png,
jbds-1983-workaround.patch
We're currently patching SpringIDE's broken plugin (JBDS-1838) which contributes
a new Welcome screen, leading to this issue if unpatched:
!https://issues.jboss.org/secure/attachment/12346976/2011-09-09-105303.png!
However, it's been revealed that in addition to Spring, PMD, FindBugs, and now JRebel
also have this failing.
!https://issues.jboss.org/secure/attachment/12349923/2011-12-15_0052.png!
Therefore we ought to find a new way to suppress the effect across all of JBT/JBDS
instead of per-plugin, or get it fixed upstream.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:12 a.m.
New subject: [JBoss JIRA] (JBDS-1983) Handle issues concerning multiple welcome screens in Eclipse product
[
https://issues.jboss.org/browse/JBDS-1983?page=com.atlassian.jira.plugin....
]
Max Rydahl Andersen commented on JBDS-1983:
-------------------------------------------
This issue is now about what the patch relates to: avoiding showing the useless dialog and
causing welcome editor to be opened instead.
Subissue JBDS-2086 is about future options on allowing welcome content to be shown.
Handle issues concerning multiple welcome screens in Eclipse product
--------------------------------------------------------------------
Key: JBDS-1983
URL: https://issues.jboss.org/browse/JBDS-1983
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: 3rdPartyCertification, 3rdPartyDependencies, Upstream, Welcome
Affects Versions: 5.0.0.M5
Reporter: Nick Boldt
Assignee: Victor Rubezhny
Priority: Blocker
Fix For: 5.0.0.Beta3
Attachments: install-all-of-central-welcome-screen-breaks.png,
jbds-1983-workaround.patch
We're currently patching SpringIDE's broken plugin (JBDS-1838) which contributes
a new Welcome screen, leading to this issue if unpatched:
!https://issues.jboss.org/secure/attachment/12346976/2011-09-09-105303.png!
However, it's been revealed that in addition to Spring, PMD, FindBugs, and now JRebel
also have this failing.
!https://issues.jboss.org/secure/attachment/12349923/2011-12-15_0052.png!
Therefore we ought to find a new way to suppress the effect across all of JBT/JBDS
instead of per-plugin, or get it fixed upstream.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:37 a.m.
New subject: [JBoss JIRA] (JBDS-1983) Handle issues concerning multiple welcome screens in Eclipse product
[
https://issues.jboss.org/browse/JBDS-1983?page=com.atlassian.jira.plugin....
]
Victor Rubezhny commented on JBDS-1983:
---------------------------------------
I've installed Spring IDE Core (not patched, from http://springide.org/updatesite
update site) which has welcome.xml page on JBDS 5.0.0.beta2+jbds-1983-workaround.patch. No
WelcomeEditor appears by Help->Welcome. So, it seems that workaround works.
Snjezana, could you review the workaround patch?
Handle issues concerning multiple welcome screens in Eclipse product
--------------------------------------------------------------------
Key: JBDS-1983
URL: https://issues.jboss.org/browse/JBDS-1983
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: 3rdPartyCertification, 3rdPartyDependencies, Upstream, Welcome
Affects Versions: 5.0.0.M5
Reporter: Nick Boldt
Assignee: Victor Rubezhny
Priority: Blocker
Fix For: 5.0.0.Beta3
Attachments: install-all-of-central-welcome-screen-breaks.png,
jbds-1983-workaround.patch
We're currently patching SpringIDE's broken plugin (JBDS-1838) which contributes
a new Welcome screen, leading to this issue if unpatched:
!https://issues.jboss.org/secure/attachment/12346976/2011-09-09-105303.png!
However, it's been revealed that in addition to Spring, PMD, FindBugs, and now JRebel
also have this failing.
!https://issues.jboss.org/secure/attachment/12349923/2011-12-15_0052.png!
Therefore we ought to find a new way to suppress the effect across all of JBT/JBDS
instead of per-plugin, or get it fixed upstream.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:37 p.m.
New subject: [JBoss JIRA] (JBDS-1983) Handle issues concerning multiple welcome screens in Eclipse product
[
https://issues.jboss.org/browse/JBDS-1983?page=com.atlassian.jira.plugin....
]
Victor Rubezhny commented on JBDS-1983:
---------------------------------------
The fix is applied for BugZilla issue, but Target Milestone is set to be 3.8 M7, so, for
JBDS 5 we need to have a workaround for
https://bugs.eclipse.org/bugs/show_bug.cgi?id=370119
Handle issues concerning multiple welcome screens in Eclipse product
--------------------------------------------------------------------
Key: JBDS-1983
URL: https://issues.jboss.org/browse/JBDS-1983
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: 3rdPartyCertification, 3rdPartyDependencies, Upstream, Welcome
Affects Versions: 5.0.0.M5
Reporter: Nick Boldt
Assignee: Victor Rubezhny
Priority: Blocker
Fix For: 5.0.0.Beta3
Attachments: install-all-of-central-welcome-screen-breaks.png,
jbds-1983-workaround.patch
We're currently patching SpringIDE's broken plugin (JBDS-1838) which contributes
a new Welcome screen, leading to this issue if unpatched:
!https://issues.jboss.org/secure/attachment/12346976/2011-09-09-105303.png!
However, it's been revealed that in addition to Spring, PMD, FindBugs, and now JRebel
also have this failing.
!https://issues.jboss.org/secure/attachment/12349923/2011-12-15_0052.png!
Therefore we ought to find a new way to suppress the effect across all of JBT/JBDS
instead of per-plugin, or get it fixed upstream.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:07 p.m.
New subject: [JBoss JIRA] (JBDS-1983) Handle issues concerning multiple welcome screens in Eclipse product
[
https://issues.jboss.org/browse/JBDS-1983?page=com.atlassian.jira.plugin....
]
Snjezana Peco commented on JBDS-1983:
-------------------------------------
Victor,
The patch fixes the issue related to opening WelcomeEditor.
Handle issues concerning multiple welcome screens in Eclipse product
--------------------------------------------------------------------
Key: JBDS-1983
URL: https://issues.jboss.org/browse/JBDS-1983
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: 3rdPartyCertification, 3rdPartyDependencies, Upstream, Welcome
Affects Versions: 5.0.0.M5
Reporter: Nick Boldt
Assignee: Victor Rubezhny
Priority: Blocker
Fix For: 5.0.0.Beta3
Attachments: install-all-of-central-welcome-screen-breaks.png,
jbds-1983-workaround.patch
We're currently patching SpringIDE's broken plugin (JBDS-1838) which contributes
a new Welcome screen, leading to this issue if unpatched:
!https://issues.jboss.org/secure/attachment/12346976/2011-09-09-105303.png!
However, it's been revealed that in addition to Spring, PMD, FindBugs, and now JRebel
also have this failing.
!https://issues.jboss.org/secure/attachment/12349923/2011-12-15_0052.png!
Therefore we ought to find a new way to suppress the effect across all of JBT/JBDS
instead of per-plugin, or get it fixed upstream.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:24 p.m.
New subject: [JBoss JIRA] (JBDS-1983) Handle issues concerning multiple welcome screens in Eclipse product
[
https://issues.jboss.org/browse/JBDS-1983?page=com.atlassian.jira.plugin....
]
Max Rydahl Andersen commented on JBDS-1983:
-------------------------------------------
Snjezana - and that includes not showing the weird dialog up front or not ?
Handle issues concerning multiple welcome screens in Eclipse product
--------------------------------------------------------------------
Key: JBDS-1983
URL: https://issues.jboss.org/browse/JBDS-1983
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: 3rdPartyCertification, 3rdPartyDependencies, Upstream, Welcome
Affects Versions: 5.0.0.M5
Reporter: Nick Boldt
Assignee: Victor Rubezhny
Priority: Blocker
Fix For: 5.0.0.Beta3
Attachments: install-all-of-central-welcome-screen-breaks.png,
jbds-1983-workaround.patch
We're currently patching SpringIDE's broken plugin (JBDS-1838) which contributes
a new Welcome screen, leading to this issue if unpatched:
!https://issues.jboss.org/secure/attachment/12346976/2011-09-09-105303.png!
However, it's been revealed that in addition to Spring, PMD, FindBugs, and now JRebel
also have this failing.
!https://issues.jboss.org/secure/attachment/12349923/2011-12-15_0052.png!
Therefore we ought to find a new way to suppress the effect across all of JBT/JBDS
instead of per-plugin, or get it fixed upstream.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:44 p.m.
New subject: [JBoss JIRA] (JBDS-1983) Handle issues concerning multiple welcome screens in Eclipse product
[
https://issues.jboss.org/browse/JBDS-1983?page=com.atlassian.jira.plugin....
]
Snjezana Peco commented on JBDS-1983:
-------------------------------------
The weird dialog isn't shown when using Victor's patch.
Handle issues concerning multiple welcome screens in Eclipse product
--------------------------------------------------------------------
Key: JBDS-1983
URL: https://issues.jboss.org/browse/JBDS-1983
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: 3rdPartyCertification, 3rdPartyDependencies, Upstream, Welcome
Affects Versions: 5.0.0.M5
Reporter: Nick Boldt
Assignee: Victor Rubezhny
Priority: Blocker
Fix For: 5.0.0.Beta3
Attachments: install-all-of-central-welcome-screen-breaks.png,
jbds-1983-workaround.patch
We're currently patching SpringIDE's broken plugin (JBDS-1838) which contributes
a new Welcome screen, leading to this issue if unpatched:
!https://issues.jboss.org/secure/attachment/12346976/2011-09-09-105303.png!
However, it's been revealed that in addition to Spring, PMD, FindBugs, and now JRebel
also have this failing.
!https://issues.jboss.org/secure/attachment/12349923/2011-12-15_0052.png!
Therefore we ought to find a new way to suppress the effect across all of JBT/JBDS
instead of per-plugin, or get it fixed upstream.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:30 p.m.
New subject: [JBoss JIRA] (JBDS-1983) Handle issues concerning multiple welcome screens in Eclipse product
[
https://issues.jboss.org/browse/JBDS-1983?page=com.atlassian.jira.plugin....
]
Victor Rubezhny commented on JBDS-1983:
---------------------------------------
Patch is comitted, JBDS-2089 is created due to remove the patch after the UpStream issue
is fixed.
Handle issues concerning multiple welcome screens in Eclipse product
--------------------------------------------------------------------
Key: JBDS-1983
URL: https://issues.jboss.org/browse/JBDS-1983
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: 3rdPartyCertification, 3rdPartyDependencies, Upstream, Welcome
Affects Versions: 5.0.0.M5
Reporter: Nick Boldt
Assignee: Victor Rubezhny
Priority: Blocker
Fix For: 5.0.0.Beta3
Attachments: install-all-of-central-welcome-screen-breaks.png,
jbds-1983-workaround.patch
We're currently patching SpringIDE's broken plugin (JBDS-1838) which contributes
a new Welcome screen, leading to this issue if unpatched:
!https://issues.jboss.org/secure/attachment/12346976/2011-09-09-105303.png!
However, it's been revealed that in addition to Spring, PMD, FindBugs, and now JRebel
also have this failing.
!https://issues.jboss.org/secure/attachment/12349923/2011-12-15_0052.png!
Therefore we ought to find a new way to suppress the effect across all of JBT/JBDS
instead of per-plugin, or get it fixed upstream.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:30 p.m.
New subject: [JBoss JIRA] (JBDS-1983) Handle issues concerning multiple welcome screens in Eclipse product
[
https://issues.jboss.org/browse/JBDS-1983?page=com.atlassian.jira.plugin....
]
Victor Rubezhny reassigned JBDS-1983:
-------------------------------------
Assignee: Denis Golovin (was: Victor Rubezhny)
Issue is fixed, please verify.
Handle issues concerning multiple welcome screens in Eclipse product
--------------------------------------------------------------------
Key: JBDS-1983
URL: https://issues.jboss.org/browse/JBDS-1983
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: 3rdPartyCertification, 3rdPartyDependencies, Upstream, Welcome
Affects Versions: 5.0.0.M5
Reporter: Nick Boldt
Assignee: Denis Golovin
Priority: Blocker
Fix For: 5.0.0.Beta3
Attachments: install-all-of-central-welcome-screen-breaks.png,
jbds-1983-workaround.patch
We're currently patching SpringIDE's broken plugin (JBDS-1838) which contributes
a new Welcome screen, leading to this issue if unpatched:
!https://issues.jboss.org/secure/attachment/12346976/2011-09-09-105303.png!
However, it's been revealed that in addition to Spring, PMD, FindBugs, and now JRebel
also have this failing.
!https://issues.jboss.org/secure/attachment/12349923/2011-12-15_0052.png!
Therefore we ought to find a new way to suppress the effect across all of JBT/JBDS
instead of per-plugin, or get it fixed upstream.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:20 a.m.
New subject: [JBoss JIRA] (JBDS-1983) Handle issues concerning multiple welcome screens in Eclipse product
[
https://issues.jboss.org/browse/JBDS-1983?page=com.atlassian.jira.plugin....
]
Victor Rubezhny updated JBDS-1983:
----------------------------------
Steps to Reproduce:
EXECUTE: Install JBDS 5.0.0.beta3
EXECUTE: Install Spring IDE Core (not patched, from http://springide.org/updatesite update
site) into JBDS.
Note: Do not install Spring IDE Core from Central because this version is patched and
doesn't contains an old Welcome Page.
EXECUTE: Restart JBDS after the installation of Spring IDE Core.
EXECUTE: Close the Welcome Screen (in case it is opened)
EXECUTE: Open the Welcome Screen by selecting Help->Welcome menu item.
ASSERT: See the JBDS Welcome Screen appeared
FAIL (was in JBDS 5.0.0.beta2): WelcomePageEditor Dialog appears instead of JBDS Welcome
Screen.
Steps to reproduce field is updated.
Handle issues concerning multiple welcome screens in Eclipse product
--------------------------------------------------------------------
Key: JBDS-1983
URL: https://issues.jboss.org/browse/JBDS-1983
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: 3rdPartyCertification, 3rdPartyDependencies, Upstream, Welcome
Affects Versions: 5.0.0.M5
Reporter: Nick Boldt
Assignee: Denis Golovin
Priority: Blocker
Fix For: 5.0.0.Beta3
Attachments: install-all-of-central-welcome-screen-breaks.png,
jbds-1983-workaround.patch
We're currently patching SpringIDE's broken plugin (JBDS-1838) which contributes
a new Welcome screen, leading to this issue if unpatched:
!https://issues.jboss.org/secure/attachment/12346976/2011-09-09-105303.png!
However, it's been revealed that in addition to Spring, PMD, FindBugs, and now JRebel
also have this failing.
!https://issues.jboss.org/secure/attachment/12349923/2011-12-15_0052.png!
Therefore we ought to find a new way to suppress the effect across all of JBT/JBDS
instead of per-plugin, or get it fixed upstream.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:56 p.m.
New subject: [JBoss JIRA] (JBDS-1983) Handle issues concerning multiple welcome screens in Eclipse product
[
https://issues.jboss.org/browse/JBDS-1983?page=com.atlassian.jira.plugin....
]
Denis Golovin resolved JBDS-1983.
---------------------------------
Resolution: Done
verified on jbdevstudio-product-universal-5.0.0.v201204301418M-H119-Beta3.jar
Handle issues concerning multiple welcome screens in Eclipse product
--------------------------------------------------------------------
Key: JBDS-1983
URL: https://issues.jboss.org/browse/JBDS-1983
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: 3rdPartyCertification, 3rdPartyDependencies, Upstream, Welcome
Affects Versions: 5.0.0.M5
Reporter: Nick Boldt
Assignee: Denis Golovin
Priority: Blocker
Fix For: 5.0.0.Beta3
Attachments: install-all-of-central-welcome-screen-breaks.png,
jbds-1983-workaround.patch
We're currently patching SpringIDE's broken plugin (JBDS-1838) which contributes
a new Welcome screen, leading to this issue if unpatched:
!https://issues.jboss.org/secure/attachment/12346976/2011-09-09-105303.png!
However, it's been revealed that in addition to Spring, PMD, FindBugs, and now JRebel
also have this failing.
!https://issues.jboss.org/secure/attachment/12349923/2011-12-15_0052.png!
Therefore we ought to find a new way to suppress the effect across all of JBT/JBDS
instead of per-plugin, or get it fixed upstream.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:40 a.m.
New subject: [JBoss JIRA] (JBDS-1983) Handle issues concerning multiple welcome screens in Eclipse product
[
https://issues.jboss.org/browse/JBDS-1983?page=com.atlassian.jira.plugin....
]
Vlado Pakan closed JBDS-1983.
-----------------------------
Verified with jbdevstudio-product-linux-gtk-5.0.0.v201204301418M-H119-Beta3.
Handle issues concerning multiple welcome screens in Eclipse product
--------------------------------------------------------------------
Key: JBDS-1983
URL: https://issues.jboss.org/browse/JBDS-1983
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: 3rdPartyCertification, 3rdPartyDependencies, Upstream, Welcome
Affects Versions: 5.0.0.M5
Reporter: Nick Boldt
Assignee: Denis Golovin
Priority: Blocker
Fix For: 5.0.0.Beta3
Attachments: install-all-of-central-welcome-screen-breaks.png,
jbds-1983-workaround.patch
We're currently patching SpringIDE's broken plugin (JBDS-1838) which contributes
a new Welcome screen, leading to this issue if unpatched:
!https://issues.jboss.org/secure/attachment/12346976/2011-09-09-105303.png!
However, it's been revealed that in addition to Spring, PMD, FindBugs, and now JRebel
also have this failing.
!https://issues.jboss.org/secure/attachment/12349923/2011-12-15_0052.png!
Therefore we ought to find a new way to suppress the effect across all of JBT/JBDS
instead of per-plugin, or get it fixed upstream.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
5083
days inactive
5218
days old
jbosstools-issues@lists.jboss.org
39 comments
9 participants
participants (9)
-
Denis Golovin (JIRA) -
mark yarborough (JIRA)
-
Max Rydahl Andersen (JIRA)
-
Nick Boldt (Created) (JIRA)
-
Nick Boldt (JIRA)
-
Nick Boldt (Updated) (JIRA)
-
Snjezana Peco (JIRA)
-
Victor Rubezhny (JIRA)
-
Vlado Pakan (JIRA)