[JBoss JIRA] (JBIDE-20219) Arquillian Cruiser: NPE when trying to display Deployment
by Lucia Jelinkova (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20219?page=com.atlassian.jira.plugi... ]
Lucia Jelinkova closed JBIDE-20219.
-----------------------------------
Verified that NPE is fixed in nightly build.
> Arquillian Cruiser: NPE when trying to display Deployment
> ---------------------------------------------------------
>
> Key: JBIDE-20219
> URL: https://issues.jboss.org/browse/JBIDE-20219
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: arquillian
> Affects Versions: 4.3.0.Beta1
> Reporter: Aslak Knutsen
> Assignee: Snjezana Peco
> Fix For: 4.3.0.Beta2
>
>
> Getting the following error when trying to view NodeTest class in Cruiser:
> https://github.com/arquillian/arquillian-cube/blob/master/containerless/s...
> {code}
> eclipse.buildId=4.5.0.I20150603-2000
> java.version=1.8.0_45
> java.vendor=Oracle Corporation
> BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
> Command-line arguments: -data file:/home/aslak/workspace/arq_mars/ -os linux -ws gtk -arch x86_64
> org.eclipse.e4.ui.workbench
> Error
> Thu Jul 09 02:52:57 CEST 2015
> java.lang.NullPointerException
> at org.jboss.tools.arquillian.ui.internal.utils.ArquillianUIUtil.getSelectedProject(ArquillianUIUtil.java:1087)
> at org.jboss.tools.arquillian.ui.internal.views.ArquillianView$1.selectionChanged(ArquillianView.java:90)
> at org.eclipse.ui.internal.e4.compatibility.SelectionService.notifyListeners(SelectionService.java:237)
> at org.eclipse.ui.internal.e4.compatibility.SelectionService.handleSelectionChanged(SelectionService.java:107)
> at org.eclipse.ui.internal.e4.compatibility.SelectionService.access$0(SelectionService.java:91)
> at org.eclipse.ui.internal.e4.compatibility.SelectionService$1.selectionChanged(SelectionService.java:66)
> at org.eclipse.e4.ui.internal.workbench.SelectionAggregator$2.run(SelectionAggregator.java:126)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.e4.ui.internal.workbench.SelectionAggregator.notifyListeners(SelectionAggregator.java:123)
> at org.eclipse.e4.ui.internal.workbench.SelectionAggregator.access$6(SelectionAggregator.java:120)
> at org.eclipse.e4.ui.internal.workbench.SelectionAggregator$7$1.run(SelectionAggregator.java:233)
> at org.eclipse.e4.core.contexts.RunAndTrack.runExternalCode(RunAndTrack.java:56)
> at org.eclipse.e4.ui.internal.workbench.SelectionAggregator$7.changed(SelectionAggregator.java:230)
> at org.eclipse.e4.core.internal.contexts.TrackableComputationExt.update(TrackableComputationExt.java:114)
> at org.eclipse.e4.core.internal.contexts.EclipseContext.processScheduled(EclipseContext.java:341)
> at org.eclipse.e4.core.internal.contexts.EclipseContext.set(EclipseContext.java:356)
> at org.eclipse.e4.ui.internal.workbench.SelectionServiceImpl.setSelection(SelectionServiceImpl.java:31)
> at org.eclipse.ui.internal.e4.compatibility.CompatibilityPart.selectionChanged(CompatibilityPart.java:441)
> at org.eclipse.jface.viewers.Viewer$2.run(Viewer.java:163)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:50)
> at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:173)
> at org.eclipse.jface.viewers.Viewer.fireSelectionChanged(Viewer.java:160)
> at org.eclipse.jface.viewers.StructuredViewer.updateSelection(StructuredViewer.java:2197)
> at org.eclipse.jface.viewers.StructuredViewer.handleSelect(StructuredViewer.java:1228)
> at org.eclipse.ui.navigator.CommonViewer.handleSelect(CommonViewer.java:461)
> at org.eclipse.jface.viewers.StructuredViewer$4.widgetSelected(StructuredViewer.java:1257)
> at org.eclipse.jface.util.OpenStrategy.fireSelectionEvent(OpenStrategy.java:242)
> at org.eclipse.jface.util.OpenStrategy.access$4(OpenStrategy.java:236)
> at org.eclipse.jface.util.OpenStrategy$1.handleEvent(OpenStrategy.java:408)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4481)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1327)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3819)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3430)
> at org.eclipse.jface.window.Window.runEventLoop(Window.java:827)
> at org.eclipse.jface.window.Window.open(Window.java:803)
> at org.eclipse.ui.internal.views.log.EventDetailsDialog.open(EventDetailsDialog.java:181)
> at org.eclipse.ui.internal.views.log.EventDetailsDialogAction.run(EventDetailsDialogAction.java:98)
> at org.eclipse.ui.internal.views.log.LogView$15.doubleClick(LogView.java:546)
> at org.eclipse.jface.viewers.StructuredViewer$1.run(StructuredViewer.java:832)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:50)
> at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:173)
> at org.eclipse.jface.viewers.StructuredViewer.fireDoubleClick(StructuredViewer.java:829)
> at org.eclipse.jface.viewers.AbstractTreeViewer.handleDoubleSelect(AbstractTreeViewer.java:1470)
> at org.eclipse.jface.viewers.StructuredViewer$4.widgetDefaultSelected(StructuredViewer.java:1263)
> at org.eclipse.jface.util.OpenStrategy.fireDefaultSelectionEvent(OpenStrategy.java:252)
> at org.eclipse.jface.util.OpenStrategy.access$0(OpenStrategy.java:249)
> at org.eclipse.jface.util.OpenStrategy$1.handleEvent(OpenStrategy.java:311)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4481)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1327)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3819)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3430)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1127)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1018)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:654)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:598)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:139)
> 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:380)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235)
> 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:497)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:669)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:608)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1515)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1488)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (JBIDE-20260) Incorporate newer CXF version menus than CXF 2.x
by Jan Richter (JIRA)
Jan Richter created JBIDE-20260:
-----------------------------------
Summary: Incorporate newer CXF version menus than CXF 2.x
Key: JBIDE-20260
URL: https://issues.jboss.org/browse/JBIDE-20260
Project: Tools (JBoss Tools)
Issue Type: Task
Components: webservices
Affects Versions: 4.3.0.Beta1
Reporter: Jan Richter
Priority: Minor
Since 4.3.0.Beta1 requires Java 8 and Java 8 is supported by CXF 3.x, it would be nice to have menu entries that don't look like they are specifically targeted at CXF 2.x.
So far I noticed them in the Web Service preferences and Web Service/Web Service Client wizards. It says CXF 2.x but it doesn't limit the version, so it would be just a job of renaming/providing new entries.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (JBIDE-19349) Fix ShrinkWrap Archive file location validation issues
by Lucia Jelinkova (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19349?page=com.atlassian.jira.plugi... ]
Lucia Jelinkova edited comment on JBIDE-19349 at 7/14/15 5:17 AM:
------------------------------------------------------------------
The validation still does not work for
{code}
war.addAsWebResource(EmptyAsset.INSTANCE, "persistence.xml");
{code}
I think there is bug in the ArquillianBuilder.class code where isAddAsManifestMethod is set to true instead of isAddAsWebResource.
{code}
if (node.getName() != null && ArquillianConstants.ADD_AS_WEB_RESOURCE.equals(node.getName().getIdentifier()) ) { //$NON-NLS-1$
List arguments = node.arguments();
if (arguments.size() == 2) {
Object o = arguments.get(1);
if (o instanceof StringLiteral) {
StringLiteral literal = (StringLiteral) o;
if (fileNames.contains(literal.getLiteralValue())) {
artifactFileName = literal;
isAddAsManifestMethod = true;
}
}
}
}
{code}
was (Author: ljelinko):
The validation still does not work for
{code}
war.addAsWebResource(EmptyAsset.INSTANCE, "persistence.xml");
{code}
I think there is bug in the code where isAddAsManifestMethod is set to true instead of isAddAsWebResource.
{code}
if (node.getName() != null && ArquillianConstants.ADD_AS_WEB_RESOURCE.equals(node.getName().getIdentifier()) ) { //$NON-NLS-1$
List arguments = node.arguments();
if (arguments.size() == 2) {
Object o = arguments.get(1);
if (o instanceof StringLiteral) {
StringLiteral literal = (StringLiteral) o;
if (fileNames.contains(literal.getLiteralValue())) {
artifactFileName = literal;
isAddAsManifestMethod = true;
}
}
}
}
{code}
> Fix ShrinkWrap Archive file location validation issues
> ------------------------------------------------------
>
> Key: JBIDE-19349
> URL: https://issues.jboss.org/browse/JBIDE-19349
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: arquillian
> Affects Versions: 4.3.0.Alpha1
> Reporter: Lucia Jelinkova
> Assignee: Snjezana Peco
> Fix For: 4.3.0.Beta2
>
>
> In JBIDE-14782, the validation was solved only partially. These issues still remain:
> - EAR - no validation for application.xml
> - WAR
> -- validation for beans.xml and web.xml going to WEB-INF
> --- addAsManifestResource - OK
> --- addAsWebResource - NOK
> -- validation for persistence.xml and ejb-jar.xml
> --- addAsWebInfResource - OK
> --- addAsWebResource - NOK
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (JBIDE-20257) Cannot create any new project via OpenShift Projects dialog
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20257?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-20257:
------------------------------------------
[~jcantrill] can you please look at this?
> Cannot create any new project via OpenShift Projects dialog
> -----------------------------------------------------------
>
> Key: JBIDE-20257
> URL: https://issues.jboss.org/browse/JBIDE-20257
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.0.Beta2
> Reporter: Marián Labuda
> Assignee: Jeff Cantrill
> Priority: Blocker
> Fix For: 4.3.0.Beta2
>
>
> In OpenShift Projects dialog opened via context menu of a v3 application, it is not possible to create a new project. There is a error that project is trying to be created in cluster scope. See full error description below:
> {code}
> Could not create project "project01dsa": User "demo" cannot create projects at the cluster scope
> com.openshift.restclient.authorization.ResourceForbiddenException: User "demo" cannot create projects at the cluster scope
> at com.openshift.internal.restclient.DefaultClient.createOpenShiftException(DefaultClient.java:393)
> at com.openshift.internal.restclient.DefaultClient.create(DefaultClient.java:185)
> at com.openshift.internal.restclient.DefaultClient.create(DefaultClient.java:169)
> at org.jboss.tools.openshift.core.connection.Connection.createResource(Connection.java:316)
> at org.jboss.tools.openshift.internal.ui.wizard.project.NewProjectWizardModel.createProject(NewProjectWizardModel.java:55)
> at org.jboss.tools.openshift.internal.ui.wizard.project.NewProjectWizard$1.doRun(NewProjectWizard.java:46)
> at org.jboss.tools.openshift.internal.common.core.job.AbstractDelegatingMonitorJob.run(AbstractDelegatingMonitorJob.java:36)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> {code}
> This is happening also on locally running OpenShift v3 and also on staging v3 server.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (JBIDE-20257) Cannot create any new project via OpenShift Projects dialog
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20257?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-20257:
-------------------------------------
Fix Version/s: 4.3.0.Beta2
> Cannot create any new project via OpenShift Projects dialog
> -----------------------------------------------------------
>
> Key: JBIDE-20257
> URL: https://issues.jboss.org/browse/JBIDE-20257
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.0.Beta2
> Reporter: Marián Labuda
> Assignee: Jeff Cantrill
> Priority: Blocker
> Fix For: 4.3.0.Beta2
>
>
> In OpenShift Projects dialog opened via context menu of a v3 application, it is not possible to create a new project. There is a error that project is trying to be created in cluster scope. See full error description below:
> {code}
> Could not create project "project01dsa": User "demo" cannot create projects at the cluster scope
> com.openshift.restclient.authorization.ResourceForbiddenException: User "demo" cannot create projects at the cluster scope
> at com.openshift.internal.restclient.DefaultClient.createOpenShiftException(DefaultClient.java:393)
> at com.openshift.internal.restclient.DefaultClient.create(DefaultClient.java:185)
> at com.openshift.internal.restclient.DefaultClient.create(DefaultClient.java:169)
> at org.jboss.tools.openshift.core.connection.Connection.createResource(Connection.java:316)
> at org.jboss.tools.openshift.internal.ui.wizard.project.NewProjectWizardModel.createProject(NewProjectWizardModel.java:55)
> at org.jboss.tools.openshift.internal.ui.wizard.project.NewProjectWizard$1.doRun(NewProjectWizard.java:46)
> at org.jboss.tools.openshift.internal.common.core.job.AbstractDelegatingMonitorJob.run(AbstractDelegatingMonitorJob.java:36)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> {code}
> This is happening also on locally running OpenShift v3 and also on staging v3 server.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (JBIDE-20257) Cannot create any new project via OpenShift Projects dialog
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20257?page=com.atlassian.jira.plugi... ]
Andre Dietisheim reassigned JBIDE-20257:
----------------------------------------
Assignee: Jeff Cantrill
> Cannot create any new project via OpenShift Projects dialog
> -----------------------------------------------------------
>
> Key: JBIDE-20257
> URL: https://issues.jboss.org/browse/JBIDE-20257
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.0.Beta2
> Reporter: Marián Labuda
> Assignee: Jeff Cantrill
> Priority: Blocker
>
> In OpenShift Projects dialog opened via context menu of a v3 application, it is not possible to create a new project. There is a error that project is trying to be created in cluster scope. See full error description below:
> {code}
> Could not create project "project01dsa": User "demo" cannot create projects at the cluster scope
> com.openshift.restclient.authorization.ResourceForbiddenException: User "demo" cannot create projects at the cluster scope
> at com.openshift.internal.restclient.DefaultClient.createOpenShiftException(DefaultClient.java:393)
> at com.openshift.internal.restclient.DefaultClient.create(DefaultClient.java:185)
> at com.openshift.internal.restclient.DefaultClient.create(DefaultClient.java:169)
> at org.jboss.tools.openshift.core.connection.Connection.createResource(Connection.java:316)
> at org.jboss.tools.openshift.internal.ui.wizard.project.NewProjectWizardModel.createProject(NewProjectWizardModel.java:55)
> at org.jboss.tools.openshift.internal.ui.wizard.project.NewProjectWizard$1.doRun(NewProjectWizard.java:46)
> at org.jboss.tools.openshift.internal.common.core.job.AbstractDelegatingMonitorJob.run(AbstractDelegatingMonitorJob.java:36)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> {code}
> This is happening also on locally running OpenShift v3 and also on staging v3 server.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (JBIDE-20047) As I user I want to be able to manually trigger builds
by Jeff Cantrill (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20047?page=com.atlassian.jira.plugi... ]
Jeff Cantrill reassigned JBIDE-20047:
-------------------------------------
Assignee: Jeff Cantrill
> As I user I want to be able to manually trigger builds
> ------------------------------------------------------
>
> Key: JBIDE-20047
> URL: https://issues.jboss.org/browse/JBIDE-20047
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.3.0.Beta1
> Reporter: Andre Dietisheim
> Assignee: Jeff Cantrill
> Fix For: 4.3.0.Beta2
>
>
> In STI a build is triggered by a change in the git repository. As a user I can thus triggered a build via a git push given that the git repo has the webhook installed. If I dont have the webhooks installed and I'm maybe not able to install them I'd like to be able to manually trigger the build.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months