October 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBTIS-960) Mark the corresponding tests with knowIssues

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-960?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky closed JBTIS-960. ----------------------------------- pushed to master > Mark the corresponding tests with knowIssues > -------------------------------------------- > > Key: JBTIS-960 > URL: https://issues.jboss.org/browse/JBTIS-960 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: BPMN2, QE > Affects Versions: 4.4.0.CR1-TP > Reporter: Jozef Marko > Assignee: Jozef Marko > Fix For: 4.4.0.Final > > > Know issues are: > * https://issues.jboss.org/browse/RHBPMS-4420 -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-966) Prepare an update site for CI builds of Teiid Designer

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-966?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky updated JBTIS-966: ------------------------------------ Description: Prepare an update site for CI builds of Teiid Designer. The point is to continuously verify bug fixes and new features. Note that this doesn't mean that we don't need test cycles but we would like to improve the process of testing. For example, fuse and switchyard already provide such update sites - http://download.jboss.org/jbosstools/neon/integration/updates/integration... - http://download.jboss.org/jbosstools/neon/integration/updates/integration... was: Prepare an upadte site for CI builds of Teiid Designer. The point is to continuously verify bug fixes and new features. Note that this doesn't mean that we don't need test cycles but we would like to improve the process of testing. For examples, fuse and switchyard already provide such update sites - http://download.jboss.org/jbosstools/neon/integration/updates/integration... - http://download.jboss.org/jbosstools/neon/integration/updates/integration... > Prepare an update site for CI builds of Teiid Designer > ------------------------------------------------------ > > Key: JBTIS-966 > URL: https://issues.jboss.org/browse/JBTIS-966 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: teiid > Affects Versions: 4.4.0.Alpha1 > Reporter: Andrej Podhradsky > > Prepare an update site for CI builds of Teiid Designer. The point is to continuously verify bug fixes and new features. Note that this doesn't mean that we don't need test cycles but we would like to improve the process of testing. > For example, fuse and switchyard already provide such update sites > - http://download.jboss.org/jbosstools/neon/integration/updates/integration... > - http://download.jboss.org/jbosstools/neon/integration/updates/integration... -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-966) Prepare an update site for CI builds of Teiid Designer

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-966?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky commented on JBTIS-966: ----------------------------------------- [~blafond], [~mmakovy] wdyt? > Prepare an update site for CI builds of Teiid Designer > ------------------------------------------------------ > > Key: JBTIS-966 > URL: https://issues.jboss.org/browse/JBTIS-966 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: teiid > Affects Versions: 4.4.0.Alpha1 > Reporter: Andrej Podhradsky > > Prepare an upadte site for CI builds of Teiid Designer. The point is to continuously verify bug fixes and new features. Note that this doesn't mean that we don't need test cycles but we would like to improve the process of testing. > For examples, fuse and switchyard already provide such update sites > - http://download.jboss.org/jbosstools/neon/integration/updates/integration... > - http://download.jboss.org/jbosstools/neon/integration/updates/integration... -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-966) Prepare an update site for CI builds of Teiid Designer

by Andrej Podhradsky (JIRA)

