January 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-21486) HTML5 Project and Java EE Web Project in the Getting Started tab do not allow clicking

by Supriya Bharadwaj (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21486?page=com.atlassian.jira.plugi... ] Supriya Bharadwaj reassigned JBIDE-21486: ----------------------------------------- Assignee: Radim Hopp > HTML5 Project and Java EE Web Project in the Getting Started tab do not allow clicking > --------------------------------------------------------------------------------------- > > Key: JBIDE-21486 > URL: https://issues.jboss.org/browse/JBIDE-21486 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Affects Versions: 4.3.1.Beta1 > Reporter: Supriya Bharadwaj > Assignee: Radim Hopp > > I have downloaded Red Hat JBoss Developer Studio 9.1.0 Beta 1 Installer with EAP from the Customer Portal (https://access.redhat.com/jbossnetwork/restricted/listSoftware.html?produ...). > In the Getting Started tab, if I hover the mouse over HTML5 Project and Java EE Web Project, the display keeps moving and does not allow me to click these two project types. A possible bug? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-667) Document how to use the EAP online maven repo

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-667?page=com.atlassian.jira.plug... ] Martin Malina commented on TOOLSDOC-667: ---------------------------------------- Hi [~supriya.bharadwaj], as discussed earlier today on IRC, the part about online maven repo is now fine with me. And I checked the rest and everything else seems ok, too. So you can proceed with publishing the update. > Document how to use the EAP online maven repo > --------------------------------------------- > > Key: TOOLSDOC-667 > URL: https://issues.jboss.org/browse/TOOLSDOC-667 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Feature Request > Affects Versions: 4.3.0.Final > Reporter: Martin Malina > Assignee: Supriya Bharadwaj > Fix For: 4.3.0.Final > > > In TOOLSDOC-499 it was mentioned that we have a guide that explains how to add jboss enterprise maven repositories, but it would be nice to also mention the alternative of using the online repo. > From TOOLSDOC-499: > {quote} > Alternatively, you can use the online repository: In the Add Maven Repository dialog, in the Profile ID field at the top, select "redhat-techpreview-all-repository" in the drop down menu. This will add http://maven.repository.redhat.com/techpreview/all/ to your settings.xml and that should satisfy the dependencies. > {quote} > Something similar could be added in a box in this doc: > https://access.redhat.com/articles/1160993#ConfigureMaven > (or a similar doc for JBDS 9 once it's ready) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3583) Cannot start JBDS 9 with jdk 1.9 EA

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBDS-3583?page=com.atlassian.jira.plugin.... ] Snjezana Peco updated JBDS-3583: -------------------------------- Component/s: upstream > Cannot start JBDS 9 with jdk 1.9 EA > ----------------------------------- > > Key: JBDS-3583 > URL: https://issues.jboss.org/browse/JBDS-3583 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer, upstream > Affects Versions: 9.1.0.Beta1 > Reporter: Martin Malina > Assignee: Snjezana Peco > Fix For: 9.1.0.Beta2, 9.1.0.CR1, 10.0.0.Alpha1 > > > Oracle changed their JDK 1.9 Early Access builds recently. Now the installed jdk reports its version as 9-ea instead of 1.9 used previously. This caused a problem with the JBDS installer: JBDS-3581 > But even if I select jdk 1.8 in the installer and change jbdevstudio.ini to point to my 1.9 installation, JBDS won't start (I'm on Mac). > It just shows an error saying where to look for log. The log is linked here: > https://issues.jboss.org/secure/attachment/12396824/1453206771791.log -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3583) Cannot start JBDS 9 with jdk 1.9 EA

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBDS-3583?page=com.atlassian.jira.plugin.... ] Snjezana Peco commented on JBDS-3583: ------------------------------------- [~jrichter1] I agree. Eclipse doesn't recognize JDK 9 as Installed JRE. > Cannot start JBDS 9 with jdk 1.9 EA > ----------------------------------- > > Key: JBDS-3583 > URL: https://issues.jboss.org/browse/JBDS-3583 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 9.1.0.Beta1 > Reporter: Martin Malina > Assignee: Snjezana Peco > Fix For: 9.1.0.Beta2, 9.1.0.CR1, 10.0.0.Alpha1 > > > Oracle changed their JDK 1.9 Early Access builds recently. Now the installed jdk reports its version as 9-ea instead of 1.9 used previously. This caused a problem with the JBDS installer: JBDS-3581 > But even if I select jdk 1.8 in the installer and change jbdevstudio.ini to point to my 1.9 installation, JBDS won't start (I'm on Mac). > It just shows an error saying where to look for log. The log is linked here: > https://issues.jboss.org/secure/attachment/12396824/1453206771791.log -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21463) Port Forwarding: No error message pop up when attempt to port-forward to a port in use

by Xia Zhao (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21463?page=com.atlassian.jira.plugi... ] Xia Zhao commented on JBIDE-21463: ---------------------------------- [~adietish] Take php as an example, we can simply modify https://github.com/openshift/cakephp-ex/blob/master/app/View/Layouts/defa... to give a different strings to the webservice call, and then deploy the application via oc new-app -f https://raw.githubusercontent.com/openshift/cakephp-ex/master/openshift/t... -p OPCACHE_REVALIDATE_FREQ=0 Note: please modify SOURCE_REPOSITORY_URL in cakephp.json to the repo contain modified strings. Another way to approach this is to occupy local port 8080 by a 3rd party app, e.g. jenkins or jboss eap. In this way we only need to deploy a single application into openshift, and see whether the 3rd app is still alive after port-forwarding. Thanks, Xia > Port Forwarding: No error message pop up when attempt to port-forward to a port in use > -------------------------------------------------------------------------------------- > > Key: JBIDE-21463 > URL: https://issues.jboss.org/browse/JBIDE-21463 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta2 > Environment: OpenShift 3 Tools: 3.1.0.Beta2-v20160114-1935-B149 > OS: Fedora 17 & MAC OS 10 > Reporter: Xia Zhao > Labels: openshift_v3, port_forwarding_wizard > Fix For: 4.3.1.CR1 > > > No error message pop up when attempt to port-forward to a port in use in Jboss Developer Studio. This issue does not repro in Eclipse on Mac OS. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21484) New Server Wizard: service tree has erroneous labels on Linux/GTK3

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21484?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-21484: ------------------------------------------ This is not an error, I caused this by mistake when using the 4.50.x target platform instead of 4.51.x > New Server Wizard: service tree has erroneous labels on Linux/GTK3 > ------------------------------------------------------------------ > > Key: JBIDE-21484 > URL: https://issues.jboss.org/browse/JBIDE-21484 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta2 > Reporter: Andre Dietisheim > Priority: Critical > Fix For: 4.3.1.Beta2 > > Attachments: erroneous-service-labels.png > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21484) New Server Wizard: service tree has erroneous labels on Linux/GTK3

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21484?page=com.atlassian.jira.plugi... ] Andre Dietisheim resolved JBIDE-21484. -------------------------------------- Fix Version/s: 4.3.1.Beta2 Assignee: Andre Dietisheim Resolution: Rejected > New Server Wizard: service tree has erroneous labels on Linux/GTK3 > ------------------------------------------------------------------ > > Key: JBIDE-21484 > URL: https://issues.jboss.org/browse/JBIDE-21484 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Critical > Fix For: 4.3.1.Beta2 > > Attachments: erroneous-service-labels.png > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21475) Use vagrant.bat to start vagrant

