August 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (TOOLSDOC-669) Document the consequences of creating a remote server without a runtime

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-669?page=com.atlassian.jira.plug... ] Misha Ali updated TOOLSDOC-669: ------------------------------- Sprint: 20-Jul >> 02-Aug 2015-JBDS/JBT, 03-Aug >> 16-Aug 2015-JBDS/J 2 (was: 20-Jul >> 02-Aug 2015-JBDS/JBT) > Document the consequences of creating a remote server without a runtime > ----------------------------------------------------------------------- > > Key: TOOLSDOC-669 > URL: https://issues.jboss.org/browse/TOOLSDOC-669 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Feature Request > Components: General documentation issues > Affects Versions: 4.3.0.Beta2 > Reporter: Martin Malina > Assignee: Misha Ali > > In a recent discussion in JBIDE-19463, we talked about some limitations that result from creating of a remote server without a runtime. > For example, the jmx connection does not work because we use libs from the runtime to connect via jmx. > We have this document about setting up a remote server: > https://access.redhat.com/articles/1515503 > There is this: > {quote} > d. A remote server can now be created without assigning a runtime to it. Depending on the requirements, select the Assign a runtime to this server check box (and select an existing runtime or create a new one) or leave the box unselected and then click Next. > {quote} > So I think it would make sense to add these details somewhere in there. > From JBIDE-19463: > {quote} > Autodetection of ports by scanning your standalone.xml (or your selected configuration file). Since there's no local runtime, and no local standalone.xml, we can't notice that you've modified your ports to be non-standard. > Also, without a local runtime, some small behavior changes might be default values. For example, sometimes we hard-code different behavior between minor or micro versions if we notice there's a bug in some previous release. For example, some of the early jboss-7 releases didn't support the -b flag. > Without a local runtime to scan, we can't know the exact version you're running against, and can't customize args (or other things) to work around bugs in those specific runtime versions. > {quote} > On top of that, you won't be able to create a JMX connection to the server. > I'll leave it to you to decide how much details we need in the article. Maybe it's not necessary to talk about early versions of jboss-7 and that part. But it makes sense to at least mention that some things may be missing, mainly JMX connection, detection of ports from standalone.xml and perhaps several more. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20409) [origin_intservice_59]port-forwarding console should stop when I stop forwarding from wizard

by Yue Wang (JIRA)

Yue Wang created JBIDE-20409: -------------------------------- Summary: [origin_intservice_59]port-forwarding console should stop when I stop forwarding from wizard Key: JBIDE-20409 URL: https://issues.jboss.org/browse/JBIDE-20409 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.3.0.CR1 Environment: 3.0.0.CR1-v20150731-0236-B931 Reporter: Yue Wang Priority: Minor Since stop port-forwarding console can stop port forwarding, port-forwarding console should be terminated when when I stop forwarding from wizard. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (LOCUS-39) Consider using Eclipse Bundle Recipes (EBR)

by Gunnar Wagenknecht (JIRA)