Andrej Podhradsky created JBTIS-966: --------------------------------------- Summary: Prepare an update site for CI builds of Teiid Designer Key: JBTIS-966 URL: https://issues.jboss.org/browse/JBTIS-966 Project: JBoss Tools Integration Stack Issue Type: Task Components: teiid Affects Versions: 4.4.0.Alpha1 Reporter: Andrej Podhradsky Prepare an upadte site for CI builds of Teiid Designer. The point is to continuously verify bug fixes and new features. Note that this doesn't mean that we don't need test cycles but we would like to improve the process of testing. For examples, fuse and switchyard already provide such update sites - http://download.jboss.org/jbosstools/neon/integration/updates/integration... - http://download.jboss.org/jbosstools/neon/integration/updates/integration... -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4137) JS editor fails to open

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4137?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-4137: ---------------------------------- Even without this fix in place, I can create a new javascript project, then a javascript source file, and then edit it with context sensitive help. Could be because I fixed the m2e problems as explained in JBDS-4136 ? !js-editor-works.png! > JS editor fails to open > ----------------------- > > Key: JBDS-4137 > URL: https://issues.jboss.org/browse/JBDS-4137 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: javascript, rpm, upstream > Affects Versions: 10.2.0.AM2 > Reporter: Alexey Kazakov > Assignee: Nick Boldt > Fix For: 10.2.0.AM3 > > Attachments: js-editor-works.png > > > JavaScript Editor is not working OOTB in Eclipse/devstudio installed via RPM. It fails because of missing JSDT/Equinox hook for Nashorn in eclipse.ini. See https://wiki.eclipse.org/JSDT/Equinox_hook_for_Nashorn > The same error occurs if JSDT installed to an existing Eclipse via p2. So it's rather an upstream issue. > The following line added to eclipse.ini fixes the problem: > {code}-Dosgi.framework.extensions=org.eclipse.wst.jsdt.nashorn.extension{code} > It works OOTB in devstudio installed via our installer because we have this hook in devstudio.ini -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4137) JS editor fails to open

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4137?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-4137: ----------------------------- Attachment: js-editor-works.png > JS editor fails to open > ----------------------- > > Key: JBDS-4137 > URL: https://issues.jboss.org/browse/JBDS-4137 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: javascript, rpm, upstream > Affects Versions: 10.2.0.AM2 > Reporter: Alexey Kazakov > Assignee: Nick Boldt > Fix For: 10.2.0.AM3 > > Attachments: js-editor-works.png > > > JavaScript Editor is not working OOTB in Eclipse/devstudio installed via RPM. It fails because of missing JSDT/Equinox hook for Nashorn in eclipse.ini. See https://wiki.eclipse.org/JSDT/Equinox_hook_for_Nashorn > The same error occurs if JSDT installed to an existing Eclipse via p2. So it's rather an upstream issue. > The following line added to eclipse.ini fixes the problem: > {code}-Dosgi.framework.extensions=org.eclipse.wst.jsdt.nashorn.extension{code} > It works OOTB in devstudio installed via our installer because we have this hook in devstudio.ini -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23420) Update RedDeer in TP for JBT 4.4.2.Final

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23420?page=com.atlassian.jira.plugi... ] Martin Malina updated JBIDE-23420: ---------------------------------- Description: We'd like to update the TP for JBT 4.4.2.Final to include RedDeer 1.2.0.Final - which we'll have to release first. The deadline for a PR for Nick is Nov 23. was: Due to some changes/fixes in RedDeer that we'd like to use in tests, we'd like to update the RedDeer bits in our TP. This was requested by [~rawagner] and we understand that it's just past code freeze for AM2, so this will probably have to wait until after AM2 is released. We will want to update RedDeer in the TP to include the latest from https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... I will simply create a snapshot with the rsync script and then give you the url. But it's a bit premature to do it now since it may be a week or two before you actually update the TP. So please let me know when you're ready for this task and then I can create the update site immediately. > Update RedDeer in TP for JBT 4.4.2.Final > ---------------------------------------- > > Key: JBIDE-23420 > URL: https://issues.jboss.org/browse/JBIDE-23420 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: target-platform > Affects Versions: 4.4.2.AM2 > Reporter: Martin Malina > Assignee: Martin Malina > Fix For: 4.4.2.AM3 > > > We'd like to update the TP for JBT 4.4.2.Final to include RedDeer 1.2.0.Final - which we'll have to release first. > The deadline for a PR for Nick is Nov 23. -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-960) Mark the corresponding tests with knowIssues

by Jozef Marko (JIRA)

