September 2016 - jbosstools-issues

[JBoss JIRA] (JBTIS-917) Update teiidUser groups in tests

by stanislav kaleta (JIRA)

[ https://issues.jboss.org/browse/JBTIS-917?page=com.atlassian.jira.plugin.... ] stanislav kaleta updated JBTIS-917: ----------------------------------- Git Pull Request: https://github.com/jbosstools/jbosstools-integration-stack-tests/pull/808 (was: https://issues.jboss.org/browse/JBTIS-917) > Update teiidUser groups in tests > -------------------------------- > > Key: JBTIS-917 > URL: https://issues.jboss.org/browse/JBTIS-917 > Project: JBoss Tools Integration Stack > Issue Type: Enhancement > Components: QE, teiid > Affects Versions: 4.3.1.Final > Reporter: stanislav kaleta > Assignee: Andrej Podhradsky > Fix For: 4.3.2.CR1 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23211) JS Alert popups are not disabled on Windows

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23211?page=com.atlassian.jira.plugi... ] Ilya Buziuk updated JBIDE-23211: -------------------------------- Fix Version/s: 4.4.x > JS Alert popups are not disabled on Windows > ------------------------------------------- > > Key: JBIDE-23211 > URL: https://issues.jboss.org/browse/JBIDE-23211 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: visual-page-editor-core > Affects Versions: 4.4.1.Final > Reporter: Rastislav Wagner > Assignee: Ilya Buziuk > Fix For: 4.4.x > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23211) JS Alert popups are not disabled on Windows

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23211?page=com.atlassian.jira.plugi... ] Ilya Buziuk reassigned JBIDE-23211: ----------------------------------- Assignee: Ilya Buziuk > JS Alert popups are not disabled on Windows > ------------------------------------------- > > Key: JBIDE-23211 > URL: https://issues.jboss.org/browse/JBIDE-23211 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: visual-page-editor-core > Affects Versions: 4.4.1.Final > Reporter: Rastislav Wagner > Assignee: Ilya Buziuk > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23068) Unknown extension points and bundles can't be resolved in jbt-base and jbt-server

