[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
10 years, 2 months
[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
10 years, 2 months
[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
10 years, 2 months
[JBoss JIRA] (JBIDE-15935) Android SDK not installed automatically on OS X
by Gorkem Ercan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15935?page=com.atlassian.jira.plugi... ]
Gorkem Ercan updated JBIDE-15935:
---------------------------------
Component/s: (was: aerogear-hybrid)
> Android SDK not installed automatically on OS X
> -----------------------------------------------
>
> Key: JBIDE-15935
> URL: https://issues.jboss.org/browse/JBIDE-15935
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: upstream
> Affects Versions: 4.1.1.Beta1
> Environment: JBDS 7.1.0.Beta1
> OS X Mavericks
> Reporter: Martin Malina
> Assignee: Vlado Pakan
> Fix For: 4.2.x
>
> Attachments: android-sdk.png, Central_AndTools.png, installadk.png
>
> Original Estimate: 0 minutes
> Remaining Estimate: 0 minutes
>
> When I install android tools from central and then I restart the IDE as requested, I should be asked to automatically download and install Android SDK (I got word it works this way on Linux). I got nothing like that on OS X.
> So I had to download and setup SDK manually.
--
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
10 years, 2 months
[JBoss JIRA] (JBIDE-16663) Support linked folders
by Gorkem Ercan (JIRA)
Gorkem Ercan created JBIDE-16663:
------------------------------------
Summary: Support linked folders
Key: JBIDE-16663
URL: https://issues.jboss.org/browse/JBIDE-16663
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: aerogear-hybrid
Affects Versions: 4.2.0.Alpha2
Reporter: Gorkem Ercan
Fix For: 4.2.x
Linked folders are not honored when generating the native platform projects, both at export and Run On action, HMT should properly support linked folders.
--
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
10 years, 2 months
[JBoss JIRA] (JBIDE-16636) allow drop without dialog from palette
by Daniel Azarov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16636?page=com.atlassian.jira.plugi... ]
Daniel Azarov edited comment on JBIDE-16636 at 2/27/14 8:07 PM:
----------------------------------------------------------------
[~maxandersen], I faced some troubles when I tried to read Alt key:
UBUNTU:
There are two ways which I tried:
1. method dragOperationChanged in DropTargetListener - it works fine with *Ctrl* and *Shift* keys. It does not work with *Alt* key at all.
2. KeyListener - it works fine with any kind of key combinations, but it does not work during drag&drop at all.
One more thing - on Ubuntu if you press *Alt* and start dragging element from palette - Ubuntu will move current window. It looks like there is nothing we can do about it.
WINDOWS:
Method dragOperationChanged in DropTargetListener works fine with *Ctrl* and *Alt* keys. It does not work with *Shift* (called but does not change operation)
MacOs:
Method dragOperationChanged in DropTargetListener works fine only with *Alt/Option* key.
But if we go with *Ctrl* on Ubuntu and Window, *Ctrl* changes drop operation to *Copy* operation
On Mac - the same operation you can get with *Alt/Option* key (just as you asked)
Is it OK to have different keys on different operating systems (*Ctrl* for Linux and Windows and *Alt/Option* for Mac)for this feature?
WDYT?
was (Author: dazarov):
[~maxandersen], I faced some troubles when I tried to read Alt key:
UBUNTU:
There are two ways which I tried:
1. method dragOperationChanged in DropTargetListener - it works fine with *Ctrl* and *Shift* keys. It does not work with *Alt* key at all.
2. KeyListener - it works fine with any kind of key combinations, but it does not work during drag&drop at all.
One more thing - on Ubuntu if you press *Alt* and start dragging element from palette - Ubuntu will move current window. It looks like there is nothing we can do about it.
WINDOWS:
1. method dragOperationChanged in DropTargetListener - it works fine with *Ctrl* and *Alt* keys. It does not work with *Shift* (called but does not change operation)
MacOs:
If we go with *Ctrl* on Ubuntu and Window, *Ctrl* changes drop operation to *Copy* operation
On Mac - the same operation you can get with *Alt/Option* key (just as you asked)
Is it OK to have different keys on different operating systems (*Ctrl* for Linux and Windows and *Alt/Option* for Mac)for this feature?
WDYT?
> allow drop without dialog from palette
> --------------------------------------
>
> Key: JBIDE-16636
> URL: https://issues.jboss.org/browse/JBIDE-16636
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsp/jsf/xml/html source editing
> Reporter: Max Rydahl Andersen
> Assignee: Daniel Azarov
> Fix For: 4.2.0.Beta1
>
>
> sometimes when demoing or just trying a few things quickly or dragging trivial elements it would be nice being able to not have the wizard dialog show up.
> could we make it so when holding in Alt it will not show the dialog but just do whatever clicking the finish button would directly do ?
--
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
10 years, 2 months