March 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-21960) BrowserSim/CordovaSim doesn not run with rht-openJDK

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21960?page=com.atlassian.jira.plugi... ] Pavol Srna updated JBIDE-21960: ------------------------------- Affects Version/s: 4.3.1.CR1 > BrowserSim/CordovaSim doesn not run with rht-openJDK > ---------------------------------------------------- > > Key: JBIDE-21960 > URL: https://issues.jboss.org/browse/JBIDE-21960 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: browsersim, cordovasim > Affects Versions: 4.3.1.CR1 > Reporter: Pavol Srna > > BrowserSim/CordovaSim does not run with rht-openJDK. > In case we bundle rht-openJDK in the new all-in-1 installer how do we handle this situation? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21931) Link with Editor does not work on Windows

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21931?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-21931: --------------------------------------------- the jira says "link with editor" but PR talks about editor shortcuts...which issue was fixed here ? > Link with Editor does not work on Windows > ----------------------------------------- > > Key: JBIDE-21931 > URL: https://issues.jboss.org/browse/JBIDE-21931 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.3.1.CR1 > Reporter: Pavol Srna > Assignee: George Gastaldi > Fix For: 4.3.1.CR1 > > > Link with Editor does not work on windows. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21959) Have a way to check aeri reports opened with linked JIRA issue fixed/closed

by Aurélien Pupier (JIRA)

Aurélien Pupier created JBIDE-21959: --------------------------------------- Summary: Have a way to check aeri reports opened with linked JIRA issue fixed/closed Key: JBIDE-21959 URL: https://issues.jboss.org/browse/JBIDE-21959 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: aeri Reporter: Aurélien Pupier Have a way to check aeri reports opened with linked JIRA issue fixed/closed would help to keep the aeri system clean easily. By "clean" I mean avoid to have opened aeri report although the issue is solved I can imagine several possibilities: - hook something on JIRA side which checks the provided "link" for aeri and when resolving/closing the JIRA issue, it will ask if we want to close the related aeri report. - on aeri side, scan for linked JIRA every night (hours?) and then do an action... which can be: -- send mail to JIRA issue closer? -- close automatically the report? -- other?? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21958) Provide filters by status on Problems view

by Aurélien Pupier (JIRA)

Aurélien Pupier created JBIDE-21958: --------------------------------------- Summary: Provide filters by status on Problems view Key: JBIDE-21958 URL: https://issues.jboss.org/browse/JBIDE-21958 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: aeri Reporter: Aurélien Pupier Priority: Minor Specific use case I have in mind: - have the list of pending reports - have the list of pending reports with no issue If we can filter on every field it would be nice too but perhaps as a second iteration -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21908) Context menu to stop OS 3 Server Adapter is disabled after start, stop, start

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21908?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-21908. --------------------------------- Verified on nightly build of JBT with OpenShift plugin build B246. > Context menu to stop OS 3 Server Adapter is disabled after start, stop, start > ----------------------------------------------------------------------------- > > Key: JBIDE-21908 > URL: https://issues.jboss.org/browse/JBIDE-21908 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Assignee: Rob Stryker > Labels: openshift_v3, server_adapter > Fix For: 4.3.1.CR1 > > > Context menu to Stop an OpenShift 3 server adapter in Server view is disabled when I am trying to stop it for second time. At first adapter is stopped, after first start of it, Stop context menu gets enabled. But when I stop and start it in this point, Stop context menu is disabled permanently. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21957) Context menu to stop OS 3 Server Adapter is disabled after start, stop, start

by Marián Labuda (JIRA)

