[JBoss JIRA] (JBDS-2862) During install, I should be able to create a new directory to install into
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-2862?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-2862:
--------------------------------
CDW release: + (was: ?)
> During install, I should be able to create a new directory to install into
> --------------------------------------------------------------------------
>
> Key: JBDS-2862
> URL: https://issues.jboss.org/browse/JBDS-2862
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: installer
> Affects Versions: 7.1.0.CR1
> Environment: Mac OS X
> Reporter: Jim Tyrrell
> Assignee: Denis Golovin
> Labels: jbds711
> Fix For: 7.1.1.GA, 8.0.0.Alpha2
>
> Attachments: 2013-12-19_1512.png, Screen shot 2013-12-10 at 12.34.20 PM.png, Screen Shot 2013-12-10 at 3.11.08 PM.png, Select Target Folder_015.png
>
>
> See the attached screen shot, a create new folder button does not seem to exist anywhere to create a new folder/directory to install JBDS.
--
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, 5 months
[JBoss JIRA] (JBDS-2862) During install, I should be able to create a new directory to install into
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-2862?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-2862:
--------------------------------
CDW release: ? (was: +)
> During install, I should be able to create a new directory to install into
> --------------------------------------------------------------------------
>
> Key: JBDS-2862
> URL: https://issues.jboss.org/browse/JBDS-2862
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: installer
> Affects Versions: 7.1.0.CR1
> Environment: Mac OS X
> Reporter: Jim Tyrrell
> Assignee: Denis Golovin
> Labels: jbds711
> Fix For: 7.1.1.GA, 8.0.0.Alpha2
>
> Attachments: 2013-12-19_1512.png, Screen shot 2013-12-10 at 12.34.20 PM.png, Screen Shot 2013-12-10 at 3.11.08 PM.png, Select Target Folder_015.png
>
>
> See the attached screen shot, a create new folder button does not seem to exist anywhere to create a new folder/directory to install JBDS.
--
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, 5 months
[JBoss JIRA] (JBDS-2515) JBDS70_0011: [Commit] (Dev) (P3) Scan ~/jboss-runtimes automatically
by Len DiMaggio (JIRA)
[ https://issues.jboss.org/browse/JBDS-2515?page=com.atlassian.jira.plugin.... ]
Len DiMaggio edited comment on JBDS-2515 at 1/27/14 4:36 PM:
-------------------------------------------------------------
Just to confirm - the scanning will only happen when a new workspace is created?
> JBDS70_0011: [Commit] (Dev) (P3) Scan ~/jboss-runtimes automatically
> --------------------------------------------------------------------
>
> Key: JBDS-2515
> URL: https://issues.jboss.org/browse/JBDS-2515
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: requirements
> Affects Versions: 7.0.0.GA
> Reporter: Jiri Pallich
> Assignee: Max Rydahl Andersen
> Priority: Minor
>
> Usecase is to not have to setup runtimes every time you create a new workspace. Useful for demos and training sessions and those using many runtimes (e.g. EAP 5.0.1, EAP 6.0.0, EAP 6.0.1, SOA-P 5.x.y, etc)
--
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, 5 months
[JBoss JIRA] (JBDS-2848) Usage Stats for actual used features
by Len DiMaggio (JIRA)
[ https://issues.jboss.org/browse/JBDS-2848?page=com.atlassian.jira.plugin.... ]
Len DiMaggio edited comment on JBDS-2848 at 1/27/14 4:33 PM:
-------------------------------------------------------------
On this point:
Ideally, we would be able to distinguish between a single "hit" (end-user opened the tool) vs active usage (end-user spent repeatedly using the tool)
What threshold would we set to trigger this? Multiple hits in one day?
> Usage Stats for actual used features
> ------------------------------------
>
> Key: JBDS-2848
> URL: https://issues.jboss.org/browse/JBDS-2848
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: requirements, usage
> Reporter: Burr Sutter
> Assignee: Andre Dietisheim
>
> We currently know that people are using JBDS/JBoss Tools but not specifically which features people are actively using. Our key base metric is "daily usage".
> Areas worth tracking include (in priority order):
> - Use of the OpenShift Wizard to successful completion vs error
> - Use of the archetypes on JBoss Central (adding Hybrid/Cordova in JBDS 8)
> - Successful installation of the features found on Software/Update tab of JBoss Central
> - Use of the JSF/RichFaces Visual Page Editor
> - Use of the Hibernate Tooling
> - Use of the jQuery Mobile Palette
> - Use of BrowserSim
> - Use of CordovaSim
> We will also need to update http://www.jboss.org/tools/usage and https://devstudio.jboss.com/usage/
> Ideally, we would be able to distinguish between a single "hit" (end-user opened the tool) vs active usage (end-user spent repeatedly using the tool)
> Our metric gathering service should be "scalable" enough to allow for tracking of the individual SOA features such as Drools, jBPM, Switchyard, Camel, etc in the future.
--
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, 5 months
[JBoss JIRA] (JBDS-2844) Management API Server Adapter
by Len DiMaggio (JIRA)
[ https://issues.jboss.org/browse/JBDS-2844?page=com.atlassian.jira.plugin.... ]
Len DiMaggio edited comment on JBDS-2844 at 1/27/14 4:34 PM:
-------------------------------------------------------------
Will we be able to address the problem of having to install a local server (of the same type) to be able to manage a remote server?
https://issues.jboss.org/browse/JBIDE-15162
> Management API Server Adapter
> -----------------------------
>
> Key: JBDS-2844
> URL: https://issues.jboss.org/browse/JBDS-2844
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: requirements, server
> Reporter: Burr Sutter
> Assignee: Max Rydahl Andersen
>
> Related to JBIDE-14073 and EAP6-1
> The current EAP/JBossAS/Wildfly Server Adapter often interacts with the underlying file-system of the app server. Users have asked that the following scenarios be supported:
> - Remote Server Start/Stop
> - Remote Server Deployment/Undeployment
> - Remote Server single file update (e.g. html, js, jsp, xhtml, etc) with hot-deployment (to be worked out with the Wildfly team)
> - Remote Server Log Viewing
> and while the focus here in on remote servers, it should work just as well with localhost-based servers.
> Also related, not having the actual server code locally installed, being able to work wholly with a remote server (comes up in the Data Virt/Teiid world).
--
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, 5 months
[JBoss JIRA] (JBDS-2745) Support installation of Early Access / Experimental / Incubating plugins
by Len DiMaggio (JIRA)
[ https://issues.jboss.org/browse/JBDS-2745?page=com.atlassian.jira.plugin.... ]
Len DiMaggio edited comment on JBDS-2745 at 1/27/14 4:35 PM:
-------------------------------------------------------------
Will we be able to handle situations where a feature graduates from tech preview to supported? (Not sure if the inverse will ever happen.)
> Support installation of Early Access / Experimental / Incubating plugins
> ------------------------------------------------------------------------
>
> Key: JBDS-2745
> URL: https://issues.jboss.org/browse/JBDS-2745
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: central, requirements
> Affects Versions: 7.1.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Burr Sutter
>
> It's been suggested that it would be nice to have Central available to install non-GA content. How might this appear?
> [~burrsutter], [~maxandersen], are we talking about:
> * an additional dialog warning users about untested content? (that might be ignored / blindclicked)
> * an additional tab in Central for this type of content (what label would you use?)
> * relabelling the content's feature descriptions / titles / copyright / license terms to be clear it's unstable content? (might be ignored)
> * some other workflow?
> See also JBDS-2068.
--
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, 5 months
[JBoss JIRA] (JBDS-2849) Document Offline Usage
by Len DiMaggio (JIRA)
[ https://issues.jboss.org/browse/JBDS-2849?page=com.atlassian.jira.plugin.... ]
Len DiMaggio edited comment on JBDS-2849 at 1/27/14 4:24 PM:
-------------------------------------------------------------
Question on this statement:
We may not be able to work around this since JBDS versions and Fuse, SwitchYard, etc. versions cannot be tied together as those products may evolve to higher and higher versions while JBDS remains static for a while.
Why/how will this be a problem? If Fuse, SwitchYard, etc. are updated the corresponding changes will be made to the JBDS tooling - how will it matter if JBDS is not updated?
> Document Offline Usage
> ----------------------
>
> Key: JBDS-2849
> URL: https://issues.jboss.org/browse/JBDS-2849
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: requirements
> Reporter: Burr Sutter
> Assignee: Michelle Murray
>
> Working with the Training team, document how JBDS is to be used in an offline state.
--
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, 5 months
[JBoss JIRA] (JBDS-2849) Document Offline Usage
by Len DiMaggio (JIRA)
[ https://issues.jboss.org/browse/JBDS-2849?page=com.atlassian.jira.plugin.... ]
Len DiMaggio edited comment on JBDS-2849 at 1/27/14 4:25 PM:
-------------------------------------------------------------
We need a clear definition of the actions that we support/do not support for offline users - can we create a dedicated section in the docs for offline users?
> Document Offline Usage
> ----------------------
>
> Key: JBDS-2849
> URL: https://issues.jboss.org/browse/JBDS-2849
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: requirements
> Reporter: Burr Sutter
> Assignee: Michelle Murray
>
> Working with the Training team, document how JBDS is to be used in an offline state.
--
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, 5 months
[JBoss JIRA] (JBDS-2866) CordovaSim Debugger
by Len DiMaggio (JIRA)
[ https://issues.jboss.org/browse/JBDS-2866?page=com.atlassian.jira.plugin.... ]
Len DiMaggio edited comment on JBDS-2866 at 1/27/14 4:23 PM:
-------------------------------------------------------------
Can we see screenshots? (Before a QE ack.)
> CordovaSim Debugger
> -------------------
>
> Key: JBDS-2866
> URL: https://issues.jboss.org/browse/JBDS-2866
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: browsersim, requirements
> Reporter: Burr Sutter
> Assignee: Ilya Buziuk
> Attachments: DevToolsMenu.png
>
>
> The current FireBug Lite in CordovaSim has the following limitations:
> 1) When using LiveReload, the window closes with every reload
> 2) Various "page load" events with console.log statements are not visible in FireBug Lite console, like having console.log() in your deviceready
> http://screencast.com/t/RRGhV9PV
> Note: I forgot to add the Console Cordova plugin, not sure if that is necessary but the window closes, so not sure how I would see the message
--
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, 5 months