April 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22169) silent runtime detection for installer eap or cdk does not work on mac

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22169?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-22169: -------------------------------- Fix Version/s: 4.4.0.Alpha1 > silent runtime detection for installer eap or cdk does not work on mac > ---------------------------------------------------------------------- > > Key: JBIDE-22169 > URL: https://issues.jboss.org/browse/JBIDE-22169 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: runtime-detection > Affects Versions: 4.3.1.CR1 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.4.0.Alpha1 > > Attachments: jbds-tree-mac.txt > > > Today I learned that when you install jbdevstudio together with bundled eap, you should not get a popup from runtime detection when you start jbds. The bundled eap should be added silently. > This doesn't work on Mac. This is most probably because there is a different directory structure on mac. > See here: > {code} > ./runtimes > ./runtimes/jboss-eap > ./studio/jbdevstudio.app > ./studio/jbdevstudio.app/Contents > ./studio/jbdevstudio.app/Contents/Eclipse > ./studio/jbdevstudio.app/Contents/Eclipse/plugins > ./studio/jbdevstudio.app/Contents/MacOS > ./studio/jbdevstudio.app/Contents/MacOS/jbdevstudio > ./studio/jbdevstudio.app/Contents/Eclipse/configuration/ > {code} > See the attached txt for full tree. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3791) JBDS installer - Non-existent dir off of home dir automatically added to runtime detection

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBDS-3791?page=com.atlassian.jira.plugin.... ] Fred Bricon commented on JBDS-3791: ----------------------------------- This was requested by [~maxandersen] some time ago: JBDS-2515 > JBDS installer - Non-existent dir off of home dir automatically added to runtime detection > ------------------------------------------------------------------------------------------ > > Key: JBDS-3791 > URL: https://issues.jboss.org/browse/JBDS-3791 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 9.1.0.CR1 > Environment: Version: 9.1.0.GA > Build id: GA-v20160410-1849-B495 > Build date: 20160410-1849 > Reporter: Len DiMaggio > Priority: Minor > Attachments: homeDir.png > > > See attached screenshot - why are we adding a (potentially) non-existent directory off of the installer's homedir to runtime detection? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-22129) Watches should not try to reconnect when a project has been deleted

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22129?page=com.atlassian.jira.plugi... ] Marián Labuda commented on JBIDE-22129: --------------------------------------- I see following output in tracing log when deleting a project {code}| Worker-676 | 2016-04-12 17:40:48.362 | org.jboss.tools.openshift.client | /debug/client | org.jboss.tools.openshift.client.internal.log.Trace | trace | 86 | Deleting resource https://10.1.2.2:8443/oapi/v1/projects/newproject | | Worker-676 | 2016-04-12 17:40:48.384 | org.jboss.tools.openshift.client | /debug/client | org.jboss.tools.openshift.client.internal.log.Trace | trace | 86 | { "kind": "Status", "apiVersion": "v1", "metadata": {}, "status": "Success", "code": 200 } | | Worker-676 | 2016-04-12 17:40:48.384 | org.jboss.tools.openshift.client | /debug/client | org.jboss.tools.openshift.client.internal.log.Trace | trace | 86 | Built url: https://10.1.2.2:8443/oapi/v1/projects/newproject | | Worker-676 | 2016-04-12 17:40:48.416 | org.jboss.tools.openshift.client | /debug/client | org.jboss.tools.openshift.client.internal.log.Trace | trace | 86 | {"kind":"Project","apiVersion":"v1","metadata":{"name":"newproject","selfLink":"/oapi/v1/projects/newproject","uid":"e3b2bd19-00c4-11e6-bf0a-525400b46e1a","resourceVersion":"3328","creationTimestamp":"2016-04-12T15:40:31Z","deletionTimestamp":"2016-04-12T15:40:47Z","annotations":{"openshift.io/description":"","openshift.io/display-name":"","openshift.io/sa.scc.mcs":"s0:c10,c5","openshift.io/sa.scc.supplemental-groups":"1000100000/10000","openshift.io/sa.scc.uid-range":"1000100000/10000"}},"spec":{"finalizers":["openshift.io/origin","kubernetes"]},"status":{"phase":"Terminating"}} | | Worker-676 | 2016-04-12 17:40:48.917 | org.jboss.tools.openshift.client | /debug/client | org.jboss.tools.openshift.client.internal.log.Trace | trace | 86 | Built url: https://10.1.2.2:8443/oapi/v1/projects/newproject | | Worker-676 | 2016-04-12 17:40:48.929 | org.jboss.tools.openshift.client | /debug/client | org.jboss.tools.openshift.client.internal.log.Trace | trace | 86 | Could not get resource newproject in namespace : { "kind": "Status", "apiVersion": "v1", "metadata": {}, "status": "Failure", "message": "User \"openshift-dev\" cannot get projects in project \"newproject\"", "reason": "Forbidden", "details": { "name": "newproject", "kind": "projects" }, "code": 403 } {code} I suppose its ok, bcs there is no other watcher connected nor after some time there is any watching. But should there be that failure of getting deleted project? > Watches should not try to reconnect when a project has been deleted > ------------------------------------------------------------------- > > Key: JBIDE-22129 > URL: https://issues.jboss.org/browse/JBIDE-22129 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Fred Bricon > Assignee: Jeff Cantrill > Labels: respin-b > Fix For: 4.3.1.CR1 > > > When a project has been deleted from the webconsole, the watchmanager in eclipse is not notified. Each watch that times out tries to reconnect to some of the dead project's urls. Each access is rejected with 403 errors (the project could exist but not be visible to the user). > After each attempt, the watches will wait a little longer before trying to reconnect, until it eventually stops trying. > Since the watch manager has access to the projects, it can try to check the project exists before connecting the watch -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3791) JBDS installer - Non-existent dir off of home dir automatically added to runtime detection

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBDS-3791?page=com.atlassian.jira.plugin.... ] Len DiMaggio updated JBDS-3791: ------------------------------- Attachment: homeDir.png > JBDS installer - Non-existent dir off of home dir automatically added to runtime detection > ------------------------------------------------------------------------------------------ > > Key: JBDS-3791 > URL: https://issues.jboss.org/browse/JBDS-3791 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 9.1.0.CR1 > Environment: Version: 9.1.0.GA > Build id: GA-v20160410-1849-B495 > Build date: 20160410-1849 > Reporter: Len DiMaggio > Priority: Minor > Attachments: homeDir.png > > > See attached screenshot - why are we adding a (potentially) non-existent directory off of the installer's homedir to runtime detection? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3791) JBDS installer - Non-existent dir off of home dir automatically added to runtime detection

