January 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-18872) Promote JBoss Tools CAT in JBT/JBDS About box

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18872?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-18872: ---------------------------------------- Fix Version/s: 4.2.3.Final (was: 4.2.2.Final) moving of to 4.2.3 > Promote JBoss Tools CAT in JBT/JBDS About box > --------------------------------------------- > > Key: JBIDE-18872 > URL: https://issues.jboss.org/browse/JBIDE-18872 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: central > Affects Versions: 4.2.0.Final > Reporter: Vlado Pakan > Fix For: 4.2.3.Final > > > Would be nice to put link to JBT CAT or JBT CAT logo with link to it to JBDS/JBT About box to make JBT CAT more visible. > New link/image should be visible without resizing About box -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3303) [unit test] versionwatch should not fail silently when the report is empty

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3303?page=com.atlassian.jira.plugin.... ] Nick Boldt edited comment on JBDS-3303 at 1/8/15 11:50 AM: ----------------------------------------------------------- Jobs updated to use jbdevstudio fork and master branch, rather than my test fork. Output now includes both the *Results* tables filtered for just the release versions we want (one for all the IUs including upstream eclipse stuff, one for just JBoss stuff), and also a summary *Report*. Here are some examples: *master branch, comparing 8 and 9:* https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/devstudio.versionwat... http://download.jboss.org/jbosstools/builds/staging/devstudio.versionwatc... http://download.jboss.org/jbosstools/builds/staging/devstudio.versionwatc... http://download.jboss.org/jbosstools/builds/staging/devstudio.versionwatc... http://download.jboss.org/jbosstools/builds/staging/devstudio.versionwatc... *8.0.luna branch, comparing 7 and 8:* https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/devstudio.versionwat... http://download.jboss.org/jbosstools/builds/staging/devstudio.versionwatc... http://download.jboss.org/jbosstools/builds/staging/devstudio.versionwatc... http://download.jboss.org/jbosstools/builds/staging/devstudio.versionwatc... http://download.jboss.org/jbosstools/builds/staging/devstudio.versionwatc... Note that the jobs are now yellow when there are errors in the reports, so we know when things are not clean. Red means the build failed. was (Author: nickboldt): Jobs updated to use jbdevstudio fork and master branch, rather than my test fork. Output now includes both the *Results* tables filtered for just the release versions we want (one for all the IUs including upstream eclipse stuff, one for just JBoss stuff), and also a summary *Report*. Here are some examples: *master branch, comparing 8 and 9:* http://download.jboss.org/jbosstools/builds/staging/devstudio.versionwatc... http://download.jboss.org/jbosstools/builds/staging/devstudio.versionwatc... http://download.jboss.org/jbosstools/builds/staging/devstudio.versionwatc... http://download.jboss.org/jbosstools/builds/staging/devstudio.versionwatc... *8.0.luna branch, comparing 7 and 8:* http://download.jboss.org/jbosstools/builds/staging/devstudio.versionwatc... http://download.jboss.org/jbosstools/builds/staging/devstudio.versionwatc... http://download.jboss.org/jbosstools/builds/staging/devstudio.versionwatc... http://download.jboss.org/jbosstools/builds/staging/devstudio.versionwatc... Note that the jobs are now yellow when there are errors in the reports, so we know when things are not clean. Red means the build failed. > [unit test] versionwatch should not fail silently when the report is empty > -------------------------------------------------------------------------- > > Key: JBDS-3303 > URL: https://issues.jboss.org/browse/JBDS-3303 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: build > Affects Versions: 8.0.1.GA > Reporter: Nick Boldt > Assignee: Nick Boldt > > versionwatch should not fail silently when the report is empty, such as: > {code} > JBDS Version Watch > Feature list for filter = .*(hibernate\|jboss\|xulrunner).* > Plugin list for filter = .*(hibernate\|jboss\|xulrunner).* > Generated by VersionWatch 0.3.0 in 0 min, 4 sec at 2014-12-14 20:19:34.853. > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3289) JBoss Central proxy wizards need to recognize early access.

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBDS-3289?page=com.atlassian.jira.plugin.... ] Fred Bricon commented on JBDS-3289: ----------------------------------- The list of connectors is cached in the context of the tab. The connector discovery mechanism lacks centralized access/caching. Any solution leaning towards accessing connectors state requires non-trivial changes, incompatible with a micro release. And that would also certainly degrade perceived performance as I already mentioned > JBoss Central proxy wizards need to recognize early access. > ----------------------------------------------------------- > > Key: JBDS-3289 > URL: https://issues.jboss.org/browse/JBDS-3289 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: central > Affects Versions: 8.0.2.GA > Reporter: Paul Leacu > Assignee: Fred Bricon > Priority: Blocker > Fix For: 8.0.2.GA > > Attachments: ea1.png > > > Using a JBoss Central proxy wizard that references an early access feature will install that feature correctly even if the "Early Access Enabled" checkbox is unchecked. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3303) [unit test] versionwatch should not fail silently when the report is empty

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3303?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-3303: ---------------------------------- Jobs updated to use jbdevstudio fork and master branch, rather than my test fork. Output now includes both the *Results* tables filtered for just the release versions we want (one for all the IUs including upstream eclipse stuff, one for just JBoss stuff), and also a summary *Report*. Here are some examples: *master branch, comparing 8 and 9:* http://download.jboss.org/jbosstools/builds/staging/devstudio.versionwatc... http://download.jboss.org/jbosstools/builds/staging/devstudio.versionwatc... http://download.jboss.org/jbosstools/builds/staging/devstudio.versionwatc... http://download.jboss.org/jbosstools/builds/staging/devstudio.versionwatc... *8.0.luna branch, comparing 7 and 8:* http://download.jboss.org/jbosstools/builds/staging/devstudio.versionwatc... http://download.jboss.org/jbosstools/builds/staging/devstudio.versionwatc... http://download.jboss.org/jbosstools/builds/staging/devstudio.versionwatc... http://download.jboss.org/jbosstools/builds/staging/devstudio.versionwatc... Note that the jobs are now yellow when there are errors in the reports, so we know when things are not clean. Red means the build failed. > [unit test] versionwatch should not fail silently when the report is empty > -------------------------------------------------------------------------- > > Key: JBDS-3303 > URL: https://issues.jboss.org/browse/JBDS-3303 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: build > Affects Versions: 8.0.1.GA > Reporter: Nick Boldt > Assignee: Nick Boldt > > versionwatch should not fail silently when the report is empty, such as: > {code} > JBDS Version Watch > Feature list for filter = .*(hibernate\|jboss\|xulrunner).* > Plugin list for filter = .*(hibernate\|jboss\|xulrunner).* > Generated by VersionWatch 0.3.0 in 0 min, 4 sec at 2014-12-14 20:19:34.853. > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18948) Include new jbosstools-javaee/batch component into aggregated update site

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18948?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-18948: ------------------------------------ OK, I'll put a PR together for this: * *JBT* ** add new feature(s) to aggregate/core/category.xml in Core (this is what's on Marketplace) and General Tools (just another category) ** add new test feature(s) to aggregate/coretests/category.xml * *JBDS* ** add new feature(s) to product/site/category.xml in Core and General Tools ** add new feature(s) to product/features/c.j.d.core.feature/feature.xml so it's installed via the installer OOTB (same for Marketplace) * *Central* ** Nothing to do! > Include new jbosstools-javaee/batch component into aggregated update site > ------------------------------------------------------------------------- > > Key: JBIDE-18948 > URL: https://issues.jboss.org/browse/JBIDE-18948 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build > Reporter: Alexey Kazakov > Assignee: Alexey Kazakov > Priority: Critical > Fix For: 4.3.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18715) Server Adapter: Notification should be shown once the server is started (e.g. EAP, AS...)

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18715?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-18715: ------------------------------------- Summary: Server Adapter: Notification should be shown once the server is started (e.g. EAP, AS...) (was: [Openshift Server Adapter]: Notification should be shown once the server is started (e.g. EAP, AS...)) > Server Adapter: Notification should be shown once the server is started (e.g. EAP, AS...) > ----------------------------------------------------------------------------------------- > > Key: JBIDE-18715 > URL: https://issues.jboss.org/browse/JBIDE-18715 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift, server > Affects Versions: 4.2.0.Final > Reporter: Marián Labuda > Labels: server_adapter > Fix For: 4.3.x > > > Under "server" I mean EAP, AS, WildFly, Tomcat... catridges (server runtimes). > We talked with [~adietish] about having a notification about started server. It would help with application deployment to know, when the server is running and not to check/stare into the console. > Notification should be shown in the bottom right corner and at first it should inform user about server being started and that we are going to inform him/her once the server is started. Second notification would be shown once the server is started. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19008) As a user, I want to delete OpenShift resources

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19008?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-19008: ------------------------------- Fix Version/s: 4.3.0.Beta1 > As a user, I want to delete OpenShift resources > ----------------------------------------------- > > Key: JBIDE-19008 > URL: https://issues.jboss.org/browse/JBIDE-19008 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Reporter: Jeff Cantrill > Labels: openshift_v3 > Fix For: 4.3.0.Beta1 > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14783) Licence for JBoss AS Downloads looks like HTML source

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14783?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-14783: ------------------------------- Component/s: upstream > Licence for JBoss AS Downloads looks like HTML source > ----------------------------------------------------- > > Key: JBIDE-14783 > URL: https://issues.jboss.org/browse/JBIDE-14783 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: runtime-detection, upstream > Affects Versions: 4.1.0.Beta1 > Reporter: Denis Golovin > Assignee: Rob Stryker > Priority: Minor > Fix For: 4.2.2.Final, 4.3.0.Alpha1 > > Attachments: license-3.2.8.SP1.png > > > When JBoss AS 3.2.8.SP1 download is requested from new Runtime Dialog it shows license that looke like this: > !license-3.2.8.SP1.png! -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-161) Should the JBTIS 4.1 target platform include SpringIDE 3.3 instead of 3.2?

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBTIS-161?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBTIS-161: ---------------------------------- Sorry, correction re: last comment... didn't see we were talking about JBTIS 4.1.x / JBDSIS 7.x. In that case: Ideally that should be the same version we have in JBDS 7.x Central, which is 3.4.0.201310051539-RELEASE. > Should the JBTIS 4.1 target platform include SpringIDE 3.3 instead of 3.2? > -------------------------------------------------------------------------- > > Key: JBTIS-161 > URL: https://issues.jboss.org/browse/JBTIS-161 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: target-platform > Affects Versions: 4.1.2 > Reporter: Nick Boldt > Assignee: Paul Leacu > > The version of SpringIDE vetted by QE to be included in JBDS 7 Central is Spring IDE 3.3 [1]. > [1] http://download.jboss.org/jbosstools/updates/requirements/springide/3.3.0... > However, as reported in http://fusesource.com/issues/browse/ECLIPSE-955 Fuse currently depends on Spring IDE 3.2 [2] > [2] https://github.com/jbosstools/jbosstools-integration-stack/blob/master/ta... > This disconnect may cause problems when co-installing SpringIDE 3.3 from JBDS Central and Fuse (which will bring in SpringIDE 3.2 jars). > Therefore, should Central, JBTIS TP 4.1, and Fuse all use the same version of Spring IDE, namely 3.3 instead of 3.2 and 3.3? -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-161) Should the JBTIS 4.1 target platform include SpringIDE 3.3 instead of 3.2?

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBTIS-161?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBTIS-161: ---------------------------------- Fuse should be using the same version as the IS target platform, not something else. And ideally that should be the same version we have in JBDS 8.x Central, which is 3.6.0.201407080615-RELEASE. > Should the JBTIS 4.1 target platform include SpringIDE 3.3 instead of 3.2? > -------------------------------------------------------------------------- > > Key: JBTIS-161 > URL: https://issues.jboss.org/browse/JBTIS-161 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: target-platform > Affects Versions: 4.1.2 > Reporter: Nick Boldt > Assignee: Paul Leacu > > The version of SpringIDE vetted by QE to be included in JBDS 7 Central is Spring IDE 3.3 [1]. > [1] http://download.jboss.org/jbosstools/updates/requirements/springide/3.3.0... > However, as reported in http://fusesource.com/issues/browse/ECLIPSE-955 Fuse currently depends on Spring IDE 3.2 [2] > [2] https://github.com/jbosstools/jbosstools-integration-stack/blob/master/ta... > This disconnect may cause problems when co-installing SpringIDE 3.3 from JBDS Central and Fuse (which will bring in SpringIDE 3.2 jars). > Therefore, should Central, JBTIS TP 4.1, and Fuse all use the same version of Spring IDE, namely 3.3 instead of 3.2 and 3.3? -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 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 January 2015