November 2014 - jbosstools-issues

[JBoss JIRA] (JBIDE-17956) Add progress bar to Add Arquillian profiles dialog

by Lucia Jelinkova (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17956?page=com.atlassian.jira.plugi... ] Lucia Jelinkova closed JBIDE-17956. ----------------------------------- Thank you for the explanation. I verified that there is a progress monitor displayed in the status bar. After the launcher dialog is closed, the progressbar dialog is shown. After it is closed the user can interact with the Eclipse UI. I think this behaviour is OK and I will close the issue. > Add progress bar to Add Arquillian profiles dialog > -------------------------------------------------- > > Key: JBIDE-17956 > URL: https://issues.jboss.org/browse/JBIDE-17956 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: testing-tools > Affects Versions: 4.2.0.Beta3 > Reporter: Lucia Jelinkova > Assignee: Snjezana Peco > Priority: Minor > Labels: respin-a > Fix For: 4.2.0.CR2 > > Attachments: progressbar-1.ogv, progressbar-2.ogv, progressbar-cr2a.ogv > > > In Add Arquillian profiles dialog, when I select all profiles and press OK, it takes quite a long time to finish the task. There should be a progress bar in this case. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18827) Explorer: add Application start/stop/restart

by Andre Dietisheim (JIRA)

Andre Dietisheim created JBIDE-18827: ---------------------------------------- Summary: Explorer: add Application start/stop/restart Key: JBIDE-18827 URL: https://issues.jboss.org/browse/JBIDE-18827 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: openshift Environment: Eclipse plugin Reporter: Andre Dietisheim Assignee: Marián Labuda Priority: Blocker Fix For: 4.2.1.Final, 4.3.x The OpenShift Console view should contain controls for application start|stop|restart to match the functionality of the CLI. Currently, if you select Window->Show View->Others->OpenShift Express Console, then login in and select an application. The right-click menu doesn't have start|stop|restart so users have to either install the rhc client tools or ssh onto the OpenShift host gear. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18827) Explorer: add Application start/stop/restart

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18827?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-18827: ------------------------------------- Fix Version/s: (was: 4.2.1.Final) > Explorer: add Application start/stop/restart > --------------------------------------------- > > Key: JBIDE-18827 > URL: https://issues.jboss.org/browse/JBIDE-18827 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Environment: Eclipse plugin > Reporter: Andre Dietisheim > Assignee: Marián Labuda > Priority: Blocker > Labels: explorer, new_and_noteworthy > Fix For: 4.3.x > > > The OpenShift Console view should contain controls for application start|stop|restart to match the functionality of the CLI. Currently, if you select Window->Show View->Others->OpenShift Express Console, then login in and select an application. The right-click menu doesn't have start|stop|restart so users have to either install the rhc client tools or ssh onto the OpenShift host gear. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18775) Ensure features and plugins have upversioned since 4.2.0.Final release [Arquillian]

by Lucia Jelinkova (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18775?page=com.atlassian.jira.plugi... ] Lucia Jelinkova closed JBIDE-18775. ----------------------------------- Verified JBDS 8.0.1.CR1 > Ensure features and plugins have upversioned since 4.2.0.Final release [Arquillian] > ----------------------------------------------------------------------------------- > > Key: JBIDE-18775 > URL: https://issues.jboss.org/browse/JBIDE-18775 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: testing-tools > Affects Versions: 4.2.1.CR1 > Reporter: Nick Boldt > Assignee: Snjezana Peco > Fix For: 4.2.1.CR1 > > > You have commits in your 4.2.x branch which happened AFTER 4.2.0.Final. Yet your root pom is still at version 4.2.0, and your affected plugins' versions are not incremented. > https://github.com/jbosstools/jbosstools-arquillian/commits/jbosstools-4.2.x > Please bump your stuff to a .1 version to reflect the fact you're doing maintenance in the 4.2.x branch. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-355) Enable JBDSIS Marketplace entry or entries for product groupings - Luna

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBTIS-355?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBTIS-355: ------------------------------------------- " I guess we decided to make the BYOE feature more restrictive. ". I don't think we decided that. The BYOE was supposed to support more flexible updates, but seems this was only done for parts of it - not all of it. > Enable JBDSIS Marketplace entry or entries for product groupings - Luna > ----------------------------------------------------------------------- > > Key: JBTIS-355 > URL: https://issues.jboss.org/browse/JBTIS-355 > Project: JBoss Tools Integration Stack > Issue Type: Feature Request > Components: distribution > Affects Versions: 8.0.0.GA > Reporter: Paul Leacu > Assignee: Nick Boldt > Attachments: jbtis355.png > > > * In JBDS 8.1, add a new com.jboss.devstudio.core.central.feature that packages up com.jboss.devstudio.core.central plugin - JBDS-3210 > ** include this in com.jboss.devstudio.core.feature instead of the plugin? > * enable usage tracking in JBT IS components' MANIFST.MF files - JBTIS-290 > * create four connectors, each based on the content in JBDS IS disco plugin.xml's top four BIG connectors; include com.jboss.devstudio.core.CENTRAL.feature in order to install Central along for the ride - JBTIS-358 > (For JBDS 9, we will look at making the Central feature much smaller so the footprint is significantly smaller - see JBIDE-18734.) -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18820) define how to handle ide.properties and avoid parent pom to always change

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18820?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-18820: ---------------------------------------- I believe optional dependency wouldn't be a satisfying approch. However, using Require-Capabilities with 3 bundles providing this capability (1 mock, 1 JBT, 1 JBDS) and letting p2 pick the available on sounds more consistent with our actual use-case. > define how to handle ide.properties and avoid parent pom to always change > ------------------------------------------------------------------------- > > Key: JBIDE-18820 > URL: https://issues.jboss.org/browse/JBIDE-18820 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build > Reporter: Max Rydahl Andersen > > As illustrated in JBIDE-18806 our current setup of how ide.properties and project versioning are not working or at least we seem to not get it updated right. > Current workaround applied is that parent pom now again defines the global version even though this is not reliable at all since not all plugins will be rebuilt. (see JBIDE-13452 for earlier attempts on this) > Opening this jira to make sure we walkthrough and write down which values should be in ide.properties and what level (4.2.0.CR1, 4.2.0 or 4.2. etc), when they get updated (hopefully rarely) and how to avoid parent pom from always having to respin because of a maintanence release. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18820) define how to handle ide.properties and avoid parent pom to always change

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18820?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-18820: --------------------------------------------- [~mickael_istria] none of that guarantees that it will always be available. Even if it did that optional dependency would still need to be at same level as base/foundation and rebuild between version releases would it not ? > define how to handle ide.properties and avoid parent pom to always change > ------------------------------------------------------------------------- > > Key: JBIDE-18820 > URL: https://issues.jboss.org/browse/JBIDE-18820 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build > Reporter: Max Rydahl Andersen > > As illustrated in JBIDE-18806 our current setup of how ide.properties and project versioning are not working or at least we seem to not get it updated right. > Current workaround applied is that parent pom now again defines the global version even though this is not reliable at all since not all plugins will be rebuilt. (see JBIDE-13452 for earlier attempts on this) > Opening this jira to make sure we walkthrough and write down which values should be in ide.properties and what level (4.2.0.CR1, 4.2.0 or 4.2. etc), when they get updated (hopefully rarely) and how to avoid parent pom from always having to respin because of a maintanence release. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16695) Add marker/quick fix if test contains non static deployment method

