February 2014 - jbosstools-issues

[JBoss JIRA] (TOOLSDOC-445) Document the Hybrid Mobile project artifacts that should be placed under version control

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-445?page=com.atlassian.jira.plug... ] Michelle Murray commented on TOOLSDOC-445: ------------------------------------------ Added the following text to the end of the create a HM project {quote} The project created by Hybrid Mobile Tools has some IDE-specific items, namely a <filename>.settings</filename> directory and a <filename>.project</filename> file. All other items in the Hybrid Mobile Tools generated project have the same purpose as those in projects created by the Cordova CLI. {quote} This should assist users to decipher which are the core HM project components and which to put under version control. > Document the Hybrid Mobile project artifacts that should be placed under version control > ---------------------------------------------------------------------------------------- > > Key: TOOLSDOC-445 > URL: https://issues.jboss.org/browse/TOOLSDOC-445 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: User Guide - Hybrid Mobile Tools and CordovaSim > Affects Versions: 4.1.1 > Reporter: Vineet Reynolds > Assignee: Michelle Murray > Priority: Minor > Fix For: 4.2.0.Beta1 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > I noticed the project directory containing a {{.cordova}} directory with a config.json file. Also, the Eclipse {{.project}} file contains a reference to the {[HybridAppNature}}. > I'm not sure if both of these files should be placed under version control. Only the {{www}} directory seemed obvious enough to place under SCM. It would be great if we could get this documented so that end-users are aware of how to share Hybrid Mobile projects. -- 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

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-445) Document the Hybrid Mobile project artifacts that should be placed under version control

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-445?page=com.atlassian.jira.plug... ] Michelle Murray resolved TOOLSDOC-445. -------------------------------------- Resolution: Done > Document the Hybrid Mobile project artifacts that should be placed under version control > ---------------------------------------------------------------------------------------- > > Key: TOOLSDOC-445 > URL: https://issues.jboss.org/browse/TOOLSDOC-445 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: User Guide - Hybrid Mobile Tools and CordovaSim > Affects Versions: 4.1.1 > Reporter: Vineet Reynolds > Assignee: Michelle Murray > Priority: Minor > Fix For: 4.2.0.Beta1 > > Original Estimate: 1 hour > Time Spent: 30 minutes > Remaining Estimate: 0 minutes > > I noticed the project directory containing a {{.cordova}} directory with a config.json file. Also, the Eclipse {{.project}} file contains a reference to the {[HybridAppNature}}. > I'm not sure if both of these files should be placed under version control. Only the {{www}} directory seemed obvious enough to place under SCM. It would be great if we could get this documented so that end-users are aware of how to share Hybrid Mobile projects. -- 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

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-445) Document the Hybrid Mobile project artifacts that should be placed under version control

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-445?page=com.atlassian.jira.plug... ] Michelle Murray commented on TOOLSDOC-445: ------------------------------------------ [~gercan], are there any plan to realign the tree structure of the project produced by HMT with those of Cordova CLI (e.g., moving config.xml to top level)? > Document the Hybrid Mobile project artifacts that should be placed under version control > ---------------------------------------------------------------------------------------- > > Key: TOOLSDOC-445 > URL: https://issues.jboss.org/browse/TOOLSDOC-445 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: User Guide - Hybrid Mobile Tools and CordovaSim > Affects Versions: 4.1.1 > Reporter: Vineet Reynolds > Assignee: Michelle Murray > Priority: Minor > Fix For: 4.2.0.Beta1 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > I noticed the project directory containing a {{.cordova}} directory with a config.json file. Also, the Eclipse {{.project}} file contains a reference to the {[HybridAppNature}}. > I'm not sure if both of these files should be placed under version control. Only the {{www}} directory seemed obvious enough to place under SCM. It would be great if we could get this documented so that end-users are aware of how to share Hybrid Mobile projects. -- 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

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-470) Add info on Ubuntu Eclipse workaround for menus

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-470?page=com.atlassian.jira.plug... ] Michelle Murray resolved TOOLSDOC-470. -------------------------------------- Resolution: Done > Add info on Ubuntu Eclipse workaround for menus > ----------------------------------------------- > > Key: TOOLSDOC-470 > URL: https://issues.jboss.org/browse/TOOLSDOC-470 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Installation Guide > Affects Versions: 4.1.1 > Reporter: Michelle Murray > Assignee: Michelle Murray > Fix For: 4.1.2 > > Original Estimate: 30 minutes > Time Spent: 30 minutes > Remaining Estimate: 0 minutes > > Document menu issue for Ubuntu users of Eclipse in JBDS Installation Guide. > See JBDS-2905 for details. -- 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

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-471) Add screen caps to Debug on OpenShift section

