June 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-3923) Installer: replace browser tests with UI tests

by Pavol Pitonak (JIRA)

[ https://issues.jboss.org/browse/JBDS-3923?page=com.atlassian.jira.plugin.... ] Pavol Pitonak updated JBDS-3923: -------------------------------- Story Points: 5 > Installer: replace browser tests with UI tests > ---------------------------------------------- > > Key: JBDS-3923 > URL: https://issues.jboss.org/browse/JBDS-3923 > Project: Red Hat Developer Studio (DevStudio) > Issue Type: Feature Request > Components: platform-installer > Affects Versions: 10.0.0.Alpha2 > Reporter: Pavol Pitonak > Assignee: Jan Richter > > Remove browser tests (tests for Angular directives running using Karma) and create new UI tests. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3923) Installer: replace browser tests with UI tests

by Pavol Pitonak (JIRA)

Pavol Pitonak created JBDS-3923: ----------------------------------- Summary: Installer: replace browser tests with UI tests Key: JBDS-3923 URL: https://issues.jboss.org/browse/JBDS-3923 Project: Red Hat Developer Studio (DevStudio) Issue Type: Feature Request Components: platform-installer Affects Versions: 10.0.0.Alpha2 Reporter: Pavol Pitonak Assignee: Jan Richter Remove browser tests (tests for Angular directives running using Karma) and create new UI tests. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3769) Remove JSPM from dependencies

by Pavol Pitonak (JIRA)

[ https://issues.jboss.org/browse/JBDS-3769?page=com.atlassian.jira.plugin.... ] Pavol Pitonak commented on JBDS-3769: ------------------------------------- Since we cannot fix browser-tests (tests for Angular directives running using Karma), we should first replace these tests by ui-tests. After tests are fixed, we can proceed with removing JSPM from the project (inspiration in https://github.com/ppitonak/developer-platform-install/tree/jspm_removed2) > Remove JSPM from dependencies > ----------------------------- > > Key: JBDS-3769 > URL: https://issues.jboss.org/browse/JBDS-3769 > Project: Red Hat Developer Studio (DevStudio) > Issue Type: Task > Components: platform-installer > Affects Versions: 9.1.0.CR1 > Reporter: Jan Richter > Priority: Critical > Labels: havoc > Fix For: 10.0.0.GA > > > After a change introduced in jspm 0.16.32 which caused our builds to fail (JBDS-3747) now another issue has arisen causing errors on npm install (both local and in CI environment). Even if this new issue is fixed in jspm, we would still have to face the first issue after updating. > Therefore I propose to remove jspm entirely. We only use a small fraction of its functionality and it needlessly complicates the build + causes major issues. Since such change is likely to be quite complex, we should slip it after the April release and use an existing quick fix in the mean time. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22470) Integration tests not published to snapshots update site

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22470?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-22470: --------------------------------------- Thanks, Nick. The PR is merged, but only in master and the jenkins job is currently set to use jbosstools-4.4.x. So I changed it to master, then ran a built which worked and now the update site is up to date [1] (Cc: [~rawagner]). Finally I changed the jenkins job back to use jbosstools-4.4.x. And now I would like to ask: [~rhopp], could you please push the change to jbosstools-4.4.x as well? Thanks! [1] http://download.jboss.org/jbosstools/neon/snapshots/updates/integration-t... > Integration tests not published to snapshots update site > -------------------------------------------------------- > > Key: JBIDE-22470 > URL: https://issues.jboss.org/browse/JBIDE-22470 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.0.Final > Reporter: Martin Malina > Assignee: Martin Malina > Fix For: 4.4.0.Final > > > For some reason the update site here is outdated (from March 9): > http://download.jboss.org/jbosstools/neon/snapshots/updates/integration-t... > We consume it here: > https://github.com/jbosstools/jbosstools-integration-tests/blob/master/po... > The build is building just fine: > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-integrati... > And the result is here: > http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-int... > But for some reason it's not propagated to the standard url. > Can you please check why that is? I checked the config but could not understand what's wrong. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22470) Integration tests not published to snapshots update site

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22470?page=com.atlassian.jira.plugi... ] Martin Malina reassigned JBIDE-22470: ------------------------------------- Assignee: Radim Hopp (was: Martin Malina) > Integration tests not published to snapshots update site > -------------------------------------------------------- > > Key: JBIDE-22470 > URL: https://issues.jboss.org/browse/JBIDE-22470 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.0.Final > Reporter: Martin Malina > Assignee: Radim Hopp > Fix For: 4.4.0.Final > > > For some reason the update site here is outdated (from March 9): > http://download.jboss.org/jbosstools/neon/snapshots/updates/integration-t... > We consume it here: > https://github.com/jbosstools/jbosstools-integration-tests/blob/master/po... > The build is building just fine: > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-integrati... > And the result is here: > http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-int... > But for some reason it's not propagated to the standard url. > Can you please check why that is? I checked the config but could not understand what's wrong. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3875) Split gulpfile.js to multiple modules to simplify maintenance

by Pavol Pitonak (JIRA)

[ https://issues.jboss.org/browse/JBDS-3875?page=com.atlassian.jira.plugin.... ] Pavol Pitonak updated JBDS-3875: -------------------------------- Fix Version/s: 11.0.0.Alpha1 (was: 10.0.0.GA) > Split gulpfile.js to multiple modules to simplify maintenance > ------------------------------------------------------------- > > Key: JBDS-3875 > URL: https://issues.jboss.org/browse/JBDS-3875 > Project: Red Hat Developer Studio (DevStudio) > Issue Type: Task > Components: platform-installer > Affects Versions: 10.0.0.Alpha1 > Reporter: Jan Richter > Assignee: Pavol Pitonak > Labels: havoc > Fix For: 11.0.0.Alpha1 > > > Following up from JBDS-3851. Split the gulpfile into separate modules. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3850) Test code coverage console report for platform installer unit tests

by Pavol Pitonak (JIRA)

[ https://issues.jboss.org/browse/JBDS-3850?page=com.atlassian.jira.plugin.... ] Pavol Pitonak updated JBDS-3850: -------------------------------- Fix Version/s: 11.0.0.Alpha1 (was: 10.0.0.GA) > Test code coverage console report for platform installer unit tests > ------------------------------------------------------------------- > > Key: JBDS-3850 > URL: https://issues.jboss.org/browse/JBDS-3850 > Project: Red Hat Developer Studio (DevStudio) > Issue Type: Task > Components: platform-installer > Affects Versions: 10.0.0.Alpha1 > Reporter: Denis Golovin > Assignee: Pavol Pitonak > Labels: Havoc > Fix For: 11.0.0.Alpha1 > > Attachments: code_coverage_unit.png > > > Would be good to have code coverage report for unit tests to see how reliable tests are -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22418) Update AERI Eclipse IDE Client to 2.0

by Marcel Bruch (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22418?page=com.atlassian.jira.plugi... ] Marcel Bruch reassigned JBIDE-22418: ------------------------------------ Assignee: (was: Marcel Bruch) > Update AERI Eclipse IDE Client to 2.0 > ------------------------------------- > > Key: JBIDE-22418 > URL: https://issues.jboss.org/browse/JBIDE-22418 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: aeri > Reporter: Marcel Bruch > > I'm about to release 2.0.0 for Neon.0. > [~nickboldt], what is the earliest release of JBIDE / Devstudio that will pick up 2.0.0? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22377) Jax RS service - Run on Server: default id value is ignored in WS tester

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22377?page=com.atlassian.jira.plugi... ] Xavier Coulon updated JBIDE-22377: ---------------------------------- Fix Version/s: 4.4.x > Jax RS service - Run on Server: default id value is ignored in WS tester > ------------------------------------------------------------------------ > > Key: JBIDE-22377 > URL: https://issues.jboss.org/browse/JBIDE-22377 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: webservices > Affects Versions: 4.4.0.Alpha1 > Reporter: Jan Richter > Assignee: Xavier Coulon > Fix For: 4.4.x > > > I have a project with the following jax-rs service: > {noformat} > @Path("/rest") > public class Service { > @GET > @Path("/{id}") > public String mainService(@PathParam("id") @DefaultValue("0") Integer id, > @MatrixParam("m1") @DefaultValue("m1") String m1, > @QueryParam("q1") @DefaultValue("q1") String q1) { > return id + " " + m1 + " " + q1; > } > > } > {noformat} > When I select 'run on server' on the service endpoint and then invoke the opened service tester, it shows blank id value even when the default is set to 0. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22338) NullPointerException below SocketProposalComputer.computeCompletionProposals (thrown in BasicFeatureMap.contains)

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22338?page=com.atlassian.jira.plugi... ] Xavier Coulon updated JBIDE-22338: ---------------------------------- Fix Version/s: 4.4.x > NullPointerException below SocketProposalComputer.computeCompletionProposals (thrown in BasicFeatureMap.contains) > ----------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-22338 > URL: https://issues.jboss.org/browse/JBIDE-22338 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: webservices > Affects Versions: 4.3.1.Final > Reporter: Automated Error Reporting Bot > Assignee: Xavier Coulon > Fix For: 4.4.x > > > The following problem was reported via the automated error reporting: > Message: HIDDEN > {noformat} > java.lang.NullPointerException: null > at org.eclipse.emf.ecore.util.BasicFeatureMap.contains(BasicFeatureMap.java:712) > at org.eclipse.emf.ecore.util.BasicFeatureMap.contains(BasicFeatureMap.java:684) > at org.eclipse.emf.ecore.util.BasicFeatureMap.add(BasicFeatureMap.java:1281) > at org.eclipse.emf.ecore.util.FeatureMapUtil$FeatureEList.add(FeatureMapUtil.java:744) > at org.eclipse.jst.jee.model.internal.EJBAnnotationReader.sessionBeanFound(EJBAnnotationReader.java:338) > at org.eclipse.jst.jee.model.internal.EJBAnnotationReader.processResult(EJBAnnotationReader.java:254) > at org.eclipse.jst.jee.model.internal.EJBAnnotationReader.processAddedCompilationUnit(EJBAnnotationReader.java:411) > at org.eclipse.jst.jee.model.internal.EJBAnnotationReader.processChangedCompilationUnit(EJBAnnotationReader.java:569) > at org.eclipse.jst.jee.model.internal.common.AbstractAnnotationModelProvider.recursevilyProcessCompilationUnits(AbstractAnnotationModelProvider.java:553) > at org.eclipse.jst.jee.model.internal.common.AbstractAnnotationModelProvider.internalPostReconcile(AbstractAnnotationModelProvider.java:466) > at org.eclipse.jst.jee.model.internal.common.AbstractAnnotationModelProvider.elementChanged(AbstractAnnotationModelProvider.java:446) > at org.eclipse.jdt.internal.core.DeltaProcessor$3.run(DeltaProcessor.java:1662) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.jdt.internal.core.DeltaProcessor.notifyListeners(DeltaProcessor.java:1652) > at org.eclipse.jdt.internal.core.DeltaProcessor.fireReconcileDelta(DeltaProcessor.java:1504) > at org.eclipse.jdt.internal.core.DeltaProcessor.fire(DeltaProcessor.java:1463) > at org.eclipse.jdt.internal.core.JavaModelOperation.run(JavaModelOperation.java:770) > at org.eclipse.jdt.internal.core.JavaModelOperation.runOperation(JavaModelOperation.java:789) > at org.eclipse.jdt.internal.core.CompilationUnit.reconcile(CompilationUnit.java:1250) > at org.eclipse.jdt.internal.core.CompilationUnit.reconcile(CompilationUnit.java:1227) > at org.eclipse.jdt.internal.core.CompilationUnit.reconcile(CompilationUnit.java:1192) > at org.jboss.tools.websockets.ui.internal.ca.SocketProposalComputer.computeCompletionProposals(SocketProposalComputer.java:130) > at org.eclipse.jdt.internal.ui.text.java.CompletionProposalComputerDescriptor.computeCompletionProposals(CompletionProposalComputerDescriptor.java:333) > at org.eclipse.jdt.internal.ui.text.java.CompletionProposalCategory.computeCompletionProposals(CompletionProposalCategory.java:337) > at org.eclipse.jdt.internal.ui.text.java.ContentAssistProcessor.collectProposals(ContentAssistProcessor.java:322) > at org.eclipse.jdt.internal.ui.text.java.ContentAssistProcessor.computeCompletionProposals(ContentAssistProcessor.java:279) > at org.eclipse.jface.text.contentassist.ContentAssistant$5.run(ContentAssistant.java:1904) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.jface.text.contentassist.ContentAssistant.computeCompletionProposals(ContentAssistant.java:1902) > at org.eclipse.jface.text.contentassist.CompletionProposalPopup.computeProposals(CompletionProposalPopup.java:573) > at org.eclipse.jface.text.contentassist.CompletionProposalPopup.access$16(CompletionProposalPopup.java:570) > at org.eclipse.jface.text.contentassist.CompletionProposalPopup$2.run(CompletionProposalPopup.java:505) > at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) > at org.eclipse.jface.text.contentassist.CompletionProposalPopup.showProposals(CompletionProposalPopup.java:499) > at org.eclipse.jface.text.contentassist.ContentAssistant.showPossibleCompletions(ContentAssistant.java:1720) > at org.eclipse.jdt.internal.ui.javaeditor.CompilationUnitEditor$AdaptedSourceViewer.doOperation(CompilationUnitEditor.java:180) > at org.eclipse.ui.texteditor.ContentAssistAction$1.run(ContentAssistAction.java:82) > at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) > at org.eclipse.ui.texteditor.ContentAssistAction.run(ContentAssistAction.java:80) > at org.eclipse.jface.action.Action.runWithEvent(Action.java:473) > at org.eclipse.jface.commands.ActionHandler.execute(ActionHandler.java:122) > at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:90) > at sun.reflect.GeneratedMethodAccessor.invoke(null:-1) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(null:-1) > at java.lang.reflect.Method.invoke(null:-1) > at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:56) > {noformat} > Bundles: > | org.eclipse.core.runtime | 3.11.1.v20150903-1804 | 3.11.1.v20150903-1804 | > | org.eclipse.e4.core.di | 1.5.0.v20150421-2214 | 1.5.0.v20150421-2214 | > | org.eclipse.emf.ecore | 2.11.2.v20160208-0816 | 2.11.2.v20160208-0816 | > | org.eclipse.jdt.core | 3.11.2.v20160128-0629 | 3.11.2.v20160128-0629 | > | org.eclipse.jdt.ui | 3.11.2.v20151123-1510 | 3.11.2.v20151123-1510 | > | org.eclipse.jface | 3.11.1.v20160128-1644 | 3.11.1.v20160128-1644 | > | org.eclipse.jface.text | 3.10.0.v20150603-1752 | 3.10.0.v20150603-1752 | > | org.eclipse.jst.jee | 1.0.700.v201404092004 | 1.0.700.v201404092004 | > | org.eclipse.swt | 3.104.2.v20160212-1350 | 3.104.2.v20160212-1350 | > | org.eclipse.ui | 3.107.0.v20150507-1945 | 3.107.0.v20150507-1945 | > | org.jboss.tools.websockets.ui | 1.8.1.Final-v20160331-0952-B76 | 1.8.1.Final-v20160331-0952-B76 | > Operating Systems: > | Windows | 6.3.0 | 10.0.0 | > The above information is a snapshot of the collected data. Visit [this page|https://redhat.ctrlflow.com/reviewers/#!/problems/57279e32e4b0a54983...] for the latest data. > Thank you for your assistance. > Your friendly error-reports-inbox. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 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 2016