June 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBTIS-351) Create automated test for complex SOAP binding settings

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-351?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky closed JBTIS-351. ----------------------------------- > Create automated test for complex SOAP binding settings > ------------------------------------------------------- > > Key: JBTIS-351 > URL: https://issues.jboss.org/browse/JBTIS-351 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: QE > Affects Versions: 4.2.0.Beta1 > Reporter: Andrej Podhradsky > Assignee: Andrej Podhradsky > Fix For: 4.2.2.CR1 > > > See SWITCHYARD-2195 -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19646) Move org.jboss.tools.jsf.vpe.seam into the Seam module

by Vlado Pakan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19646?page=com.atlassian.jira.plugi... ] Vlado Pakan closed JBIDE-19646. ------------------------------- Verified with JBDS 9.0.0.Beta1-v20150605-2014-B34 > Move org.jboss.tools.jsf.vpe.seam into the Seam module > ------------------------------------------------------ > > Key: JBIDE-19646 > URL: https://issues.jboss.org/browse/JBIDE-19646 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: seam2 > Affects Versions: 4.3.0.Alpha2 > Reporter: Fred Bricon > Assignee: Alexey Kazakov > Fix For: 4.3.0.Beta1 > > > Following JBDS-3354, org.jboss.tools.jsf.feature references org.jboss.tools.jsf.vpe.seam. > We should severe that dependency and move org.jboss.tools.jsf.vpe.seam under the seam module, either directly under the seam feature or a separate seam vpe feature. In the later case, it should be added to the seam connector in Central -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3454) Mobile Hybrid Project not opening on the emulator

by Supriya Bharadwaj (JIRA)

Supriya Bharadwaj created JBDS-3454: --------------------------------------- Summary: Mobile Hybrid Project not opening on the emulator Key: JBDS-3454 URL: https://issues.jboss.org/browse/JBDS-3454 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Affects Versions: 9.0.0.Alpha2 Reporter: Supriya Bharadwaj Assignee: Gorkem Ercan Priority: Minor I am trying to create a Mobile Hybrid project using the Mobile Hybrid Project wizard in JBoss Central. After its creation, the project does not open on the emulator. Also, if I export the project and try installing the apk file on a mobile android platform I get an "Application not installed" message. On certain environments (JBDS 9.0.0Alpha2 on RHEL 7) while trying to export the project it throws a "not an android project" error. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19605) Avoid need for multiple javax.servlet

