December 2016 - jbosstools-issues

[JBoss JIRA] (JBIDE-23641) Jboss AS Eclipse plugin freezes STS on Mac OS Sierra

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23641?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-23641: ------------------------------- Fix Version/s: 4.4.3.AM1 > Jboss AS Eclipse plugin freezes STS on Mac OS Sierra > ---------------------------------------------------- > > Key: JBIDE-23641 > URL: https://issues.jboss.org/browse/JBIDE-23641 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server, upstream > Reporter: fede pia > Assignee: Rob Stryker > Priority: Blocker > Fix For: 4.4.3.AM1 > > Attachments: eclipse.log > > > When installing Jboss Tool 4.4.2 (only Jboss AS plugin) in Spring Tool Suite in a Mac, the Eclipse hangs up and needs to be killed -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-1003) Add id to all repositories defined in target platform

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-1003?page=com.atlassian.jira.plugin... ] Paul Leacu commented on JBTIS-1003: ----------------------------------- Hey [~apodhrad] - sorry - I'm a little fuzzy today :) Where exactly would I add this id? Your POM defined the repositories (or your settings.xml). There already is a composite at http://download.jboss.org/jbosstools/updates/requirements/neon/ The .target file defines a 'repository location'. --p > Add id to all repositories defined in target platform > ----------------------------------------------------- > > Key: JBTIS-1003 > URL: https://issues.jboss.org/browse/JBTIS-1003 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: target-platform > Affects Versions: 4.4.0.CR1-TP > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > > Currently, the definition looks as follows > {code:title=src/targets/integration-stack-base.target} > <location includeAllPlatforms="false" includeConfigurePhase="true" includeMode="slicer" includeSource="true" type="InstallableUnit"> > ... > <repository location="http://download.jboss.org/jbosstools/updates/requirements/neon/201609281000/"/> > </location> > {code} > Please add an attribute 'id' to the tag 'repository'. Moreover, please consider using a composite site as a location, e.g. > {code} > http://download.jboss.org/jbosstools/updates/requirements/neon/ > {code} > I think that the composite site should work without any problem since all needed versions are specified in each unit. > Note that if we decide to use the composite site then the id could be 'jbt-neon', otherwise it should be 'jbt-neon-201609281000'. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23646) Refactor of batch test. Delete project in workspace via UI after patch in upstream is released

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23646?page=com.atlassian.jira.plugi... ] Ondrej Dockal reassigned JBIDE-23646: ------------------------------------- Assignee: Ondrej Dockal > Refactor of batch test. Delete project in workspace via UI after patch in upstream is released > ---------------------------------------------------------------------------------------------- > > Key: JBIDE-23646 > URL: https://issues.jboss.org/browse/JBIDE-23646 > Project: Tools (JBoss Tools) > Issue Type: Patch > Components: qa > Affects Versions: 4.4.x > Reporter: Ondrej Dockal > Assignee: Ondrej Dockal > > Due to upstream [bug|https://bugs.eclipse.org/bugs/show_bug.cgi?id=478634] we need to do a workaround to delete project in AfterClass method to have clean environment for another test class. Right away after patch is applied in upstream component (should be in eclipse platform.runtime 4.7 M5 milestone) and devstudio is build on it, change to UI delete call should be applied. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ERT-428) On projects with builders JavaScript Validator and Validation xml files are validated twice and error markers are duplicated [EBZ#495625]

by Victor Rubezhny (JIRA)

