September 2013 - jbosstools-issues

[JBoss JIRA] (TOOLSDOC-301) Document Maven How-Tos

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-301?page=com.atlassian.jira.plug... ] Michelle Murray updated TOOLSDOC-301: ------------------------------------- Fix Version/s: 4.2.0 > Document Maven How-Tos > ---------------------- > > Key: TOOLSDOC-301 > URL: https://issues.jboss.org/browse/TOOLSDOC-301 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Task > Security Level: Public(Everyone can see) > Components: User Guide - Maven Tools > Affects Versions: 3.3.0.Final > Reporter: Burr Sutter > Assignee: Michelle Murray > Fix For: 4.2.0 > > > Maven is "black magic" to the average developer and this task intends to capture the key scenarios that should be documented and/or tooling improved: > 1) Why is THIS dependency needed? What specific component is using it? > 2) Where did THIS dependency come from? What repository? > 3) How can I work offline, off the net? How do I know an artifact that I am reaching for is not on my local machine? Not on my local network? > 4) Since a property, determines the BOM and the BOM determines the versions of each included dependency, how can I trace those versions, see what is being used? > 5) Often my local .m2/repository collects a "bad" artifact, how can I detect that and clean it up? -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-294) Document Maven dependency conversion

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-294?page=com.atlassian.jira.plug... ] Michelle Murray updated TOOLSDOC-294: ------------------------------------- Fix Version/s: 4.2.0 (was: 4.0.1) > Document Maven dependency conversion > ------------------------------------ > > Key: TOOLSDOC-294 > URL: https://issues.jboss.org/browse/TOOLSDOC-294 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: User Guide - Maven Tools > Affects Versions: 4.0.0.CR1 > Reporter: Isaac Rooskov > Assignee: Michelle Murray > Fix For: 4.2.0 > > > Document the Maven tooling ability for dependency conversion. Detailed by Fred here: > http://docs.jboss.org/tools/whatsnew/maven/maven-news-4.0.0.Beta1.html > http://docs.jboss.org/tools/whatsnew/maven/maven-news-4.0.0.Alpha1.html > It is thought that this will become its own chapter called "Dependency Conversion". -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-386) Review: Devs to review Maven Tools content spec

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-386?page=com.atlassian.jira.plug... ] Michelle Murray updated TOOLSDOC-386: ------------------------------------- Fix Version/s: 4.2.0 (was: 4.1.0) > Review: Devs to review Maven Tools content spec > ----------------------------------------------- > > Key: TOOLSDOC-386 > URL: https://issues.jboss.org/browse/TOOLSDOC-386 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Task > Security Level: Public(Everyone can see) > Components: User Guide - Maven Tools > Affects Versions: 4.1.0 > Reporter: Michelle Murray > Assignee: Fred Bricon > Fix For: 4.2.0 > > Attachments: MavenTools_contentspec.pdf > > > Please review the content spec of the Maven Tools chapter from a technical viewpoint: > 1) Is the info about features correct? > 2) Are any features missing? > The content spec will be used to write the Maven Tools chapter in the JBDS User Guide. It is important that any issues are resolved before writing starts. > For ease of tracking by docs, please give feedback as comments in this JIRA. Estimated page and graphics counts will be added by docs later. > The content spec is available here as a pdf. Alternatively, the content spec is also available at: > https://mojo.redhat.com/docs/DOC-19224 -- 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, 7 months

1
0
0 / 0

