June 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-3455) Wrong version of easymport components

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBDS-3455?page=com.atlassian.jira.plugin.... ] Mickael Istria commented on JBDS-3455: -------------------------------------- For the org.eclipse.e4.ui.importer stuff, we expect the same thing as in TP: https://github.com/jbosstools/jbosstools-target-platforms/blob/4.50.x/jbo... For the specific extension, I believe we missed to branch & build jbosstools-playground: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... . This will most likely also affect Bower integration (cc [~ibuziuk]). > Wrong version of easymport components > ------------------------------------- > > Key: JBDS-3455 > URL: https://issues.jboss.org/browse/JBDS-3455 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Affects Versions: 9.0.0.Beta1 > Reporter: Lucia Jelinkova > Assignee: Mickael Istria > Priority: Critical > Fix For: 9.0.0.Beta1 > > > JBDS 9.0.0.beta1 build contains alpha2 easymport plugins > org.jboss.tools.playground.easymport.javascript_1.0.0.Alpha2-v20150417-1604-B3.jar > org.jboss.tools.playground.easymport.jee_1.0.0.Alpha2-v20150417-1604-B3.jar > org.jboss.tools.playground.easymport.maven_1.0.0.Alpha2-v20150417-1604-B3.jar > Also org.eclipse.e4.ui.importer.java_0.1.0.v20150414-1856.jar > looks quite old but maybe nothing changed there. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19968) Explorer: "Import Application..." is displayed as %openshift.command.application.import

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19968?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-19968: ------------------------------------------ That's an easy fix that we should include in a respin. > Explorer: "Import Application..." is displayed as %openshift.command.application.import > --------------------------------------------------------------------------------------- > > Key: JBIDE-19968 > URL: https://issues.jboss.org/browse/JBIDE-19968 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Reporter: Ma Deshuai > Priority: Minor > Labels: respin-a > Attachments: Import.png > > > Description of problem: > The context item of "Import Application..." display error. > Version-Release number of selected component (if applicable): > openshift-v3 plug: 3.0.0.Beta2-v20150606-0237-B829 > How reproducible: > Always. > Steps to Reproduce: > 1. Connect to the openshift server in jbt > 2. Import existing OpenShift projects into Eclipse workspace > 1) Select a connection or a project and right click > 2) Pick "Import Application" from the context menu. > Actual results: > 2.2 The context item name should be "Import Application..." > Expected results: > 2.2 The context item name is "%openshift.command.application.import" > Additional info: -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19968) Explorer: "Import Application..." is displayed as %openshift.command.application.import

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19968?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-19968: ------------------------------------- Labels: respin-a (was: ) > Explorer: "Import Application..." is displayed as %openshift.command.application.import > --------------------------------------------------------------------------------------- > > Key: JBIDE-19968 > URL: https://issues.jboss.org/browse/JBIDE-19968 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Reporter: Ma Deshuai > Priority: Minor > Labels: respin-a > Attachments: Import.png > > > Description of problem: > The context item of "Import Application..." display error. > Version-Release number of selected component (if applicable): > openshift-v3 plug: 3.0.0.Beta2-v20150606-0237-B829 > How reproducible: > Always. > Steps to Reproduce: > 1. Connect to the openshift server in jbt > 2. Import existing OpenShift projects into Eclipse workspace > 1) Select a connection or a project and right click > 2) Pick "Import Application" from the context menu. > Actual results: > 2.2 The context item name should be "Import Application..." > Expected results: > 2.2 The context item name is "%openshift.command.application.import" > Additional info: -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19968) Explorer: "Import Application..." is displayed as %openshift.command.application.import

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19968?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-19968: ------------------------------------- Summary: Explorer: "Import Application..." is displayed as %openshift.command.application.import (was: The context item name "Import Application..." in OpenShift explorer dispaly error.) > Explorer: "Import Application..." is displayed as %openshift.command.application.import > --------------------------------------------------------------------------------------- > > Key: JBIDE-19968 > URL: https://issues.jboss.org/browse/JBIDE-19968 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Reporter: Ma Deshuai > Labels: respin-a > Attachments: Import.png > > > Description of problem: > The context item of "Import Application..." display error. > Version-Release number of selected component (if applicable): > openshift-v3 plug: 3.0.0.Beta2-v20150606-0237-B829 > How reproducible: > Always. > Steps to Reproduce: > 1. Connect to the openshift server in jbt > 2. Import existing OpenShift projects into Eclipse workspace > 1) Select a connection or a project and right click > 2) Pick "Import Application" from the context menu. > Actual results: > 2.2 The context item name should be "Import Application..." > Expected results: > 2.2 The context item name is "%openshift.command.application.import" > Additional info: -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3373) Remove org.eclipse.jst.server.generic.jonas plugin from JBDS

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBDS-3373?page=com.atlassian.jira.plugin.... ] Jan Richter closed JBDS-3373. ----------------------------- Verified for 9.0.0.Beta1, closing. > Remove org.eclipse.jst.server.generic.jonas plugin from JBDS > ------------------------------------------------------------ > > Key: JBDS-3373 > URL: https://issues.jboss.org/browse/JBDS-3373 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Enhancement > Components: updatesite > Affects Versions: 9.0.0.Alpha1 > Reporter: Fred Bricon > Assignee: Nick Boldt > Priority: Optional > Fix For: 9.0.0.Beta1 > > > com.jboss.devstudio.core.feature/feature.xml declares > {quote} > <import plugin="org.eclipse.jst.server.generic.jonas"/> > {quote} > I can't see *any* reason why we'd do that in 2015. > [~burrsutter], [~ldimaggio], [~maxandersen] : is there any client requirement about JOnAS support? > [~rob.stryker] does WTP require that plugin in any way? -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19386) Content assist for <* class=""> in Batch Job XML files.

