March 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-21105) Deprecate BIRT

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21105?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-21105: ------------------------------------ [~pleacu] can you comment here if it's OK for us to move Birt out of the JBDS 10 / JBT 4.4 target platforms and into the IS target platforms? > Deprecate BIRT > -------------- > > Key: JBIDE-21105 > URL: https://issues.jboss.org/browse/JBIDE-21105 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: birt, target-platform > Affects Versions: 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.0.Alpha1 > > Attachments: birt-4.5-vs-mars-interim.txt, birt-4.5-vs-mars-interim_summary.txt, birt-depends-on-jetty-deploy-929.png, birt-depends-on-jetty-osgi-boot-929.png, birt-wizard-new-library.png, birt-wizard-new-library__NEON.png, birt-wizards.png, birt-wizards__NEON.png, eclipse-after-birt.png, install-jboss-birt-sites.png, install-jboss-birt-sites__NEON.png, install-jboss-birt.png, install-jboss-birt__NEON.png > > > {quote} > (2015-11-17 11:42:50) kmarmaliykov: nickboldt: I look into neon M3 and see that there is no jetty 9.2.9 there > (2015-11-17 11:43:18) nickboldt: kmarmaliykov: yes, 9.2.9 is from Birt site > (2015-11-17 11:43:21) nickboldt: because Birt needs it > (2015-11-17 11:43:33) nickboldt: but there's no Birt for Neon yet so we have to include the Birt for Mars > (2015-11-17 11:43:37) maxandersen: nickboldt: akazakov: are you talking about having birt in Neon ? > (2015-11-17 11:43:44) maxandersen: afaik birt is dead. > (2015-11-17 11:43:53) maxandersen: won't participate in neon release afaik. > (2015-11-17 11:43:56) nickboldt: maxandersen: so we should remove birt from JBT 4.4? > (2015-11-17 11:44:24) maxandersen: well, check first if birt is actually in neon. if it is not the decision is very easy. > (2015-11-17 11:44:38) akazakov: +1 > (2015-11-17 11:45:36) maxandersen: if it is in, then lets talk options. but if birt requires us to jump through too many hoops its not worth keeping it in. > (2015-11-17 11:45:55) nickboldt: birt 4.5.0.v201506092134 is in Neon from 201511131000 (M3) - http://download.eclipse.org/releases/neon/201511131000/ > (2015-11-17 11:47:08) nickboldt: and there's a newer birt 4.5.0.v201510231925 (same major.minor.service, newer datestamp) in http://download.eclipse.org/birt/update-site/mars-interim/ > {quote} > So, yesterday as part of updates for JBIDE-20976, I pulled a new BIRT mirror here: > http://download.jboss.org/jbosstools/updates/requirements/birt/4.5.0.v201... > But we could also just use the old one from Mars.0: > http://download.jboss.org/jbosstools/updates/requirements/birt/4.5.0.v201... > Or we could remove support for BIRT and its webtools / charting integration entirely from JBT 4.4.0.Alpha1, since as Max says BIRT is at EOL. > *DISCUSS*. > *Alexey Kazakov:* I changed the title from "Remove Birt?" to "Deprecate Birt" as we agreed to deprecate/sunset it for JBDS 10 / JBT 4.4 / Neon. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-3676) BrowserSim cannot start on Azul openjdk (windows)

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3676?page=com.atlassian.jira.plugin.... ] Alexey Kazakov reassigned JBDS-3676: ------------------------------------ Assignee: Ilya Buziuk > BrowserSim cannot start on Azul openjdk (windows) > ------------------------------------------------- > > Key: JBDS-3676 > URL: https://issues.jboss.org/browse/JBDS-3676 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: browsersim > Affects Versions: 9.1.0.CR1 > Reporter: Jan Richter > Assignee: Ilya Buziuk > Labels: havoc > > Running JBDS on Azul OpenJDK 8, Windows 10. > Starting BrowserSim fails with the following error: > {noformat} > BrowserSim has failed to start with the following error: > "To use BrowserSim please install Safari or run BrowserSim with Oracle Java 7u7 and higher." > Also see BrowserSim FAQ. > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21821) JBoss Developer Studio Marketplace Install Breaks Egit in Mars.2

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21821?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-21821: ------------------------------------ Other than your formatting, I think you pasted the same thing I did. :D But we could also test installation from Mars.0 and Mars.1, too. We have automated tests for JBT 4.3.1.CR1 and JBDS 9.1.0.CR1 installation into Mars.0,1,2 here: http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt... I could set up the same for 4.3.0/9.0.0 if we wanted. > JBoss Developer Studio Marketplace Install Breaks Egit in Mars.2 > ---------------------------------------------------------------- > > Key: JBIDE-21821 > URL: https://issues.jboss.org/browse/JBIDE-21821 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, marketplace > Reporter: Thomas Mäder > Assignee: Nick Boldt > Priority: Blocker > Fix For: 4.3.1.CR1 > > Attachments: FrameworkEvent ERROR.txt, jbt-error, jgit40_41_JBDS.installed.txt, jgit40_41_JBT.installed.txt > > > Installing Red Hat JBoss Developer Studio 9.0.0GA into a fresh Eclipse 4.5.2 (for Eclipse Committers) causes Egit to break. > # Install Eclipse 4.5.2 > # In the Marketplace, search for "jboss developer studio" > # You get a single result: Red Hat JBoss Developer Studio 9.0.0 GA > # Install it > # Restart > # Observe: the EGit views and preferences are missing > # Observe: you get messages in the Eclipse error log concerning a dependency version incompatibility -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-3643) Installer - Should display a unique build identifier

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3643?page=com.atlassian.jira.plugin.... ] Alexey Kazakov updated JBDS-3643: --------------------------------- Fix Version/s: 9.1.0.CR1 > Installer - Should display a unique build identifier > ----------------------------------------------------- > > Key: JBDS-3643 > URL: https://issues.jboss.org/browse/JBDS-3643 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 9.1.0.GA > Reporter: Len DiMaggio > Assignee: Joshua Wilson > Labels: havoc, ui > Fix For: 9.1.0.CR1 > > > This affects QE immediately, and may affect customers too. The installer UI should display a unique identifier (version number). Having a build number displayed in the UI will assist QE in testing as we iterate through the various versions of the installer. Thx! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21839) Cannot connect to Karaf via JMX

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21839?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-21839: -------------------------------------- Assignee: Rob Stryker > Cannot connect to Karaf via JMX > ------------------------------- > > Key: JBIDE-21839 > URL: https://issues.jboss.org/browse/JBIDE-21839 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jmx > Affects Versions: 4.3.1.Beta2 > Environment: JBDS 9.1.0.Beta2 > Reporter: Tomáš Sedmík > Assignee: Rob Stryker > Attachments: out.ogv > > > I'm unable to connect to Apache Karaf runtime via JMX Navigator --> Local Processes (see attached video) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-3621) Installer - if a "Developer-Platform" directory exists - presents a blank white dialog window - no error is logged