[ https://issues.jboss.org/browse/JBTIS-960?page=com.atlassian.jira.plugin.... ] Jozef Marko resolved JBTIS-960. ------------------------------- Fix Version/s: 4.4.0.Final Resolution: Done > Mark the corresponding tests with knowIssues > -------------------------------------------- > > Key: JBTIS-960 > URL: https://issues.jboss.org/browse/JBTIS-960 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: BPMN2, QE > Affects Versions: 4.4.0.CR1-TP > Reporter: Jozef Marko > Assignee: Jozef Marko > Fix For: 4.4.0.Final > > > Know issues are: > * https://issues.jboss.org/browse/RHBPMS-4420 -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4131) Can't import example project after RPM installation on RHEL 7

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4131?page=com.atlassian.jira.plugin.... ] Nick Boldt edited comment on JBDS-4131 at 10/27/16 9:21 AM: ------------------------------------------------------------ Might be a problem w/ having both lucene 3 and 5 in the same installation: {code} ./rh-eclipse46/root/usr/lib64/eclipse/plugins/org.apache.lucene.analyzers-common_5.4.1.jar ./rh-eclipse46/root/usr/lib64/eclipse/plugins/org.apache.lucene.analyzers-smartcn_5.4.1.jar ./rh-eclipse46/root/usr/lib64/eclipse/plugins/org.apache.lucene.core_5.4.1.jar ./rh-eclipse46/root/usr/lib64/eclipse/plugins/org.apache.lucene.queries_5.4.1.jar ./rh-eclipse46/root/usr/lib64/eclipse/plugins/org.apache.lucene.queryparser_5.4.1.jar ./rh-eclipse46/root/usr/lib64/eclipse/plugins/org.apache.lucene.sandbox_5.4.1.jar ./rh-eclipse46/root/usr/share/eclipse/droplets/devstudio/eclipse/plugins/org.apache.lucene.analysis_3.5.0.v20120725-1805.jar ./rh-eclipse46/root/usr/share/eclipse/droplets/devstudio/eclipse/plugins/org.apache.lucene.core_3.5.0.v20120725-1805.jar ./rh-eclipse46/root/usr/share/eclipse/droplets/devstudio/eclipse/plugins/org.eclipse.m2e.maven.indexer_1.7.0.20160603-1931/lucene-core-2.4.1.jar ./rh-eclipse46/root/usr/share/eclipse/droplets/devstudio/eclipse/plugins/org.eclipse.m2e.maven.indexer_1.7.0.20160603-1931/lucene-highlighter-2.4.1.jar {code} {code} g! ss lucene "Framework is launched." id State Bundle 23 RESOLVED org.apache.lucene.analyzers-common_5.4.1 24 RESOLVED org.apache.lucene.analyzers-smartcn_5.4.1 25 RESOLVED org.apache.lucene.core_5.4.1 26 RESOLVED org.apache.lucene.queries_5.4.1 27 RESOLVED org.apache.lucene.queryparser_5.4.1 28 RESOLVED org.apache.lucene.sandbox_5.4.1 739 RESOLVED org.apache.lucene.analysis_3.5.0.v20120725-1805 740 RESOLVED org.apache.lucene.core_3.5.0.v20120725-1805 {code} was (Author: nickboldt): Might be a problem w/ having both lucene 3 and 5 in the same installation: {code} ./rh-eclipse46/root/usr/lib64/eclipse/plugins/org.apache.lucene.analyzers-common_5.4.1.jar ./rh-eclipse46/root/usr/lib64/eclipse/plugins/org.apache.lucene.analyzers-smartcn_5.4.1.jar ./rh-eclipse46/root/usr/lib64/eclipse/plugins/org.apache.lucene.core_5.4.1.jar ./rh-eclipse46/root/usr/lib64/eclipse/plugins/org.apache.lucene.queries_5.4.1.jar ./rh-eclipse46/root/usr/lib64/eclipse/plugins/org.apache.lucene.queryparser_5.4.1.jar ./rh-eclipse46/root/usr/lib64/eclipse/plugins/org.apache.lucene.sandbox_5.4.1.jar ./rh-eclipse46/root/usr/share/eclipse/droplets/devstudio/eclipse/plugins/org.apache.lucene.analysis_3.5.0.v20120725-1805.jar ./rh-eclipse46/root/usr/share/eclipse/droplets/devstudio/eclipse/plugins/org.apache.lucene.core_3.5.0.v20120725-1805.jar ./rh-eclipse46/root/usr/share/eclipse/droplets/devstudio/eclipse/plugins/org.eclipse.m2e.maven.indexer_1.7.0.20160603-1931/lucene-core-2.4.1.jar ./rh-eclipse46/root/usr/share/eclipse/droplets/devstudio/eclipse/plugins/org.eclipse.m2e.maven.indexer_1.7.0.20160603-1931/lucene-highlighter-2.4.1.jar {code} > Can't import example project after RPM installation on RHEL 7 > ------------------------------------------------------------- > > Key: JBDS-4131 > URL: https://issues.jboss.org/browse/JBDS-4131 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: build, rpm > Affects Versions: 10.2.0.AM3 > Environment: RHEL Server 7.2. > Reporter: Lukáš Valach > Assignee: Snjezana Peco > Priority: Critical > Fix For: 10.2.0.AM3 > > Attachments: DevstudiErrorLog.txt, devstudio10.2.wtf.png, devstudio10.2.wtf2.png, html5-project-quickstart-working-after-update-to-m2e171-m2ewtp132-lucene-error.png, html5-project-quickstart-working-after-update-to-m2e171-m2ewtp132-wagon-provider-error.png, html5-project-quickstart-working-after-update-to-m2e171-m2ewtp132.png, import_wizard.png, maven-wizard-devstudio10.2-rpm-busted.png, maven.importer.error.log, rh-eclipse46-devstudio.repo > > > During the test of RPM installation on RHEL 7 I noticed that I can't import HTML5 example project from central. Only the window with message "Refreshing project examples" appear for a while and then nothing happens. > There is one warning and many errors in Error Log View. > Error log export: [^DevstudiErrorLog.txt] > I also tried to import project from file system, but there isn't the "Existing Maven Project" option in the import wizard. [^import_wizard.png] -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4131) Can't import example project after RPM installation on RHEL 7

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4131?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-4131: ---------------------------------- Might be a problem w/ having both lucene 3 and 5 in the same installation: {code} ./rh-eclipse46/root/usr/lib64/eclipse/plugins/org.apache.lucene.analyzers-common_5.4.1.jar ./rh-eclipse46/root/usr/lib64/eclipse/plugins/org.apache.lucene.analyzers-smartcn_5.4.1.jar ./rh-eclipse46/root/usr/lib64/eclipse/plugins/org.apache.lucene.core_5.4.1.jar ./rh-eclipse46/root/usr/lib64/eclipse/plugins/org.apache.lucene.queries_5.4.1.jar ./rh-eclipse46/root/usr/lib64/eclipse/plugins/org.apache.lucene.queryparser_5.4.1.jar ./rh-eclipse46/root/usr/lib64/eclipse/plugins/org.apache.lucene.sandbox_5.4.1.jar ./rh-eclipse46/root/usr/share/eclipse/droplets/devstudio/eclipse/plugins/org.apache.lucene.analysis_3.5.0.v20120725-1805.jar ./rh-eclipse46/root/usr/share/eclipse/droplets/devstudio/eclipse/plugins/org.apache.lucene.core_3.5.0.v20120725-1805.jar ./rh-eclipse46/root/usr/share/eclipse/droplets/devstudio/eclipse/plugins/org.eclipse.m2e.maven.indexer_1.7.0.20160603-1931/lucene-core-2.4.1.jar ./rh-eclipse46/root/usr/share/eclipse/droplets/devstudio/eclipse/plugins/org.eclipse.m2e.maven.indexer_1.7.0.20160603-1931/lucene-highlighter-2.4.1.jar {code} > Can't import example project after RPM installation on RHEL 7 > ------------------------------------------------------------- > > Key: JBDS-4131 > URL: https://issues.jboss.org/browse/JBDS-4131 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: build, rpm > Affects Versions: 10.2.0.AM3 > Environment: RHEL Server 7.2. > Reporter: Lukáš Valach > Assignee: Snjezana Peco > Priority: Critical > Fix For: 10.2.0.AM3 > > Attachments: DevstudiErrorLog.txt, devstudio10.2.wtf.png, devstudio10.2.wtf2.png, html5-project-quickstart-working-after-update-to-m2e171-m2ewtp132-lucene-error.png, html5-project-quickstart-working-after-update-to-m2e171-m2ewtp132-wagon-provider-error.png, html5-project-quickstart-working-after-update-to-m2e171-m2ewtp132.png, import_wizard.png, maven-wizard-devstudio10.2-rpm-busted.png, maven.importer.error.log, rh-eclipse46-devstudio.repo > > > During the test of RPM installation on RHEL 7 I noticed that I can't import HTML5 example project from central. Only the window with message "Refreshing project examples" appear for a while and then nothing happens. > There is one warning and many errors in Error Log View. > Error log export: [^DevstudiErrorLog.txt] > I also tried to import project from file system, but there isn't the "Existing Maven Project" option in the import wizard. [^import_wizard.png] -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 5 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 October 2016