by Dmitrii Bocharov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23068?page=com.atlassian.jira.plugi... ] Dmitrii Bocharov updated JBIDE-23068: ------------------------------------- Fix Version/s: 4.4.2.Final (was: 4.4.x) > Unknown extension points and bundles can't be resolved in jbt-base and jbt-server > --------------------------------------------------------------------------------- > > Key: JBIDE-23068 > URL: https://issues.jboss.org/browse/JBIDE-23068 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform > Reporter: Dmitrii Bocharov > Assignee: Dmitrii Bocharov > Fix For: 4.4.2.Final > > Attachments: magic_error_disapperance.webm > > > Builds in terminal (mvn clean install) run successfully. However in eclipse i have 3 errors for jjbt-base and 3 for jbt-server: > jbt-base: > Unknown extension point: 'org.eclipse.mylyn.tasks.bugs.support' in /org.jboss.tools.common.mylyn > Unknown extension point: 'org.eclipse.mylyn.tasks.core.templates' in /org.jboss.tools.common.mylyn > Unknown extension point: 'org.eclipse.ui.activities' plugin.xml in /org.jboss.tools.common.model.ui.capabilities > jbt-server: > Bundle 'org.jboss.ide.eclipse.as.management.eap61plus' cannot be resolved in /org.jboss.tools.as.management.itests/META-INF > Unknown extension point: 'org.eclipse.help.contexts' in /org.jboss.ide.eclipse.as.doc.user > Unknown extension point: 'org.eclipse.help.toc' in /org.jboss.ide.eclipse.as.doc.user > [dbocharo@dbocharo jbosstools-target-platforms]$ git pull upstream 4.60.x > From https://github.com/jbosstools/jbosstools-target-platforms > * branch 4.60.x -> FETCH_HEAD > Already up-to-date. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23274) Rename of batch artefact should affect batch.xml file

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23274?page=com.atlassian.jira.plugi... ] Ondrej Dockal updated JBIDE-23274: ---------------------------------- Issue Type: Enhancement (was: Feature Request) > Rename of batch artefact should affect batch.xml file > ----------------------------------------------------- > > Key: JBIDE-23274 > URL: https://issues.jboss.org/browse/JBIDE-23274 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: batch > Affects Versions: 4.4.2.AM1 > Reporter: Lukáš Valach > Assignee: Alexey Kazakov > Fix For: 4.5.x > > Attachments: BatchRenameManualTest.zip > > > There are three ways how to refer batch artefact in job.xml file. > * Using @Name annotation > * Using fully qualified class name > * Using batch.xml > I noticed that the class name is not changed in batch.xml file during refactoring and the job.xml file become invalid for this reason. > There is a way how to avoid this problem. User can check the "Update fully qualified names in non-Java text files" option in Rename window, but this solution is not intuitive/is not user friendly I think. > In another case, when I don't use batch.xml and use the name comming from @Named annotation. The artefact is renamed in job.xml file even if the "Update fully qualified names in non-Java text files" option aren't selected. Non-Java text file (job.xml) is updated automatically in this case. > There is attached project that you can use to reproduce this problem. > [^BatchRenameManualTest.zip]. Just try to rename Writer class. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23275) Rename doesn't change fully qualified name in job.xml file

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23275?page=com.atlassian.jira.plugi... ] Ondrej Dockal updated JBIDE-23275: ---------------------------------- Priority: Minor (was: Major) > Rename doesn't change fully qualified name in job.xml file > ---------------------------------------------------------- > > Key: JBIDE-23275 > URL: https://issues.jboss.org/browse/JBIDE-23275 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: batch > Affects Versions: 4.4.2.AM1 > Environment: Fedora 24 > Reporter: Lukáš Valach > Priority: Minor > Fix For: 4.5.x > > Attachments: BatchRenameManualTest.zip > > > Refactoring doesn't modify job.xml when I renaming class which is referred in job.xml using the fully qualified name. > For example, when I have batchlet class > {code:java} > package test; > public class BatchletWithProperty extends AbstractBatchlet { > ... > } > {code} > ...and job.xml > {code:xml} > <job ...> > <step id="step1"> > <batchlet ref="test.BatchletWithProperty">  > ... > </batchlet> > </step> > ... > </job> > {code} > ...then, when I try to rename test.BatchletWithProperty the refactoring doesn't change fully qualified name in job.xml. > Renaming works properly when I refer to class using name coming from @Named annotation. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23275) Rename doesn't change fully qualified name in job.xml file

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23275?page=com.atlassian.jira.plugi... ] Ondrej Dockal updated JBIDE-23275: ---------------------------------- Priority: Major (was: Minor) > Rename doesn't change fully qualified name in job.xml file > ---------------------------------------------------------- > > Key: JBIDE-23275 > URL: https://issues.jboss.org/browse/JBIDE-23275 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: batch > Affects Versions: 4.4.2.AM1 > Environment: Fedora 24 > Reporter: Lukáš Valach > Fix For: 4.5.x > > Attachments: BatchRenameManualTest.zip > > > Refactoring doesn't modify job.xml when I renaming class which is referred in job.xml using the fully qualified name. > For example, when I have batchlet class > {code:java} > package test; > public class BatchletWithProperty extends AbstractBatchlet { > ... > } > {code} > ...and job.xml > {code:xml} > <job ...> > <step id="step1"> > <batchlet ref="test.BatchletWithProperty">  > ... > </batchlet> > </step> > ... > </job> > {code} > ...then, when I try to rename test.BatchletWithProperty the refactoring doesn't change fully qualified name in job.xml. > Renaming works properly when I refer to class using name coming from @Named annotation. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23278) Validation of class reference in job.xml produces false-positive warning

by Lukáš Valach (JIRA)

