November 2014 - jbosstools-issues

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

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-11903?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-11903 at 11/24/14 1:40 PM: -------------------------------------------------------------------- as discussed with max: {quote} [4:40:40 PM] Max Rydahl Andersen: andre - I think these are okey to add in maintaencne yes since they are not changing anything, just additions ...and they were actually part of requirement of the product. [4:40:52 PM] Max Rydahl Andersen: I see it similar to the "add iphone 6" skin to browsersim. [4:45:58 PM] Max Rydahl Andersen: andre - start/stop of these does not map to server start/stop ...they would be in the openshift menu too. [4:46:15 PM] André Dietisheim: in OpenShift menu, not in the main items of the server adapter? [4:46:50 PM] Max Rydahl Andersen: yes. {quote} was (Author: adietish): [~mlabuda] please test before we merge into maintenance branch. > Explorer: add Application start/stop/restart > --------------------------------------------- > > Key: JBIDE-11903 > URL: https://issues.jboss.org/browse/JBIDE-11903 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 3.3.0.Beta2 > Environment: Eclipse plugin > Reporter: Nam Duong > Assignee: Marián Labuda > Priority: Blocker > Labels: explorer, new_and_noteworthy > 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-18824) Server adapter: Remove replicated actions, use default actions instead

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18824?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-18824: -------------------------------------- Assignee: Andre Dietisheim > Server adapter: Remove replicated actions, use default actions instead > ---------------------------------------------------------------------- > > Key: JBIDE-18824 > URL: https://issues.jboss.org/browse/JBIDE-18824 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.2.0.Final > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.3.x > > Attachments: duplicate-application-actions.png > > > In JBIDE-11903 we added Start and Stop to the Explorer and Server adapter. In the server adapter we already have default items for start, stop and restart. We should remove our items from the OpenShift submenu and use the default actions instead: > !duplicate-application-actions.png! -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18771) BrowserSim: Create new navigation bar and buttons for iphone 6 / 6+ skins

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18771?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-18771: ---------------------------------------- {quote} This navbar will be used only for iphone 6 / iphone 6+ skin. {quote} So, let's wait for the skins first and then merge both PRs. > BrowserSim: Create new navigation bar and buttons for iphone 6 / 6+ skins > ------------------------------------------------------------------------- > > Key: JBIDE-18771 > URL: https://issues.jboss.org/browse/JBIDE-18771 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: browsersim, cordovasim > Affects Versions: 4.2.0.Final > Reporter: Ilya Buziuk > Assignee: Ilya Buziuk > Labels: new_and_noteworthy > Fix For: 4.2.1.Final, 4.3.0.Alpha1 > > Attachments: nav-mockup.png, sample.png > > > Navigation bar and buttons will be created from iphone 6 IOS 8 screenshots -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18818) Test timeout in org.jboss.tools.jsf.verification.test

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18818?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-18818: ----------------------------------- Fix Version/s: 4.2.1.Final > Test timeout in org.jboss.tools.jsf.verification.test > ----------------------------------------------------- > > Key: JBIDE-18818 > URL: https://issues.jboss.org/browse/JBIDE-18818 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsf > Affects Versions: 4.2.1.CR1 > Reporter: Nick Boldt > Assignee: Alexey Kazakov > Priority: Blocker > Fix For: 4.2.1.Final > > > Tests that time out due to blocking UI or other thread lock result in builds that are recorded as ABORTED [0]. This isn't a problem in terms of publishing new content because the build runs quickly, publishes the new bits, and THEN starts running tests. > [0] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-javaee_4.... > But where it IS a problem is where we use a buildflow job to run the whole stack of JBT projects. Buildflows will also abort if they encounter an aborted job [1]. > [1] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-buildflow... > Why is this a problem? Because when we do a weekend spin (or respin) not all the projects in the stack are guaranteed to rebuild to verify all the downstream component tests all still work. > -- > If you cannot fix these tests so they run cleanly in Jenkins, please disable them or move them such that they can still be run LOCALLY using a profile, but will be skipped in Jenkins. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18749) JBossWS Runtime Preferences only checks for wsconsume.sh when adding a runtime

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18749?page=com.atlassian.jira.plugi... ] Xavier Coulon updated JBIDE-18749: ---------------------------------- Assignee: Brian Fitzpatrick > JBossWS Runtime Preferences only checks for wsconsume.sh when adding a runtime > ------------------------------------------------------------------------------ > > Key: JBIDE-18749 > URL: https://issues.jboss.org/browse/JBIDE-18749 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: webservices > Environment: Windows > Reporter: Kyle Lape > Assignee: Brian Fitzpatrick > Fix For: LATER > > > This poses an issue in Windows when a user has removed all .sh files from their installation since they serve no purpose in Windows. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3191) Improve the way we switch between development and GA

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBDS-3191?page=com.atlassian.jira.plugin.... ] Mickael Istria edited comment on JBDS-3191 at 11/24/14 12:32 PM: ----------------------------------------------------------------- {code}Eclipse is often described as being too slow (because of lots of background tasks and listeners). Do we really need to add another one to the pile, simply to work around having 2 (or 1) update sites listed in the Avail Software Sites list?{code} Those jobs would be fully asynchronous, no listeners, I don't expect them to slow down startup or usage. Also, doing additional computation to avoid people doing additional stuff is the exact purpose of a dev tools ;) {code}What happens if Dave installs JBDS 8.0.0.Beta3, gets /updates/8.0/ and /updates/8.0-development/ because it's a development milestone. Then updates to GA, then wants to try 8.1.0.Alpha1? If you removed the /8.0-development/ site, he'd have to re-add it even though he STARTED there, and is therefore a user who wants dev milestones.{code} I believe it's acceptable to require an additional effort to test a dev milestone instead of requiring an additional effort to those who want to use the GA. Or what if Edgar installs 8.0.0.GA from the /8.0-development/ site (because he's been following dev milestones, and used the same bookmarked URL instead of the /8.0/ one). Would you then remove his access to future milestones from /8.0-development because the com.jboss.devstudio.core plugin thinks that it's a GA verison, and assumes the the user therefore doesn't want milestones, only GA releases? was (Author: nickboldt): Sounds a bit like using a nuclear warhead to kill a mosquito... Eclipse is often described as being too slow (because of lots of background tasks and listeners). Do we really need to add another one to the pile, simply to work around having 2 (or 1) update sites listed in the Avail Software Sites list? What happens if Dave installs JBDS 8.0.0.Beta3, gets /updates/8.0/ and /updates/8.0-development/ because it's a development milestone. Then updates to GA, then wants to try 8.1.0.Alpha1? If you removed the /8.0-development/ site, he'd have to re-add it even though he STARTED there, and is therefore a user who wants dev milestones. Or what if Edgar installs 8.0.0.GA from the /8.0-development/ site (because he's been following dev milestones, and used the same bookmarked URL instead of the /8.0/ one). Would you then remove his access to future milestones from /8.0-development because the com.jboss.devstudio.core plugin thinks that it's a GA verison, and assumes the the user therefore doesn't want milestones, only GA releases? > Improve the way we switch between development and GA > ---------------------------------------------------- > > Key: JBDS-3191 > URL: https://issues.jboss.org/browse/JBDS-3191 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Enhancement > Components: build > Reporter: Mickael Istria > Fix For: 8.0.1.GA > > > JBDS-3190 has shown that there are too many changes to perform when willing to create a GA candidate, and it's almost certain that we'll forever forget to change one or some of them when switching between GA and development stream. > We need to improve that. > Changes are necessary in: > * features/com.jboss.devstudio.core/feature/p2.inf > * site/associate.properties > * results/pom.xml > As an alternative, I suggest that the final site be ALWAYS added to the referenced site, even if it's empty. This has no cost for build nor user, and this would simplify a few things here and there. > Also, instead of a p2.inf, we could think a a "startup" extension that would add reference to development site in case qualifier for the feature doesn't contain GA. > The property to the "current site" (GA or development) could be factorized in JBDS parent pom. so that both results/pom.xml and site/pom.xml could use it (instead of associateSites.properties). > CC [~nickboldt] [~maxandersen] -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18748) Create and use an Eclipse Mars M3 target-platform

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18748?page=com.atlassian.jira.plugi... ] Mickael Istria resolved JBIDE-18748. ------------------------------------ Resolution: Done All PRs have been merged and jobs use the TP. So closing. Individual build failures are tracked by their component owners. > Create and use an Eclipse Mars M3 target-platform > ------------------------------------------------- > > Key: JBIDE-18748 > URL: https://issues.jboss.org/browse/JBIDE-18748 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build, discovery, target-platform > Affects Versions: 4.3.0.Alpha1 > Reporter: Mickael Istria > Assignee: Mickael Istria > Priority: Blocker > Fix For: 4.3.0.Alpha1 > > > Eclipse Mars M3 is already there. We should adopt it ASAP in order to be able to make tests and contribute early enough. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3191) Improve the way we switch between development and GA

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3191?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-3191: ---------------------------------- Sounds a bit like using a nuclear warhead to kill a mosquito... Eclipse is often described as being too slow (because of lots of background tasks and listeners). Do we really need to add another one to the pile, simply to work around having 2 (or 1) update sites listed in the Avail Software Sites list? What happens if Dave installs JBDS 8.0.0.Beta3, gets /updates/8.0/ and /updates/8.0-development/ because it's a development milestone. Then updates to GA, then wants to try 8.1.0.Alpha1? If you removed the /8.0-development/ site, he'd have to re-add it even though he STARTED there, and is therefore a user who wants dev milestones. Or what if Edgar installs 8.0.0.GA from the /8.0-development/ site (because he's been following dev milestones, and used the same bookmarked URL instead of the /8.0/ one). Would you then remove his access to future milestones from /8.0-development because the com.jboss.devstudio.core plugin thinks that it's a GA verison, and assumes the the user therefore doesn't want milestones, only GA releases? > Improve the way we switch between development and GA > ---------------------------------------------------- > > Key: JBDS-3191 > URL: https://issues.jboss.org/browse/JBDS-3191 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Enhancement > Components: build > Reporter: Mickael Istria > Fix For: 8.0.1.GA > > > JBDS-3190 has shown that there are too many changes to perform when willing to create a GA candidate, and it's almost certain that we'll forever forget to change one or some of them when switching between GA and development stream. > We need to improve that. > Changes are necessary in: > * features/com.jboss.devstudio.core/feature/p2.inf > * site/associate.properties > * results/pom.xml > As an alternative, I suggest that the final site be ALWAYS added to the referenced site, even if it's empty. This has no cost for build nor user, and this would simplify a few things here and there. > Also, instead of a p2.inf, we could think a a "startup" extension that would add reference to development site in case qualifier for the feature doesn't contain GA. > The property to the "current site" (GA or development) could be factorized in JBDS parent pom. so that both results/pom.xml and site/pom.xml could use it (instead of associateSites.properties). > CC [~nickboldt] [~maxandersen] -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18822) JBT 4.2.0 is installed from staging update site instead of 4.2.1.CR1

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18822?page=com.atlassian.jira.plugi... ] Nick Boldt closed JBIDE-18822. ------------------------------ Resolution: Done Missing step is now scripted instead of just being documented, so it can be run more easily. https://github.com/jbdevstudio/jbdevstudio-devdoc/commit/bc9c3b10f077475a... http://download.jboss.org/jbosstools/updates/staging/luna/ now points to the specific staged version (4.2.1.CR1) instead of the previous. > JBT 4.2.0 is installed from staging update site instead of 4.2.1.CR1 > -------------------------------------------------------------------- > > Key: JBIDE-18822 > URL: https://issues.jboss.org/browse/JBIDE-18822 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: updatesite > Affects Versions: 4.2.1.CR1 > Reporter: Radim Hopp > Assignee: Nick Boldt > Priority: Blocker > Fix For: 4.2.1.CR1 > > > it seems that compositeContent.xml and compositeArtifacts.xml from http://download.jboss.org/jbosstools/updates/staging/luna/ are pointing to old version of tools: > http://download.jboss.org/jbosstools/static/releases/jbosstools-4.2.0.Fin... -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18822) JBT 4.2.0 is installed from staging update site instead of 4.2.1.CR1

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18822?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-18822: ------------------------------- Fix Version/s: 4.2.1.CR1 > JBT 4.2.0 is installed from staging update site instead of 4.2.1.CR1 > -------------------------------------------------------------------- > > Key: JBIDE-18822 > URL: https://issues.jboss.org/browse/JBIDE-18822 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: updatesite > Affects Versions: 4.2.1.CR1 > Reporter: Radim Hopp > Priority: Blocker > Fix For: 4.2.1.CR1 > > > it seems that compositeContent.xml and compositeArtifacts.xml from http://download.jboss.org/jbosstools/updates/staging/luna/ are pointing to old version of tools: > http://download.jboss.org/jbosstools/static/releases/jbosstools-4.2.0.Fin... -- 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