November 2014 - jbosstools-issues

[JBoss JIRA] (JBDS-3163) change publishing process so that JBDS staging builds go to devstudio.redhat.com instead of www.qa server

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3163?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBDS-3163: ------------------------------------------- " Would skip only ONE step in the release process, but it would certainly save some time." ..I read that as you are saying that even if we dont co-locate the installers and updatesites this will still save time in the process, correct ? And I assume when installers are built it knows where its updatesites will be so could cross link from it if need be. > change publishing process so that JBDS staging builds go to devstudio.redhat.com instead of www.qa server > --------------------------------------------------------------------------------------------------------- > > Key: JBDS-3163 > URL: https://issues.jboss.org/browse/JBDS-3163 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: build > Affects Versions: 8.0.0.CR1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 8.0.1.GA, 9.0.0.Alpha1 > > > To simplify release/publishing process, we ought to start publishing nightlies and builds staged for QE onto devstudio.redhat.com (filemgmt) instead of the internal www.qa box. This will also allow us to use nightly URLs in ide-config.properties. > See https://github.com/jbosstools/jbosstools-download.jboss.org/pull/409/files for a bad solution to this problem. > Better solution is to move that content onto the new filemgmt instance and update promote.sh to push to the new location. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-290) enable jboss tools usage tracking for plugins installed directly

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBTIS-290?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBTIS-290: ------------------------------------------- I left comments on the PR but I'll repeat it here in summary: A) the names gets appended into a lenght limited string thus we want as *short* names as we can, thus TEIID is better than TEIIDDESIGNER B) we want to limit what we track to truly unique features - for example we don't no more track ARCHIVES since its always part of Server now. In that context, is Guvnor really relevant to track independently ? > enable jboss tools usage tracking for plugins installed directly > ---------------------------------------------------------------- > > Key: JBTIS-290 > URL: https://issues.jboss.org/browse/JBTIS-290 > Project: JBoss Tools Integration Stack > Issue Type: Feature Request > Reporter: Max Rydahl Andersen > Assignee: Paul Leacu > Priority: Critical > Attachments: settings.xml > > > I think it is time we get integration stack components stats to show up more consistently in stats (right now we only collect switchyard - we should do more) > There are two parts to it. > 1) add a line to https://github.com/jbosstools/jbosstools-base/blob/master/usage/plugins/o... for the key feature we want to count as "one install" > 2) add an *optional* dependency to your plugins to org.jboss.tools.usage - this ensures the statistics gathering happens no matter how the feature gets installed. > The following line should be added to plugins manifest.mf: > {code} > org.jboss.tools.usage;resolution:=optional;x-installation:=greedy > {code} > Example: https://github.com/jbosstools/jbosstools-server/blob/master/archives/plug... -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18833) luna nightly are not being updated preventing QE to do easy testing of committed code

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18833?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-18833: ---------------------------------------- Priority: Blocker (was: Major) > luna nightly are not being updated preventing QE to do easy testing of committed code > ------------------------------------------------------------------------------------- > > Key: JBIDE-18833 > URL: https://issues.jboss.org/browse/JBIDE-18833 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Reporter: Max Rydahl Andersen > Priority: Blocker > > http://download.jboss.org/jbosstools/updates/nightly/luna/ composite*.xml was updated 26-nov but latest build there is from 28-oct-2014 (29 days ago) > I could not spot updates in https://github.com/jbdevstudio/jbdevstudio-ci related to this. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18833) luna nightly are not being updated preventing QE to do easy testing of committed code

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18833?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-18833: ---------------------------------------- Fix Version/s: 4.2.1.Final > luna nightly are not being updated preventing QE to do easy testing of committed code > ------------------------------------------------------------------------------------- > > Key: JBIDE-18833 > URL: https://issues.jboss.org/browse/JBIDE-18833 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Reporter: Max Rydahl Andersen > Priority: Blocker > Fix For: 4.2.1.Final > > > http://download.jboss.org/jbosstools/updates/nightly/luna/ composite*.xml was updated 26-nov but latest build there is from 28-oct-2014 (29 days ago) > I could not spot updates in https://github.com/jbdevstudio/jbdevstudio-ci related to this. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18833) luna nightly are not being updated preventing QE to do easy testing of committed code

by Max Rydahl Andersen (JIRA)

Max Rydahl Andersen created JBIDE-18833: ------------------------------------------- Summary: luna nightly are not being updated preventing QE to do easy testing of committed code Key: JBIDE-18833 URL: https://issues.jboss.org/browse/JBIDE-18833 Project: Tools (JBoss Tools) Issue Type: Bug Components: build Reporter: Max Rydahl Andersen http://download.jboss.org/jbosstools/updates/nightly/luna/ composite*.xml was updated 26-nov but latest build there is from 28-oct-2014 (29 days ago) I could not spot updates in https://github.com/jbdevstudio/jbdevstudio-ci related to this. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18832) Cannot run Arquillian test on WELD SE 1.1

by Lucia Jelinkova (JIRA)