Lukáš Valach created JBIDE-23278: ------------------------------------ Summary: Validation of class reference in job.xml produces false-positive warning Key: JBIDE-23278 URL: https://issues.jboss.org/browse/JBIDE-23278 Project: Tools (JBoss Tools) Issue Type: Bug Components: batch Affects Versions: 4.4.2.AM1 Environment: Fedora 24 Reporter: Lukáš Valach Attachments: BatchRenameManualTest.zip, Rename-Warning.png When I refer to some class using fully qualified name and that class is annotated by @Named or is mentioned in bean.xml, then the eclipse shows warning "Item ... not found." although class exists and code is valid (test passes). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4059) RPM errors: Installing rh-eclipse46-devstudio.10.1 into rh-eclipse46 beta.

by Václav Kadlčík (JIRA)

[ https://issues.jboss.org/browse/JBDS-4059?page=com.atlassian.jira.plugin.... ] Václav Kadlčík commented on JBDS-4059: -------------------------------------- Thanks for working on the issue. I checked rh-eclipse46-devstudio-10.2-0.20160930.0121.el7.x86_64.rpm; all fine except libnotify.so.1 (needed for .../org.mozilla.xulrunner.gtk.linux.x86_64_1.9.2.19pre/xulrunner/components/libmozgnome.so). As I wrote a week ago, libnotify.so.1 cannot be resolved in RHEL 7. I believe that Eclipse wouldn't load that libmozgnome.so. I see two possibilities: 1. Maybe libmozgnome.so is dead code and I'd be happy to add the reference to libnotify.so.1 as a known false positive (though cutting the dead code out would be better). 2. Maybe it's not dead; then libmozgnome.so would need to be fixed somehow - supplemented with libnotify.so.1 or rebuilt against libnotify.so.4 etc. Please look into this specific problem. I'd like to reopen this issue but I don't see how, maybe I'm missing permissions? > RPM errors: Installing rh-eclipse46-devstudio.10.1 into rh-eclipse46 beta. > -------------------------------------------------------------------------- > > Key: JBDS-4059 > URL: https://issues.jboss.org/browse/JBDS-4059 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: build > Reporter: Pavol Srna > Assignee: Nick Boldt > Fix For: 10.2.0.AM2 > > > [~vkadlcik] has run some rpm sanity tests. The findings can be seen here: http://nest.test.redhat.com/mnt/qa/scratch/bkr-hv03-guest19/2016:24366/tp... > [~nickboldt] can you please investigate? Thanks! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23192) For JBIDE 4.4.2.AM1: Prepare for 4.4.2.AM1 / 10.2.0.AM1 [Hibernate]

by Rastislav Wagner (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23192?page=com.atlassian.jira.plugi... ] Rastislav Wagner closed JBIDE-23192. ------------------------------------ > For JBIDE 4.4.2.AM1: Prepare for 4.4.2.AM1 / 10.2.0.AM1 [Hibernate] > ------------------------------------------------------------------- > > Key: JBIDE-23192 > URL: https://issues.jboss.org/browse/JBIDE-23192 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: hibernate > Reporter: Friendly Jira Robot > Assignee: Jeff MAURY > Priority: Blocker > Labels: task > Fix For: 4.4.2.AM1 > > > For JBIDE 4.4.2.AM1 [Hibernate]: Please perform the following tasks: > 1. Check out your existing *{color:orange}master{color}* branch: > {code} > git checkout master > {code} > 2. Update your *{color:orange}master branch{color}* root pom to use the latest parent pom version, *{color:orange}4.4.2.AM1-SNAPSHOT{color}*: > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.4.2.AM1-SNAPSHOT</version> > </parent> > {code} > Now, your root pom will use parent pom version: > * *{color:orange}4.4.2.AM1-SNAPSHOT{color}* in your *{color:orange}master{color}* branch > 3. Ensure that component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1. > {code} > mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.25.0:set-version -DnewVersion=1.0.1-SNAPSHOT > {code} > 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.60.1.Final > {code} > mvn clean verify -Dtpc.version=4.60.1.Final > {code} > 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.60.1.Final > {code} > mvn clean verify -Dtpc.version=4.60.1.Final > {code} > 5. Close (do not resolve) this JIRA when done. > 6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] to do, please complete them next. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Hibernate task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

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 September 2016