by Joshua Wilson (JIRA)

[ https://issues.jboss.org/browse/JBDS-3621?page=com.atlassian.jira.plugin.... ] Joshua Wilson commented on JBDS-3621: ------------------------------------- [~ldimaggio] as I said that should not go in this bug report. > Installer - if a "Developer-Platform" directory exists - presents a blank white dialog window - no error is logged > ------------------------------------------------------------------------------------------------------------------ > > Key: JBDS-3621 > URL: https://issues.jboss.org/browse/JBDS-3621 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Reporter: Len DiMaggio > Assignee: Joshua Wilson > Labels: havoc > Fix For: 9.1.0.CR1 > > Attachments: Screenshot (24).png > > > See attached screenshot - if there is an existing Developer-Platform directory - the installer presents the blank white dialog. No error message is logged or displayed for the user. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-3621) Installer - if a "Developer-Platform" directory exists - presents a blank white dialog window - no error is logged

by Joshua Wilson (JIRA)

[ https://issues.jboss.org/browse/JBDS-3621?page=com.atlassian.jira.plugin.... ] Joshua Wilson commented on JBDS-3621: ------------------------------------- If you are talking about letting the user change location, that would be a new jira. This is a bug fix and that would be a new feature. > Installer - if a "Developer-Platform" directory exists - presents a blank white dialog window - no error is logged > ------------------------------------------------------------------------------------------------------------------ > > Key: JBDS-3621 > URL: https://issues.jboss.org/browse/JBDS-3621 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Reporter: Len DiMaggio > Assignee: Joshua Wilson > Labels: havoc > Fix For: 9.1.0.CR1 > > Attachments: Screenshot (24).png > > > See attached screenshot - if there is an existing Developer-Platform directory - the installer presents the blank white dialog. No error message is logged or displayed for the user. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-3674) Find location where to keep archives with FOSS downloaded/bundled by installer

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3674?page=com.atlassian.jira.plugin.... ] Alexey Kazakov updated JBDS-3674: --------------------------------- Fix Version/s: 9.1.0.CR1 (was: 9.1.0.Beta2) > Find location where to keep archives with FOSS downloaded/bundled by installer > ------------------------------------------------------------------------------ > > Key: JBDS-3674 > URL: https://issues.jboss.org/browse/JBDS-3674 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Components: installer > Affects Versions: 9.1.0.Beta2 > Reporter: Denis Golovin > Assignee: Denis Golovin > Priority: Blocker > Labels: havoc > Fix For: 9.1.0.CR1 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-3621) Installer - if a "Developer-Platform" directory exists - presents a blank white dialog window - no error is logged

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBDS-3621?page=com.atlassian.jira.plugin.... ] Len DiMaggio commented on JBDS-3621: ------------------------------------ And...provide the user with the ability to overwrite an existing installation too. ;-) > Installer - if a "Developer-Platform" directory exists - presents a blank white dialog window - no error is logged > ------------------------------------------------------------------------------------------------------------------ > > Key: JBDS-3621 > URL: https://issues.jboss.org/browse/JBDS-3621 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Reporter: Len DiMaggio > Assignee: Joshua Wilson > Labels: havoc > Fix For: 9.1.0.CR1 > > Attachments: Screenshot (24).png > > > See attached screenshot - if there is an existing Developer-Platform directory - the installer presents the blank white dialog. No error message is logged or displayed for the user. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-3621) Installer - if a "Developer-Platform" directory exists - presents a blank white dialog window - no error is logged

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3621?page=com.atlassian.jira.plugin.... ] Denis Golovin commented on JBDS-3621: ------------------------------------- Current implementation is just using c:\DeveloperPlatform as target location. We should let to change default location to different one if user wants to. > Installer - if a "Developer-Platform" directory exists - presents a blank white dialog window - no error is logged > ------------------------------------------------------------------------------------------------------------------ > > Key: JBDS-3621 > URL: https://issues.jboss.org/browse/JBDS-3621 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Reporter: Len DiMaggio > Assignee: Joshua Wilson > Labels: havoc > Fix For: 9.1.0.CR1 > > Attachments: Screenshot (24).png > > > See attached screenshot - if there is an existing Developer-Platform directory - the installer presents the blank white dialog. No error message is logged or displayed for the user. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

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