[JBoss JIRA] (JBIDE-23380) MOJO that fails or logs errors for build if manifest in .core plugin has .ui dependency
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23380?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-23380 at 10/20/16 1:40 PM:
--------------------------------------------------------------
Create 7 issues for central, common, cdi, visual-page-editor-core, hibernate, webservices, server with:
{code}
# create console log summary files
# run in a given jbosstools-* git checkout folder
p=$(pwd); p=${p##*/}; mvn clean install -DskipTests | \
tee ~/Screenshots/${p}-log.txt && cat ~/Screenshots/${p}-log.txt | \
egrep -B1 "\[CoreUIDependency\]| > " | grep -v "failed" | \
tee ~/Screenshots/${p}-log-coreui.txt
# rename console log files to match JIRA component names (as required, eg., for vpe => visual-page-editor-core, javaee => cdi, base => common)
# create JIRAs
for c in central common cdi visual-page-editor-core \
hibernate webservices server; do \
file="$(cat ~/Screenshots/coreui/jbosstools-$\{c}-log-coreui.txt)"; \
python createTaskJIRAs.py -u USER -p PWD -s https://issues.stage.jboss.org \
-i 4.4.2.AM3 -d 10.2.0.AM3 \
-t "UI dependencies from Core plugins" \
-f "The following core plugins depend on UI plugins directly or indirectly. \{code\}$\{file\}\{code\}" \
-c $\{c} -A; \
done
{code}
was (Author: nickboldt):
Create 7 issues for central, common, cdi, visual-page-editor-core, hibernate, webservices, server with:
{code}
# create console log summary files
# run in a given jbosstools-* git checkout folder
p=$(pwd); p=${p##*/}; mvn clean install -DskipTests | \
tee ~/Screenshots/${p}-log.txt && cat ~/Screenshots/${p}-log.txt | \
egrep -B1 "\[CoreUIDependency\]| > " | grep -v "failed" | \
tee ~/Screenshots/${p}-log-coreui.txt
# rename console log files to match JIRA component names (as required, eg., for vpe => visual-page-editor-core
# create JIRAs
for c in central common cdi visual-page-editor-core \
hibernate webservices server; do \
file="$(cat ~/Screenshots/coreui/jbosstools-$\{c}-log-coreui.txt)"; \
python createTaskJIRAs.py -u USER -p PWD -s https://issues.stage.jboss.org \
-i 4.4.2.AM3 -d 10.2.0.AM3 \
-t "UI dependencies from Core plugins" \
-f "The following core plugins depend on UI plugins directly or indirectly. \{code\}$\{file\}\{code\}" \
-c $\{c} -A; \
done
{code}
> MOJO that fails or logs errors for build if manifest in .core plugin has .ui dependency
> ---------------------------------------------------------------------------------------
>
> Key: JBIDE-23380
> URL: https://issues.jboss.org/browse/JBIDE-23380
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: build
> Reporter: Rob Stryker
> Assignee: Rob Stryker
> Fix For: 4.4.2.AM3
>
>
> At a minimum, the mojo should:
> foreach plugin, if plugin ends in .core, check plugin/META-INF/MANIFEST for Dependencies manifest header, and verify .ui is not included in the dependencies at all.
> However, this minimum goal would not have solved the issue we are experiencing with foundation.checkup. The foundation.checkup plugin does not end in .core and so would be skipped by this simple algorithm.
> So... we may wish to check transitive dependencies *only in the same repo*. For example, foundation.core depends on foundation.checker, and foundation.checker is in the same repo, so foundation.checker should also be checked for ui deps or fail.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 5 months
[JBoss JIRA] (JBIDE-23380) MOJO that fails or logs errors for build if manifest in .core plugin has .ui dependency
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23380?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-23380:
------------------------------------
Create 7 issues for central, common, cdi, visual-page-editor-core, hibernate, webservices, server with:
{code}
# create console log summary files
# run in a given jbosstools-* git checkout folder
p=$(pwd); p=${p##*/}; mvn clean install -DskipTests | tee ~/Screenshots/${p}-log.txt && cat ~/Screenshots/${p}-log.txt | egrep -B1 "\[CoreUIDependency\]| > " | grep -v "failed" | tee ~/Screenshots/${p}-log-coreui.txt
# rename console log files to match JIRA component names (as required, eg., for vpe => visual-page-editor-core
# create JIRAs
for c in central common cdi visual-page-editor-core \
hibernate webservices server; do \
file="$(cat ~/Screenshots/coreui/jbosstools-$\{c}-log-coreui.txt)"; \
python createTaskJIRAs.py -u USER -p PWD -s https://issues.stage.jboss.org \
-i 4.4.2.AM3 -d 10.2.0.AM3 \
-t "UI dependencies from Core plugins" \
-f "The following core plugins depend on UI plugins directly or indirectly. \{code\}$\{file\}\{code\}" \
-c $\{c} -A; \
done
{code}
> MOJO that fails or logs errors for build if manifest in .core plugin has .ui dependency
> ---------------------------------------------------------------------------------------
>
> Key: JBIDE-23380
> URL: https://issues.jboss.org/browse/JBIDE-23380
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: build
> Reporter: Rob Stryker
> Assignee: Rob Stryker
> Fix For: 4.4.2.AM3
>
>
> At a minimum, the mojo should:
> foreach plugin, if plugin ends in .core, check plugin/META-INF/MANIFEST for Dependencies manifest header, and verify .ui is not included in the dependencies at all.
> However, this minimum goal would not have solved the issue we are experiencing with foundation.checkup. The foundation.checkup plugin does not end in .core and so would be skipped by this simple algorithm.
> So... we may wish to check transitive dependencies *only in the same repo*. For example, foundation.core depends on foundation.checker, and foundation.checker is in the same repo, so foundation.checker should also be checked for ui deps or fail.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 5 months
[JBoss JIRA] (JBIDE-23397) For JBIDE 4.4.2.AM3: UI dependencies from Core plugins [server]
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-23397:
----------------------------------
Summary: For JBIDE 4.4.2.AM3: UI dependencies from Core plugins [server]
Key: JBIDE-23397
URL: https://issues.jboss.org/browse/JBIDE-23397
Project: Tools (JBoss Tools)
Issue Type: Task
Components: server
Reporter: Nick Boldt
Priority: Blocker
Fix For: 4.4.2.AM3
For JBIDE 4.4.2.AM3 [server]: The following core plugins depend on UI plugins directly or indirectly. {code}[CoreUIDependency] org.jboss.ide.eclipse.as.classpath.core is a Core plugin, but depends on these UI plugins directly or transitively:
> org.eclipse.ui
> org.eclipse.ui.navigator
> org.eclipse.wst.server.ui
> org.eclipse.ui.ide
> org.eclipse.wst.common.modulecore.ui
> org.jboss.ide.eclipse.archives.ui
> org.jboss.ide.eclipse.as.ui
--
[CoreUIDependency] org.jboss.ide.eclipse.as.rse.core is a Core plugin, but depends on these UI plugins directly or transitively:
> org.eclipse.ui
> org.eclipse.ui.navigator
> org.eclipse.wst.server.ui
> org.eclipse.ui.ide
> org.eclipse.wst.common.modulecore.ui
> org.jboss.ide.eclipse.archives.ui
> org.jboss.ide.eclipse.as.ui
--
[CoreUIDependency] org.jboss.tools.as.test.core is a Core plugin, but depends on these UI plugins directly or transitively:
> org.eclipse.rse.ui
> org.eclipse.jdt.ui
> org.jboss.ide.eclipse.as.rse.ui
> org.eclipse.wst.server.ui
> org.eclipse.wst.xml.ui.infopop
> org.eclipse.wst.web.ui
> org.jboss.tools.jmx.jvmmonitor.ui
> org.eclipse.wst.common.project.facet.ui
> org.eclipse.wst.common.modulecore.ui
> org.eclipse.jdt.debug.ui
> org.eclipse.ui.browser
> org.eclipse.ui.views
> org.jboss.ide.eclipse.as.ui.mbeans
> org.eclipse.jst.j2ee.ui
> org.eclipse.wst.xml.ui
> org.jboss.ide.eclipse.as.wtp.ui
> org.eclipse.ui.editors
> org.jboss.tools.foundation.ui
> org.eclipse.rse.files.ui
> org.eclipse.jst.server.ui
> org.eclipse.jst.common.project.facet.ui
> org.jboss.ide.eclipse.archives.ui
> org.eclipse.ui.ide
> org.jboss.ide.eclipse.as.ui
> org.jboss.tools.runtime.ui
> org.eclipse.ui.views.log
> org.jboss.ide.eclipse.as.classpath.ui
> org.eclipse.ui.workbench.texteditor
> org.eclipse.ui
> org.eclipse.ui.navigator
> org.eclipse.ui.console
> org.eclipse.wst.sse.ui
> org.eclipse.debug.ui
> org.eclipse.wst.common.frameworks.ui
> org.jboss.tools.jmx.ui
> org.eclipse.ui.views.properties.tabbed
> org.eclipse.ui.forms{code}
[Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for server task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 5 months
[JBoss JIRA] (JBIDE-23396) For JBIDE 4.4.2.AM3: UI dependencies from Core plugins [webservices]
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-23396:
----------------------------------
Summary: For JBIDE 4.4.2.AM3: UI dependencies from Core plugins [webservices]
Key: JBIDE-23396
URL: https://issues.jboss.org/browse/JBIDE-23396
Project: Tools (JBoss Tools)
Issue Type: Task
Components: webservices
Reporter: Nick Boldt
Priority: Blocker
Fix For: 4.4.2.AM3
For JBIDE 4.4.2.AM3 [webservices]: The following core plugins depend on UI plugins directly or indirectly. {code}[CoreUIDependency] org.jboss.tools.ws.core is a Core plugin, but depends on these UI plugins directly or transitively:
> org.eclipse.ui
> org.eclipse.jst.jsf.ui
> org.eclipse.jst.ws.consumption.ui
--
[CoreUIDependency] org.jboss.tools.ws.creation.core is a Core plugin, but depends on these UI plugins directly or transitively:
> org.eclipse.ui
> org.eclipse.jdt.ui
> org.eclipse.jst.jsf.ui
> org.eclipse.jst.ws.consumption.ui
--
[CoreUIDependency] org.jboss.tools.ws.jaxrs.core is a Core plugin, but depends on these UI plugins directly or transitively:
> org.eclipse.wst.common.frameworks.ui
--
[CoreUIDependency] org.jboss.tools.websockets.core is a Core plugin, but depends on these UI plugins directly or transitively:
> org.eclipse.ui{code}
[Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for webservices task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 5 months
[JBoss JIRA] (JBIDE-23392) For JBIDE 4.4.2.AM3: UI dependencies from Core plugins [common]
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-23392:
----------------------------------
Summary: For JBIDE 4.4.2.AM3: UI dependencies from Core plugins [common]
Key: JBIDE-23392
URL: https://issues.jboss.org/browse/JBIDE-23392
Project: Tools (JBoss Tools)
Issue Type: Task
Components: common
Reporter: Nick Boldt
Priority: Blocker
Fix For: 4.4.2.AM3
For JBIDE 4.4.2.AM3 [common]: The following core plugins depend on UI plugins directly or indirectly. {code}[CoreUIDependency] org.jboss.tools.foundation.core is a Core plugin, but depends on these UI plugins directly or transitively:
> org.eclipse.ui.workbench
> org.eclipse.ui.views.log
--
[CoreUIDependency] org.jboss.tools.common.core is a Core plugin, but depends on these UI plugins directly or transitively:
> org.eclipse.ui.workbench
> org.eclipse.ui.views.log
--
[CoreUIDependency] org.jboss.tools.common.resref.core is a Core plugin, but depends on these UI plugins directly or transitively:
> org.eclipse.ui
> org.eclipse.jdt.ui
> org.eclipse.wst.sse.ui
> org.eclipse.ui.workbench
> org.eclipse.ui.ide
> org.eclipse.ui.views.log
> org.eclipse.ui.workbench.texteditor
> org.eclipse.wst.xml.ui
--
[CoreUIDependency] org.jboss.tools.common.el.core is a Core plugin, but depends on these UI plugins directly or transitively:
> org.eclipse.ui
> org.eclipse.wst.sse.ui
> org.eclipse.jdt.ui
> org.eclipse.ui.workbench
> org.eclipse.ui.ide
> org.eclipse.ui.views.log
> org.eclipse.ui.workbench.texteditor
> org.eclipse.wst.xml.ui
--
[CoreUIDependency] org.jboss.tools.stacks.core is a Core plugin, but depends on these UI plugins directly or transitively:
> org.eclipse.ui.workbench
> org.eclipse.ui.views.log
--
[CoreUIDependency] org.jboss.tools.runtime.core is a Core plugin, but depends on these UI plugins directly or transitively:
> org.eclipse.ui.workbench
> org.eclipse.ui.views.log{code}
[Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for common task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 5 months
[JBoss JIRA] (JBIDE-23391) For JBIDE 4.4.2.AM3: UI dependencies from Core plugins [central]
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-23391:
----------------------------------
Summary: For JBIDE 4.4.2.AM3: UI dependencies from Core plugins [central]
Key: JBIDE-23391
URL: https://issues.jboss.org/browse/JBIDE-23391
Project: Tools (JBoss Tools)
Issue Type: Task
Components: central
Reporter: Nick Boldt
Priority: Blocker
Fix For: 4.4.2.AM3
For JBIDE 4.4.2.AM3 [central]: The following core plugins depend on UI plugins directly or indirectly. {code}[CoreUIDependency] org.jboss.tools.discovery.core is a Core plugin, but depends on these UI plugins directly or transitively:
> org.eclipse.ui.workbench
> org.eclipse.equinox.p2.ui
> org.eclipse.mylyn.discovery.ui
--
[CoreUIDependency] org.jboss.tools.maven.core is a Core plugin, but depends on these UI plugins directly or transitively:
> org.eclipse.jdt.ui
> org.eclipse.ui.workbench
> org.eclipse.m2e.core.ui
--
[CoreUIDependency] org.jboss.tools.maven.sourcelookup.core is a Core plugin, but depends on these UI plugins directly or transitively:
> org.eclipse.ui
> org.eclipse.jdt.ui
> org.eclipse.ui.workbench
> org.eclipse.m2e.core.ui{code}
[Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for central task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 5 months
[JBoss JIRA] (JBIDE-23393) For JBIDE 4.4.2.AM3: UI dependencies from Core plugins [cdi]
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-23393:
----------------------------------
Summary: For JBIDE 4.4.2.AM3: UI dependencies from Core plugins [cdi]
Key: JBIDE-23393
URL: https://issues.jboss.org/browse/JBIDE-23393
Project: Tools (JBoss Tools)
Issue Type: Task
Components: cdi
Reporter: Nick Boldt
Priority: Blocker
Fix For: 4.4.2.AM3
For JBIDE 4.4.2.AM3 [cdi]: The following core plugins depend on UI plugins directly or indirectly. {code}[CoreUIDependency] org.jboss.tools.batch.core is a Core plugin, but depends on these UI plugins directly or transitively:
> org.eclipse.jdt.ui
> org.eclipse.sapphire.ui.swt.gef
> org.eclipse.ui.ide
> org.eclipse.ui.workbench.texteditor
> org.eclipse.sapphire.workspace.ui
> org.eclipse.wst.common.ui
> org.eclipse.sapphire.ui.swt.xml.editor
> org.eclipse.ui
> org.eclipse.wst.sse.ui
> org.eclipse.sapphire.ui
> org.eclipse.wst.common.frameworks.ui
> org.eclipse.ui.views
> org.eclipse.ui.forms
> org.eclipse.wst.xml.ui
--
[CoreUIDependency] org.jboss.tools.batch.core.itest is a Core plugin, but depends on these UI plugins directly or transitively:
> org.eclipse.jst.servlet.ui
> org.eclipse.jdt.ui
> org.eclipse.sapphire.ui.swt.gef
> org.jboss.tools.jst.web.ui
> org.jboss.tools.foundation.ui
> org.eclipse.ui.ide
> org.jboss.tools.common.ui
> org.eclipse.ui.workbench.texteditor
> org.eclipse.sapphire.workspace.ui
> org.eclipse.sapphire.ui.swt.xml.editor
> org.eclipse.wst.common.ui
> org.jboss.tools.batch.ui
> org.eclipse.ui
> org.eclipse.wst.sse.ui
> org.eclipse.sapphire.ui
> org.eclipse.wst.web.ui
> org.eclipse.ltk.ui.refactoring
> org.eclipse.wst.common.project.facet.ui
> org.eclipse.wst.common.frameworks.ui
> org.eclipse.ui.views
> org.eclipse.ui.forms
> org.eclipse.wst.xml.ui
--
[CoreUIDependency] org.jboss.tools.cdi.core is a Core plugin, but depends on these UI plugins directly or transitively:
> org.eclipse.ui
> org.jboss.tools.common.model.ui
> org.eclipse.jdt.ui
> org.eclipse.ui.editors
> org.eclipse.ui.ide
> org.eclipse.ltk.ui.refactoring
> org.eclipse.ui.views
> org.jboss.tools.common.ui
> org.eclipse.ui.workbench.texteditor
--
[CoreUIDependency] org.jboss.tools.cdi.extension.core is a Core plugin, but depends on these UI plugins directly or transitively:
> org.eclipse.ui
> org.jboss.tools.common.model.ui
> org.eclipse.jdt.ui
> org.eclipse.ui.editors
> org.eclipse.ui.ide
> org.eclipse.ltk.ui.refactoring
> org.eclipse.ui.views
> org.jboss.tools.common.ui
> org.eclipse.ui.workbench.texteditor
--
[CoreUIDependency] org.jboss.tools.cdi.deltaspike.core is a Core plugin, but depends on these UI plugins directly or transitively:
> org.eclipse.jst.servlet.ui
> org.eclipse.jdt.ui
> org.eclipse.ui.editors
> org.jboss.tools.jst.web.ui
> org.eclipse.ui.ide
> org.jboss.tools.cdi.ui
> org.jboss.tools.common.ui
> org.eclipse.ui.workbench.texteditor
> org.eclipse.ui
> org.jboss.tools.common.model.ui
> org.eclipse.ui.navigator
> org.eclipse.wst.sse.ui
> org.eclipse.ui.navigator.resources
> org.eclipse.wst.web.ui
> org.eclipse.ltk.ui.refactoring
> org.eclipse.wst.common.project.facet.ui
> org.eclipse.debug.ui
> org.eclipse.jst.jsf.ui
> org.eclipse.wst.common.frameworks.ui
> org.eclipse.ui.views
> org.jboss.tools.common.el.ui
> org.eclipse.jst.j2ee.ui
> org.eclipse.wst.xml.ui
--
[CoreUIDependency] org.jboss.tools.cdi.seam.core is a Core plugin, but depends on these UI plugins directly or transitively:
> org.eclipse.ui
> org.jboss.tools.common.model.ui
> org.eclipse.jdt.ui
> org.eclipse.ui.editors
> org.eclipse.ui.ide
> org.eclipse.ltk.ui.refactoring
> org.eclipse.ui.views
> org.jboss.tools.common.ui
> org.eclipse.ui.workbench.texteditor
--
[CoreUIDependency] org.jboss.tools.cdi.seam.solder.core is a Core plugin, but depends on these UI plugins directly or transitively:
> org.eclipse.ui
> org.jboss.tools.common.model.ui
> org.eclipse.jdt.ui
> org.eclipse.ui.editors
> org.eclipse.ui.ide
> org.eclipse.ltk.ui.refactoring
> org.eclipse.ui.views
> org.jboss.tools.common.ui
> org.eclipse.ui.workbench.texteditor
--
[CoreUIDependency] org.jboss.tools.cdi.seam.config.core is a Core plugin, but depends on these UI plugins directly or transitively:
> org.eclipse.ui
> org.jboss.tools.common.model.ui
> org.eclipse.jdt.ui
> org.eclipse.ui.editors
> org.eclipse.ui.ide
> org.eclipse.ltk.ui.refactoring
> org.eclipse.ui.views
> org.jboss.tools.common.ui
> org.eclipse.ui.workbench.texteditor
--
[CoreUIDependency] org.jboss.tools.cdi.seam.faces.core is a Core plugin, but depends on these UI plugins directly or transitively:
> org.eclipse.ui
> org.jboss.tools.common.model.ui
> org.eclipse.jdt.ui
> org.eclipse.ui.editors
> org.eclipse.ui.ide
> org.eclipse.ltk.ui.refactoring
> org.eclipse.ui.views
> org.jboss.tools.common.ui
> org.eclipse.ui.workbench.texteditor
--
[CoreUIDependency] org.jboss.tools.seam.core is a Core plugin, but depends on these UI plugins directly or transitively:
> org.eclipse.jdt.ui
> org.jboss.tools.jst.web.ui
> org.eclipse.ui.editors
> org.eclipse.ui.ide
> org.eclipse.jst.jsp.ui
> org.jboss.tools.common.ui
> org.eclipse.ui.workbench.texteditor
> org.eclipse.datatools.connectivity.ui.dse
> org.eclipse.ui
> org.eclipse.wst.sse.ui
> org.eclipse.jst.jsf.ui
> org.eclipse.ltk.ui.refactoring
> org.eclipse.wst.common.frameworks.ui
> org.eclipse.ui.views{code}
[Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for cdi task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 5 months
[JBoss JIRA] (ERT-438) Nullpointer in JavaScript Development Tools Chromium/V8 Remote Debugger: BreakpointAdapterFactory [EBZ#496914]
by Friendly Jira Robot (JIRA)
Friendly Jira Robot created ERT-438:
---------------------------------------
Summary: Nullpointer in JavaScript Development Tools Chromium/V8 Remote Debugger: BreakpointAdapterFactory [EBZ#496914]
Key: ERT-438
URL: https://issues.jboss.org/browse/ERT-438
Project: Eclipse Release Train
Issue Type: Task
Components: JSDT
Reporter: Friendly Jira Robot
Fix For: Oxygen (4.7)
Fresh installation of Eclipse Neon for Java EE Developers (contains the plugin 'JavaScript Development Tools Chromium/V8 Remote Debugger').
Installed ResourceBundle Editor V1.0.5 via Eclipse marketplace.
A Nullpointer occurs when opening any ResourceBundle file with ResourceBundle Editor. Stacktrace see end of post. After deinstalling the Chromium Debugger plugin, the nullpointer is not reproducable anymore and ResourceBundle Editor is working again.
NPE probably caused by empty editorinput?
IResource resource = (IResource) editorPart.getEditorInput().getAdapter(IResource.class);
java.lang.NullPointerException
at org.eclipse.wst.jsdt.chromium.debug.core.model.BreakpointAdapterFactory.getAdapter(BreakpointAdapterFactory.java:25)
at org.eclipse.core.internal.adapter.AdapterFactoryProxy.getAdapter(AdapterFactoryProxy.java:82)
at org.eclipse.core.internal.runtime.AdapterManager.getAdapter(AdapterManager.java:294)
at org.eclipse.ui.part.WorkbenchPart.getAdapter(WorkbenchPart.java:143)
at org.eclipse.ui.texteditor.AbstractTextEditor.getAdapter(AbstractTextEditor.java:6185)
at com.essiembre.eclipse.rbe.ui.editor.i18n.I18nPageEditor.getAdapter(I18nPageEditor.java:90)
at org.eclipse.core.runtime.Adapters.adapt(Adapters.java:59)
at org.eclipse.core.runtime.Adapters.adapt(Adapters.java:100)
at org.eclipse.ui.part.MultiPageEditorPart.getAdapter(MultiPageEditorPart.java:1199)
at com.essiembre.eclipse.rbe.ui.editor.ResourceBundleEditor.getAdapter(ResourceBundleEditor.java:208)
at org.eclipse.debug.internal.ui.actions.ToggleBreakpointsTargetManager$ToggleBreakpointsTargetAdapterFactory.canGetToggleBreakpointsTarget(ToggleBreakpointsTargetManager.java:318)
at org.eclipse.debug.internal.ui.actions.ToggleBreakpointsTargetManager$ToggleBreakpointsTargetAdapterFactory.isEnabled(ToggleBreakpointsTargetManager.java:361)
at org.eclipse.debug.internal.ui.actions.ToggleBreakpointsTargetManager.getEnabledFactories(ToggleBreakpointsTargetManager.java:502)
at org.eclipse.debug.internal.ui.actions.ToggleBreakpointsTargetManager.getPreferredToggleBreakpointsTargetID(ToggleBreakpointsTargetManager.java:542)
at org.eclipse.debug.internal.ui.actions.ToggleBreakpointsTargetManager.getToggleBreakpointsTarget(ToggleBreakpointsTargetManager.java:549)
at org.eclipse.debug.internal.ui.actions.breakpoints.RetargetBreakpointAction.getAdapter(RetargetBreakpointAction.java:49)
at org.eclipse.debug.internal.ui.actions.RetargetAction.partActivated(RetargetAction.java:169)
at org.eclipse.ui.internal.PartService$1.run(PartService.java:84)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.ui.internal.PartService.partActivated(PartService.java:81)
at org.eclipse.ui.internal.WorkbenchWindow$WWinPartService.partActivated(WorkbenchWindow.java:3002)
at org.eclipse.ui.internal.WorkbenchPage$14.run(WorkbenchPage.java:4977)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.ui.internal.WorkbenchPage.firePartActivated(WorkbenchPage.java:4974)
at org.eclipse.ui.internal.WorkbenchPage.access$19(WorkbenchPage.java:4962)
at org.eclipse.ui.internal.WorkbenchPage$E4PartListener.partActivated(WorkbenchPage.java:210)
at org.eclipse.e4.ui.internal.workbench.PartServiceImpl$3.run(PartServiceImpl.java:250)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.firePartActivated(PartServiceImpl.java:247)
at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.activate(PartServiceImpl.java:757)
at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.activate(PartServiceImpl.java:682)
at org.eclipse.e4.ui.internal.workbench.swt.AbstractPartRenderer.activate(AbstractPartRenderer.java:95)
at org.eclipse.e4.ui.workbench.renderers.swt.StackRenderer$4.handleEvent(StackRenderer.java:1077)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Display.sendEvent(Display.java:5219)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1340)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1366)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1349)
at org.eclipse.swt.widgets.Shell.setActiveControl(Shell.java:1817)
at org.eclipse.swt.widgets.Control.gtk_button_press_event(Control.java:3215)
at org.eclipse.swt.widgets.Control.gtk_button_press_event(Control.java:3151)
at org.eclipse.swt.widgets.Composite.gtk_button_press_event(Composite.java:750)
at org.eclipse.swt.widgets.Widget.windowProc(Widget.java:1979)
at org.eclipse.swt.widgets.Control.windowProc(Control.java:5819)
at org.eclipse.swt.widgets.Display.windowProc(Display.java:5490)
at org.eclipse.swt.internal.gtk.OS._gtk_main_do_event(Native Method)
at org.eclipse.swt.internal.gtk.OS.gtk_main_do_event(OS.java:9545)
at org.eclipse.swt.widgets.Display.eventProc(Display.java:1275)
at org.eclipse.swt.internal.gtk.OS._g_main_context_iteration(Native Method)
at org.eclipse.swt.internal.gtk.OS.g_main_context_iteration(OS.java:2495)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:4141)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1121)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1022)
at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:150)
at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:687)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:604)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:148)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:138)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:388)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:243)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:673)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:610)
at org.eclipse.equinox.launcher.Main.run(Main.java:1519)
at org.eclipse.equinox.launcher.Main.main(Main.java:1492)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 5 months