[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: ------------------------------------- Fix Version/s: 4.2.0 (was: 4.1.1) > 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 > > > 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, 7 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-388) Update explicit 7.0 text references in docs to 7.1

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-388?page=com.atlassian.jira.plug... ] Michelle Murray updated TOOLSDOC-388: ------------------------------------- Fix Version/s: 4.2.0 (was: 4.1.1) > Update explicit 7.0 text references in docs to 7.1 > -------------------------------------------------- > > Key: TOOLSDOC-388 > URL: https://issues.jboss.org/browse/TOOLSDOC-388 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Task > Affects Versions: 4.1.0 > Reporter: Michelle Murray > Assignee: Michelle Murray > Fix For: 4.2.0 > > > Section that need updating > *Installation Guide* > * 2.2. Supported Operating Systems and Architectures > * 2.3. Computer Memory > * 2.4. Compatible Java Developer Kits > * 3.2. Install JBoss Developer Studio > * 3.3. Install JBoss Developer Studio BYOE > * 5.2. Upgrade JBoss Developer Studio > * 5.3. Upgrade JBoss Developer Studio BYOE > *Migration Guide* (2.2 and 2.3 shared with Installation Guide) > * 2.2. Upgrade JBoss Developer Studio > * 2.3. Upgrade JBoss Developer Studio BYOE > * 3.1. Change the Version of Eclipse Being Used with JBoss Developer Studio BYOE > *Getting Started Guide* (3.2 shared with Installation Guide) > * 2.1. About Getting Started > * 3.1. Installation Assumptions > * 3.2. Install JBoss Developer Studio > * 4.3. Tutorial Assumptions > *User Guide* > * None -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-371) Document LiveReload preferences for BrowserSim

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-371?page=com.atlassian.jira.plug... ] Michelle Murray updated TOOLSDOC-371: ------------------------------------- Fix Version/s: 4.1.0 (was: 4.1.1) > Document LiveReload preferences for BrowserSim > ---------------------------------------------- > > Key: TOOLSDOC-371 > URL: https://issues.jboss.org/browse/TOOLSDOC-371 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: User Guide - BrowserSim, User Guide - LiveReload Tools > Affects Versions: 4.1.0 > Reporter: Michelle Murray > Assignee: Michelle Murray > Fix For: 4.1.0 > > > Need to document the following: > 1. Open a simulated device. > 2. Right-click, Preferences, Settings tab > 3. Enable LiveReload check box and Port field > See http://docs.jboss.org/tools/whatsnew/browsersim/browsersim-news-4.1.0.CR1... -- 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, 7 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: ------------------------------------- Fix Version/s: 4.2.0 (was: 4.1.1) > 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.2.0 > > > 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, 7 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-370) Document CR1 N&N in User Guide

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-370?page=com.atlassian.jira.plug... ] Michelle Murray updated TOOLSDOC-370: ------------------------------------- Fix Version/s: 4.1.0 (was: 4.1.1) > Document CR1 N&N in User Guide > ------------------------------ > > Key: TOOLSDOC-370 > URL: https://issues.jboss.org/browse/TOOLSDOC-370 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: User Guide > Affects Versions: 4.1.0 > Reporter: Michelle Murray > Assignee: Michelle Murray > Fix For: 4.1.0 > > > Left to do: > http://docs.jboss.org/tools/whatsnew/openshift/openshift-news-2.5.0.Beta1... > http://docs.jboss.org/tools/whatsnew/openshift/openshift-news-2.5.0.Beta2... -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-353) Add info about how to update JBDS for minor releases

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-353?page=com.atlassian.jira.plug... ] Michelle Murray updated TOOLSDOC-353: ------------------------------------- Fix Version/s: 4.2.0 (was: 4.1.1) > Add info about how to update JBDS for minor releases > ---------------------------------------------------- > > Key: TOOLSDOC-353 > URL: https://issues.jboss.org/browse/TOOLSDOC-353 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Feature Request > Components: Migration Guide > Affects Versions: 4.1.0 > Reporter: Michelle Murray > Assignee: Michelle Murray > Fix For: 4.2.0 > > > The Migration Guide contains info about moving between JBDS 6 to JBDS 7. > Will need to add info to the guide on how to update from 7.0.0 to 7.0.x - is a fresh install required? > Not necessary to do this for 7.0.0, but should do this in time for 7.0.1 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, 7 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-389) Figure Typo: Install Guide Fig 3.12, work > Work

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-389?page=com.atlassian.jira.plug... ] Michelle Murray updated TOOLSDOC-389: ------------------------------------- Priority: Minor (was: Major) > Figure Typo: Install Guide Fig 3.12, work > Work > ------------------------------------------------ > > Key: TOOLSDOC-389 > URL: https://issues.jboss.org/browse/TOOLSDOC-389 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Bug > Components: Installation Guide > Affects Versions: 4.1.0 > Reporter: Michelle Murray > Assignee: Michelle Murray > Priority: Minor > Fix For: 4.2.0 > > > Typo in Installation Guide Figure 3.12. title: > *work* from a Local Copy of the Update .zip File > *Work* from a Local Copy of the Update .zip File -- 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, 7 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 September 2013