February 2014 - jbosstools-issues

[JBoss JIRA] (TOOLSDOC-313) Copyrights and versions stated in documents do not align with the release version of the doc & the JBT release version

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-313?page=com.atlassian.jira.plug... ] Michelle Murray updated TOOLSDOC-313: ------------------------------------- Sprint: (was: Sprint 8 w2) > Copyrights and versions stated in documents do not align with the release version of the doc & the JBT release version > ---------------------------------------------------------------------------------------------------------------------- > > Key: TOOLSDOC-313 > URL: https://issues.jboss.org/browse/TOOLSDOC-313 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: General documentation issues > Affects Versions: 4.0.1, 4.1.0 > Reporter: Nick Boldt > Assignee: Michelle Murray > Fix For: 4.2.0.Beta1 > > > Some places where docs' copyright dates and stated versions do not align with the version of the doc: > {code:title=http://docs.jboss.org/tools/4.0.1.Final/en/GettingStartedGuide/html/index.html} > Version: 4.0.0 > Copyright © 2012 JBoss by Red Hat > {code} > {code:title=http://docs.jboss.org/tools/4.0.1.Final/en/beginners_guide/html/index.html} > Version: 3.3.0.M5 > Copyright © 2011 JBoss by Red Hat > {code} > {code:title=http://docs.jboss.org/tools/4.0.1.Final/en/as/html/index.html} > Version: 3.3.0.M5 > Copyright © 2007, 2008, 2009, 2010 JBoss by Red Hat > {code} > {code:title=http://docs.jboss.org/tools/4.0.1.Final/en/jmx_ref_guide/html/index.html} > Copyright © 2007, 2008, 2009, 2010, 2011 JBoss by Red Hat > {code} > And yes, this is still a problem in trunk: > {code:title=http://docs.jboss.org/tools/nightly/trunk/en/beginners_guide/html/index.html} > Version: 3.3.0.M5 > Copyright © 2011 JBoss by Red Hat > {code} > {code:title=http://docs.jboss.org/tools/nightly/trunk/en/forge_reference/html/index.html} > Version: 3.3.1 > Copyright © 2012 JBoss by Red Hat > {code} -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16419) JUnit Test failure: investigate time out/deadlock in JSF UI JUnit Tests

by Victor Rubezhny (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16419?page=com.atlassian.jira.plugi... ] Victor Rubezhny updated JBIDE-16419: ------------------------------------ Attachment: jstack.27042.log Stacktrace log of possible deadlock is attached (jstack.27042.log) > JUnit Test failure: investigate time out/deadlock in JSF UI JUnit Tests > ----------------------------------------------------------------------- > > Key: JBIDE-16419 > URL: https://issues.jboss.org/browse/JBIDE-16419 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsp/jsf/xml/html source editing > Affects Versions: 4.2.0.Alpha1 > Reporter: Victor Rubezhny > Assignee: Victor Rubezhny > Attachments: jstack.27042.log > > > Sometimes JUnit Tests for jbosstools-javaee component fail with timeout (probably deadlocked). > See example stacktrace attached -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16419) JUnit Test failure: investigate time out/deadlock in JSF UI JUnit Tests

by Victor Rubezhny (JIRA)

