January 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (TOOLSDOC-164) Extend JSF tutorial to include web services and add JSPRedirect template

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-164?page=com.atlassian.jira.plug... ] Michelle Murray reassigned TOOLSDOC-164: ---------------------------------------- Assignee: Michelle Murray (was: Isaac Rooskov) > Extend JSF tutorial to include web services and add JSPRedirect template > ------------------------------------------------------------------------ > > Key: TOOLSDOC-164 > URL: https://issues.jboss.org/browse/TOOLSDOC-164 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Task > Security Level: Public(Everyone can see) > Components: JSF Tools Tutorial > Affects Versions: 3.0.1.GA > Reporter: Isaac Rooskov > Assignee: Michelle Murray > Fix For: 4.1.0 > > > Extend JSF tutorial to include web services and add JSPRedirect template. -- 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

13 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-187) Portlet guide should show examples and screenshots using supported Red Hat releases (ie: EAP, EPP) not community releases of these products

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-187?page=com.atlassian.jira.plug... ] Michelle Murray reassigned TOOLSDOC-187: ---------------------------------------- Assignee: Michelle Murray (was: Isaac Rooskov) > Portlet guide should show examples and screenshots using supported Red Hat releases (ie: EAP, EPP) not community releases of these products > ------------------------------------------------------------------------------------------------------------------------------------------- > > Key: TOOLSDOC-187 > URL: https://issues.jboss.org/browse/TOOLSDOC-187 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Portlet Tools User Guide > Affects Versions: 3.2.0.Final > Reporter: Peter Larsen > Assignee: Michelle Murray > Priority: Critical > Fix For: Future > > > From Peter Larsen: > "http://docs.redhat.com/docs/en-US/JBoss_Developer_Studio/4.0/html-single/... > In this guide on how to create portlets, a community version > (unsupported, not provided by red hat) is used to illustrate how a > developer should setup an environment to develop EPP portlets. That > should refer to a supported version of EPP/EAP not community." -- 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

13 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-187) Portlet guide should show examples and screenshots using supported Red Hat releases (ie: EAP, EPP) not community releases of these products

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-187?page=com.atlassian.jira.plug... ] Michelle Murray updated TOOLSDOC-187: ------------------------------------- Fix Version/s: 4.1.0 (was: Future) > Portlet guide should show examples and screenshots using supported Red Hat releases (ie: EAP, EPP) not community releases of these products > ------------------------------------------------------------------------------------------------------------------------------------------- > > Key: TOOLSDOC-187 > URL: https://issues.jboss.org/browse/TOOLSDOC-187 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Portlet Tools User Guide > Affects Versions: 3.2.0.Final > Reporter: Peter Larsen > Assignee: Michelle Murray > Priority: Critical > Fix For: 4.1.0 > > > From Peter Larsen: > "http://docs.redhat.com/docs/en-US/JBoss_Developer_Studio/4.0/html-single/... > In this guide on how to create portlets, a community version > (unsupported, not provided by red hat) is used to illustrate how a > developer should setup an environment to develop EPP portlets. That > should refer to a supported version of EPP/EAP not community." -- 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

13 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-187) Portlet guide should show examples and screenshots using supported Red Hat releases (ie: EAP, EPP) not community releases of these products

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-187?page=com.atlassian.jira.plug... ] Michelle Murray commented on TOOLSDOC-187: ------------------------------------------ This will be reviewed during the creation of the new Portlet chapter in the JBDS/JBT user guide. > Portlet guide should show examples and screenshots using supported Red Hat releases (ie: EAP, EPP) not community releases of these products > ------------------------------------------------------------------------------------------------------------------------------------------- > > Key: TOOLSDOC-187 > URL: https://issues.jboss.org/browse/TOOLSDOC-187 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Portlet Tools User Guide > Affects Versions: 3.2.0.Final > Reporter: Peter Larsen > Assignee: Michelle Murray > Priority: Critical > Fix For: 4.1.0 > > > From Peter Larsen: > "http://docs.redhat.com/docs/en-US/JBoss_Developer_Studio/4.0/html-single/... > In this guide on how to create portlets, a community version > (unsupported, not provided by red hat) is used to illustrate how a > developer should setup an environment to develop EPP portlets. That > should refer to a supported version of EPP/EAP not community." -- 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

13 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-192) EPP and GateIn specific content for JBoss Portlet Guide

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-192?page=com.atlassian.jira.plug... ] Michelle Murray commented on TOOLSDOC-192: ------------------------------------------ [~irooskov] Has this JIRA already been resolve? The links for information no longer work and I have no idea what this JIRA is about. Please can you comment. > EPP and GateIn specific content for JBoss Portlet Guide > ------------------------------------------------------- > > Key: TOOLSDOC-192 > URL: https://issues.jboss.org/browse/TOOLSDOC-192 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Portlet Tools User Guide > Affects Versions: 3.2.1.Final > Reporter: Isaac Rooskov > Assignee: Isaac Rooskov > Fix For: Future > > > This JIRA will capture all the content differences I find that are specific to EPP and GateIn, for the Portlet Tools User Guide -- 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

