July 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-20176) Webtools server adapter shows "null" for company/organization name for JBoss

by Len DiMaggio (JIRA)

Len DiMaggio created JBIDE-20176: ------------------------------------ Summary: Webtools server adapter shows "null" for company/organization name for JBoss Key: JBIDE-20176 URL: https://issues.jboss.org/browse/JBIDE-20176 Project: Tools (JBoss Tools) Issue Type: Bug Components: server Affects Versions: 4.3.0.Beta1 Reporter: Len DiMaggio See the attached (annotated) screenshot. Why are we "null?" -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20120) Batch.xml references are not considered in editor

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20120?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-20120: ----------------------------------- Fix Version/s: 4.3.0.Beta2 > Batch.xml references are not considered in editor > ------------------------------------------------- > > Key: JBIDE-20120 > URL: https://issues.jboss.org/browse/JBIDE-20120 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: batch > Affects Versions: 4.3.0.Beta1 > Reporter: Lucia Jelinkova > Assignee: Viacheslav Kabanovich > Fix For: 4.3.0.Beta2 > > Attachments: job-listener-suggestions.png, job-listener-validation.png > > > I created 2 job listeners - one with \@Named annotation and one with reference in META-INF/batch.xml file. > When I invoke content assist, the one from batch.xml file is not referenced by its id but a full class name is suggested instead. > Also, when I type the id from the batch.xml file manually, it is not recognized. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20120) Batch.xml references are not considered in editor

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20120?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-20120: ---------------------------------------- We do not support batch.xml files yet. > Batch.xml references are not considered in editor > ------------------------------------------------- > > Key: JBIDE-20120 > URL: https://issues.jboss.org/browse/JBIDE-20120 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: batch > Affects Versions: 4.3.0.Beta1 > Reporter: Lucia Jelinkova > Assignee: Viacheslav Kabanovich > Attachments: job-listener-suggestions.png, job-listener-validation.png > > > I created 2 job listeners - one with \@Named annotation and one with reference in META-INF/batch.xml file. > When I invoke content assist, the one from batch.xml file is not referenced by its id but a full class name is suggested instead. > Also, when I type the id from the batch.xml file manually, it is not recognized. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20173) Clean up UI errors in case RSE is not installed

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20173?page=com.atlassian.jira.plugi... ] Rob Stryker resolved JBIDE-20173. --------------------------------- Assignee: Rob Stryker Resolution: Done More prominent error messaging, UI doesn't NPE, start and stop actions fail to enable, all-in-all, looks much better. > Clean up UI errors in case RSE is not installed > ----------------------------------------------- > > Key: JBIDE-20173 > URL: https://issues.jboss.org/browse/JBIDE-20173 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: server > Affects Versions: 4.3.0.Beta1 > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.3.0.Beta2 > > > In an environment where RSE is not available, the UI fails in multiple fashions. It allows you to create RSE servers, even though it shouldn't. If there's a previously-existing RSE server, the server editor will fail to load with NPE. There is also no warning in the editor anywhere indicating that the server is incompatible with current profile. > Also, start / debug / etc should fail indicating profile is unavailable. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20120) Batch.xml references are not considered in editor

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20120?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-20120: -------------------------------------- Assignee: Viacheslav Kabanovich > Batch.xml references are not considered in editor > ------------------------------------------------- > > Key: JBIDE-20120 > URL: https://issues.jboss.org/browse/JBIDE-20120 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: batch > Affects Versions: 4.3.0.Beta1 > Reporter: Lucia Jelinkova > Assignee: Viacheslav Kabanovich > Attachments: job-listener-suggestions.png, job-listener-validation.png > > > I created 2 job listeners - one with \@Named annotation and one with reference in META-INF/batch.xml file. > When I invoke content assist, the one from batch.xml file is not referenced by its id but a full class name is suggested instead. > Also, when I type the id from the batch.xml file manually, it is not recognized. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20119) Restartable attribute of job element should restrict values

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20119?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-20119: ----------------------------------- Issue Type: Enhancement (was: Bug) > Restartable attribute of job element should restrict values > ----------------------------------------------------------- > > Key: JBIDE-20119 > URL: https://issues.jboss.org/browse/JBIDE-20119 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: batch > Affects Versions: 4.3.0.Beta1 > Reporter: Lucia Jelinkova > Assignee: Viacheslav Kabanovich > Fix For: 4.3.0.Beta2 > > > At the moment, there is no validation for restartable attribute of job element. According to specification, if specified, only "true" and "false" values are allowed. > _Specifies whether or not this job is restartable . It must specify true or false. This is an optional attribute. The default is true._ > Also, content assist should suggest these values. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20119) Restartable attribute of job element should restrict values

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20119?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-20119: ----------------------------------- Fix Version/s: 4.3.0.Beta2 > Restartable attribute of job element should restrict values > ----------------------------------------------------------- > > Key: JBIDE-20119 > URL: https://issues.jboss.org/browse/JBIDE-20119 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: batch > Affects Versions: 4.3.0.Beta1 > Reporter: Lucia Jelinkova > Fix For: 4.3.0.Beta2 > > > At the moment, there is no validation for restartable attribute of job element. According to specification, if specified, only "true" and "false" values are allowed. > _Specifies whether or not this job is restartable . It must specify true or false. This is an optional attribute. The default is true._ > Also, content assist should suggest these values. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20119) Restartable attribute of job element should restrict values

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20119?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-20119: -------------------------------------- Assignee: Viacheslav Kabanovich > Restartable attribute of job element should restrict values > ----------------------------------------------------------- > > Key: JBIDE-20119 > URL: https://issues.jboss.org/browse/JBIDE-20119 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: batch > Affects Versions: 4.3.0.Beta1 > Reporter: Lucia Jelinkova > Assignee: Viacheslav Kabanovich > Fix For: 4.3.0.Beta2 > > > At the moment, there is no validation for restartable attribute of job element. According to specification, if specified, only "true" and "false" values are allowed. > _Specifies whether or not this job is restartable . It must specify true or false. This is an optional attribute. The default is true._ > Also, content assist should suggest these values. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20100) how to make users aware of fuse and other tooling only being available from earlyaccess?

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20100?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-20100: ---------------------------------------- A new user reported me that going to click on "Enable Early-Access" is not something he'd do by himself. The idea is that they would enable early-access is they know it's worth it, and in order to show whether it's worth it or not, we should show all connectors (even early-access ones). Then if users selects an Early-Access connector, we can show the warning. In case a connector exists in both Early-Access and regular shape, we should only enable the checkbox of the one that is relevant at that time. Overall, the principle is to show everything, but not enable everything. > how to make users aware of fuse and other tooling only being available from earlyaccess? > ----------------------------------------------------------------------------------------- > > Key: JBIDE-20100 > URL: https://issues.jboss.org/browse/JBIDE-20100 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Reporter: Max Rydahl Andersen > Assignee: Mickael Istria > > [~jtyrrell] find it confusing when he cannot see Fuse and other earlyaccess features immediately on the install page. > Some comments: > "I install JBDS 8.1 and click on the JBoss Integration and SOA Development, but where is the Fuse tooling in that list." > "<without earlyaccess> why doesn’t my screen shot tell me to use an older version of JBDS or something." > Suggestion: > "when I picked the Integration Stack a greyed out Fuse IDE thingy in the list of choices, and something like (Select early Access) to enable this feature." > I'm fine exploring options to show early access features more prominently but would prefer we would not need to treat Fuse "special" so maybe we should have a "Early Access" section at the bottom instead of filtered in between everything else ? > and for any connectors that has additional/different features just add a "Extra features available in Early access " comment ? > But what to do when Fuse or others dont even have an earlyaccess out yet ? (like is currently the state for devstudio 9) > [~crobson], [~aileenc] and [~lhein] got any suggestions ? -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20171) buildinfo.json reader fails if upstream MANIFEST.MF contains no SHA

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20171?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-20171: ---------------------------------- Assignee: Max Rydahl Andersen (was: Nick Boldt) > buildinfo.json reader fails if upstream MANIFEST.MF contains no SHA > ------------------------------------------------------------------- > > Key: JBIDE-20171 > URL: https://issues.jboss.org/browse/JBIDE-20171 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build > Affects Versions: 4.3.0.Beta2 > Reporter: Nick Boldt > Assignee: Max Rydahl Andersen > Fix For: 4.3.0.Beta2 > > > Since the addition of a check that verifies exactly this condition: > https://github.com/jbosstools/jbosstools-maven-plugins/commit/916f4521ba6... > I've now got a situation where it's OK to have no SHA in the MANIFEST.MF, but a SHA in buildinfo.json. > {code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-build-sites.aggregate.site_master/10216/console} > [ERROR] Failed to execute goal org.jboss.tools.tycho-plugins:repository-utils:0.22.1-SNAPSHOT:fetch-sources-from-manifests (fetch-sources) on project org.jboss.tools.site.core: Problem occurred checking upstream buildinfo.json files! > [ERROR] /mnt/hudson_workspace/workspace/jbosstools-build-sites.aggregate.site_master/sources/aggregate/site/target/buildinfo/buildinfo_jbosstools-xulrunner.json > [ERROR] contains 2edce933f7d64efbb4d7a5b16be8dadae8de766e, but upstream project's MANIFEST.MF has Eclipse-SourceReferences > [ERROR] commitId . > [ERROR] If you have locally built projects which are aggregated here, > [ERROR] ensure they are built from the latest SHA from HEAD, not a local topic branch. > [ERROR] Or, use -DskipCheckSHAs=true to bypass this check. > [ERROR] -> [Help 1]{code} > This happened after I put a buildinfo.json file here: > http://download.jboss.org/jbosstools/updates/requirements/xulrunner-1.9.2... > I've since moved the file here to temporarily work around the build failure: > http://download.jboss.org/jbosstools/updates/requirements/xulrunner-1.9.2... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

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