Victor Rubezhny created JBIDE-16419: --------------------------------------- Summary: JUnit Test failure: investigate time out/deadlock in JSF UI JUnit Tests Key: JBIDE-16419 URL: https://issues.jboss.org/browse/JBIDE-16419 Project: Tools (JBoss Tools) Issue Type: Bug Components: jsp/jsf/xml/html source editing Affects Versions: 4.2.0.Alpha1 Reporter: Victor Rubezhny Assignee: Victor Rubezhny Sometimes JUnit Tests for jbosstools-javaee component fail with timeout (probably deadlocked). See example stacktrace attached -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-455) OpenShift connection: Explanation of default server

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-455?page=com.atlassian.jira.plug... ] Michelle Murray updated TOOLSDOC-455: ------------------------------------- Assignee: Suz Dorfield (was: Michelle Murray) > OpenShift connection: Explanation of default server > --------------------------------------------------- > > Key: TOOLSDOC-455 > URL: https://issues.jboss.org/browse/TOOLSDOC-455 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: User Guide - OpenShift Tools > Affects Versions: 4.1.0 > Reporter: Marián Labuda > Assignee: Suz Dorfield > Priority: Minor > Fix For: 4.1.2 > > > When creating new connection to OpenShift server there is a CheckBox with default server. In documentation is unfortunately no explanation, what does it mean (there is just, that it's openshift.redhat.com - this is partially true - just in case, when user has in express.conf set up this server as default). It should be nice to have some explanation where are stored this value for default server and how does it behave after having values (see JBIDE-16401) -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-446) document how to debug on openshift JEE applications

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-446?page=com.atlassian.jira.plug... ] Michelle Murray updated TOOLSDOC-446: ------------------------------------- Assignee: Suz Dorfield (was: Michelle Murray) > document how to debug on openshift JEE applications > --------------------------------------------------- > > Key: TOOLSDOC-446 > URL: https://issues.jboss.org/browse/TOOLSDOC-446 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: User Guide - OpenShift Tools > Reporter: Max Rydahl Andersen > Assignee: Suz Dorfield > Fix For: 4.1.2, 4.2.0.Beta1 > > Original Estimate: 3 hours > Remaining Estimate: 3 hours > > would be great if Docs at https://access.redhat.com/site/documentation/en-US/Red_Hat_JBoss_Develope... > could outline how to enable/disable debugging and how to use port forwarding to connect to the debugger. > References: > https://community.jboss.org/en/tools/blog/2012/02/08/debugging-and-browsi... > http://vimeo.com/44548968 -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-447) Explain how to configure SSL options for connecting to Enterprise Servers.

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-447?page=com.atlassian.jira.plug... ] Michelle Murray updated TOOLSDOC-447: ------------------------------------- Assignee: Suz Dorfield (was: Michelle Murray) > Explain how to configure SSL options for connecting to Enterprise Servers. > -------------------------------------------------------------------------- > > Key: TOOLSDOC-447 > URL: https://issues.jboss.org/browse/TOOLSDOC-447 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: User Guide - OpenShift Tools > Affects Versions: 4.1.1 > Environment: Build Name: 22443, User Guide-7.1 > Build Date: 11-12-2013 15:10:49 > Topic ID: 25166-566980 [Latest] > Reporter: Eric Rich > Assignee: Suz Dorfield > Priority: Minor > Fix For: 4.1.1, 4.2.0.Beta1 > > Original Estimate: 30 minutes > Remaining Estimate: 30 minutes > > Title: Customizing Overview > Describe the issue: > It would be good to explain configuration options for connecting to multiple or different Enterprise Servers. > Also explaining how to manage your SSL certificates or update them for connection to Enterprise Servers or Online would be helpful. > Suggestions for improvement: > Additional information: -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-454) Generate Release Notes doc for JBDS 8.0.0CR1/GA

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-454?page=com.atlassian.jira.plug... ] Michelle Murray updated TOOLSDOC-454: ------------------------------------- Fix Version/s: 4.2.0.CR1 (was: 4.2.0.Beta1) > Generate Release Notes doc for JBDS 8.0.0CR1/GA > ----------------------------------------------- > > Key: TOOLSDOC-454 > URL: https://issues.jboss.org/browse/TOOLSDOC-454 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Release Notes > Reporter: Michelle Murray > Assignee: Michelle Murray > Fix For: 4.2.0.CR1 > > Original Estimate: 6 hours > Remaining Estimate: 6 hours > > Doc sections: > 1. Introduction to Red Hat JBoss Developer Studio > 1.1. About Red Hat JBoss Developer Studio > 1.2. Use Cases of JBoss Developer Studio > 2. About this Release > 3. New Features > 4. Resolved Issues > 5. Known Issues > 6. Apply this Release -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-453) Generate Release Notes doc for JBDS 8.0.0Beta2

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-453?page=com.atlassian.jira.plug... ] Michelle Murray updated TOOLSDOC-453: ------------------------------------- Fix Version/s: 4.2.0.Beta2 (was: 4.2.0.Beta1) > Generate Release Notes doc for JBDS 8.0.0Beta2 > ---------------------------------------------- > > Key: TOOLSDOC-453 > URL: https://issues.jboss.org/browse/TOOLSDOC-453 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Release Notes > Reporter: Michelle Murray > Assignee: Michelle Murray > Fix For: 4.2.0.Beta2 > > Original Estimate: 6 hours > Remaining Estimate: 6 hours > > Doc sections: > 1. Introduction to Red Hat JBoss Developer Studio > 1.1. About Red Hat JBoss Developer Studio > 1.2. Use Cases of JBoss Developer Studio > 2. About this Release > 3. New Features > 4. Resolved Issues > 5. Known Issues > 6. Apply this Release -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16343) "Materialize Libraries" is not obvious

by Burr Sutter (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16343?page=com.atlassian.jira.plugi... ] Burr Sutter commented on JBIDE-16343: ------------------------------------- I think one of the challenges is the word "library" - it is not really a word used in Java dev, nor in Maven world. Jars, artifacts, dependencies, archives, etc are more often used. > "Materialize Libraries" is not obvious > -------------------------------------- > > Key: JBIDE-16343 > URL: https://issues.jboss.org/browse/JBIDE-16343 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: maven > Affects Versions: 4.2.0.Alpha1 > Reporter: Mickael Istria > Assignee: Fred Bricon > Fix For: 4.2.x > > > While looking at [~fbricon] doing a demo I (and [~FroMage] and [~xcoulon]) felt that "Materialize Libraries" is not a clear name for what it does. > Why not renaming it to "Copy libraries into Project..." or "Turn into Libraries inside project..." ? -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16418) "Add Arquillian support" doesn't work for some pom.xml files

by Snjezana Peco (JIRA)

Snjezana Peco created JBIDE-16418: ------------------------------------- Summary: "Add Arquillian support" doesn't work for some pom.xml files Key: JBIDE-16418 URL: https://issues.jboss.org/browse/JBIDE-16418 Project: Tools (JBoss Tools) Issue Type: Bug Components: testing-tools Affects Versions: 4.2.0.Alpha2 Reporter: Snjezana Peco Assignee: Snjezana Peco Fix For: 4.2.0.Alpha2 Test case: - create a maven project with the following pom.xml: {code} <project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd"> <modelVersion>4.0.0</modelVersion> <groupId>org.jboss.tools.arquillian</groupId> <artifactId>test</artifactId> <version>0.0.1-SNAPSHOT</version> <properties> </properties> </project> {code} - select Configure>Add Arquillian support..., check all the checkboxes and click the OK button Just the properties section will be created. -- 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, 2 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 February 2014