Marián Labuda created JBIDE-21957: ------------------------------------- Summary: Context menu to stop OS 3 Server Adapter is disabled after start, stop, start Key: JBIDE-21957 URL: https://issues.jboss.org/browse/JBIDE-21957 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.3.1.CR1 Reporter: Marián Labuda Assignee: Rob Stryker Fix For: 4.3.1.CR1 Context menu to Stop an OpenShift 3 server adapter in Server view is disabled when I am trying to stop it for second time. At first adapter is stopped, after first start of it, Stop context menu gets enabled. But when I stop and start it in this point, Stop context menu is disabled permanently. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21957) Context menu to stop OS 3 Server Adapter is disabled after start, stop, start

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21957?page=com.atlassian.jira.plugi... ] Marián Labuda updated JBIDE-21957: ---------------------------------- Fix Version/s: 4.4.0.Alpha1 (was: 4.3.1.CR1) > Context menu to stop OS 3 Server Adapter is disabled after start, stop, start > ----------------------------------------------------------------------------- > > Key: JBIDE-21957 > URL: https://issues.jboss.org/browse/JBIDE-21957 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Assignee: Rob Stryker > Labels: openshift_v3, server_adapter > Fix For: 4.4.0.Alpha1 > > > Context menu to Stop an OpenShift 3 server adapter in Server view is disabled when I am trying to stop it for second time. At first adapter is stopped, after first start of it, Stop context menu gets enabled. But when I stop and start it in this point, Stop context menu is disabled permanently. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21957) Context menu to stop OS 3 Server Adapter is disabled after start, stop, start

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21957?page=com.atlassian.jira.plugi... ] Marián Labuda resolved JBIDE-21957. ----------------------------------- Resolution: Done > Context menu to stop OS 3 Server Adapter is disabled after start, stop, start > ----------------------------------------------------------------------------- > > Key: JBIDE-21957 > URL: https://issues.jboss.org/browse/JBIDE-21957 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Assignee: Rob Stryker > Labels: openshift_v3, server_adapter > Fix For: 4.4.0.Alpha1 > > > Context menu to Stop an OpenShift 3 server adapter in Server view is disabled when I am trying to stop it for second time. At first adapter is stopped, after first start of it, Stop context menu gets enabled. But when I stop and start it in this point, Stop context menu is disabled permanently. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBTIS-531) Bouncy Castle causes Fuse Tooling full source TP build failure.

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-531?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky closed JBTIS-531. ----------------------------------- Closed as obsolete. Verified that the issue is not present in - JBDS-IS 8.0.5.GA / JBDS-IS 8.0.6.CR3 - JBDS-IS 9.0.0.Beta1 > Bouncy Castle causes Fuse Tooling full source TP build failure. > --------------------------------------------------------------- > > Key: JBTIS-531 > URL: https://issues.jboss.org/browse/JBTIS-531 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: target-platform > Affects Versions: 8.0.4.GA, 9.0.0.Alpha2 > Reporter: Paul Leacu > Assignee: Paul Richardson > Priority: Blocker > Fix For: 4.2.9.Final-TP > > Attachments: TP-issues.png > > > Here is the issue. The JBTIS TP has a reliance on bouncycastle that was introduced as an indirect dependency by Teiid Designer because they needed the Apache directory features including the org.apache.directory.studio.connection.ui feature. The bcprov feature was removed from the JBTIS TP and Teiid Designer added a dummy feature to satisfy maven. This was built and everything in the IS builds and installs fine - no one directly needed bouncycastle. > Fuse Tooling builds a local development-only full source target platform based on the JBTIS TP. This causes all dependencies to be fully resolved which causes them to fail their target platform development-only build: > {code} > mvn -Pmultiple2repo -U -Dmirror-target-to-repo.includeSources=true clean install > ... > [ERROR] Software being installed: org.apache.directory.studio.connection.ui 2.0.0.v20150618 > [ERROR] Missing requirement: org.apache.directory.studio.connection.ui 2.0.0.v20150618 requires 'package org.bouncycastle.x509.extension 0.0.0' but it could not be found > {code} > you may also see this error: > {code} > [ERROR] Software being installed: org.apache.directory.studio.connection.ui 2.0.0.v20150618 > [ERROR] Missing requirement: org.apache.directory.studio.connection.ui 2.0.0.v20150618 requires 'package org.bouncycastle.asn1 0.0.0' but it could not be found > {code} > Both of these plugins can be found (in stub form) here: > http://download.jboss.org/jbosstools/updates/stable/luna/integration-stac... > How should this be fixed? Both Teiid Designer and Fuse Tooling use the JBTIS TP. Fuse needs this development TP to debug Fuse and SAP issues. They shouldn't have to incur a dependency that has nothing to do with them. If we pull the entire Apache directory dependency block out of the IS TP then Teiid Des will have to go back to creating their own merged TP. > WDYT? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21761) Port mapping validation is not correct

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21761?page=com.atlassian.jira.plugi... ] Xavier Coulon commented on JBIDE-21761: --------------------------------------- thanks, [~mlabuda] ! > Port mapping validation is not correct > -------------------------------------- > > Key: JBIDE-21761 > URL: https://issues.jboss.org/browse/JBIDE-21761 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Assignee: Xavier Coulon > Labels: docker, openshift_v3 > Fix For: 4.3.1.CR1 > > Attachments: validation_msg.png > > > In Deploy docker image on the page with port mapping when adding a new port mapping there is a validation error telling that correct format of pod is alphanumeric, what is wrong. See following image. > !validation_msg.png! > There should be allowed only numbers in range 0-65535. It is not only validation message but it allows to create also mapping to port e.g. "abc123" what should not be possible. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

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