by Hardy Ferentschik (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21475?page=com.atlassian.jira.plugi... ] Hardy Ferentschik commented on JBIDE-21475: ------------------------------------------- {quote} When I tested it in windows, just 'vagrant' worked 100% as expected. {quote} Right, that would be my expectation. We definitely should work towards this in case there are problems. > Use vagrant.bat to start vagrant > -------------------------------- > > Key: JBIDE-21475 > URL: https://issues.jboss.org/browse/JBIDE-21475 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.3.1.Beta2 > Environment: Windows > Reporter: Denis Golovin > Priority: Blocker > > CDK adapter uses %VRGANT_PATH%\bin\vagrant to start vagrant on windows, but vargant file is a shell script. vagrant.bat should be used instead. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21485) webservices artifacts should extend ModuleArtifactDelegate to be used by launchbar

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21485?page=com.atlassian.jira.plugi... ] Xavier Coulon resolved JBIDE-21485. ----------------------------------- Fix Version/s: 4.4.0.Alpha1 (was: 4.3.1.Beta2) Resolution: Done PR merged on {{master}} branch for 4.4.0.Alpha1 version > webservices artifacts should extend ModuleArtifactDelegate to be used by launchbar > ---------------------------------------------------------------------------------- > > Key: JBIDE-21485 > URL: https://issues.jboss.org/browse/JBIDE-21485 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: webservices > Reporter: Rob Stryker > Assignee: Xavier Coulon > Priority: Minor > Fix For: 4.4.0.Alpha1 > > > WTP will customize the 'run on server' action to use launch configurations rather than their standard API if the module artifact in question extends ModuleArtifactDelegate instead of implements IModuleArtifact. Launchbar works entirely on launch configurations, and so can only really allow quick access to the run-on-server actions for such modules. > The ModuleArtifactDelegate class provides two methods that you will need to override to give it enough information to properly locate the artifact: serialize and deserialize. The idea is to serialize with enough information such that the artifact can be re-instantiated and unserialized later. > The only class using the getEndpoint() method in JaxrsEndpointModuleArtifact is WSTesterClientDelegate, and this class only gets the endpoint so that it can calculate the endpoint URI and get the HTTP method.... so you'd probably want to move the computeEndpointURI logic into the JaxrsEndpointModuleArtifact, and, on serialization, save the endpoint URI and the http verb. > See also: https://issues.jboss.org/browse/JBIDE-20802 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21485) webservices artifacts should extend ModuleArtifactDelegate to be used by launchbar

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21485?page=com.atlassian.jira.plugi... ] Xavier Coulon edited comment on JBIDE-21485 at 1/20/16 5:48 AM: ---------------------------------------------------------------- PR merged on {{master}} branch for version {{4.4.0.Alpha1}}. was (Author: xcoulon): PR merged on {{master}} branch for 4.4.0.Alpha1 version > webservices artifacts should extend ModuleArtifactDelegate to be used by launchbar > ---------------------------------------------------------------------------------- > > Key: JBIDE-21485 > URL: https://issues.jboss.org/browse/JBIDE-21485 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: webservices > Reporter: Rob Stryker > Assignee: Xavier Coulon > Priority: Minor > Fix For: 4.4.0.Alpha1 > > > WTP will customize the 'run on server' action to use launch configurations rather than their standard API if the module artifact in question extends ModuleArtifactDelegate instead of implements IModuleArtifact. Launchbar works entirely on launch configurations, and so can only really allow quick access to the run-on-server actions for such modules. > The ModuleArtifactDelegate class provides two methods that you will need to override to give it enough information to properly locate the artifact: serialize and deserialize. The idea is to serialize with enough information such that the artifact can be re-instantiated and unserialized later. > The only class using the getEndpoint() method in JaxrsEndpointModuleArtifact is WSTesterClientDelegate, and this class only gets the endpoint so that it can calculate the endpoint URI and get the HTTP method.... so you'd probably want to move the computeEndpointURI logic into the JaxrsEndpointModuleArtifact, and, on serialization, save the endpoint URI and the http verb. > See also: https://issues.jboss.org/browse/JBIDE-20802 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 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 January 2016