13 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-251) Add documentation for Runtime detection

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-251?page=com.atlassian.jira.plug... ] Michelle Murray commented on TOOLSDOC-251: ------------------------------------------ This information should go in the new Installation Guide and Getting Started Guide. > Add documentation for Runtime detection > --------------------------------------- > > Key: TOOLSDOC-251 > URL: https://issues.jboss.org/browse/TOOLSDOC-251 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Beginners Guide, Getting Started Guide > Affects Versions: 3.2.2.Final > Reporter: Libor Zoubek > Assignee: Michelle Murray > Fix For: 4.1.0 > > > Hi Isaac, > I am going through begginers guide now (2.2.2. Adding a new application server for use with the JBoss Developer Studio). JBDS and JBoss Tools has a quite long time nice feature for adding server (and other) runtimes. I think it is a good idea to include it into guides or to switch current recommended way of adding runtimes to it - it is much more simple and it is one of many added values of JBT compared to eclipse. > You can play with runtime detection if you open Preferences->Jboss Tools->Runtime Detection. Main idea is, that you just select any directory and JBT scans it recursively and searches for runtimes. If it founds any, you can select it to be added. Good thing is that both server runtime and server with all other runtimes (seam,jbpm) is added. > You can contact Snjezana, she is developing runtime detectors and has much deeper details about it. -- 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

13 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-251) Add documentation for Runtime detection

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-251?page=com.atlassian.jira.plug... ] Michelle Murray updated TOOLSDOC-251: ------------------------------------- Fix Version/s: 4.1.0 (was: Future) > Add documentation for Runtime detection > --------------------------------------- > > Key: TOOLSDOC-251 > URL: https://issues.jboss.org/browse/TOOLSDOC-251 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Beginners Guide, Getting Started Guide > Affects Versions: 3.2.2.Final > Reporter: Libor Zoubek > Assignee: Isaac Rooskov > Fix For: 4.1.0 > > > Hi Isaac, > I am going through begginers guide now (2.2.2. Adding a new application server for use with the JBoss Developer Studio). JBDS and JBoss Tools has a quite long time nice feature for adding server (and other) runtimes. I think it is a good idea to include it into guides or to switch current recommended way of adding runtimes to it - it is much more simple and it is one of many added values of JBT compared to eclipse. > You can play with runtime detection if you open Preferences->Jboss Tools->Runtime Detection. Main idea is, that you just select any directory and JBT scans it recursively and searches for runtimes. If it founds any, you can select it to be added. Good thing is that both server runtime and server with all other runtimes (seam,jbpm) is added. > You can contact Snjezana, she is developing runtime detectors and has much deeper details about it. -- 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

13 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-251) Add documentation for Runtime detection

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-251?page=com.atlassian.jira.plug... ] Michelle Murray reassigned TOOLSDOC-251: ---------------------------------------- Assignee: Michelle Murray (was: Isaac Rooskov) > Add documentation for Runtime detection > --------------------------------------- > > Key: TOOLSDOC-251 > URL: https://issues.jboss.org/browse/TOOLSDOC-251 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Beginners Guide, Getting Started Guide > Affects Versions: 3.2.2.Final > Reporter: Libor Zoubek > Assignee: Michelle Murray > Fix For: 4.1.0 > > > Hi Isaac, > I am going through begginers guide now (2.2.2. Adding a new application server for use with the JBoss Developer Studio). JBDS and JBoss Tools has a quite long time nice feature for adding server (and other) runtimes. I think it is a good idea to include it into guides or to switch current recommended way of adding runtimes to it - it is much more simple and it is one of many added values of JBT compared to eclipse. > You can play with runtime detection if you open Preferences->Jboss Tools->Runtime Detection. Main idea is, that you just select any directory and JBT scans it recursively and searches for runtimes. If it founds any, you can select it to be added. Good thing is that both server runtime and server with all other runtimes (seam,jbpm) is added. > You can contact Snjezana, she is developing runtime detectors and has much deeper details about it. -- 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

13 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-279) Missing documentation about connection configuration possibilities

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-279?page=com.atlassian.jira.plug... ] Michelle Murray commented on TOOLSDOC-279: ------------------------------------------ [~dgeraskov] [~koen.aers] I am looking to resolve this JIRA. I had a look at the latest version of the Hibernate Tools Reference Guide (http://docs.jboss.org/tools/nightly/trunk/en/hibernatetools/html_single/i...) but could not determine if this information has been added yet. Please can you confirm if it has been added or still needs to be? Thanks. > Missing documentation about connection configuration possibilities > ------------------------------------------------------------------ > > Key: TOOLSDOC-279 > URL: https://issues.jboss.org/browse/TOOLSDOC-279 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Hibernate Tools Reference Guide > Affects Versions: 3.3.0.Beta1 > Reporter: Jiri Peterka > Assignee: Koen Aers > Fix For: Future > > > Connection configuration possibilities chapter should be added (connection from data tool, hibernate.cfg.xml in persistence unit, persitence.xml, etc.), datasources usage > http://documentation-stage.bne.redhat.com/docs/en-US/JBoss_Developer_Stud... -- 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

13 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-286) BYOE - Warn of upgrade scenario for Bring Your Own Eclipse in Release Notes (per GSS)

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-286?page=com.atlassian.jira.plug... ] Michelle Murray reassigned TOOLSDOC-286: ---------------------------------------- Assignee: Michelle Murray (was: Isaac Rooskov) > BYOE - Warn of upgrade scenario for Bring Your Own Eclipse in Release Notes (per GSS) > ------------------------------------------------------------------------------------- > > Key: TOOLSDOC-286 > URL: https://issues.jboss.org/browse/TOOLSDOC-286 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Release Notes > Affects Versions: 4.0.0.Final > Reporter: mark yarborough > Assignee: Michelle Murray > Fix For: 4.0.1 > > -- 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

13 years, 6 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 2013