by Michelle Murray (JIRA)

Michelle Murray created TOOLSDOC-471: ---------------------------------------- Summary: Add screen caps to Debug on OpenShift section Key: TOOLSDOC-471 URL: https://issues.jboss.org/browse/TOOLSDOC-471 Project: Documentation for JBoss Tools and Developer Studio Issue Type: Enhancement Security Level: Public (Everyone can see) Components: User Guide - OpenShift Tools Reporter: Michelle Murray Assignee: Michelle Murray Fix For: 4.1.2 Add screen capture to this section once QE'd. -- 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

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-471) Add screen caps to Debug on OpenShift section

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-471?page=com.atlassian.jira.plug... ] Michelle Murray updated TOOLSDOC-471: ------------------------------------- Sprint: 2014/S4 (17-Mar > 30-Mar) > Add screen caps to Debug on OpenShift section > --------------------------------------------- > > Key: TOOLSDOC-471 > URL: https://issues.jboss.org/browse/TOOLSDOC-471 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: User Guide - OpenShift Tools > Reporter: Michelle Murray > Assignee: Michelle Murray > Fix For: 4.1.2 > > Original Estimate: 2 hours, 15 minutes > Remaining Estimate: 2 hours, 15 minutes > > Add screen capture to this section once QE'd. -- 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

11 years, 10 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 resolved TOOLSDOC-446. -------------------------------------- Resolution: Done > 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: Michelle Murray > Fix For: 4.1.2, 4.2.0.Beta1 > > Original Estimate: 3 hours > Time Spent: 1 day, 5 hours > Remaining Estimate: 0 minutes > > 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

11 years, 10 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 edited comment on TOOLSDOC-446 at 2/28/14 4:02 AM: ------------------------------------------------------------------- >From 1-o-1 with Max: The JBoss Maven Source Container is named so because: * JBoss as it is distributed by JBoss - so is basically a Maven Source Container * Maven Source Container is a source container specifically for Maven; where other source containers might be .zip with java code, the Maven source container looks up source * The locations where the Maven source container looks are set in Window>Preferences>JBoss>Tools> Remote Repositories - JBoss Nexus by default was (Author: mmurray): From 1-o-1 with Max: The JBoss Maven Source Container is named so because: * JBoss as it is distributed by JBoss - so is basically a Maven Source Container * Maven Source Container is a source container specifically for Maven; where other source containers might be .zip with java code, the Maven source container looks up source * The locations were the Maven source container looks are set in Window>Preferences>JBoss>Tools> Remote Repositories - JBoss Nexus by default > 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: Michelle Murray > Fix For: 4.1.2, 4.2.0.Beta1 > > Original Estimate: 3 hours > Time Spent: 1 day, 5 hours > Remaining Estimate: 0 minutes > > 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

11 years, 10 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 commented on TOOLSDOC-446: ------------------------------------------ >From 1-o-1 with Max: The JBoss Maven Source Container is named so because: * JBoss as it is distributed by JBoss - so is basically a Maven Source Container * Maven Source Container is a source container specifically for Maven; where other source containers might be .zip with java code, the Maven source container looks up source * The locations were the Maven source container looks are set in Window>Preferences>JBoss>Tools> Remote Repositories - JBoss Nexus by default > 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: Michelle Murray > Fix For: 4.1.2, 4.2.0.Beta1 > > Original Estimate: 3 hours > Time Spent: 1 day, 5 hours > Remaining Estimate: 0 minutes > > 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

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2776) Support quickstarts in OpenShift UI

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBDS-2776?page=com.atlassian.jira.plugin.... ] Len DiMaggio commented on JBDS-2776: ------------------------------------ Information provided by Burr: Q: Are we supplying any defaults? A: JBDS is NOT - OSE might, but there were zero the last time I asked Q: Or is the content that the users will see completely determined by - what? A: The customer uses vi and edits a .json file, at least that is what I last heard. Q: The cartridges that they have installed? A: No, quickstarts can span multiple cartridges - so they have to be inputed separately into OpenShift Enterprise. > Support quickstarts in OpenShift UI > ----------------------------------- > > Key: JBDS-2776 > URL: https://issues.jboss.org/browse/JBDS-2776 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: openshift, requirements > Affects Versions: 7.0.0.GA > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Critical > Labels: QE_JBDS80_needinfo > Fix For: 8.0.0.GA > > Attachments: new-application-2.png > > > OpenShift offers a comprehensive list of available cartridges and quickstarts In the Web-UI: > !new-application-2.png! > JBoss Tools/JBDS should offer the same to provide a smoother experience for newbie users. -- 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

11 years, 10 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