January 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-3566) include AERI in JBDS

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBDS-3566?page=com.atlassian.jira.plugin.... ] Martin Malina closed JBDS-3566. ------------------------------- The feature and plugins are included in both JBDS 9.1.0.Beta2 B256 and JBDS 10.0.0.Alpha1 B2325 > include AERI in JBDS > -------------------- > > Key: JBDS-3566 > URL: https://issues.jboss.org/browse/JBDS-3566 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: build, target-platform > Affects Versions: 9.1.0.Beta1, 10.0.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 9.1.0.Beta2, 10.0.0.Alpha1 > > > Include required bundles for AERI in JBDS. Details TBD. > Maybe need these? > {code} > org.eclipse.epp.logging.aeri.feature_1.0.1.v20150913-0716 > org.eclipse.epp.logging.aeri.ide_1.0.1.v20150913-0657.jar > org.eclipse.epp.logging.aeri.ui_1.0.1.v20150913-0716.jar > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3586) Cannot install Integration Stack from central with: OpenJDK-1.8.0.65, OpenJDK-1.8.0.71

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBDS-3586?page=com.atlassian.jira.plugin.... ] Jan Richter commented on JBDS-3586: ----------------------------------- [~nickboldt] Looks like it is a problem with installing graphiti into JBDS. I got this when I tried installing graphiti on its own: {noformat} An error occurred while collecting items to be installed session context was:(profile=jbds, phase=org.eclipse.equinox.internal.p2.engine.phases.Collect, operand=, action=). Problems downloading artifact: osgi.bundle,org.apache.batik.ext.awt,1.7.0.v201011041433. Unpacking fails because intermediate file is empty: /tmp/work1431292851719743852/p2.optimizers.incoming2192528927085252475.jar Problems downloading artifact: osgi.bundle,org.eclipse.graphiti.ui,0.12.1.v20150916-0905. Unpacking fails because intermediate file is empty: /tmp/work7392256781947386123/p2.optimizers.incoming6034293587745812299.jar {noformat} It does not happen in eclipse/JBT however. > Cannot install Integration Stack from central with: OpenJDK-1.8.0.65, OpenJDK-1.8.0.71 > -------------------------------------------------------------------------------------- > > Key: JBDS-3586 > URL: https://issues.jboss.org/browse/JBDS-3586 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: central, updatesite > Affects Versions: 9.1.0.Beta2 > Reporter: Jan Richter > Priority: Critical > > Trying to install IS from central early access, I'm getting the following error: > {noformat} > An error occurred while collecting items to be installed > session context was:(profile=jbds, phase=org.eclipse.equinox.internal.p2.engine.phases.Collect, operand=, action=). > Problems downloading artifact: osgi.bundle,org.eclipse.graphiti.ui,0.13.0.v20150818-1354. > Unpacking fails because intermediate file is empty: /tmp/work8606338891825741513/p2.optimizers.incoming8698731202719996837.jar > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-708) JBDS 9.1 Beta2: Update support page with fedora versions

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-708?page=com.atlassian.jira.plug... ] Martin Malina commented on TOOLSDOC-708: ---------------------------------------- Thanks, [~mhusnain], now it looks ok. > JBDS 9.1 Beta2: Update support page with fedora versions > -------------------------------------------------------- > > Key: TOOLSDOC-708 > URL: https://issues.jboss.org/browse/TOOLSDOC-708 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Bug > Components: General documentation issues > Affects Versions: 9.1 Beta2 > Reporter: Misha Ali > Assignee: Misha Ali > Labels: Support > Attachments: screenshot_support.png, Screenshot_support_update.png > > > We should update the support matrix of JBDS to include the latest Fedora releases: 22 and 23. At the same time, 21 can be dropped. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21518) CoreException when validating wrong credentials (Unknown response code: 503)

