July 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-19637) Runtime download hyperlink not working from New Server dialog on Mac

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19637?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-19637: ------------------------------------- I agree with you... but issue 1) is out of our hands, so 2) and 3) was the best I could accomplish ;) Either way, I see this as a success at debugging and the power of open source (since I got the solution from upstream bug). I'll update the upstream bug to indicate the workaround worked for us but how the workaround will not work for critical workflows. > Runtime download hyperlink not working from New Server dialog on Mac > -------------------------------------------------------------------- > > Key: JBIDE-19637 > URL: https://issues.jboss.org/browse/JBIDE-19637 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.3.0.Alpha2 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.3.0.CR1 > > > When you go through Servers view -> New Server -> EAP 6.1 -> New Runtime and then click "Download and install runtime...", it won't do anything. > If you go through Preferences -> Server -> Runtime Environments -> Add -> EAP 6.1+ and then click the Download button, it will work. > This issue applies to both JBDS 8.1.0.GA and JBoss Tools 4.3.0.Alpha2 testing build, but I doubt we will be able to fix this for 4.2.x. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19637) Runtime download hyperlink not working from New Server dialog on Mac

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19637?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-19637: -------------------------------- Labels: (was: help_wanted) > Runtime download hyperlink not working from New Server dialog on Mac > -------------------------------------------------------------------- > > Key: JBIDE-19637 > URL: https://issues.jboss.org/browse/JBIDE-19637 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.3.0.Alpha2 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.3.0.CR1 > > > When you go through Servers view -> New Server -> EAP 6.1 -> New Runtime and then click "Download and install runtime...", it won't do anything. > If you go through Preferences -> Server -> Runtime Environments -> Add -> EAP 6.1+ and then click the Download button, it will work. > This issue applies to both JBDS 8.1.0.GA and JBoss Tools 4.3.0.Alpha2 testing build, but I doubt we will be able to fix this for 4.2.x. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15250) Explode utility jars in EAR/WAR deployments

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15250?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-15250: ------------------------------------- In general, there's a setting in the server editor's deployment page indicating if you prefer zipped deployment. When that is checked, we always zip. When that is unchecked, we attempt to use exploded as much as is possible based on what the server beneath it allows. > Explode utility jars in EAR/WAR deployments > ------------------------------------------- > > Key: JBIDE-15250 > URL: https://issues.jboss.org/browse/JBIDE-15250 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Affects Versions: 4.0.1.Final > Reporter: Kevin Formsma > Assignee: Rob Stryker > Labels: respin-a > Fix For: 4.3.0.Beta2 > > Attachments: test-ear.zip > > > For larger projects that utilize utility jars within the EAR, it would be nice to have these deployed exploded as well. This would allow hot code replacement for those utility projects. > A current work around is to make the utility projects modules so that the tooling treats them as a EJB module and deploys them exploded. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17686) get TCF and RSE terminals to coexist without bad UX of multiple terminals

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17686?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-17686: ------------------------------------- I guess setting up a remote host in the RSE explorer views and trying to open a terminal to it should still function. There should be some actions in that view to open a terminal to the host. > get TCF and RSE terminals to coexist without bad UX of multiple terminals > ------------------------------------------------------------------------- > > Key: JBIDE-17686 > URL: https://issues.jboss.org/browse/JBIDE-17686 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: server, upstream > Affects Versions: 4.2.0.Beta2 > Reporter: Max Rydahl Andersen > Assignee: Rob Stryker > Priority: Minor > Labels: new_and_noteworthy > Fix For: 4.3.0.Beta2 > > Attachments: eclipse-can-has-many-consoles.png, org.jboss.tools.as.management.itests.AS7IntegrationTestSuite.txt > > > luna has new Eclipse TCF terminal that brings better Terminal support. > I would assume it is in there but I couldn't find a way to actually open it. Maybe we havent included the full set of plugins. > http://marketplace.eclipse.org/content/tcf-terminals#.U6sJ92Vp7wV > http://eclipsesource.com/blogs/2014/06/17/tcf-terminal-top-eclipse-luna-f... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20399) Cannot create new OpenShift v3 application when launching wizard from Central in 4.3.0.beta2

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20399?page=com.atlassian.jira.plugi... ] Len DiMaggio commented on JBIDE-20399: -------------------------------------- Duplicate of: JBIDE-20372 > Cannot create new OpenShift v3 application when launching wizard from Central in 4.3.0.beta2 > -------------------------------------------------------------------------------------------- > > Key: JBIDE-20399 > URL: https://issues.jboss.org/browse/JBIDE-20399 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central, openshift > Affects Versions: 4.3.0.Beta2 > Reporter: Len DiMaggio > Assignee: Len DiMaggio > Attachments: Screenshot-4.png, Screenshot-5.png > > > See attached screen shots - any combination of user inputs returns this error if the user attempts to create a new v3 application: > The server type, credentials, or auth scheme might be incorrect. Could not get resource ~ in namespace : <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> > <html><head> > <title>404 Not Found</title> > </head><body> > <h1>Not Found</h1> > <p>The requested URL /oapi was not found on this server.</p> > <p>Additionally, a 403 Forbidden > error was encountered while trying to use an ErrorDocument to handle the request.</p> > <hr> > <address>Apache/2.2.15 (Red Hat) Server at openshift.redhat.com Port 443</address> > </body></html> -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20399) Cannot create new OpenShift v3 application when launching wizard from Central in 4.3.0.beta2

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20399?page=com.atlassian.jira.plugi... ] Len DiMaggio closed JBIDE-20399. -------------------------------- Resolution: Duplicate Issue > Cannot create new OpenShift v3 application when launching wizard from Central in 4.3.0.beta2 > -------------------------------------------------------------------------------------------- > > Key: JBIDE-20399 > URL: https://issues.jboss.org/browse/JBIDE-20399 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central, openshift > Affects Versions: 4.3.0.Beta2 > Reporter: Len DiMaggio > Assignee: Len DiMaggio > Attachments: Screenshot-4.png, Screenshot-5.png > > > See attached screen shots - any combination of user inputs returns this error if the user attempts to create a new v3 application: > The server type, credentials, or auth scheme might be incorrect. Could not get resource ~ in namespace : <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> > <html><head> > <title>404 Not Found</title> > </head><body> > <h1>Not Found</h1> > <p>The requested URL /oapi was not found on this server.</p> > <p>Additionally, a 403 Forbidden > error was encountered while trying to use an ErrorDocument to handle the request.</p> > <hr> > <address>Apache/2.2.15 (Red Hat) Server at openshift.redhat.com Port 443</address> > </body></html> -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20399) Cannot create new OpenShift v3 application when launching wizard from Central in 4.3.0.beta2

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20399?page=com.atlassian.jira.plugi... ] Len DiMaggio reassigned JBIDE-20399: ------------------------------------ Assignee: Len DiMaggio > Cannot create new OpenShift v3 application when launching wizard from Central in 4.3.0.beta2 > -------------------------------------------------------------------------------------------- > > Key: JBIDE-20399 > URL: https://issues.jboss.org/browse/JBIDE-20399 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central, openshift > Affects Versions: 4.3.0.Beta2 > Reporter: Len DiMaggio > Assignee: Len DiMaggio > Attachments: Screenshot-4.png, Screenshot-5.png > > > See attached screen shots - any combination of user inputs returns this error if the user attempts to create a new v3 application: > The server type, credentials, or auth scheme might be incorrect. Could not get resource ~ in namespace : <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> > <html><head> > <title>404 Not Found</title> > </head><body> > <h1>Not Found</h1> > <p>The requested URL /oapi was not found on this server.</p> > <p>Additionally, a 403 Forbidden > error was encountered while trying to use an ErrorDocument to handle the request.</p> > <hr> > <address>Apache/2.2.15 (Red Hat) Server at openshift.redhat.com Port 443</address> > </body></html> -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3119) XML Schema validation fails when importing external schema