by Lucia Jelinkova (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16695?page=com.atlassian.jira.plugi... ] Lucia Jelinkova commented on JBIDE-16695: ----------------------------------------- CR1 > Add marker/quick fix if test contains non static deployment method > ------------------------------------------------------------------ > > Key: JBIDE-16695 > URL: https://issues.jboss.org/browse/JBIDE-16695 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: testing-tools > Affects Versions: 4.1.1.Final > Reporter: Rich DiCroce > Assignee: Snjezana Peco > Labels: new_and_noteworthy > Fix For: 4.2.1.CR1, 4.3.0.Alpha1 > > > In an Arquillian test class, any method marked @Deployment that returns something other than Archive is not being detected. For example, this method is not detected by the tooling, despite the fact that WebArchive extends Archive: > {code} > @Deployment > public static WebArchive createDeployment() { > ...code to create deployment here... > } > {code} > As a result, the deployment validation features do not work, and the Arquillian Cruiser view does not allow the archive to be browsed. Curiously, however, there is no warning about a missing @Deployment method. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18826) ClassNotFoundException for creating new Hybrid project

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18826?page=com.atlassian.jira.plugi... ] Ilya Buziuk updated JBIDE-18826: -------------------------------- Description: stack trace: {code} Caused by: java.lang.ClassNotFoundException: org.apache.http.client.cache.HttpCacheStorage cannot be found by org.eclipse.thym.core_0.1.0.201411202306 at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:432) at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:345) at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:337) at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:160) at java.lang.ClassLoader.loadClass(ClassLoader.java:357) ... 64 more {code} this is most likely a version range issue - http://snag.gy/6EHNd.jpg was: stack trace: {code} Caused by: java.lang.ClassNotFoundException: org.apache.http.client.cache.HttpCacheStorage cannot be found by org.eclipse.thym.core_0.1.0.201411202306 at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:432) at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:345) at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:337) at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:160) at java.lang.ClassLoader.loadClass(ClassLoader.java:357) ... 64 more {code} > ClassNotFoundException for creating new Hybrid project > ------------------------------------------------------ > > Key: JBIDE-18826 > URL: https://issues.jboss.org/browse/JBIDE-18826 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid > Affects Versions: 4.3.0.Alpha1 > Reporter: Ilya Buziuk > Assignee: Gorkem Ercan > Fix For: 4.3.0.Alpha1 > > > stack trace: > {code} > Caused by: java.lang.ClassNotFoundException: org.apache.http.client.cache.HttpCacheStorage cannot be found by org.eclipse.thym.core_0.1.0.201411202306 > at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:432) > at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:345) > at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:337) > at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:160) > at java.lang.ClassLoader.loadClass(ClassLoader.java:357) > ... 64 more > {code} > this is most likely a version range issue - http://snag.gy/6EHNd.jpg -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16695) Add marker/quick fix if test contains non static deployment method

by Lucia Jelinkova (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16695?page=com.atlassian.jira.plugi... ] Lucia Jelinkova closed JBIDE-16695. ----------------------------------- Verified JBDS 8.0.1 > Add marker/quick fix if test contains non static deployment method > ------------------------------------------------------------------ > > Key: JBIDE-16695 > URL: https://issues.jboss.org/browse/JBIDE-16695 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: testing-tools > Affects Versions: 4.1.1.Final > Reporter: Rich DiCroce > Assignee: Snjezana Peco > Labels: new_and_noteworthy > Fix For: 4.2.1.CR1, 4.3.0.Alpha1 > > > In an Arquillian test class, any method marked @Deployment that returns something other than Archive is not being detected. For example, this method is not detected by the tooling, despite the fact that WebArchive extends Archive: > {code} > @Deployment > public static WebArchive createDeployment() { > ...code to create deployment here... > } > {code} > As a result, the deployment validation features do not work, and the Arquillian Cruiser view does not allow the archive to be browsed. Curiously, however, there is no warning about a missing @Deployment method. -- 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