by Radim Hopp (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21518?page=com.atlassian.jira.plugi... ] Radim Hopp closed JBIDE-21518. ------------------------------ Resolution: Cannot Reproduce Bug Yep.... Today, using JBDS 9.1.0.Beta2 I'm also seeing the right message. > CoreException when validating wrong credentials (Unknown response code: 503) > ---------------------------------------------------------------------------- > > Key: JBIDE-21518 > URL: https://issues.jboss.org/browse/JBIDE-21518 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: common/jst/core, runtime-detection > Affects Versions: 4.3.1.Beta2 > Environment: JBDS 9.1.0.Beta2-v20160121-0657-B250 > Reporter: Radim Hopp > Assignee: Rob Stryker > Fix For: 4.3.1.CR1, 4.4.0.Alpha1 > > > Validating wrong credentials in DownloadRuntime wizard throws "An error occurred while validating your credentials. org.eclipse.core.runtime.CoreException - Unknown response code: 503" > {noformat:title=ErrorLog} > org.eclipse.core.runtime.CoreException: Unknown response code: 503 > at org.jboss.tools.runtime.ui.internal.wizard.workflow.DownloadManagerWorkflowUtility.getWorkflowStatus(DownloadManagerWorkflowUtility.java:58) > at org.jboss.tools.runtime.ui.internal.wizard.workflow.DownloadManagerCredentialsFragment.validateCredentials(DownloadManagerCredentialsFragment.java:205) > at org.jboss.tools.runtime.ui.internal.wizard.workflow.DownloadManagerCredentialsFragment.access$1(DownloadManagerCredentialsFragment.java:203) > at org.jboss.tools.runtime.ui.internal.wizard.workflow.DownloadManagerCredentialsFragment$3.run(DownloadManagerCredentialsFragment.java:168) > at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:119) > {noformat} > My blind guess is that it's relevant to https://issues.jboss.org/browse/JBIDE-21514, because I think, that correct message was displayed yesterday when one used wrong credentials. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3586) Cannot install Integration Stack from central with: OpenJDK-1.8.0.65, OpenJDK-1.8.0.71

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBDS-3586?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky commented on JBDS-3586: ----------------------------------------- Alternatively, you can try to install JBoss Fuse (which is a part of Integration Stack) from the following update site https://devstudio.redhat.com/9.0/development/updates/integration-stack/ea... > Cannot install Integration Stack from central with: OpenJDK-1.8.0.65, OpenJDK-1.8.0.71 > -------------------------------------------------------------------------------------- > > Key: JBDS-3586 > URL: https://issues.jboss.org/browse/JBDS-3586 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: central, updatesite > Affects Versions: 9.1.0.Beta2 > Reporter: Jan Richter > Priority: Critical > > Trying to install IS from central early access, I'm getting the following error: > {noformat} > An error occurred while collecting items to be installed > session context was:(profile=jbds, phase=org.eclipse.equinox.internal.p2.engine.phases.Collect, operand=, action=). > Problems downloading artifact: osgi.bundle,org.eclipse.graphiti.ui,0.13.0.v20150818-1354. > Unpacking fails because intermediate file is empty: /tmp/work8606338891825741513/p2.optimizers.incoming8698731202719996837.jar > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3586) Cannot install Integration Stack from central with: OpenJDK-1.8.0.65, OpenJDK-1.8.0.71

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBDS-3586?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky commented on JBDS-3586: ----------------------------------------- Hi [~omajid], the issue can be reproduced on any JBDS 9.x 1. Help > JBoss Central 2. At the bottom of JBoss Central select tab Software/Update 3. Check "Enable Early Access" (this checkbox is located bellow the list of categories on the right side) 4. Now, you should see more categories 5. Install JBoss Fuse Development 6. During the installation you should get the error message > Cannot install Integration Stack from central with: OpenJDK-1.8.0.65, OpenJDK-1.8.0.71 > -------------------------------------------------------------------------------------- > > Key: JBDS-3586 > URL: https://issues.jboss.org/browse/JBDS-3586 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: central, updatesite > Affects Versions: 9.1.0.Beta2 > Reporter: Jan Richter > Priority: Critical > > Trying to install IS from central early access, I'm getting the following error: > {noformat} > An error occurred while collecting items to be installed > session context was:(profile=jbds, phase=org.eclipse.equinox.internal.p2.engine.phases.Collect, operand=, action=). > Problems downloading artifact: osgi.bundle,org.eclipse.graphiti.ui,0.13.0.v20150818-1354. > Unpacking fails because intermediate file is empty: /tmp/work8606338891825741513/p2.optimizers.incoming8698731202719996837.jar > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21581) Include Yaml editor in JBoss Tools (& JBDS) via feature dep from o.j.t.central & add to CoreTools category, too

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21581?page=com.atlassian.jira.plugi... ] Jan Richter commented on JBIDE-21581: ------------------------------------- [~nickboldt], because nobody verified it in master. I split the original issue into 4.3 and 4.4 fix versions to track that. > Include Yaml editor in JBoss Tools (& JBDS) via feature dep from o.j.t.central & add to CoreTools category, too > --------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-21581 > URL: https://issues.jboss.org/browse/JBIDE-21581 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: updatesite > Affects Versions: 4.3.1.Beta1 > Reporter: Mickael Istria > Assignee: Nick Boldt > Fix For: 4.4.0.Alpha1 > > Attachments: jbtcentral-p2diff-summary.txt, jbtcentral-p2diff.txt, jbtcentral-p2diff_460.txt > > > There is a decent Yaml editor existing for Eclipse IDE: https://github.com/oyse/yedit . It has 21 stars and is included in STS ( JBDS-3465 ). Similarly to JSon Editor, we should provide it to JBoss Tools users by default. > This would require adding it to the TP and adding a dependency from a JBT feature to it. > On longer-term, we should get it touch with the author to get this plugin migrated to Eclipse.org world, most likely under the WTP/SSE project (cc [~vrubezhny]) > -- > Story points - 8 (fibonacci): > * update Central TP, > * update JBT/JBDS TPs, > * update JBT/JBDS category.xml files, > * update JBDS feature.xml, > * send announcement email re: TP changes -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21460) NPE at Show In Web Browser for OpenShift server if connection is not connected

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21460?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich edited comment on JBIDE-21460 at 1/27/16 1:22 AM: ------------------------------------------------------------------------ When a NPE was prevented, we know what happens and may just inform user of a problem without stack trace. If some non-trivial error happens inside OpenShift, we better let it be logged, what Job manager does when it catches an exception. [~adietish], please take a look at the refactored pull request. Original OpenShiftException is passed into GetApplicationException as the cause, and then our message dialog is shown instead of 'Problem Occured', and the original OpenShiftException is logged. was (Author: scabanovich): When a NPE was prevented, we know what happens and may just inform user of a problem without stack trace. If some non-trivial error happens inside OpenShift, we better let it be logged, what Job manager does when it catches an exception. [~adietish], should we wrap OpenShiftException into GetApplicationException and then show our message dialog instead of 'Problem Occured', and do the logging? > NPE at Show In Web Browser for OpenShift server if connection is not connected > ------------------------------------------------------------------------------ > > Key: JBIDE-21460 > URL: https://issues.jboss.org/browse/JBIDE-21460 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Viacheslav Kabanovich > Fix For: 4.3.1.CR1 > > Attachments: not-authorized-error.png > > > 1. Create an OpenShift connection, do not choose save password/token. > 2. Create an OpenShift server for the connection. > 3. Close Eclipse with Server view active > 4. Restart Eclipse, select Server view. > 5. In context menu of the server, select Show In Web Browser. > 6. 'Sign In' dialog appears, select cancel. > (Note: First time when I got it, dialog did not appear, later I could not repeat steps that would skip the dialog.) > 7. Failure: NPE while executing getWelcomePageUrl(). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21580) TernError: No type found at the given position when invoking Open On for taglib definition

