February 2016 - jbosstools-issues

[JBoss JIRA] (JBIDE-21069) Application wizard: long project display names mess up project selection

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21069?page=com.atlassian.jira.plugi... ] Fred Bricon reassigned JBIDE-21069: ----------------------------------- Assignee: Viacheslav Kabanovich > Application wizard: long project display names mess up project selection > ------------------------------------------------------------------------ > > Key: JBIDE-21069 > URL: https://issues.jboss.org/browse/JBIDE-21069 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Jan Richter > Assignee: Viacheslav Kabanovich > Labels: application_wizard, openshift_v3 > Fix For: 4.4.0.Alpha1 > > > I've created a project with the longest display name OpenShift would let me. Then when I go to the application wizard and try to select a project from the combo, all hell breaks loose. > I'm on Gnome with GTK3 and clicking the combo at this point messes up the entire screen to a point that I can't even take a screenshot (sorry I can't show you, it looks awesome). Looks like something overflowing somewhere. > I also tried a bit shorter name, which just resulted in a selection spanning both my screens and beyond. > I think cutting the text at certain length and just adding '...' or somthing like that might make it look better. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-553) Cannot install Integration Stack from central with: OpenJDK-1.8.0.65, OpenJDK-1.8.0.71

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBTIS-553?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBTIS-553: ---------------------------------- Tried to create a clean site (w/ pack.gz files & correct CRCs) via ant script but every attempt seems to remove some of the original .jars when mirroring, and only takes the .pack.gz artifacts. So, I'm giving up on creating such a script for now. :( But Paul created a site *by hand* w/ fixed CRC here: http://download.jboss.org/jbosstools/updates/requirements/graphiti/S-0.13... which can be used for IS TP creation. > Cannot install Integration Stack from central with: OpenJDK-1.8.0.65, OpenJDK-1.8.0.71 > -------------------------------------------------------------------------------------- > > Key: JBTIS-553 > URL: https://issues.jboss.org/browse/JBTIS-553 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Reporter: Jan Richter > Assignee: Paul Leacu > Priority: Critical > > Trying to install IS from central early access, I'm getting the following error: > {noformat} > An error occurred while collecting items to be installed > session context was:(profile=jbds, phase=org.eclipse.equinox.internal.p2.engine.phases.Collect, operand=, action=). > Problems downloading artifact: osgi.bundle,org.eclipse.graphiti.ui,0.13.0.v20150818-1354. > Unpacking fails because intermediate file is empty: /tmp/work8606338891825741513/p2.optimizers.incoming8698731202719996837.jar > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21643) use rebuilt Birt 1.8.0 or build 1.8.1 (with no changes) ?

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21643?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-21643: ---------------------------------- Assignee: Nick Boldt (was: Snjezana Peco) > use rebuilt Birt 1.8.0 or build 1.8.1 (with no changes) ? > --------------------------------------------------------- > > Key: JBIDE-21643 > URL: https://issues.jboss.org/browse/JBIDE-21643 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: birt, build > Affects Versions: 4.3.1.Beta2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.1.CR1 > > > Since feature freeze is done for Birt 1.8.x in JBT 4.3.1.Beta2, we have two choices for what to include in JBT 4.3.1.CR1 and .Final: > a) since nothing important has happened in the 4.3.x branch [1] of jbosstools-birt, we could re-use the 1.8.0.Final bits, which I've just rebuilt [2] from the 4.3.0.Final tag, and published [3]. > b) or we could upversion the 1.8.1.Beta2 bits to 1.8.1.CR1 (and then later to 1.8.1.Final) even though there's functionally nothing new in there beyond what was released in 1.8.0.Final on Sept 24. > [1] https://github.com/jbosstools/jbosstools-birt/commits/jbosstools-4.3.x > [2] http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-birt_4.3.m... > [3] http://download.jboss.org/jbosstools/mars/stable/updates/core/birt/1.8.0.... > I'm inclined to go with the rebuilt 1.8.0 instead of the needlessly upversioned 1.8.1. > WDYT? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21643) use rebuilt Birt 1.8.0 or build 1.8.1 (with no changes) ?

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21643?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-21643: ------------------------------------ TODO: ensure birt builds & tests pass after updating TP for CR1. No need to republish bits if all tests pass. > use rebuilt Birt 1.8.0 or build 1.8.1 (with no changes) ? > --------------------------------------------------------- > > Key: JBIDE-21643 > URL: https://issues.jboss.org/browse/JBIDE-21643 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: birt, build > Affects Versions: 4.3.1.Beta2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.1.CR1 > > > Since feature freeze is done for Birt 1.8.x in JBT 4.3.1.Beta2, we have two choices for what to include in JBT 4.3.1.CR1 and .Final: > a) since nothing important has happened in the 4.3.x branch [1] of jbosstools-birt, we could re-use the 1.8.0.Final bits, which I've just rebuilt [2] from the 4.3.0.Final tag, and published [3]. > b) or we could upversion the 1.8.1.Beta2 bits to 1.8.1.CR1 (and then later to 1.8.1.Final) even though there's functionally nothing new in there beyond what was released in 1.8.0.Final on Sept 24. > [1] https://github.com/jbosstools/jbosstools-birt/commits/jbosstools-4.3.x > [2] http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-birt_4.3.m... > [3] http://download.jboss.org/jbosstools/mars/stable/updates/core/birt/1.8.0.... > I'm inclined to go with the rebuilt 1.8.0 instead of the needlessly upversioned 1.8.1. > WDYT? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21643) use rebuilt Birt 1.8.0 or build 1.8.1 (with no changes) ?

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21643?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-21643: ------------------------------------ OK, I've updated the parent poms and composite sites to use the stable Birt bits, and have disabled BIRT from the list of projects to send task JIRAs for the next codefreeze. https://github.com/jbosstools/jbosstools-build/blob/master/parent/pom.xml... & https://github.com/jbosstools/jbosstools-build/blob/jbosstools-4.3.x/pare... https://github.com/jbosstools/jbosstools-download.jboss.org/commit/98cf64... (for 4.3.x and master/4.4.x) https://github.com/jbdevstudio/jbdevstudio-ci/commit/c959571dc77999f412a9... > use rebuilt Birt 1.8.0 or build 1.8.1 (with no changes) ? > --------------------------------------------------------- > > Key: JBIDE-21643 > URL: https://issues.jboss.org/browse/JBIDE-21643 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: birt, build > Affects Versions: 4.3.1.Beta2 > Reporter: Nick Boldt > Assignee: Snjezana Peco > Fix For: 4.3.1.CR1 > > > Since feature freeze is done for Birt 1.8.x in JBT 4.3.1.Beta2, we have two choices for what to include in JBT 4.3.1.CR1 and .Final: > a) since nothing important has happened in the 4.3.x branch [1] of jbosstools-birt, we could re-use the 1.8.0.Final bits, which I've just rebuilt [2] from the 4.3.0.Final tag, and published [3]. > b) or we could upversion the 1.8.1.Beta2 bits to 1.8.1.CR1 (and then later to 1.8.1.Final) even though there's functionally nothing new in there beyond what was released in 1.8.0.Final on Sept 24. > [1] https://github.com/jbosstools/jbosstools-birt/commits/jbosstools-4.3.x > [2] http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-birt_4.3.m... > [3] http://download.jboss.org/jbosstools/mars/stable/updates/core/birt/1.8.0.... > I'm inclined to go with the rebuilt 1.8.0 instead of the needlessly upversioned 1.8.1. > WDYT? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21625) Server adapter: Enable debug mode on OpenShift servers

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21625?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-21625 at 2/5/16 2:00 PM: ------------------------------------------------------------------ As specificed in CLOUD-243: Enabling debugging in our eap-images works via an env var {code} com.redhat.dev-mode com.redhat.dev-mode.port {code} In [oc|https://docs.openshift.com/enterprise/3.0/dev_guide/environment_variab...] one can do {code} $ oc env <object-selection> KEY_1=VAL_1 ... KEY_N=VAL_N [<set-env-options>] [<common-options>] {code} Those get picked on pod deployment. So we can change the deployment config resource and start for the triggered build to finish or change the number of replicas 1->0->1 {quote} (06:19:17 PM) kconner: adietisheim: The env needs to be set when the pod starts, you may find that modifying the dc will redeploy it {quote} was (Author: adietish): As specificed in CLOUD-243: Enabling debugging in our eap-images works via an env var {code} com.redhat.dev-mode com.redhat.dev-mode.port {code} Those get picked on pod deployment. So we can change the deployment config resource and start for the triggered build to finish or change the number of replicas 1->0->1 {quote} (06:19:17 PM) kconner: adietisheim: The env needs to be set when the pod starts, you may find that modifying the dc will redeploy it {quote} > Server adapter: Enable debug mode on OpenShift servers > ------------------------------------------------------ > > Key: JBIDE-21625 > URL: https://issues.jboss.org/browse/JBIDE-21625 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Reporter: Fred Bricon > Assignee: Andre Dietisheim > Priority: Critical > Labels: openshift_v3, server_adapter > Fix For: 4.3.1.CR1 > > > Need to easily enable debug mode on EAP/Node images. That should allow hot reloading of server.js or java classes -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21625) Server adapter: Enable debug mode on OpenShift servers

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21625?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-21625 at 2/5/16 1:54 PM: ------------------------------------------------------------------ As specificed in CLOUD-243: Enabling debugging in our eap-images works via an env var {code} com.redhat.dev-mode com.redhat.dev-mode.port {code} Those get picked on pod deployment. So we can change the deployment config resource and start for the triggered build to finish or change the number of replicas 1->0->1 {quote} (06:19:17 PM) kconner: adietisheim: The env needs to be set when the pod starts, you may find that modifying the dc will redeploy it {quote} was (Author: adietish): As specificed in CLOUD-243: Enabling debugging in our eap-images works via an env var {code} com.redhat.dev-mode com.redhat.dev-mode.port {code} Those get picked on pod deployment. So we can change the deployment config resource and start for the triggered build to finish or change the number of replicas 1->0->1 > Server adapter: Enable debug mode on OpenShift servers > ------------------------------------------------------ > > Key: JBIDE-21625 > URL: https://issues.jboss.org/browse/JBIDE-21625 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Reporter: Fred Bricon > Assignee: Andre Dietisheim > Priority: Critical > Labels: openshift_v3, server_adapter > Fix For: 4.3.1.CR1 > > > Need to easily enable debug mode on EAP/Node images. That should allow hot reloading of server.js or java classes -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21625) Server adapter: Enable debug mode on OpenShift servers

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21625?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-21625: ------------------------------------------ As specificed in CLOUD-243: Enabling debugging in our eap-images works via an env var {code} com.redhat.dev-mode com.redhat.dev-mode.port {code} Those get picked on pod deployment. So we can change the deployment config resource and start for the triggered build to finish or change the number of replicas 1->0->1 > Server adapter: Enable debug mode on OpenShift servers > ------------------------------------------------------ > > Key: JBIDE-21625 > URL: https://issues.jboss.org/browse/JBIDE-21625 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Reporter: Fred Bricon > Assignee: Andre Dietisheim > Priority: Critical > Labels: openshift_v3, server_adapter > Fix For: 4.3.1.CR1 > > > Need to easily enable debug mode on EAP/Node images. That should allow hot reloading of server.js or java classes -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21656) Update OpenShift images to be consistent with web UI

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21656?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-21656: ------------------------------------------ [~jcantrill] in Eclipse one can use either gif or png as icons, svg is not supported > Update OpenShift images to be consistent with web UI > ---------------------------------------------------- > > Key: JBIDE-21656 > URL: https://issues.jboss.org/browse/JBIDE-21656 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.1.Beta2 > Reporter: Jeff Cantrill > Fix For: 4.3.x > > > After demo, OpenShift UXD suggested to review the icon set used to be consistent with the webconsole. The patternfly images used can be extracted by: > * load https://github.com/patternfly/patternfly/blob/master/PatternFlyIcons-webf... as a project in https://icomoon.io/app > * export svgs. > We may need to ultimately convert to PNG. Not sure if we can load SVG in the tooling. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21371) Server Adapter: implement automatic publishing

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21371?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-21371: ---------------------------------------- Why did this issue was closed? Has it been verified? Reopened (as resolved) for clarification. I also don't see this autopublishing stuff works in my Windows. At least by default. See https://www.youtube.com/watch?v=OZ1O6Tl0oZs (start with 26:25) > Server Adapter: implement automatic publishing > ---------------------------------------------- > > Key: JBIDE-21371 > URL: https://issues.jboss.org/browse/JBIDE-21371 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Andre Dietisheim > Assignee: Rob Stryker > Labels: new_and_noteworthy, openshift_v3, server_adapter > Fix For: 4.3.1.Beta2 > > > Currently the OpenShift 3 server adapter is only publishing when you manually triggering it to do so. We should now have fully automatic publishing that happens whenever the project that it is bound to changes on disk. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 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 February 2016