by Vlado Pakan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19605?page=com.atlassian.jira.plugi... ] Vlado Pakan closed JBIDE-19605. ------------------------------- Verified with JBDS 9.0.0.Beta1-v20150605-2014-B34 > Avoid need for multiple javax.servlet > ------------------------------------- > > Key: JBIDE-19605 > URL: https://issues.jboss.org/browse/JBIDE-19605 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: target-platform, webservices > Affects Versions: 4.3.0.Alpha2 > Reporter: Mickael Istria > Assignee: Brian Fitzpatrick > Fix For: 4.3.0.Beta1 > > Attachments: org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.JavaElement11ChangedProcessingTestCase.txt, org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.JaxrsMetamodelChangedProcessorTestCase.txt, org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.ResourceChangedProcessingTestCase.txt, org.jboss.tools.ws.jaxrs.core.internal.metamodel.domain.Jaxrs11ElementFactoryTestCase.txt, org.jboss.tools.ws.jaxrs.core.internal.metamodel.domain.Jaxrs20EndpointTestCase.txt > > > We currently use 2 different version of javax.servlet bundle. We'd rather decide on sticking to 1. > {code} > On 04/15/2015 11:56 PM, Nick Boldt wrote: > > Just wondering if anyone knows WHY we include javax.servlet 3.0.0 and > > 3.1.0 in JBDS. > > More importantly... SHOULD we be including both? Or can we just include > > 3.1.0 and drop 3.0.0? > I have JBDS installed from installer, which basically ran a p2 director. And I get jetty 3.0.0 and jetty 3.1.0. Than means that while resolving what to installed, p2 has to keep both versions of javax.servlet. That's definitely a sign that our dependency chain currently need both (or p2 wouldn't have installed both). > So I've tried the ultimate test: > $ cd jbdevstudio-9.0.0.Alpha2/studio > $ rm plugins/javax.servlet_3.0.0* > $ ./jbdevstudio > And saw > !ENTRY org.jboss.tools.ws.ui 4 0 2015-04-16 10:35:49.110 > !MESSAGE FrameworkEvent ERROR > !STACK 0 > org.osgi.framework.BundleException: Could not resolve module: org.jboss.tools.ws.ui [967] > Unresolved requirement: Import-Package: javax.servlet; version="[2.4.0,3.0.0)" > at org.eclipse.osgi.container.Module.start(Module.java:434) > at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1582) > at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1561) > at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1533) > at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1476) > at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1) > at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230) > at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:340) > Fun thing is that the javax.servlet_3.0.0 actually exports packages in version 2.6.0, whereas javax.servlet_3.1.0 exports them in version 3.1.0. > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19718) No source zip produced when buildinfo.json can't be resolved

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19718?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-19718: --------------------------------------- [~nickboldt], I'm verifying JIRAs for Beta1 and saw this JIRA. I just checked http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-bui... and it doesn't exist ATM. Can you check and reopen or close? Thanks! > No source zip produced when buildinfo.json can't be resolved > ------------------------------------------------------------ > > Key: JBIDE-19718 > URL: https://issues.jboss.org/browse/JBIDE-19718 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.0.Alpha2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Fix For: 4.3.0.Beta1 > > > From the latest master build: > http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-bui... > {code} > [INFO] --- repository-utils:0.22.1-SNAPSHOT:generate-repository-facade (generate-facade) @ org.jboss.tools.site.core --- > [WARNING] Could not access build info at http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-bas... > [WARNING] Could not access build info at http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-ser... > [WARNING] Could not access build info at http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-ope... > [WARNING] Could not access build info at http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-jst... > [WARNING] Could not access build info at http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-bro... > [WARNING] Could not access build info at http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-aer... > [WARNING] Could not access build info at http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-hib... > [WARNING] Could not access build info at http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-jav... > [WARNING] Could not access build info at http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-web... > [WARNING] Could not access build info at http://download.jboss.org/jbosstools/updates/stable/luna/core/portlet/bui... > [WARNING] Could not access build info at http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-vpe... > [WARNING] Could not access build info at http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-arq... > [WARNING] Could not access build info at http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-for... > [WARNING] Could not access build info at http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-liv... > [WARNING] Could not access build info at http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-cen... > [WARNING] Could not access build info at http://download.jboss.org/jbosstools/updates/requirements/xulrunner-1.9.2... > [WARNING] Could not access build info at http://download.jboss.org/jbosstools/updates/stable/luna/core/freemarker/... > [WARNING] Could not access build info at http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-bir... > [WARNING] Could not access build info at http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.5... > [INFO] Building zip: /mnt/hudson_workspace/workspace/jbosstools-build-sites.aggregate.site_master/sources/aggregate/site/target/org.jboss.tools.site.core-4.3.0-SNAPSHOT.zip > {code} > Seems the problem is twofold: > a) when no json files are found, we should fall back to another URL. (I think I might have an open PR for this.) > For example, instead of http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-ope... we should be looking at http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-ope... > b) the generated sources zip needs to exist even it's empty (?) -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19778) Add eclipse project descriptor files to jbosstool-target-platform maven modules

by Vlado Pakan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19778?page=com.atlassian.jira.plugi... ] Vlado Pakan closed JBIDE-19778. ------------------------------- Verified on github > Add eclipse project descriptor files to jbosstool-target-platform maven modules > ------------------------------------------------------------------------------- > > Key: JBIDE-19778 > URL: https://issues.jboss.org/browse/JBIDE-19778 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: target-platform > Affects Versions: 4.3.0.Beta1 > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 4.3.0.Beta1 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19686) Rename new batch XML wizard label

by Lucia Jelinkova (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19686?page=com.atlassian.jira.plugi... ] Lucia Jelinkova closed JBIDE-19686. ----------------------------------- Verified JBDS 9.0.0.beta1 > Rename new batch XML wizard label > --------------------------------- > > Key: JBIDE-19686 > URL: https://issues.jboss.org/browse/JBIDE-19686 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: batch > Affects Versions: 4.3.0.Alpha2 > Reporter: Lucia Jelinkova > Assignee: Alexey Kazakov > Priority: Minor > Fix For: 4.3.0.Beta1 > > > At the moment, the new batch wizard has label "File Batch Job XML". I think "Batch Job XML File" is better. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18699) Angular.js is present in both supported and Early Access

