[JBoss JIRA] (JBDS-2881) Make clear the distinction between update.zip and central.zip on access.redhat
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/JBDS-2881?page=com.atlassian.jira.plugin.... ]
Michelle Murray updated JBDS-2881:
----------------------------------
Description:
[1] https://access.redhat.com/jbossnetwork/restricted/softwareDetail.html?sof...
[2] https://access.redhat.com/jbossnetwork/restricted/softwareDetail.html?sof...
On the download pages for individual JBDS zips, we need to make clear the distinction between update.zip and central.zip.
update.zip and central.zip Detailed Description both read: "It can be used to install JBoss Developer Studio features into your existing Eclipse 4.3 installation."
Can the text [1] for update.zip be modified to: "It can be used to install JBoss Developer Studio features into your existing Eclipse 4.3 installation if working offline."
Can the text [2] for central.zip be modified to read something like: "It can be used to install additional JBoss Developer Studio and third-party features available from JBoss Central into JBoss Developer Studio if working offline."
was:
https://access.redhat.com/jbossnetwork/restricted/listSoftware.html?produ...
On the download pages for individual JBDS zips, we need to make clear the distinction between update.zip and central.zip.
update.zip and central.zip Detailed Description both read: "It can be used to install JBoss Developer Studio features into your existing Eclipse 4.3 installation."
Can the text for update.zip be modified to: "It can be used to install JBoss Developer Studio features into your existing Eclipse 4.3 installation if working offline."
Can the text for central.zip be modified to read something like: "It can be used to install additional JBoss Developer Studio and third-party features available from JBoss Central into JBoss Developer Studio if working offline."
> Make clear the distinction between update.zip and central.zip on access.redhat
> ------------------------------------------------------------------------------
>
> Key: JBDS-2881
> URL: https://issues.jboss.org/browse/JBDS-2881
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: build, updatesite
> Affects Versions: 7.1.0.GA
> Reporter: Michelle Murray
>
> [1] https://access.redhat.com/jbossnetwork/restricted/softwareDetail.html?sof...
> [2] https://access.redhat.com/jbossnetwork/restricted/softwareDetail.html?sof...
> On the download pages for individual JBDS zips, we need to make clear the distinction between update.zip and central.zip.
> update.zip and central.zip Detailed Description both read: "It can be used to install JBoss Developer Studio features into your existing Eclipse 4.3 installation."
> Can the text [1] for update.zip be modified to: "It can be used to install JBoss Developer Studio features into your existing Eclipse 4.3 installation if working offline."
> Can the text [2] for central.zip be modified to read something like: "It can be used to install additional JBoss Developer Studio and third-party features available from JBoss Central into JBoss Developer Studio if working offline."
--
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-2881) Make clear the distinction between update.zip and central.zip on access.redhat
by Michelle Murray (JIRA)
Michelle Murray created JBDS-2881:
-------------------------------------
Summary: Make clear the distinction between update.zip and central.zip on access.redhat
Key: JBDS-2881
URL: https://issues.jboss.org/browse/JBDS-2881
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Enhancement
Security Level: Public (Everyone can see)
Components: build, updatesite
Affects Versions: 7.1.0.GA
Reporter: Michelle Murray
https://access.redhat.com/jbossnetwork/restricted/listSoftware.html?produ...
On the download pages for individual JBDS zips, we need to make clear the distinction between update.zip and central.zip.
update.zip and central.zip Detailed Description both read: "It can be used to install JBoss Developer Studio features into your existing Eclipse 4.3 installation."
Can the text for update.zip be modified to: "It can be used to install JBoss Developer Studio features into your existing Eclipse 4.3 installation if working offline."
Can the text for central.zip be modified to read something like: "It can be used to install additional JBoss Developer Studio and third-party features available from JBoss Central into JBoss Developer Studio if working offline."
--
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] (JBIDE-16400) Timeout shutdown poller does not wait for timeout
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16400?page=com.atlassian.jira.plugi... ]
Michelle Murray commented on JBIDE-16400:
-----------------------------------------
[~rob.stryker], [~mmalina] - JBDS/JBT User Guide currently states the following:
{quote}
*Server state detectors*
This section specifies which method the IDE should use to verify the started and stopped status of the server.
There are four methods from which to choose:
* Web Port, which pings the web port on the host to see if the server responds
* Timeout, which waits for a specified time duration and then declares the start or stop operation a success without any actual verification
* Process Terminated (available for Shutdown Poller of local servers only), which checks if a server process is still alive and sets the server status to stopped when it is terminated
* JMX, which polls JMX, the JBoss Management service
Note that server state detection options are disabled if the Server is externally managed check box under Server Behavior is selected.Server state detectors
{quote}
Perhaps the Timeout statement should be modified to:
"Timeout, which waits for a specified time duration and then declares the start or stop operation a success without actual verification *(note that for local servers the termination of the server process immediately changes the server state to stopped regardless of whether the end of the timeout period is reached)*
> Timeout shutdown poller does not wait for timeout
> -------------------------------------------------
>
> Key: JBIDE-16400
> URL: https://issues.jboss.org/browse/JBIDE-16400
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.1.1.Final
> Environment: JBDS 7.1.0.GA
> EAP 6.2.0
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.2.0.Alpha2
>
>
> When you select "Timeout" as the Shutdown poller in server editor, one would expect the server to show stopped only after the timeout has elapsed (like it happens with the Timeout startup poller). Instead, the server is shown instantly once you stop the server.
--
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 Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-2745?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBDS-2745:
----------------------------------
Assuming that the implementation is just eye candy, making it obvious what is and what is not EA/Exp/Inc content, then a user should definitely be able to upgrade from an early access version of a connector (set of features) to a newer connector, provided that the usual OSGi rules are respected and the only real distinction between the EA version and the non-EA version is in the features or plugins metadata (eg., feature.properties setting the feature name to include " (Incubating)" in the name.
> 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] (TOOLSDOC-435) Update 8.0 User Guide text and screen caps for IDE look & behavior changes
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-435?page=com.atlassian.jira.plug... ]
Michelle Murray updated TOOLSDOC-435:
-------------------------------------
Description:
Add list of potential impacting JBIDE and JBDS jiras here (note that not all are currently scheduled for 4.2.0):
*Usage Data*
* Report JVM name (JBIDE-15596)
* Report 32/64-bit Eclipse/Java (JBIDE-16333)
* Report installs from JBDS Central (JBDS-2732)
* Report actual used features (JBDS-2848)
*Server Tools*
* Some server wizards for Wildfly 8.0 still say JBoss AS (JBIDE-16349)
*Forge Tools*
* Integrate F2 command line into JBT, assume JBDS too (JBIDE-16263)
** F2: Ctrl+5 to open a list of actions (from JBIDE-16079)
** F2: Quick Access menu with Ctrl+4 (JBIDE-16113) + subtasks (JBIDE-16114, JBIDE-16115, JBIDE-16116, JBIDE-16117)
** F2: Ctrl+4 menu available even when forge not running (JBIDE-16109)
** F2: Ctrl+4 menu usable via keyboard (JBIDE-16111)
* Ctrl+3?? (from JBIDE-16111)
*Web Service Tools*
* Support JAX-RS 2.0 (JBIDE-16329)
*Mobile Web Tools*
* Support jQuery Mobile 1.4 (JBIDE-16271) + subtasks (JBIDE-16293, JBIDE-16294, JBIDE-16319, JBIDE-16325, JBIDE-16326, JBIDE-16338, JBIDE-16339, JBIDE-16346, JBIDE-16347, JBIDE-16348)
** Option to select which jQM version in mobile palette (JBIDE-16293)
** New widget wizards in palette: New Button, New Grouped Buttons, New Select Menu, New Flip Toggle Switch, New Text Input, New Dialog, New Tabs (JBIDE-16319, JBIDE-16325, JBIDE-16339, JBIDE-16347)
** New popup wizard?? (JBIDE-16326)
*BrowserSim*
* Change layout of BrowserSim/CordovaSim pane in preferences window (JBIDE-16298)
*Hybrid Mobile Tools + CordovaSim*
* Disable add and remove buttons on parameters table in certain instances (JBIDE-16059)
* Use of LiveReload with Firebug Lite results in the latter closing on each refresh (from JBIDE-16090)
* Disable deployment to AVDs and devices that don't support minimum SDK version (JBIDE-16213)
* Add section about importing HM project (from JBIDE-16275, new functionality JBIDE-16312)
* Issue exporting project if Android SDK location not set (JBIDE-16276)
* Changes to layout of CordovaSim UI (JBIDE-16323)
* Run configuration ignored for Android emulator (JBIDE-16330)
* 'Debug as' option/workflow for emulators other than CordovaSim (JBIDE-16337)
*OpenShift*
* New SSH Key Wizard: add a passphrase confirmation field (JBIDE-13450)
* Environment variable disabled if servers does not support them (JBIDE-16030, JBIDE-15861/JBIDE-16031)
* Web balancer cartridge should not be listed (JBIDE-16040)
* Change to button names in port forwarding wizard (JBIDE-13963)
* Select which ports to forward rather than forward all (JBIDE-12600)
* Provide user-friendly way to increase Git timeout (JBIDE-12812)
* Fix timeout typo in Preferences pane (JBIDE-16157)
* Fix missing info i icon in new app wizard (JBIDE-16145)
* Only show gear sizes appropriate for domain in new app wizard (JBIDE-15936)
* Can't import git project is necessary .git is in parent directory (JBIDE-16356)
* Add ability to set markers in new app wizard (JBIDE-16371)
* Hide RemoteSystemsTempFiles when selecting existing project (JBIDE-16357)
was:
Add list of potential impacting JBIDE and JBDS jiras here (note that not all are currently scheduled for 4.2.0):
*Usage Data*
* Report JVM name (JBIDE-15596)
* Report 32/64-bit Eclipse/Java (JBIDE-16333)
* Report installs from JBDS Central (JBDS-2732)
* Report actual used features (JBDS-2848)
*Server Tools*
* Some server wizards for Wildfly 8.0 still say JBoss AS (JBIDE-16349)
*Forge Tools*
* Integrate F2 command line into JBT, assume JBDS too (JBIDE-16263)
** F2: Ctrl+5 to open a list of actions (from JBIDE-16079)
** F2: Quick Access menu with Ctrl+4 (JBIDE-16113) + subtasks (JBIDE-16114, JBIDE-16115, JBIDE-16116, JBIDE-16117)
** F2: Ctrl+4 menu available even when forge not running (JBIDE-16109)
** F2: Ctrl+4 menu usable via keyboard (JBIDE-16111)
* Ctrl+3?? (from JBIDE-16111)
*Web Service Tools*
* Support JAX-RS 2.0 (JBIDE-16329)
*Mobile Web Tools*
* Support jQuery Mobile 1.4 (JBIDE-16271) + subtasks (JBIDE-16293, JBIDE-16294, JBIDE-16319, JBIDE-16325, JBIDE-16326, JBIDE-16338, JBIDE-16339, JBIDE-16346, JBIDE-16347, JBIDE-16348)
** Option to select which jQM version in mobile palette (JBIDE-16293)
** New widget wizards in palette: New Button, New Grouped Buttons, New Select Menu, New Flip Toggle Switch, New Text Input, New Dialog, New Tabs (JBIDE-16319, JBIDE-16325, JBIDE-16339, JBIDE-16347)
** New popup wizard?? (JBIDE-16326)
*BrowserSim*
* Change layout of BrowserSim/CordovaSim pane in preferences window (JBIDE-16298)
*Hybrid Mobile Tools + CordovaSim*
* Disable add and remove buttons on parameters table in certain instances (JBIDE-16059)
* Use of LiveReload with Firebug Lite results in the latter closing on each refresh (from JBIDE-16090)
* Disable deployment to AVDs and devices that don't support minimum SDK version (JBIDE-16213)
* Add section about importing HM project (from JBIDE-16275, new functionality JBIDE-16312)
* Issue exporting project if Android SDK location not set (JBIDE-16276)
* Changes to layout of CordovaSim UI (JBIDE-16323)
* Run configuration ignored for Android emulator (JBIDE-16330)
* 'Debug as' option/workflow for emulators other than CordovaSim (JBIDE-16337)
*OpenShift*
* New SSH Key Wizard: add a passphrase confirmation field (JBIDE-13450)
* Environment variable disabled if servers does not support them (JBIDE-16030, JBIDE-15861/JBIDE-16031)
* Web balancer cartridge should not be listed (JBIDE-16040)
* Change to button names in port forwarding wizard (JBIDE-13963)
* Select which ports to forward rather than forward all (JBIDE-12600)
* Provide user-friendly way to increase Git timeout (JBIDE-12812)
* Fix timeout typo in Preferences pane (JBIDE-16157)
* Fix missing info i icon in new app wizard (JBIDE-16145)
* Only show gear sizes appropriate for domain in new app wizard (JBIDE-15936)
* Can't import git project is necessary .git is in parent directory (JBIDE-16356)
* Add ability to set markers in new app wizard (JBIDE-16371)
> Update 8.0 User Guide text and screen caps for IDE look & behavior changes
> --------------------------------------------------------------------------
>
> Key: TOOLSDOC-435
> URL: https://issues.jboss.org/browse/TOOLSDOC-435
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Sub-task
> Security Level: Public(Everyone can see)
> Components: User Guide
> Affects Versions: 4.2.0
> Reporter: Michelle Murray
> Assignee: Michelle Murray
> Fix For: 4.2.0
>
>
> Add list of potential impacting JBIDE and JBDS jiras here (note that not all are currently scheduled for 4.2.0):
> *Usage Data*
> * Report JVM name (JBIDE-15596)
> * Report 32/64-bit Eclipse/Java (JBIDE-16333)
> * Report installs from JBDS Central (JBDS-2732)
> * Report actual used features (JBDS-2848)
> *Server Tools*
> * Some server wizards for Wildfly 8.0 still say JBoss AS (JBIDE-16349)
> *Forge Tools*
> * Integrate F2 command line into JBT, assume JBDS too (JBIDE-16263)
> ** F2: Ctrl+5 to open a list of actions (from JBIDE-16079)
> ** F2: Quick Access menu with Ctrl+4 (JBIDE-16113) + subtasks (JBIDE-16114, JBIDE-16115, JBIDE-16116, JBIDE-16117)
> ** F2: Ctrl+4 menu available even when forge not running (JBIDE-16109)
> ** F2: Ctrl+4 menu usable via keyboard (JBIDE-16111)
> * Ctrl+3?? (from JBIDE-16111)
> *Web Service Tools*
> * Support JAX-RS 2.0 (JBIDE-16329)
> *Mobile Web Tools*
> * Support jQuery Mobile 1.4 (JBIDE-16271) + subtasks (JBIDE-16293, JBIDE-16294, JBIDE-16319, JBIDE-16325, JBIDE-16326, JBIDE-16338, JBIDE-16339, JBIDE-16346, JBIDE-16347, JBIDE-16348)
> ** Option to select which jQM version in mobile palette (JBIDE-16293)
> ** New widget wizards in palette: New Button, New Grouped Buttons, New Select Menu, New Flip Toggle Switch, New Text Input, New Dialog, New Tabs (JBIDE-16319, JBIDE-16325, JBIDE-16339, JBIDE-16347)
> ** New popup wizard?? (JBIDE-16326)
> *BrowserSim*
> * Change layout of BrowserSim/CordovaSim pane in preferences window (JBIDE-16298)
> *Hybrid Mobile Tools + CordovaSim*
> * Disable add and remove buttons on parameters table in certain instances (JBIDE-16059)
> * Use of LiveReload with Firebug Lite results in the latter closing on each refresh (from JBIDE-16090)
> * Disable deployment to AVDs and devices that don't support minimum SDK version (JBIDE-16213)
> * Add section about importing HM project (from JBIDE-16275, new functionality JBIDE-16312)
> * Issue exporting project if Android SDK location not set (JBIDE-16276)
> * Changes to layout of CordovaSim UI (JBIDE-16323)
> * Run configuration ignored for Android emulator (JBIDE-16330)
> * 'Debug as' option/workflow for emulators other than CordovaSim (JBIDE-16337)
> *OpenShift*
> * New SSH Key Wizard: add a passphrase confirmation field (JBIDE-13450)
> * Environment variable disabled if servers does not support them (JBIDE-16030, JBIDE-15861/JBIDE-16031)
> * Web balancer cartridge should not be listed (JBIDE-16040)
> * Change to button names in port forwarding wizard (JBIDE-13963)
> * Select which ports to forward rather than forward all (JBIDE-12600)
> * Provide user-friendly way to increase Git timeout (JBIDE-12812)
> * Fix timeout typo in Preferences pane (JBIDE-16157)
> * Fix missing info i icon in new app wizard (JBIDE-16145)
> * Only show gear sizes appropriate for domain in new app wizard (JBIDE-15936)
> * Can't import git project is necessary .git is in parent directory (JBIDE-16356)
> * Add ability to set markers in new app wizard (JBIDE-16371)
> * Hide RemoteSystemsTempFiles when selecting existing project (JBIDE-16357)
--
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 commented on JBDS-2862:
-------------------------------------
pushed to both (7.1.1 and 8.0.0) streams
> 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 devel_ack: + (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