October 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-23398) check Import-Package declarations to find more ui deps in core plugins

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23398?page=com.atlassian.jira.plugi... ] Nick Boldt closed JBIDE-23398. ------------------------------ Resolution: Won't Fix > check Import-Package declarations to find more ui deps in core plugins > ---------------------------------------------------------------------- > > Key: JBIDE-23398 > URL: https://issues.jboss.org/browse/JBIDE-23398 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build, common > Affects Versions: 4.4.2.AM2 > Reporter: Nick Boldt > Assignee: Rob Stryker > Priority: Minor > Fix For: 4.4.2.AM3 > > > Current enforcer is good in that it finds Require-Bundle paths of dependencies. > But we should really be checking Import-Package relationships too, since some plugins (eg., openshift.client) don't use Require-Bundle at all. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23398) check Import-Package declarations to find more ui deps in core plugins

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23398?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-23398: ------------------------------- Fix Version/s: 4.4.2.AM3 (was: 4.4.x) > check Import-Package declarations to find more ui deps in core plugins > ---------------------------------------------------------------------- > > Key: JBIDE-23398 > URL: https://issues.jboss.org/browse/JBIDE-23398 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build, common > Affects Versions: 4.4.2.AM2 > Reporter: Nick Boldt > Assignee: Rob Stryker > Priority: Minor > Fix For: 4.4.2.AM3 > > > Current enforcer is good in that it finds Require-Bundle paths of dependencies. > But we should really be checking Import-Package relationships too, since some plugins (eg., openshift.client) don't use Require-Bundle at all. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23380) MOJO that fails or logs errors for build if manifest in .core plugin has .ui dependency

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23380?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-23380: ------------------------------------- Passing to you nicky-b. Up to you how far to take it ;) > MOJO that fails or logs errors for build if manifest in .core plugin has .ui dependency > --------------------------------------------------------------------------------------- > > Key: JBIDE-23380 > URL: https://issues.jboss.org/browse/JBIDE-23380 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Reporter: Rob Stryker > Assignee: Nick Boldt > Fix For: 4.4.2.AM3 > > > At a minimum, the mojo should: > foreach plugin, if plugin ends in .core, check plugin/META-INF/MANIFEST for Dependencies manifest header, and verify .ui is not included in the dependencies at all. > However, this minimum goal would not have solved the issue we are experiencing with foundation.checkup. The foundation.checkup plugin does not end in .core and so would be skipped by this simple algorithm. > So... we may wish to check transitive dependencies *only in the same repo*. For example, foundation.core depends on foundation.checker, and foundation.checker is in the same repo, so foundation.checker should also be checked for ui deps or fail. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23380) MOJO that fails or logs errors for build if manifest in .core plugin has .ui dependency

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23380?page=com.atlassian.jira.plugi... ] Rob Stryker reassigned JBIDE-23380: ----------------------------------- Assignee: Nick Boldt (was: Rob Stryker) > MOJO that fails or logs errors for build if manifest in .core plugin has .ui dependency > --------------------------------------------------------------------------------------- > > Key: JBIDE-23380 > URL: https://issues.jboss.org/browse/JBIDE-23380 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Reporter: Rob Stryker > Assignee: Nick Boldt > Fix For: 4.4.2.AM3 > > > At a minimum, the mojo should: > foreach plugin, if plugin ends in .core, check plugin/META-INF/MANIFEST for Dependencies manifest header, and verify .ui is not included in the dependencies at all. > However, this minimum goal would not have solved the issue we are experiencing with foundation.checkup. The foundation.checkup plugin does not end in .core and so would be skipped by this simple algorithm. > So... we may wish to check transitive dependencies *only in the same repo*. For example, foundation.core depends on foundation.checker, and foundation.checker is in the same repo, so foundation.checker should also be checked for ui deps or fail. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23392) For JBIDE 4.4.2.AM3: UI dependencies from Core plugins [common]

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23392?page=com.atlassian.jira.plugi... ] Rob Stryker resolved JBIDE-23392. --------------------------------- Resolution: Done Pushed to master > For JBIDE 4.4.2.AM3: UI dependencies from Core plugins [common] > --------------------------------------------------------------- > > Key: JBIDE-23392 > URL: https://issues.jboss.org/browse/JBIDE-23392 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: common > Reporter: Nick Boldt > Assignee: Rob Stryker > Priority: Minor > Labels: task > Fix For: 4.4.2.AM3 > > > For JBIDE 4.4.2.AM3 [common]: The following core plugins depend on UI plugins directly or indirectly. {code}[CoreUIDependency] org.jboss.tools.foundation.core is a Core plugin, but depends on these UI plugins directly or transitively: > > org.eclipse.ui.workbench > > org.eclipse.ui.views.log > -- > [CoreUIDependency] org.jboss.tools.common.core is a Core plugin, but depends on these UI plugins directly or transitively: > > org.eclipse.ui.workbench > > org.eclipse.ui.views.log > -- > [CoreUIDependency] org.jboss.tools.common.resref.core is a Core plugin, but depends on these UI plugins directly or transitively: > > org.eclipse.ui > > org.eclipse.jdt.ui > > org.eclipse.wst.sse.ui > > org.eclipse.ui.workbench > > org.eclipse.ui.ide > > org.eclipse.ui.views.log > > org.eclipse.ui.workbench.texteditor > > org.eclipse.wst.xml.ui > -- > [CoreUIDependency] org.jboss.tools.common.el.core is a Core plugin, but depends on these UI plugins directly or transitively: > > org.eclipse.ui > > org.eclipse.wst.sse.ui > > org.eclipse.jdt.ui > > org.eclipse.ui.workbench > > org.eclipse.ui.ide > > org.eclipse.ui.views.log > > org.eclipse.ui.workbench.texteditor > > org.eclipse.wst.xml.ui > -- > [CoreUIDependency] org.jboss.tools.stacks.core is a Core plugin, but depends on these UI plugins directly or transitively: > > org.eclipse.ui.workbench > > org.eclipse.ui.views.log > -- > [CoreUIDependency] org.jboss.tools.runtime.core is a Core plugin, but depends on these UI plugins directly or transitively: > > org.eclipse.ui.workbench > > org.eclipse.ui.views.log{code} > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for common task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23392) For JBIDE 4.4.2.AM3: UI dependencies from Core plugins [common]

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23392?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-23392: -------------------------------- Fix Version/s: 4.4.2.AM3 (was: 4.4.x) > For JBIDE 4.4.2.AM3: UI dependencies from Core plugins [common] > --------------------------------------------------------------- > > Key: JBIDE-23392 > URL: https://issues.jboss.org/browse/JBIDE-23392 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: common > Reporter: Nick Boldt > Assignee: Rob Stryker > Priority: Minor > Labels: task > Fix For: 4.4.2.AM3 > > > For JBIDE 4.4.2.AM3 [common]: The following core plugins depend on UI plugins directly or indirectly. {code}[CoreUIDependency] org.jboss.tools.foundation.core is a Core plugin, but depends on these UI plugins directly or transitively: > > org.eclipse.ui.workbench > > org.eclipse.ui.views.log > -- > [CoreUIDependency] org.jboss.tools.common.core is a Core plugin, but depends on these UI plugins directly or transitively: > > org.eclipse.ui.workbench > > org.eclipse.ui.views.log > -- > [CoreUIDependency] org.jboss.tools.common.resref.core is a Core plugin, but depends on these UI plugins directly or transitively: > > org.eclipse.ui > > org.eclipse.jdt.ui > > org.eclipse.wst.sse.ui > > org.eclipse.ui.workbench > > org.eclipse.ui.ide > > org.eclipse.ui.views.log > > org.eclipse.ui.workbench.texteditor > > org.eclipse.wst.xml.ui > -- > [CoreUIDependency] org.jboss.tools.common.el.core is a Core plugin, but depends on these UI plugins directly or transitively: > > org.eclipse.ui > > org.eclipse.wst.sse.ui > > org.eclipse.jdt.ui > > org.eclipse.ui.workbench > > org.eclipse.ui.ide > > org.eclipse.ui.views.log > > org.eclipse.ui.workbench.texteditor > > org.eclipse.wst.xml.ui > -- > [CoreUIDependency] org.jboss.tools.stacks.core is a Core plugin, but depends on these UI plugins directly or transitively: > > org.eclipse.ui.workbench > > org.eclipse.ui.views.log > -- > [CoreUIDependency] org.jboss.tools.runtime.core is a Core plugin, but depends on these UI plugins directly or transitively: > > org.eclipse.ui.workbench > > org.eclipse.ui.views.log{code} > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for common task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21065) Server host name address should not be defaulted during server adapter creation

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21065?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-21065: -------------------------------- Sprint: devex #123 November 2016 (was: devex #122 October 2016) > Server host name address should not be defaulted during server adapter creation > ------------------------------------------------------------------------------- > > Key: JBIDE-21065 > URL: https://issues.jboss.org/browse/JBIDE-21065 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server, upstream > Affects Versions: 4.3.0.Final > Reporter: Xavier Coulon > Assignee: Rob Stryker > Fix For: 4.4.3.AM1, 4.5.0.AM1 > > > I've noticed that when I create a server adapter and I give it an IP address as the hostname, the hostname remains the default value, ie, {{localhost}}. > This is annoying in the case where I want to connect to a VM running on my own host (eg, a VM running Docker). In this particular case, I set the hostname at something like {{192.168.99.100}} but it is reverted as {{localhost}} which gives {{127.0.0.1}} as the primary IP address. As a consequence, the server adapter fails to connect to the server since it uses the wrong IP address. > Note that the host name can be changed for good in the Server Configuration Editor _after_ its creation. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23320) New server window server type picker is single line long on Cinnamon

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23320?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-23320: -------------------------------- Component/s: upstream > New server window server type picker is single line long on Cinnamon > -------------------------------------------------------------------- > > Key: JBIDE-23320 > URL: https://issues.jboss.org/browse/JBIDE-23320 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server, upstream > Environment: Fedora 24 x86-64 > Cinnamon 3.0.7 > Linux 4.7.6 > JBDS 10.1.0.GA > Reporter: Michal Jurc > Assignee: Rob Stryker > Fix For: 4.4.3.AM1, 4.5.0.AM1 > > Attachments: jbds-10.1-new-server.png > > > In JBoss Developer Studio 10.1.0.GA, the New Server window server type choice only displays single server at time without scrolling which is uncomfortable to navigate through. > Screenshot attached. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23320) New server window server type picker is single line long on Cinnamon

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23320?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-23320: -------------------------------- Fix Version/s: 4.4.3.AM1 4.5.0.AM1 (was: 4.4.2.AM3) > New server window server type picker is single line long on Cinnamon > -------------------------------------------------------------------- > > Key: JBIDE-23320 > URL: https://issues.jboss.org/browse/JBIDE-23320 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server, upstream > Environment: Fedora 24 x86-64 > Cinnamon 3.0.7 > Linux 4.7.6 > JBDS 10.1.0.GA > Reporter: Michal Jurc > Assignee: Rob Stryker > Fix For: 4.4.3.AM1, 4.5.0.AM1 > > Attachments: jbds-10.1-new-server.png > > > In JBoss Developer Studio 10.1.0.GA, the New Server window server type choice only displays single server at time without scrolling which is uncomfortable to navigate through. > Screenshot attached. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21065) Server host name address should not be defaulted during server adapter creation

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21065?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-21065: -------------------------------- Fix Version/s: 4.4.3.AM1 4.5.0.AM1 (was: 4.4.2.AM3) > Server host name address should not be defaulted during server adapter creation > ------------------------------------------------------------------------------- > > Key: JBIDE-21065 > URL: https://issues.jboss.org/browse/JBIDE-21065 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server, upstream > Affects Versions: 4.3.0.Final > Reporter: Xavier Coulon > Assignee: Rob Stryker > Fix For: 4.4.3.AM1, 4.5.0.AM1 > > > I've noticed that when I create a server adapter and I give it an IP address as the hostname, the hostname remains the default value, ie, {{localhost}}. > This is annoying in the case where I want to connect to a VM running on my own host (eg, a VM running Docker). In this particular case, I set the hostname at something like {{192.168.99.100}} but it is reverted as {{localhost}} which gives {{127.0.0.1}} as the primary IP address. As a consequence, the server adapter fails to connect to the server since it uses the wrong IP address. > Note that the host name can be changed for good in the Server Configuration Editor _after_ its creation. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 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 October 2016