[ https://issues.jboss.org/browse/ERT-428?page=com.atlassian.jira.plugin.sy... ] Victor Rubezhny resolved ERT-428. --------------------------------- Fix Version/s: Neon.1 (4.6) Resolution: Done > On projects with builders JavaScript Validator and Validation xml files are validated twice and error markers are duplicated [EBZ#495625] > ----------------------------------------------------------------------------------------------------------------------------------------- > > Key: ERT-428 > URL: https://issues.jboss.org/browse/ERT-428 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Friendly Jira Robot > Assignee: Victor Rubezhny > Labels: General, bzira > Fix For: Neon.1 (4.6) > > > When a project has enabled builders JavaScript Validator and Validation, org.eclipse.wst.xml.core.internal.validation.eclipse.Validator is called twice from org.eclipse.wst.validation.internal.ValManager and all results are summed. As the result, validation error messages are duplicated. > ValBuilderJob.runInWorkspace() has a loop in which it repeats validation until getRequest() returns null. Then ValManager.validate(IProject,...) calls delete markers, but it works only for the first call, it is designed to accumulate markers created in multiple calls from ValBuilderJob during the same build. > Two requests that make the same file to be validated twice come independently from > 1) org.eclipse.wst.validation.internal.operations.ValidationBuilder > 2) org.eclipse.wst.jsdt.internal.core.builder.JavaBuilder > by method newBuild(). > When I disable JavaScript Validator in project properties in section Builders, there is no more duplication of markers. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23646) Refactor of batch test. Delete project in workspace via UI after patch in upstream is released

by Ondrej Dockal (JIRA)

Ondrej Dockal created JBIDE-23646: ------------------------------------- Summary: Refactor of batch test. Delete project in workspace via UI after patch in upstream is released Key: JBIDE-23646 URL: https://issues.jboss.org/browse/JBIDE-23646 Project: Tools (JBoss Tools) Issue Type: Patch Components: qa Affects Versions: 4.4.x Reporter: Ondrej Dockal Due to upstream [bug|https://bugs.eclipse.org/bugs/show_bug.cgi?id=478634] we need to do a workaround to delete project in AfterClass method to have clean environment for another test class. Right away after patch is applied in upstream component (should be in eclipse platform.runtime 4.7 M5 milestone) and devstudio is build on it, change to UI delete call should be applied. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-1003) Add id to all repositories defined in target platform

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-1003?page=com.atlassian.jira.plugin... ] Paul Leacu reassigned JBTIS-1003: --------------------------------- Assignee: Paul Leacu > Add id to all repositories defined in target platform > ----------------------------------------------------- > > Key: JBTIS-1003 > URL: https://issues.jboss.org/browse/JBTIS-1003 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: target-platform > Affects Versions: 4.4.0.CR1-TP > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > > Currently, the definition looks as follows > {code:title=src/targets/integration-stack-base.target} > <location includeAllPlatforms="false" includeConfigurePhase="true" includeMode="slicer" includeSource="true" type="InstallableUnit"> > ... > <repository location="http://download.jboss.org/jbosstools/updates/requirements/neon/201609281000/"/> > </location> > {code} > Please add an attribute 'id' to the tag 'repository'. Moreover, please consider using a composite site as a location, e.g. > {code} > http://download.jboss.org/jbosstools/updates/requirements/neon/ > {code} > I think that the composite site should work without any problem since all needed versions are specified in each unit. > Note that if we decide to use the composite site then the id could be 'jbt-neon', otherwise it should be 'jbt-neon-201609281000'. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23645) Remove org.jboss.tools.ui.bot.ext from integration tests

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23645?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-23645: --------------------------------------- [~psrna], you said org.jboss.tools.jst.ui.bot can just be removed? What about the others? We need to discuss those. > Remove org.jboss.tools.ui.bot.ext from integration tests > -------------------------------------------------------- > > Key: JBIDE-23645 > URL: https://issues.jboss.org/browse/JBIDE-23645 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: integration-tests > Affects Versions: 4.4.3.AM1 > Reporter: Martin Malina > Assignee: Martin Malina > > org.jboss.tools.ui.bot.ext is an old and unmaintained test library. We should find out if/what tests still use it and fix those and ultimately remove bot.ext. > https://github.com/jbosstools/jbosstools-integration-tests/tree/master/pl... > This was previously discussed in JBIDE-23593 where I found the following tests that still use bot.ext. > I found out that some tests still use bot.ext: > {code} > $ find . -iname 'manifest.mf' -path '*/META-INF/*'|xargs grep 'ui\.bot\.ext'|sed 's/:.*//'|uniq > ./plugins/org.jboss.tools.jst.ui.bot/META-INF/MANIFEST.MF > ./plugins/org.jboss.tools.ui.bot.ext/META-INF/MANIFEST.MF > ./tests/org.jboss.tools.portlet.ui.bot.test/META-INF/MANIFEST.MF > ./tests/org.jboss.tools.seam.ui.bot.test/META-INF/MANIFEST.MF > ./tests/org.jboss.tools.ws.ui.bot.test/META-INF/MANIFEST.MF > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23645) Remove org.jboss.tools.ui.bot.ext from integration tests

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23645?page=com.atlassian.jira.plugi... ] Martin Malina updated JBIDE-23645: ---------------------------------- Description: org.jboss.tools.ui.bot.ext is an old and unmaintained test library. We should find out if/what tests still use it and fix those and ultimately remove bot.ext. https://github.com/jbosstools/jbosstools-integration-tests/tree/master/pl... This was previously discussed in JBIDE-23593 where I found the following tests that still use bot.ext. I found out that some tests still use bot.ext: {code} $ find . -iname 'manifest.mf' -path '*/META-INF/*'|xargs grep 'ui\.bot\.ext'|sed 's/:.*//'|uniq ./plugins/org.jboss.tools.jst.ui.bot/META-INF/MANIFEST.MF ./plugins/org.jboss.tools.ui.bot.ext/META-INF/MANIFEST.MF ./tests/org.jboss.tools.portlet.ui.bot.test/META-INF/MANIFEST.MF ./tests/org.jboss.tools.seam.ui.bot.test/META-INF/MANIFEST.MF ./tests/org.jboss.tools.ws.ui.bot.test/META-INF/MANIFEST.MF {code} was: org.jboss.tools.ui.bot.ext is an old and unmaintained test library. We should find out if/what tests still use it and fix those and ultimately remove bot.ext. https://github.com/jbosstools/jbosstools-integration-tests/tree/master/pl... > Remove org.jboss.tools.ui.bot.ext from integration tests > -------------------------------------------------------- > > Key: JBIDE-23645 > URL: https://issues.jboss.org/browse/JBIDE-23645 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: integration-tests > Affects Versions: 4.4.3.AM1 > Reporter: Martin Malina > Assignee: Martin Malina > > org.jboss.tools.ui.bot.ext is an old and unmaintained test library. We should find out if/what tests still use it and fix those and ultimately remove bot.ext. > https://github.com/jbosstools/jbosstools-integration-tests/tree/master/pl... > This was previously discussed in JBIDE-23593 where I found the following tests that still use bot.ext. > I found out that some tests still use bot.ext: > {code} > $ find . -iname 'manifest.mf' -path '*/META-INF/*'|xargs grep 'ui\.bot\.ext'|sed 's/:.*//'|uniq > ./plugins/org.jboss.tools.jst.ui.bot/META-INF/MANIFEST.MF > ./plugins/org.jboss.tools.ui.bot.ext/META-INF/MANIFEST.MF > ./tests/org.jboss.tools.portlet.ui.bot.test/META-INF/MANIFEST.MF > ./tests/org.jboss.tools.seam.ui.bot.test/META-INF/MANIFEST.MF > ./tests/org.jboss.tools.ws.ui.bot.test/META-INF/MANIFEST.MF > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23645) Remove org.jboss.tools.ui.bot.ext from integration tests

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23645?page=com.atlassian.jira.plugi... ] Martin Malina updated JBIDE-23645: ---------------------------------- Parent: JBIDE-23567 Issue Type: Sub-task (was: Task) > Remove org.jboss.tools.ui.bot.ext from integration tests > -------------------------------------------------------- > > Key: JBIDE-23645 > URL: https://issues.jboss.org/browse/JBIDE-23645 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: integration-tests > Affects Versions: 4.4.3.AM1 > Reporter: Martin Malina > Assignee: Martin Malina > > org.jboss.tools.ui.bot.ext is an old and unmaintained test library. We should find out if/what tests still use it and fix those and ultimately remove bot.ext. > https://github.com/jbosstools/jbosstools-integration-tests/tree/master/pl... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23645) Remove org.jboss.tools.ui.bot.ext from integration tests

by Martin Malina (JIRA)

Martin Malina created JBIDE-23645: ------------------------------------- Summary: Remove org.jboss.tools.ui.bot.ext from integration tests Key: JBIDE-23645 URL: https://issues.jboss.org/browse/JBIDE-23645 Project: Tools (JBoss Tools) Issue Type: Task Components: integration-tests Affects Versions: 4.4.3.AM1 Reporter: Martin Malina Assignee: Martin Malina org.jboss.tools.ui.bot.ext is an old and unmaintained test library. We should find out if/what tests still use it and fix those and ultimately remove bot.ext. https://github.com/jbosstools/jbosstools-integration-tests/tree/master/pl... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 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 December 2016