[ https://issues.jboss.org/browse/LOCUS-39?page=com.atlassian.jira.plugin.s... ] Gunnar Wagenknecht commented on LOCUS-39: ----------------------------------------- [~mickael_istria] It might be possible to try it again. See my latest comment on the Eclipse bug. > Consider using Eclipse Bundle Recipes (EBR) > ------------------------------------------- > > Key: LOCUS-39 > URL: https://issues.jboss.org/browse/LOCUS-39 > Project: JBoss Tools Locus > Issue Type: Enhancement > Reporter: Mickael Istria > > I've had the opportunity to attend a presentation about EBR, a technology to turn plain jars from Maven as OSGi bunle (generating MANIFEST, source bundle, p2 metadata...). I have the impression that it fits quite nicely most of our Locus bundles, we should consider adopting it. > More background about EBR: > * http://www.eclipse.org/ebr > * http://de.slideshare.net/guw/tasty-recipes-for-osgi-bundles -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20408) Display port-forward wizard from the connection or project level

by Jeff Cantrill (JIRA)

Jeff Cantrill created JBIDE-20408: ------------------------------------- Summary: Display port-forward wizard from the connection or project level Key: JBIDE-20408 URL: https://issues.jboss.org/browse/JBIDE-20408 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: openshift Affects Versions: 4.3.0.CR1 Reporter: Jeff Cantrill Allow a user to display the wizard from the connection or project level. This will require the user to choose the pod to use to port forward. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20298) Projects wizard: removing all projects makes explorer show an empty child for connection

by Jeff Cantrill (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20298?page=com.atlassian.jira.plugi... ] Jeff Cantrill updated JBIDE-20298: ---------------------------------- Priority: Minor (was: Major) > Projects wizard: removing all projects makes explorer show an empty child for connection > ---------------------------------------------------------------------------------------- > > Key: JBIDE-20298 > URL: https://issues.jboss.org/browse/JBIDE-20298 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Beta2 > Reporter: Andre Dietisheim > Priority: Minor > Fix For: 4.3.0.CR1 > > Attachments: empty-child-for-connection.png > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20397) [origin_intservice_59]Port forwarding wizard: can "Start All" even though local port is already used (by other process)

by Jeff Cantrill (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20397?page=com.atlassian.jira.plugi... ] Jeff Cantrill commented on JBIDE-20397: --------------------------------------- I used the hello-world example to try and start port-forwarding twice. The second instance reports an error but the process hangs. I would expect it to exist with a non-zero exit code. Created https://github.com/openshift/origin/issues/3975 against the origin code since we depend upon the binary. We will only be able to resolve this without binary changes by checking the output/error stream for the message that identifies the binding issue. I'm not sure that makes sense. [~adietish] thoughrs? > [origin_intservice_59]Port forwarding wizard: can "Start All" even though local port is already used (by other process) > ----------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-20397 > URL: https://issues.jboss.org/browse/JBIDE-20397 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.CR1 > Environment: 3.0.0.CR1-v20150728-1708-B905 > Reporter: Chunyun Chen > Assignee: Jeff Cantrill > Labels: application_wizard, openshift_v3, port_forwarding_wizard > Fix For: 4.3.0.CR1 > > > Port forward successfully even if the relevant local port is used by other process. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20349) Port forwarding wizard: can "Start All" even though no ports to forward exist

by Jeff Cantrill (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20349?page=com.atlassian.jira.plugi... ] Jeff Cantrill reassigned JBIDE-20349: ------------------------------------- Assignee: Jeff Cantrill > Port forwarding wizard: can "Start All" even though no ports to forward exist > ----------------------------------------------------------------------------- > > Key: JBIDE-20349 > URL: https://issues.jboss.org/browse/JBIDE-20349 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Beta2 > Reporter: Andre Dietisheim > Assignee: Jeff Cantrill > Priority: Minor > Labels: port_forwarding_wizard > Fix For: 4.3.0.CR1 > > Attachments: no-ports-but-can-start-all.png > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3490) Include capabilities preference page into jbdevstudio product

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3490?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3490: -------------------------------- Summary: Include capabilities preference page into jbdevstudio product (was: Include capabilities preference page into target-platform) > Include capabilities preference page into jbdevstudio product > ------------------------------------------------------------- > > Key: JBDS-3490 > URL: https://issues.jboss.org/browse/JBDS-3490 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Enhancement > Components: javascript, target-platform > Affects Versions: 9.0.0.Beta2 > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 9.0.0.CR1 > > Attachments: jbds-preferences.png > > > Currently there is no way to enable/disable capabilities to see hidden nodes in preferences/properties dialogs. It might be needed as a backup to be able to debug for example tern related issues. > Current approach is using capabilities to hide Tern category from Preferences and Properties dialogs. If something goes wrong there is no way to see preferences and properties in hidden categories, because Capabilities Preference page is not included into ibdevstudio product. Before it was included by default but in Mars release it seems moved to EPP side. For example Committer Package does not provide Capabilities preference page, but Java EE Package does. > In current devstudio product package preferences categories looks like > !jbds-preferences.png! > as you see there is no Capabilities node in categories tree (1) because Capabilities preference page is not defined for jbdevstudio product and Tern node (2) is filtered out by default. It means in case of any problem with tern it is not possible do enable tern console tracing using Tern Preferences or see node.js configuration. > It is probably should be implemented as additional feature/plugin to include it into JBDS product, but it should beexcluded from BYOE feature to avoid preferences categories conflict in case of installation BYOE feature into Java EE EPP. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3276) JBDS-IS Installer support

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3276?page=com.atlassian.jira.plugin.... ] Denis Golovin commented on JBDS-3276: ------------------------------------- I would also add a test for generated JBDSIS installer to verify all the IS features can be installed when offline. Look into jbdevstudio/jbdevstudio-product/installer/pom.xml for details. It uses installer automation mode and run jbdevstudio-installer with automation xml file plus java policy file to disable internet access. > JBDS-IS Installer support > ------------------------- > > Key: JBDS-3276 > URL: https://issues.jboss.org/browse/JBDS-3276 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: installer, integration-platform, requirements > Affects Versions: 8.0.0.GA > Reporter: Burr Sutter > Assignee: Paul Leacu > Attachments: Red Hat JBoss Developer Studio 9.0.0.Alpha2_105.png > > > As a Fuse, integration-focused developer, I need a downloadable installer that will allow me to quickly and easily install JBDS with Fuse capabilities. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3067) Use JBDevStudio.icns with higher resolution on mac

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3067?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3067: -------------------------------- Sprint: Sprint 20141112, Sprint to CR1 Release, Sprint #1 April 2015, Sprint #2 April 2015, Sprint #3 May 2015, Sprint #4 May 2015, Sprint #5 Jun 2015, Sprint #7 July 2015 (was: Sprint 20141112, Sprint to CR1 Release, Sprint #1 April 2015, Sprint #2 April 2015, Sprint #3 May 2015, Sprint #4 May 2015, Sprint #5 Jun 2015) > Use JBDevStudio.icns with higher resolution on mac > -------------------------------------------------- > > Key: JBDS-3067 > URL: https://issues.jboss.org/browse/JBDS-3067 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Enhancement > Components: installer > Affects Versions: 9.0.0.Alpha1 > Environment: Mac OS X 10.9.3 (Mavericks) > Reporter: Denis Golovin > Assignee: Denis Golovin > Priority: Minor > Fix For: 9.0.0.CR1 > > Attachments: jbds-in-finder.png > > > Current icon resolution is too low and looks like this > !jbds-in-finder.png! -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 2 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues August 2015