November 2013 - jbosstools-issues

[JBoss JIRA] (JBIDE-16106) Bump maven-war-plugin version to 2.4 in openshift profile

by Fred Bricon (JIRA)

Fred Bricon created JBIDE-16106: ----------------------------------- Summary: Bump maven-war-plugin version to 2.4 in openshift profile Key: JBIDE-16106 URL: https://issues.jboss.org/browse/JBIDE-16106 Project: Tools (JBoss Tools) Issue Type: Enhancement Reporter: Fred Bricon -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16105) openshift-java-client: offer access to timeout

by Andre Dietisheim (JIRA)

Andre Dietisheim created JBIDE-16105: ---------------------------------------- Summary: openshift-java-client: offer access to timeout Key: JBIDE-16105 URL: https://issues.jboss.org/browse/JBIDE-16105 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: openshift Affects Versions: 4.1.1.CR1 Reporter: Andre Dietisheim Fix For: 4.2.x express.conf now offers a setting for timeouts: {code} # The default timeout for network operations #timeout=<integer> {code} we currently offer direct access via identical key. Since *timeout* is a very common name we should most likely offer also prefixed access (ex. openshift.timeout). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2636) rebrand devstudio.jboss.com pages with "Red Hat JBoss Developer Studio" instead of "JBoss Developer Studio"

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2636?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-2636: ---------------------------------- FYI, the PDF linked in the original problem statement here has not been updated, but there's a new one linked: https://www.redhat.com/resourcelibrary/datasheets/JBoss-Developer-Studio-... -> https://www.redhat.com/rhecm/rest-rhecm/jcr/repository/collaboration/jcr:... [latest version #6] https://www.redhat.com/rhecm/rest-rhecm/jcr/repository/collaboration/jcr:... [old version #5] > rebrand devstudio.jboss.com pages with "Red Hat JBoss Developer Studio" instead of "JBoss Developer Studio" > ----------------------------------------------------------------------------------------------------------- > > Key: JBDS-2636 > URL: https://issues.jboss.org/browse/JBDS-2636 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Security Level: Public(Everyone can see) > Components: updatesite > Affects Versions: 7.0.0.Beta1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Critical > Fix For: 7.0.0.CR1 > > Attachments: devstudio_logo_132x95.png, jbds-marketplace-download-now.png, RHJBDS_banner.png > > > New requirement from MW management. Rebrand the pages to state "Red Hat JBoss Developer Studio" instead of "JBoss Developer Studio". > Similar changes should happen on jboss.org/tools pages which mention JBDS as well. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15796) Deployment error: No servlet class has been specified for servlet javax.ws.rs.core.Application

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15796?page=com.atlassian.jira.plugi... ] Pavol Srna closed JBIDE-15796. ------------------------------ The problem is tracked in FORGEPLUGINS-149 and a workaround exists. I'm gonna close the issue. > Deployment error: No servlet class has been specified for servlet javax.ws.rs.core.Application > ----------------------------------------------------------------------------------------------- > > Key: JBIDE-15796 > URL: https://issues.jboss.org/browse/JBIDE-15796 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.1.1.Beta1 > Reporter: Pavol Srna > Assignee: Koen Aers > Fix For: 4.1.1.CR1 > > Attachments: forge-html5.server.log > > > Deployment with error: No servlet class has been specified for servlet javax.ws.rs.core.Application. > Prepare app in forge console: > 1) new-project --named testp --type war > 2) setup persistence (HIBERNATE, JBOSS_AS7) > 3) scaffold-x setup --scaffoldType angularjs --overwrite > 4) entity --named Customer > 5) field string --named name > Scaffold HTML5: > * scaffold-x from Customer.java > Build and deploy on the server. > See server.log attached for more description. > I assume this should work out of the box right? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15788) Download runtime wizard shouldn't complain if install folder doesn't exist

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15788?page=com.atlassian.jira.plugi... ] Martin Malina updated JBIDE-15788: ---------------------------------- Fix Version/s: 4.1.2 (was: 4.1.1.CR1) Labels: (was: respin-a) I don't think there will be another respin, so this will not make it into 4.1.1. Or do you prefer to resolve this as partially fixed and open a new jira? Let me know. > Download runtime wizard shouldn't complain if install folder doesn't exist > -------------------------------------------------------------------------- > > Key: JBIDE-15788 > URL: https://issues.jboss.org/browse/JBIDE-15788 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: runtime-detection, server > Affects Versions: 4.1.1.Alpha2 > Reporter: Fred Bricon > Assignee: Rob Stryker > Fix For: 4.1.2 > > Attachments: cr1-nonexistent-folder.png, install_folder_must_exist.png > > > If the install folder is missing, the download runtime wizard should cope with it, instead of displaying an error (i.e. create the missing folders when necessary) > - assert no EAP/AS7 are installed > - create a new html5 project from central > - click download and install for the server requirement > - enter a non-existing location for the install folder > !install_folder_must_exist.png! -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15773) Forge Generate Entities wizard: Select connection profile name automatically

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15773?page=com.atlassian.jira.plugi... ] Pavol Srna closed JBIDE-15773. ------------------------------ Verified in JBT 4.1.1.CR1a build. > Forge Generate Entities wizard: Select connection profile name automatically > ----------------------------------------------------------------------------- > > Key: JBIDE-15773 > URL: https://issues.jboss.org/browse/JBIDE-15773 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: forge > Reporter: Pavol Srna > Assignee: Koen Aers > Fix For: 4.1.1.CR1 > > Attachments: forge-connection.png > > > Imagine a situation when there is no connection profile defined. You click on new, fill in all details - click on finish (in the new profile connection dialog). Then I would expect to have Connection Profile Name pre-filled with the 'in previous step' created connection profile. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16001) JBoss Central New and Noteworthy for 4.1.1.CR1

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16001?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-16001: ------------------------------------ AFAIK the major N&N changes to Central are: * drag and drop support added :: JBIDE-15499 * 3 new connectors added: m2e-wro4j, Mylyn Jenkins Build, Checkstyle (eclipsecs) :: JBDS-2710 * 6 connectors under Software/Update tab updated to newer versions: Atlassian, PMD, TestNG, VJET, SpringIDE, GWT :: JBDS-2710 ** In particular, Google Plugin for Eclipse 4.2 (e42) version 3.2.3 updated to Google Plugin for Eclipse 4.3 (e43) version 3.4.2, which may require remediation/uninstall to perform an update/upgrade :: JBDS-2801 > JBoss Central New and Noteworthy for 4.1.1.CR1 > ---------------------------------------------- > > Key: JBIDE-16001 > URL: https://issues.jboss.org/browse/JBIDE-16001 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: central > Reporter: Max Rydahl Andersen > Priority: Critical > Fix For: 4.1.1.CR1 > > > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...]. > If JBoss Central is not listed here check if there are issues that should be added and add them. > Document the ones relevant for JBoss Central by adding to [whatsnew|https://github.com/jbosstools/jbosstools-documentation/tree/mast...] and submit a pullrequest. > If no news for this component please reject and close this issue. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15828) Forge wizards don't report any errors to the user

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15828?page=com.atlassian.jira.plugi... ] Pavol Srna closed JBIDE-15828. ------------------------------ > Forge wizards don't report any errors to the user > ------------------------------------------------- > > Key: JBIDE-15828 > URL: https://issues.jboss.org/browse/JBIDE-15828 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.1.1.Beta1 > Reporter: Pavol Srna > Assignee: Koen Aers > Fix For: 4.1.1.CR1 > > > Sometimes happens that forge wizard (e.g. Scaffolding) didn't generate code at all. And there is no obvious reason for that. In my opinion forge wizard should say on a very last page if the operation was successful or not. And if not then display the error message to the user. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16063) Aborting a command has strange behavior

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16063?page=com.atlassian.jira.plugi... ] Pavol Srna closed JBIDE-16063. ------------------------------ > Aborting a command has strange behavior > ---------------------------------------- > > Key: JBIDE-16063 > URL: https://issues.jboss.org/browse/JBIDE-16063 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Reporter: Pavol Srna > Assignee: Koen Aers > Labels: respin-a > Fix For: 4.1.1.CR1 > > Attachments: forge-screen-1.png, forge-screen-2.png > > > I see 2 problems how aborting a command currently works. > * If the console is empty and you send Ctrl+C, then the text "[killed]" appears in the console. I guess nothing was actually killed. Then I try to for example create a new project and trigger: 'new-project --named testProject' and this command is swallowed or killed? Please see attached screenshot: > !forge-screen-1.png! > * Second, .. I tried several times to abort "an already in progress new-project" command but sometimes it succeeds and sometimes not. Like on my next screenshot. I figured out that it depends on the speed how fast I press the abort keys on the keyboard. It wasn't very hard for me to simulate the error. > !forge-screen-2.png! -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13374) Building JAX-RS metamodel is sometimes slow when running swt bot tests

by Vlado Pakan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13374?page=com.atlassian.jira.plugi... ] Vlado Pakan reassigned JBIDE-13374: ----------------------------------- Assignee: Radoslav Rábara (was: Vlado Pakan) > Building JAX-RS metamodel is sometimes slow when running swt bot tests > ---------------------------------------------------------------------- > > Key: JBIDE-13374 > URL: https://issues.jboss.org/browse/JBIDE-13374 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: webservices > Affects Versions: 4.0.0.Final > Reporter: Jaroslav Jankovič > Assignee: Radoslav Rábara > Fix For: 4.2.x > > Attachments: jaxrs-metamodel.avi > > > When I run web services swtbot tests, I am sometimes facing really slow JAX-RS metamodel building, it can take almost a minute to finish it, so it really affects running time of my tests. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 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 November 2013