by Len DiMaggio (JIRA)

Len DiMaggio created JBDS-3791: ---------------------------------- Summary: JBDS installer - Non-existent dir off of home dir automatically added to runtime detection Key: JBDS-3791 URL: https://issues.jboss.org/browse/JBDS-3791 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Components: installer Affects Versions: 9.1.0.CR1 Environment: Version: 9.1.0.GA Build id: GA-v20160410-1849-B495 Build date: 20160410-1849 Reporter: Len DiMaggio Priority: Minor See attached screenshot - why are we adding a (potentially) non-existent directory off of the installer's homedir to runtime detection? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3790) Copyright notices for installer and IDE are "2004-2015" - must we update this to "2004-2016?"

by Len DiMaggio (JIRA)

Len DiMaggio created JBDS-3790: ---------------------------------- Summary: Copyright notices for installer and IDE are "2004-2015" - must we update this to "2004-2016?" Key: JBDS-3790 URL: https://issues.jboss.org/browse/JBDS-3790 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Components: installer Affects Versions: 9.1.0.CR1 Environment: Version: 9.1.0.GA Build id: GA-v20160410-1849-B495 Build date: 20160410-1849 Reporter: Len DiMaggio Assignee: Alexey Kazakov See the attached screenshots - Must we update these to 2016 before GA? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3790) Copyright notices for installer and IDE are "2004-2015" - must we update this to "2004-2016?"

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBDS-3790?page=com.atlassian.jira.plugin.... ] Len DiMaggio updated JBDS-3790: ------------------------------- Attachment: copyright_installer.png copyright_IDE.png > Copyright notices for installer and IDE are "2004-2015" - must we update this to "2004-2016?" > --------------------------------------------------------------------------------------------- > > Key: JBDS-3790 > URL: https://issues.jboss.org/browse/JBDS-3790 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 9.1.0.CR1 > Environment: Version: 9.1.0.GA > Build id: GA-v20160410-1849-B495 > Build date: 20160410-1849 > Reporter: Len DiMaggio > Assignee: Alexey Kazakov > Attachments: copyright_IDE.png, copyright_installer.png > > > See the attached screenshots - Must we update these to 2016 before GA? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-22169) silent runtime detection for installer eap or cdk does not work on mac

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22169?page=com.atlassian.jira.plugi... ] Martin Malina updated JBIDE-22169: ---------------------------------- Description: Today I learned that when you install jbdevstudio together with bundled eap, you should not get a popup from runtime detection when you start jbds. The bundled eap should be added silently. This doesn't work on Mac. This is most probably because there is a different directory structure on mac. See here: {code} ./runtimes ./runtimes/jboss-eap ./studio/jbdevstudio.app ./studio/jbdevstudio.app/Contents ./studio/jbdevstudio.app/Contents/Eclipse ./studio/jbdevstudio.app/Contents/Eclipse/plugins ./studio/jbdevstudio.app/Contents/MacOS ./studio/jbdevstudio.app/Contents/MacOS/jbdevstudio ./studio/jbdevstudio.app/Contents/Eclipse/configuration/ {code} See the attached txt for full tree. was: Today I learned that when you install jbdevstudio together with bundled eap, you should not get a popup from runtime detection when you start jbds. The bundled eap should be added silently. This doesn't work on Mac. This is most probably because there is a different directory structure on mac. See here: {code} ./runtimes ./runtimes/jboss-eap ./studio/jbdevstudio.app ./studio/jbdevstudio.app/Contents ./studio/jbdevstudio.app/Contents/Eclipse ./studio/jbdevstudio.app/Contents/Eclipse/plugins ./studio/jbdevstudio.app/Contents/MacOS ./studio/jbdevstudio.app/Contents/MacOS/jbdevstudio {code} See the attached txt for full tree. > silent runtime detection for installer eap or cdk does not work on mac > ---------------------------------------------------------------------- > > Key: JBIDE-22169 > URL: https://issues.jboss.org/browse/JBIDE-22169 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: runtime-detection > Affects Versions: 4.3.1.CR1 > Reporter: Martin Malina > Assignee: Rob Stryker > Attachments: jbds-tree-mac.txt > > > Today I learned that when you install jbdevstudio together with bundled eap, you should not get a popup from runtime detection when you start jbds. The bundled eap should be added silently. > This doesn't work on Mac. This is most probably because there is a different directory structure on mac. > See here: > {code} > ./runtimes > ./runtimes/jboss-eap > ./studio/jbdevstudio.app > ./studio/jbdevstudio.app/Contents > ./studio/jbdevstudio.app/Contents/Eclipse > ./studio/jbdevstudio.app/Contents/Eclipse/plugins > ./studio/jbdevstudio.app/Contents/MacOS > ./studio/jbdevstudio.app/Contents/MacOS/jbdevstudio > ./studio/jbdevstudio.app/Contents/Eclipse/configuration/ > {code} > See the attached txt for full tree. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-22169) silent runtime detection for installer eap or cdk does not work on mac

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22169?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-22169: ------------------------------------- The current hard-coded paths for eap vs cdk are: private static final String JBOSS_EAP_HOME = "../../runtimes/jboss-eap"; // JBoss EAP home directory (relative to plugin)- <RHDS_HOME>/jbossas. //$NON-NLS-1$ private static final String CDK_HOME = "../../../cdk/"; //$NON-NLS-1$ It will search these paths recursively to an additional depth of 3. These paths are relative to the "configuration" location, as discovered by Platform.getConfigurationLocation(); > silent runtime detection for installer eap or cdk does not work on mac > ---------------------------------------------------------------------- > > Key: JBIDE-22169 > URL: https://issues.jboss.org/browse/JBIDE-22169 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: runtime-detection > Affects Versions: 4.3.1.CR1 > Reporter: Martin Malina > Assignee: Rob Stryker > Attachments: jbds-tree-mac.txt > > > Today I learned that when you install jbdevstudio together with bundled eap, you should not get a popup from runtime detection when you start jbds. The bundled eap should be added silently. > This doesn't work on Mac. This is most probably because there is a different directory structure on mac. > See here: > {code} > ./runtimes > ./runtimes/jboss-eap > ./studio/jbdevstudio.app > ./studio/jbdevstudio.app/Contents > ./studio/jbdevstudio.app/Contents/Eclipse > ./studio/jbdevstudio.app/Contents/Eclipse/plugins > ./studio/jbdevstudio.app/Contents/MacOS > ./studio/jbdevstudio.app/Contents/MacOS/jbdevstudio > {code} > See the attached txt for full tree. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBTIS-527) com.jboss.devstudio.integration-stack.*.feature versions don't have qualifier, just a timestamp

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-527?page=com.atlassian.jira.plugin.... ] Paul Leacu commented on JBTIS-527: ---------------------------------- Jenkins job was introducing a BUILD_ALIAS that set the multiple versions in the format - this will be corrected in the .Final build. > com.jboss.devstudio.integration-stack.*.feature versions don't have qualifier, just a timestamp > ----------------------------------------------------------------------------------------------- > > Key: JBTIS-527 > URL: https://issues.jboss.org/browse/JBTIS-527 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 9.0.0.Alpha2 > Reporter: Nick Boldt > Assignee: Paul Leacu > Priority: Blocker > Fix For: 9.0.0.Beta1 > > > Looking in https://devstudio.redhat.com/9.0/stable/updates/integration-stack/9.0.0.A... I see these 4 IUs: > {code} > com.jboss.devstudio.integration-stack.bpr.feature.feature.jar 9.0.0.201510070121 > com.jboss.devstudio.integration-stack.ds.feature.feature.jar 9.0.0.201510070121 > com.jboss.devstudio.integration-stack.fuse.feature.feature.jar 9.0.0.201510070121 > com.jboss.devstudio.integration-stack.soa.feature.feature.jar 9.0.0.201510070121 > {code} > They should be versioned like everything else in JBT/JBDS/IS, using a full qualifier like: > * 9.0.0.Alpha2-v20151006-2058-B148 -- 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 April 2016