by Lucia Jelinkova (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19386?page=com.atlassian.jira.plugi... ] Lucia Jelinkova closed JBIDE-19386. ----------------------------------- Verified in JBDS 9.0.0.beta1 that content assis lists available classes. Created new issue for filtering those classes only to real exception JBIDE-19972. > Content assist for <* class=""> in Batch Job XML files. > ------------------------------------------------------- > > Key: JBIDE-19386 > URL: https://issues.jboss.org/browse/JBIDE-19386 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: batch > Reporter: Alexey Kazakov > Assignee: Alexey Kazakov > Labels: new_and_noteworthy > Fix For: 4.3.0.Beta1 > > Attachments: scr.png > > > Works for all class="" attributes. > For example: > {code:xml} > <?xml version="1.0" encoding="UTF-8"?> > <job id="myJob" xmlns="http://xmlns.jcp.org/xml/ns/javaee" version="1.0"> > <step id="step1"> > <chunk> > <retryable-exception-classes> > <exclude class="excepT"/> > </retryable-exception-classes> > <no-rollback-exception-classes> > <exclude class="runtimee"/> > </no-rollback-exception-classes> > <skippable-exception-classes> > <include class="java.lang.Excep"/> > </skippable-exception-classes> > </chunk> > </step> > </job> > {code} > Limitations: > - Content assist doesn't work for empty strings. You have to type at least the first character in the class="<any_character>" before invoke the content assist. > - Content assist may not show all available classes if java indexing is not completed yet. > !scr.png! -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19972) Filter content assist suggestions only to exception classes for class attribute

by Lucia Jelinkova (JIRA)

Lucia Jelinkova created JBIDE-19972: --------------------------------------- Summary: Filter content assist suggestions only to exception classes for class attribute Key: JBIDE-19972 URL: https://issues.jboss.org/browse/JBIDE-19972 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: batch Affects Versions: 4.3.0.Beta1 Reporter: Lucia Jelinkova JBIDE-19386 introduced the content assist for class attribute. However, it lists all available classes. Would it be possible to suggest only classes derived from java.lang.Exception? -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3379) Error message in JBDS when installing into existing folder needs work

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBDS-3379?page=com.atlassian.jira.plugin.... ] Jan Richter closed JBDS-3379. ----------------------------- Verified for 9.0.0.Beta1, closing. > Error message in JBDS when installing into existing folder needs work > --------------------------------------------------------------------- > > Key: JBDS-3379 > URL: https://issues.jboss.org/browse/JBDS-3379 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 8.1.0.Beta1 > Reporter: Nick Boldt > Assignee: Denis Golovin > Fix For: 9.0.0.Beta1 > > Attachments: over-the-top-message-JBDS8.1Beta1.png > > > Got an error message trying to install JBDS into an existing JBDS folder: > {quote}You can't upgrade by installing over the top (sic){quote} > !over-the-top-message-JBDS8.1Beta1.png! > We should consider fixing this message in JBDS 9. Perhaps something like this? > {quote}Specified folder already contains a JBoss Developer Studio installation. One does not simply install into an existing install folder. Choose another folder or cancel this installer and run JBoss Developer Studio to perform an update.{quote} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19714) seam.core test failure

by Vlado Pakan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19714?page=com.atlassian.jira.plugi... ] Vlado Pakan closed JBIDE-19714. ------------------------------- Verified on Jenkins > seam.core test failure > ---------------------- > > Key: JBIDE-19714 > URL: https://issues.jboss.org/browse/JBIDE-19714 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: seam2 > Affects Versions: 4.3.0.Alpha2 > Reporter: Alexey Kazakov > Assignee: Daniel Azarov > Fix For: 4.3.0.Beta1 > > > Failed tests: > SeamComponentRefactoringTest.testSeamComponentRename:90->renameComponent:142 There is unexpected number of changes expected:<7> but was:<3> > SeamContextVariableRefactoringTest.testSeamContextVariable_Component_Rename:76->AbstractRefactorTest.checkRename:33 expected:<2> but was:<1> > SeamEARTest.testEarProject:80 War project must see component 'org.jboss.seam.core.interpolator' declared in ejb project -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19774) Visual Editor: XulRunner Engine on Linux is always used if browser was opened before Visual Editor

by Vlado Pakan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19774?page=com.atlassian.jira.plugi... ] Vlado Pakan commented on JBIDE-19774: ------------------------------------- Please add test cases for QE to verify > Visual Editor: XulRunner Engine on Linux is always used if browser was opened before Visual Editor > -------------------------------------------------------------------------------------------------- > > Key: JBIDE-19774 > URL: https://issues.jboss.org/browse/JBIDE-19774 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: visual-page-editor-core > Affects Versions: 4.3.0.Alpha2 > Environment: Linux > Reporter: Konstantin Marmalyukov > Assignee: Konstantin Marmalyukov > Priority: Critical > Fix For: 4.3.0.Beta1 > > > While testing new Central I notice that if Central was opened before visual editor, XulRunner engine is always used. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 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 June 2015