by Radim Hopp (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18699?page=com.atlassian.jira.plugi... ] Radim Hopp closed JBIDE-18699. ------------------------------ > Angular.js is present in both supported and Early Access > -------------------------------------------------------- > > Key: JBIDE-18699 > URL: https://issues.jboss.org/browse/JBIDE-18699 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: central > Affects Versions: 4.2.0.Final > Environment: JBDS 8.0.0.GA > Reporter: Karel Piwko > Assignee: Max Rydahl Andersen > Fix For: 4.3.0.Beta1 > > Attachments: early-access.png, no-early-access.png > > > If I click on enable early access in JBoss Central page Software/Update tab, Angular JS is in Early access. > However, it is in supported as well. I guess only Arquillian should pop up in early access. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19270) Unhandled event loop exception when opening Batch Job Configuration editor

by Lucia Jelinkova (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19270?page=com.atlassian.jira.plugi... ] Lucia Jelinkova closed JBIDE-19270. ----------------------------------- Verified JBDS 9.0.0.beta1 > Unhandled event loop exception when opening Batch Job Configuration editor > -------------------------------------------------------------------------- > > Key: JBIDE-19270 > URL: https://issues.jboss.org/browse/JBIDE-19270 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: batch, upstream > Affects Versions: 4.3.0.Alpha2 > Reporter: Alexey Kazakov > Assignee: Alexey Kazakov > Priority: Critical > Fix For: 4.3.0.Beta1 > > > 1. Close all Batch Job Configuration editors > 2. Open any Batch Job Configuration editor (the Design tab should be opened by default, if not then open that tab and re-open the editor). > 3. See the log: > {code} > java.lang.IllegalArgumentException: Argument not valid > at org.eclipse.swt.SWT.error(SWT.java:4458) > at org.eclipse.swt.SWT.error(SWT.java:4392) > at org.eclipse.swt.SWT.error(SWT.java:4363) > at org.eclipse.swt.graphics.Image.init(Image.java:1294) > at org.eclipse.swt.graphics.Image.<init>(Image.java:200) > at org.eclipse.ui.forms.widgets.Section.onPaint(Section.java:344) > at org.eclipse.ui.forms.widgets.ExpandableComposite$1.paintControl(ExpandableComposite.java:561) > at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:230) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4480) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1413) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1437) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1422) > at org.eclipse.swt.widgets.Control.gtk_draw(Control.java:3212) > at org.eclipse.swt.widgets.Canvas.gtk_draw(Canvas.java:171) > at org.eclipse.swt.widgets.Widget.windowProc(Widget.java:2085) > at org.eclipse.swt.widgets.Control.windowProc(Control.java:5563) > at org.eclipse.swt.widgets.Display.windowProc(Display.java:4712) > 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:9174) > at org.eclipse.swt.widgets.Display.eventProc(Display.java:1253) > at org.eclipse.swt.internal.gtk.OS._gdk_window_process_all_updates(Native Method) > at org.eclipse.swt.internal.gtk.OS.gdk_window_process_all_updates(OS.java:5980) > at org.eclipse.swt.widgets.Display.update(Display.java:4665) > at org.eclipse.swt.widgets.Display.runDeferredLayouts(Display.java:3844) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3415) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1151) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1032) > at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156) > at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:648) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:592) > at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150) > 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: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:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:648) > at org.eclipse.equinox.launcher.Main.basicRun(Main.java:603) > at org.eclipse.equinox.launcher.Main.run(Main.java:1465) > at org.eclipse.equinox.launcher.Main.main(Main.java:1438) > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19340) Batch editor does not draw tree properly

by Lucia Jelinkova (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19340?page=com.atlassian.jira.plugi... ] Lucia Jelinkova closed JBIDE-19340. ----------------------------------- The issue is fixed in JBDS 9.0.0.beta1 > Batch editor does not draw tree properly > ---------------------------------------- > > Key: JBIDE-19340 > URL: https://issues.jboss.org/browse/JBIDE-19340 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: batch, upstream > Affects Versions: 4.3.0.Alpha1 > Reporter: Lucia Jelinkova > Assignee: Viacheslav Kabanovich > Fix For: 4.3.0.Beta1 > > > Sometimes the tree in batch editor is not properly drawn or it disappears completely if you right-click some tree item. > You can see in at the end of the screencast in the JBIDE-19339 issue. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues June 2015