October 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-18327) Add a "Open Log" button in the Forge Console

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18327?page=com.atlassian.jira.plugi... ] George Gastaldi closed JBIDE-18327. ----------------------------------- Fix Version/s: (was: 4.2.x) Resolution: Won't Fix Eclipse Error Log already logs the errors occurred in Forge > Add a "Open Log" button in the Forge Console > -------------------------------------------- > > Key: JBIDE-18327 > URL: https://issues.jboss.org/browse/JBIDE-18327 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: forge > Reporter: George Gastaldi > Priority: Trivial > > This would open the {{~/.forge/log/forge.log}} file when clicked -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-20990) Add "CDK Server" for start/stop for the CDK

by Burr Sutter (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20990?page=com.atlassian.jira.plugi... ] Burr Sutter commented on JBIDE-20990: ------------------------------------- Concerning "Red Hat CDK" - at what point does this string become permanent? It is possible we will have another name in the future. > Add "CDK Server" for start/stop for the CDK > ------------------------------------------- > > Key: JBIDE-20990 > URL: https://issues.jboss.org/browse/JBIDE-20990 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Reporter: Max Rydahl Andersen > Assignee: Rob Stryker > > We want to be able to start/stop CDK easily. > Current suggestion is to use a server entry in server view that can start/stop vagrant by simply knowing its file location would be a good start. > note: the vagrant image might already be running so just need to be able to take care of that. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-20982) JBDS consumes 40-50% CPU without any noticeable job in progress

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20982?page=com.atlassian.jira.plugi... ] Snjezana Peco commented on JBIDE-20982: --------------------------------------- I can't reproduce the issue on Linux and Windows. Importing 200+ javaee7-samples projects takes a long time. Once they are imported, Eclipse/Java consumes 2+ GB RAM, but a minimal percent (<1%) of CPU. I can't test on Mac. Try to test Eclipse Mars and some newer JDK. > JBDS consumes 40-50% CPU without any noticeable job in progress > --------------------------------------------------------------- > > Key: JBIDE-20982 > URL: https://issues.jboss.org/browse/JBIDE-20982 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: upstream > Affects Versions: 4.2.0.Final > Reporter: Xavier Coulon > Assignee: Snjezana Peco > Fix For: 4.4.x > > Attachments: jstack-JBDS-3147-1.txt, jstack-JBDS-3147-2.txt, jstack-JBDS-3147-3.txt, jstack-JBDS-3147-4.txt, Screen Shot 2014-09-11 at 16.06.20.png, Screen Shot 2014-09-12 at 09.22.31.png, Screen Shot 2014-09-12 at 12.33.40.png, Screen Shot 2014-09-12 at 17.49.48.png > > > Steps to reproduce (on MacOSX): > - import all WildFly Quickstarts (https://github.com/wildfly/quickstart) > - restart the workbench > - once all projects have been built and no job appears in the progress view, JBDS still consumes ~40% a CPU -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-20442) Create SWTBot integration tests for tern related features

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20442?page=com.atlassian.jira.plugi... ] Denis Golovin commented on JBIDE-20442: --------------------------------------- [~vpakan], do you have something to look at or run? > Create SWTBot integration tests for tern related features > --------------------------------------------------------- > > Key: JBIDE-20442 > URL: https://issues.jboss.org/browse/JBIDE-20442 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: jsp/jsf/xml/html-source-editing > Affects Versions: 4.3.0.Beta2 > Reporter: Denis Golovin > Assignee: Denis Golovin > Priority: Critical > Fix For: 4.3.x > > > There should be set of SWTBot tests that would cover functionality related to tern.java and angularjs-eclipse integration. These tests would simplify migration to new tern.java and angularjs-eclipse releases. > Current process for migration to new version of tern-java/angularjs-eclipse is manual. Steps below describe current approach: > 1. Manual mirroring of latest tern-java/angularjs-eclipse versions to local filesystem; > 2. Build jbosstools-jst with local mirrors and run JUnit tests; > 3. Install latest tern-java and angularjs-eclipse form mirrors done in (1) into JBDS nightly build from master branch (it has open version range for tern features) and restart; > 4. Run manual tests; > 5. If (2) and (3) idenify no problems then local mirrors should be published to http://download.jboss.org/jbosstools/updates/requirements/tern and http://download.jboss.org/jbosstools/updates/requirements/angularjs respectively; > 6. Update jbosstools-jst with new versions for tern-java/angularjs-eclipse and push local branch to upstream > With step 4 implemented as SWT bot tests and automated mirroring for tern-java and angularjs-eclipse (see jenkins job here https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/All/job/jbosstools-...) we can fully automate the process above. > QA also can skip step (1) and just use external p2 repos: > * http://oss.opensagres.fr/tern.repository/1.0.0-SNAPSHOT/ > * http://oss.opensagres.fr/angularjs-eclipse/1.0.0-SNAPSHOT/ > in step (2) by building jbosstools-jst as: > {code}mvn clean install -Dtern.repo.url=http://oss.opensagres.fr/tern.repository/1.0.0-SNAPSHOT/ -Dhttp://oss.opensagres.fr/angularjs-eclipse/1.0.0-SNAPSHOT/{code} > and installing latest versions for step (3). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBTIS-480) JBDSIS 8.0.3.GA/ JBTIS 4.2.3.Final - update jbosstools/devstudio infrastructure

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-480?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky closed JBTIS-480. ----------------------------------- > JBDSIS 8.0.3.GA/ JBTIS 4.2.3.Final - update jbosstools/devstudio infrastructure > ------------------------------------------------------------------------------- > > Key: JBTIS-480 > URL: https://issues.jboss.org/browse/JBTIS-480 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: distribution > Affects Versions: 8.0.3.GA, 4.2.3.Final > Reporter: Paul Leacu > Assignee: Paul Leacu > Fix For: 8.0.3.GA, 4.2.3.Final > > > Update jbosstools-download.jboss.org and jbdevstudio-website with 4.2.3.Final/ 8.0.3.GA distribution infrastructure. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBTIS-466) JBTIS 4.2.3.Final component updates

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-466?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky commented on JBTIS-466: ----------------------------------------- Verified with JBDS 8.1.0.GA + JBDS-IS 8.0.3.GA > JBTIS 4.2.3.Final component updates > ----------------------------------- > > Key: JBTIS-466 > URL: https://issues.jboss.org/browse/JBTIS-466 > Project: JBoss Tools Integration Stack > Issue Type: Feature Request > Components: distribution > Affects Versions: 4.2.3.Final > Reporter: Paul Leacu > Assignee: Paul Leacu > Fix For: 4.2.3.Final > > > Component updated to JBTIS composites and discovery metadata. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBTIS-517) Update web pages for JBDS-IS 9.x

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-517?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky updated JBTIS-517: ------------------------------------ Attachment: jbdsis9_webpage_2015_10_29.png jbdsis9_ea_webpage_2015_10_29.png > Update web pages for JBDS-IS 9.x > -------------------------------- > > Key: JBTIS-517 > URL: https://issues.jboss.org/browse/JBTIS-517 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: distribution > Affects Versions: 9.0.0.Alpha2 > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > Priority: Minor > Fix For: 9.0.0.Alpha2 > > Attachments: jbdsis-900alpha2-webpage.png, jbdsis-900alpha2ea-webpage.png, jbdsis9_ea_webpage_2015_10_29.png, jbdsis9_webpage_2015_10_29.png > > > Update web pages for JBDS-IS 9.x at > * https://devstudio.redhat.com/9.0/development/updates/integration-stack/ > * https://devstudio.redhat.com/9.0/development/updates/integration-stack/ea... > See the attached screenshots of the current web pages. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBTIS-529) fuse fails to install from jboss central

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-529?page=com.atlassian.jira.plugin.... ] Paul Leacu commented on JBTIS-529: ---------------------------------- Hey [~fbricon] - this appears to be resolved to me: https://github.com/jbosstools/jbosstools-integration-stack/commit/6904f23... https://github.com/jbosstools/jbosstools-integration-stack/commit/deed7bb... > fuse fails to install from jboss central > ---------------------------------------- > > Key: JBTIS-529 > URL: https://issues.jboss.org/browse/JBTIS-529 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Reporter: Max Rydahl Andersen > Assignee: Fred Bricon > Priority: Blocker > Labels: respin-b > Fix For: 4.3.0.Alpha2 > > Attachments: JBDSIS_Alpha2b_vs_Alpha2a.png, JBDSIS_EA_Alpha2b_vs_Alpha2a.png, JBDSIS_EA_Alpha2b_vs_Alpha2a_MANIFEST.png > > > not sure where the fault is here but when you open JBDS 9 and type in 'Fuse' you get the "Fuse Integration Project" despite Fuse is only earlyaccess. > But even with or without earlyaccess installing via the wizard result in: > Problems occurred while performing installation: There are no connectors to install > There are no connectors to install > /cc [~fbricon] any idea ? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21032) Application wizard: Parameter table is empty when new app with local templates

by Yue Wang (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21032?page=com.atlassian.jira.plugi... ] Yue Wang updated JBIDE-21032: ----------------------------- Summary: Application wizard: Parameter table is empty when new app with local templates (was: Parameter table is empty when new app with local templates) > Application wizard: Parameter table is empty when new app with local templates > ------------------------------------------------------------------------------ > > Key: JBIDE-21032 > URL: https://issues.jboss.org/browse/JBIDE-21032 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta1 > Environment: 3.1.0.Beta1-v20151023-2117-B60 > Reporter: Yue Wang > Labels: application_wizard, openshift_v3 > > When new app from local templates with application wizard, no parameters is displayed in Templates Parameters table. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21032) Parameter table is empty when new app with local templates

by Yue Wang (JIRA)

Yue Wang created JBIDE-21032: -------------------------------- Summary: Parameter table is empty when new app with local templates Key: JBIDE-21032 URL: https://issues.jboss.org/browse/JBIDE-21032 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.3.1.Beta1 Environment: 3.1.0.Beta1-v20151023-2117-B60 Reporter: Yue Wang When new app from local templates with application wizard, no parameters is displayed in Templates Parameters table. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues October 2015