by Vlado Pakan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21580?page=com.atlassian.jira.plugi... ] Vlado Pakan commented on JBIDE-21580: ------------------------------------- 1. No dialog opened only errors in Log 2. JSF Open On works > TernError: No type found at the given position when invoking Open On for taglib definition > ------------------------------------------------------------------------------------------ > > Key: JBIDE-21580 > URL: https://issues.jboss.org/browse/JBIDE-21580 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsp/jsf/xml/html-source-editing, upstream > Affects Versions: 4.3.1.Beta2 > Environment: JBDS 9.1.0.Beta2-v20160122-0528-B256 + Mobile Tooling + AngularJS > Oracle Java 1.8 > Fedora 22 64 bit > Reporter: Vlado Pakan > Assignee: Victor Rubezhny > Priority: Critical > Fix For: 4.3.1.CR1, 4.4.0.Alpha1 > > > 1. Create JSF 1.2 project > 2. Open inputUserName.jsp in VPE > 3. Hover over <%@ taglib uri="http://java.sun.com/jsf/core" > 4. Press Ctrl > ERROR: > {noformat} > tern.TernException: TernError: No type found at the given position. > at tern.server.DefaultResponseHandler.getData(DefaultResponseHandler.java:45) > at tern.server.protocol.TernResultsProcessorsFactory.makeRequestAndProcess(TernResultsProcessorsFactory.java:43) > at tern.eclipse.ide.internal.core.resources.IDETernServerAsyncReqProcessor.run(IDETernServerAsyncReqProcessor.java:104) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > Caused by: tern.TernException: TernError: No type found at the given position. > at tern.server.nodejs.NodejsTernHelper.makeRequest(NodejsTernHelper.java:86) > at tern.server.nodejs.NodejsTernServer.makeRequest(NodejsTernServer.java:163) > at tern.server.nodejs.NodejsTernServer.request(NodejsTernServer.java:127) > at tern.server.protocol.TernResultsProcessorsFactory.makeRequestAndProcess(TernResultsProcessorsFactory.java:42) > ... 2 more > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-705) JBDS 9.1 Beta2: Release Notes

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-705?page=com.atlassian.jira.plug... ] Misha Ali updated TOOLSDOC-705: ------------------------------- Description: Create new Beta2 release notes, fix the script and update the relevant details. > JBDS 9.1 Beta2: Release Notes > ----------------------------- > > Key: TOOLSDOC-705 > URL: https://issues.jboss.org/browse/TOOLSDOC-705 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Bug > Reporter: Misha Ali > Assignee: Misha Ali > > Create new Beta2 release notes, fix the script and update the relevant details. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 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 January 2016