August 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (TOOLSDOC-16) New algorithm for layout of mapping diagrams

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-16?page=com.atlassian.jira.plugi... ] Michelle Murray updated TOOLSDOC-16: ------------------------------------ Fix Version/s: 4.2.0 (was: 4.1.0) > New algorithm for layout of mapping diagrams > -------------------------------------------- > > Key: TOOLSDOC-16 > URL: https://issues.jboss.org/browse/TOOLSDOC-16 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Feature Request > Components: User Guide - Hibernate Tools > Affects Versions: 3.0.0.GA > Reporter: Svetlana Mukhina > Assignee: Michelle Murray > Fix For: 4.2.0 > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > update 4.10.1.1. Mapping Diagram > see the linked task and its subtask -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-309) Amend nightly build for new JBT 4.1 docs

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-309?page=com.atlassian.jira.plug... ] Michelle Murray commented on TOOLSDOC-309: ------------------------------------------ Jenkins job done. Now need to update http://docs.jboss.org/tools/ > Amend nightly build for new JBT 4.1 docs > ---------------------------------------- > > Key: TOOLSDOC-309 > URL: https://issues.jboss.org/browse/TOOLSDOC-309 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Website > Affects Versions: 4.1.0 > Reporter: Michelle Murray > Assignee: Michelle Murray > > Nightly builds of developing docs currently uses 'jbosstools-documentation/guides' dir as the source of build info and docs locations. > 1) New docs are in 'jbosstools-documentation/docs' dir so nightly build config needs updating. > 2) Should also create new dir to hold build source info (pom.xml, master.xml). Creating from scratch will ensure bare minimum of information during transitioning. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-319) Complete use case for mobile applications

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-319?page=com.atlassian.jira.plug... ] Michelle Murray commented on TOOLSDOC-319: ------------------------------------------ Deferred as CordovaSim is only part of JBT as tech preview at this time. > Complete use case for mobile applications > ----------------------------------------- > > Key: TOOLSDOC-319 > URL: https://issues.jboss.org/browse/TOOLSDOC-319 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Getting Started Guide, Installation Guide, Migration Guide, User Guide > Affects Versions: 4.1.0 > Reporter: Michelle Murray > Assignee: Michelle Murray > -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-319) Complete use case for mobile applications

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-319?page=com.atlassian.jira.plug... ] Michelle Murray resolved TOOLSDOC-319. -------------------------------------- Resolution: Deferred > Complete use case for mobile applications > ----------------------------------------- > > Key: TOOLSDOC-319 > URL: https://issues.jboss.org/browse/TOOLSDOC-319 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Getting Started Guide, Installation Guide, Migration Guide, User Guide > Affects Versions: 4.1.0 > Reporter: Michelle Murray > Assignee: Michelle Murray > -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-307) Document OpenShift Drag and Drop functionality

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-307?page=com.atlassian.jira.plug... ] Michelle Murray updated TOOLSDOC-307: ------------------------------------- Issue Type: Feature Request (was: Task) > Document OpenShift Drag and Drop functionality > ---------------------------------------------- > > Key: TOOLSDOC-307 > URL: https://issues.jboss.org/browse/TOOLSDOC-307 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: User Guide - OpenShift Tools > Affects Versions: 4.1.0 > Reporter: Michelle Murray > Assignee: Michelle Murray > Fix For: 4.1.1 > > > Need to document this: > Drag and Drop > http://docs.jboss.org/tools/whatsnew/openshift/openshift-news-2.3.0.Beta1... > In addition we now also support you to drag any existing deployable artifact such as WTP projects, deployable datasources etc. to the OpenShift server. If these artifacts are not part of the "source" project the server adapter will package them up and place by default inside the /deployments folder of the project. Then when git push occurs these binaries will be part of the deployments on OpenShift for the "source" project. > This is what we call "binary" deployment and is useful for applications that for any reasons or another cannot be build remotely. > Note: OpenShift have a storage limit thus storing to many binaries or doing too many binary changes will make you reach this limit faster so be careful. > http://docs.jboss.org/tools/whatsnew/openshift/openshift-news-2.4.0.Alpha... > Previously, when a user performed a drag-and-drop action to publish a project it was ignored. In Alpha1 you'll now be able to publishing your project to your OpenShift cloud by drag and dropping your project to the OpenShift server adapter. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-356) Update tutorial example in GSG to incorporate more of the new features

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-356?page=com.atlassian.jira.plug... ] Michelle Murray updated TOOLSDOC-356: ------------------------------------- Issue Type: Enhancement (was: Task) > Update tutorial example in GSG to incorporate more of the new features > ---------------------------------------------------------------------- > > Key: TOOLSDOC-356 > URL: https://issues.jboss.org/browse/TOOLSDOC-356 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Getting Started Guide > Affects Versions: 4.1.0 > Reporter: Michelle Murray > Assignee: Michelle Murray > Fix For: 4.2.0 > > > For the next major release, the Getting Started Guide tutorial should be extended/updated. With more understanding of the product, could move away from Ticket Monster tutorial and have something unique. > Things to incorporate include: > * jQuery Mobile palette > * more BrowserSim features > * OpenShift (with Weinre?) > ... > _(add more)_ -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-381) Technical Review of 7.0 Getting Started Guide

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-381?page=com.atlassian.jira.plug... ] Michelle Murray commented on TOOLSDOC-381: ------------------------------------------ PR applied to master and 4.1.x: https://github.com/jbosstools/jbosstools-documentation/pull/151 Doc brewed and available for review: http://documentation-devel.engineering.redhat.com/docs/en-US/Red_Hat_JBos... > Technical Review of 7.0 Getting Started Guide > --------------------------------------------- > > Key: TOOLSDOC-381 > URL: https://issues.jboss.org/browse/TOOLSDOC-381 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: Getting Started Guide > Affects Versions: 4.1.0 > Reporter: Michelle Murray > Assignee: Michelle Murray > Fix For: 4.1.0 > > > Conduct a post release technical review of 7.0 Getting Started Guide to catch any previously missed technical or copy errors. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-381) Technical Review of 7.0 Getting Started Guide

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-381?page=com.atlassian.jira.plug... ] Michelle Murray resolved TOOLSDOC-381. -------------------------------------- Resolution: Done > Technical Review of 7.0 Getting Started Guide > --------------------------------------------- > > Key: TOOLSDOC-381 > URL: https://issues.jboss.org/browse/TOOLSDOC-381 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: Getting Started Guide > Affects Versions: 4.1.0 > Reporter: Michelle Murray > Assignee: Michelle Murray > Fix For: 4.1.0 > > > Conduct a post release technical review of 7.0 Getting Started Guide to catch any previously missed technical or copy errors. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-381) Technical Review of 7.0 Getting Started Guide

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-381?page=com.atlassian.jira.plug... ] Michelle Murray commented on TOOLSDOC-381: ------------------------------------------ Anchors fixed: * 5.2. Set Up a Server Using Runtime Detection * 5.7. Deploy the Application using JBoss Server Tools > Technical Review of 7.0 Getting Started Guide > --------------------------------------------- > > Key: TOOLSDOC-381 > URL: https://issues.jboss.org/browse/TOOLSDOC-381 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: Getting Started Guide > Affects Versions: 4.1.0 > Reporter: Michelle Murray > Assignee: Michelle Murray > Fix For: 4.1.0 > > > Conduct a post release technical review of 7.0 Getting Started Guide to catch any previously missed technical or copy errors. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-381) Technical Review of 7.0 Getting Started Guide

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-381?page=com.atlassian.jira.plug... ] Michelle Murray commented on TOOLSDOC-381: ------------------------------------------ Typos fixed: * 2.1 About Getting Started = For more information about the alternative installation *method* (> methods) And: see *JBoss Developer Studio 7 Installation Guide and JBoss Developer Studio 7 User Guide*. (> Red Hat JBoss Developer Studio 7.0 Installation Guide and User Guide) And: These are available at *https://access.redhat.com/site/documentation/JBoss_Developer_Studio/* (> https://access.redhat.com/site/documentation/Red_Hat_JBoss_Developer_Studio/) * 3.1 Installation Assumptions = If you wish to install JBoss Developer Studio BYOE, *you should* follow ... (> delete) And: the instructions in *JBoss Developer Studio 7* Installation Guide (> Red Hat JBoss Developer Studio 7.0) * 3.2 Install JBoss Developer Studio = On Linux distributions and Microsoft Windows operating systems, *type* the path to the appropriate bit version of the Java developer kit. (> in the text field type) And: added condition=gsg step for skipping setting up runtime detection in GSG And: Figure 3.5. Installation Step 7: Installation Progress in *the* Finished State (> delete) * 4.2 Tutorial Outline = Deploy the application on a runtime server using *Server Manager* (> JBoss Server Tools) And: Add a user interface to the application that is optimized for mobile *devices* (> devices using Mobile Web Tools) And: You *should* work through these tasks in the order they are presented because *many are prerequisites for the later tutorial tasks*. (> must; > the earlier tasks are prerequisites for the later tutorial tasks) And: *Information* about building the complete TicketMonster application using JBoss Developer *Studio can be seen at* http://www.jboss.org/jdf/examples/get-started/ (> For information; > Studio, see <link>; > ) * 4.3 Tutorial Assumptions = JBoss Developer Studio *7* is installed. (> 7.0) And: removed note about AS 7.1 * 5.1 Configure Maven = removed note about AS 7.1 from procedure * 5.4 Add an Entity using Forge Tools = removed save file step as forge does this automatically * 5.5 Add an Entity Using Hibernate Tools = *Save the Venue.java file*. (> To save the Venue.java file, press Ctrl+S.) * 5.6 Prepare Event Records = *By default this web project uses H2 for data storage*. (> This web project uses H2 for data storage by default.) * 5.7 Deploy the Application = The TicketMonster application can be deployed on the JBoss Enterprise Application Platform *6* server ... (> 6.x) And: *In* the Select the server that you want to use table, (> From) And: Figure 5.20. *Completed Run on Server Window* (> JBoss Enterprise Application Platform 6.x Selected in Run on Server Wizard) * 5.8 Access and Query the Database = In *JBoss Developer Studio* open a new ... (> the IDE) * 5.9 Add a RESTful Wed Service = To resolve the errors relating to missing imports, right-click anywhere in the EventService class and clickSource→*Organise* Imports. (> Organize) > Technical Review of 7.0 Getting Started Guide > --------------------------------------------- > > Key: TOOLSDOC-381 > URL: https://issues.jboss.org/browse/TOOLSDOC-381 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: Getting Started Guide > Affects Versions: 4.1.0 > Reporter: Michelle Murray > Assignee: Michelle Murray > Fix For: 4.1.0 > > > Conduct a post release technical review of 7.0 Getting Started Guide to catch any previously missed technical or copy errors. -- 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, 8 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 August 2013