by Brian Fitzpatrick (JIRA)

[ https://issues.jboss.org/browse/JBDS-3119?page=com.atlassian.jira.plugin.... ] Brian Fitzpatrick edited comment on JBDS-3119 at 7/29/15 12:58 PM: ------------------------------------------------------------------- This simpler SY example shows the same errors without all the extra baggage of the quickstart. With SY installed you'll see the same issues. I've included all the schema files from the org.switchyard.tools.xsd plug-in as well. We export all the schemas as part of a schema catalog file. You can see that at github. https://github.com/jboss-switchyard/tools/tree/master/eclipse/plugins/org... was (Author: bfitzpat): This simpler SY example shows the same errors without all the extra baggage of the quickstart. With SY installed you'll see the same issues. I've included all the schema files from the org.switchyard.tools.xsd plug-in as well. > XML Schema validation fails when importing external schema > ---------------------------------------------------------- > > Key: JBDS-3119 > URL: https://issues.jboss.org/browse/JBDS-3119 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: 3rd-party-dependencies, server > Affects Versions: 8.0.0.Beta3 > Reporter: Mustafa Musaji > Assignee: Rob Stryker > Attachments: bean-service-quickstart.zip, simplerSYexample.zip > > > Product JIRA for upstream bug - https://bugs.eclipse.org/bugs/show_bug.cgi?id=315741 > This is to track the upstream bug in Eclipse that we need to pull in to JBDS at some point. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3119) XML Schema validation fails when importing external schema

by Brian Fitzpatrick (JIRA)

[ https://issues.jboss.org/browse/JBDS-3119?page=com.atlassian.jira.plugin.... ] Brian Fitzpatrick edited comment on JBDS-3119 at 7/29/15 12:57 PM: ------------------------------------------------------------------- This simpler SY example shows the same errors without all the extra baggage of the quickstart. With SY installed you'll see the same issues. I've included all the schema files from the org.switchyard.tools.xsd plug-in as well. was (Author: bfitzpat): This simpler SY example shows the same errors without all the extra baggage of the quickstart. > XML Schema validation fails when importing external schema > ---------------------------------------------------------- > > Key: JBDS-3119 > URL: https://issues.jboss.org/browse/JBDS-3119 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: 3rd-party-dependencies, server > Affects Versions: 8.0.0.Beta3 > Reporter: Mustafa Musaji > Assignee: Rob Stryker > Attachments: bean-service-quickstart.zip, simplerSYexample.zip > > > Product JIRA for upstream bug - https://bugs.eclipse.org/bugs/show_bug.cgi?id=315741 > This is to track the upstream bug in Eclipse that we need to pull in to JBDS at some point. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3119) XML Schema validation fails when importing external schema

by Brian Fitzpatrick (JIRA)

[ https://issues.jboss.org/browse/JBDS-3119?page=com.atlassian.jira.plugin.... ] Brian Fitzpatrick updated JBDS-3119: ------------------------------------ Attachment: simplerSYexample.zip This simpler SY example shows the same errors without all the extra baggage of the quickstart. > XML Schema validation fails when importing external schema > ---------------------------------------------------------- > > Key: JBDS-3119 > URL: https://issues.jboss.org/browse/JBDS-3119 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: 3rd-party-dependencies, server > Affects Versions: 8.0.0.Beta3 > Reporter: Mustafa Musaji > Assignee: Rob Stryker > Attachments: bean-service-quickstart.zip, simplerSYexample.zip > > > Product JIRA for upstream bug - https://bugs.eclipse.org/bugs/show_bug.cgi?id=315741 > This is to track the upstream bug in Eclipse that we need to pull in to JBDS at some point. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 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 July 2015