Lucia Jelinkova created JBIDE-18832: --------------------------------------- Summary: Cannot run Arquillian test on WELD SE 1.1 Key: JBIDE-18832 URL: https://issues.jboss.org/browse/JBIDE-18832 Project: Tools (JBoss Tools) Issue Type: Bug Components: testing-tools Affects Versions: 4.2.1.CR1 Reporter: Lucia Jelinkova When I try to run simple Arquillian test on WELD SE 1.1, it crashes with the following exception: {code} java.lang.NoSuchMethodError: org.jboss.weld.context.SingletonContext.invalidate()V at org.jboss.weld.bootstrap.WeldRuntime.shutdown(WeldRuntime.java:55) at org.jboss.weld.bootstrap.WeldBootstrap.shutdown(WeldBootstrap.java:113) at org.jboss.arquillian.container.weld.se.embedded_1_1.WeldSEContainer.undeploy(WeldSEContainer.java:156) at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$4.call(ContainerDeployController.java:205) at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$4.call(ContainerDeployController.java:185) at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.executeOperation(ContainerDeployController.java:271) at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.undeploy(ContainerDeployController.java:184) 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.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) at org.jboss.arquillian.container.impl.client.ContainerDeploymentContextHandler.createDeploymentContext(ContainerDeploymentContextHandler.java:78) 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.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) at org.jboss.arquillian.container.impl.client.ContainerDeploymentContextHandler.createContainerContext(ContainerDeploymentContextHandler.java:57) 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.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$2.perform(ContainerDeployController.java:119) at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$2.perform(ContainerDeployController.java:110) at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.forEachDeployment(ContainerDeployController.java:263) at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.forEachDeployedDeployment(ContainerDeployController.java:249) at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.undeployManaged(ContainerDeployController.java:109) 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.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) at org.jboss.arquillian.container.test.impl.client.ContainerEventController.execute(ContainerEventController.java:108) 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.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) at org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:84) 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.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:65) 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.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.afterClass(EventTestRunnerAdaptor.java:87) at org.jboss.arquillian.junit.Arquillian$3$1.evaluate(Arquillian.java:204) at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:314) at org.jboss.arquillian.junit.Arquillian.access$100(Arquillian.java:46) at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:199) at org.junit.runners.ParentRunner.run(ParentRunner.java:300) at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:147) at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:50) at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:459) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:675) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:382) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:192) {code} -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-364) Fuse: Enhance XML parsing in tests

by Tomáš Sedmík (JIRA)

[ https://issues.jboss.org/browse/JBTIS-364?page=com.atlassian.jira.plugin.... ] Tomáš Sedmík updated JBTIS-364: ------------------------------- Summary: Fuse: Enhance XML parsing in tests (was: Fuse: Enhance XML parsing in test) > Fuse: Enhance XML parsing in tests > ---------------------------------- > > Key: JBTIS-364 > URL: https://issues.jboss.org/browse/JBTIS-364 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: QE > Reporter: Tomáš Sedmík > Assignee: Tomáš Sedmík > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > use XPath validation in tests instead of comparison of file contents -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-364) Fuse: Enhance XML parsing in test

by Tomáš Sedmík (JIRA)

[ https://issues.jboss.org/browse/JBTIS-364?page=com.atlassian.jira.plugin.... ] Tomáš Sedmík commented on JBTIS-364: ------------------------------------ It affects _CamelEditorTest_ > Fuse: Enhance XML parsing in test > --------------------------------- > > Key: JBTIS-364 > URL: https://issues.jboss.org/browse/JBTIS-364 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: QE > Reporter: Tomáš Sedmík > Assignee: Tomáš Sedmík > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > use XPath validation in tests instead of comparison of file contents -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18732) CordovaSim must save preferences (tabs / settings / etc.)

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18732?page=com.atlassian.jira.plugi... ] Ilya Buziuk commented on JBIDE-18732: ------------------------------------- PR works fine on Ubuntu 12.04 both gtk2 & gtk3 > CordovaSim must save preferences (tabs / settings / etc.) > --------------------------------------------------------- > > Key: JBIDE-18732 > URL: https://issues.jboss.org/browse/JBIDE-18732 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: cordovasim > Affects Versions: 4.2.0.Final, 4.3.0.Alpha1 > Reporter: Ilya Buziuk > Assignee: Ilya Buziuk > Fix For: 4.2.1.Final, 4.3.0.Alpha1 > > > For now all CordovaSim's preferences are hardcoded - https://github.com/jbosstools/incubator-ripple/commit/d2b46fdc5cfa74cc8c6... > CordovaSim must save all user's preferences: tab order, setting, etc. > NOTE: Preferences will *not* be saved for *javaFX* web engine oracle *JDK 7*, due to localstorage absence. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-364) Fuse: Enhance XML parsing in test

by Tomáš Sedmík (JIRA)

Tomáš Sedmík created JBTIS-364: ---------------------------------- Summary: Fuse: Enhance XML parsing in test Key: JBTIS-364 URL: https://issues.jboss.org/browse/JBTIS-364 Project: JBoss Tools Integration Stack Issue Type: Task Components: QE Reporter: Tomáš Sedmík Assignee: Tomáš Sedmík use XPath validation in tests instead of comparison of file contents -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 8 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 November 2014