[JBoss JIRA] (TOOLSDOC-480) Add info about new Select/Deselect all buttons in Software/Update tab
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-480?page=com.atlassian.jira.plug... ]
Michelle Murray updated TOOLSDOC-480:
-------------------------------------
Original Estimate: 1 hour
Remaining Estimate: 1 hour
> Add info about new Select/Deselect all buttons in Software/Update tab
> ---------------------------------------------------------------------
>
> Key: TOOLSDOC-480
> URL: https://issues.jboss.org/browse/TOOLSDOC-480
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: User Guide
> Affects Versions: 4.2.0.Beta1
> Reporter: Michelle Murray
> Assignee: Michelle Murray
> Fix For: 4.2.0.Beta1
>
> Original Estimate: 1 hour
> Remaining Estimate: 1 hour
>
> The JBoss Central Software/Update tab has two new buttons next to the Install button: Select All and Deselect All. These need documenting.
> Edit topic 22798 Install Software in JBoss Central:
> * Add info about Select All and Deselect All buttons to first para of 'Install available Software'.
> * Create new screen cap for Figure 2.9. Find and Install Software
> Edit topic 24053 Install Hybrid Mobile Tools and CordovaSim:
> * Create new screen cap for Figure 8.3. Find Hybrid Mobile Tools and CordovaSim in JBoss Central Software/Update Tab
> ** *note* previously this figure had two versions, 1 for JBDS and 1 for JBT; think we can successfully capture this with just one version; set up view as in Fig 2.9 but for HMT+CS
> ** will also need to change topic XML so one figure used for both JBT and 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
[JBoss JIRA] (TOOLSDOC-480) Add info about new Select/Deselect all buttons in Software/Update tab
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-480?page=com.atlassian.jira.plug... ]
Michelle Murray updated TOOLSDOC-480:
-------------------------------------
Sprint: 2014/S5 (31-Mar > 13-Apr)
> Add info about new Select/Deselect all buttons in Software/Update tab
> ---------------------------------------------------------------------
>
> Key: TOOLSDOC-480
> URL: https://issues.jboss.org/browse/TOOLSDOC-480
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: User Guide
> Affects Versions: 4.2.0.Beta1
> Reporter: Michelle Murray
> Assignee: Michelle Murray
> Fix For: 4.2.0.Beta1
>
> Original Estimate: 1 hour
> Remaining Estimate: 1 hour
>
> The JBoss Central Software/Update tab has two new buttons next to the Install button: Select All and Deselect All. These need documenting.
> Edit topic 22798 Install Software in JBoss Central:
> * Add info about Select All and Deselect All buttons to first para of 'Install available Software'.
> * Create new screen cap for Figure 2.9. Find and Install Software
> Edit topic 24053 Install Hybrid Mobile Tools and CordovaSim:
> * Create new screen cap for Figure 8.3. Find Hybrid Mobile Tools and CordovaSim in JBoss Central Software/Update Tab
> ** *note* previously this figure had two versions, 1 for JBDS and 1 for JBT; think we can successfully capture this with just one version; set up view as in Fig 2.9 but for HMT+CS
> ** will also need to change topic XML so one figure used for both JBT and 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
[JBoss JIRA] (TOOLSDOC-480) Add info about new Select/Deselect all buttons in Software/Update tab
by Michelle Murray (JIRA)
Michelle Murray created TOOLSDOC-480:
----------------------------------------
Summary: Add info about new Select/Deselect all buttons in Software/Update tab
Key: TOOLSDOC-480
URL: https://issues.jboss.org/browse/TOOLSDOC-480
Project: Documentation for JBoss Tools and Developer Studio
Issue Type: Enhancement
Security Level: Public (Everyone can see)
Components: User Guide
Affects Versions: 4.2.0.Beta1
Reporter: Michelle Murray
Assignee: Michelle Murray
Fix For: 4.2.0.Beta1
The JBoss Central Software/Update tab has two new buttons next to the Install button: Select All and Deselect All. These need documenting.
Edit topic 22798 Install Software in JBoss Central:
* Add info about Select All and Deselect All buttons to first para of 'Install available Software'.
* Create new screen cap for Figure 2.9. Find and Install Software
Edit topic 24053 Install Hybrid Mobile Tools and CordovaSim:
* Create new screen cap for Figure 8.3. Find Hybrid Mobile Tools and CordovaSim in JBoss Central Software/Update Tab
** *note* previously this figure had two versions, 1 for JBDS and 1 for JBT; think we can successfully capture this with just one version; set up view as in Fig 2.9 but for HMT+CS
** will also need to change topic XML so one figure used for both JBT and 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
[JBoss JIRA] (JBIDE-16947) Beans are not automatically validated when beans.xml is changed
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16947?page=com.atlassian.jira.plugi... ]
Viacheslav Kabanovich edited comment on JBIDE-16947 at 3/31/14 9:17 PM:
------------------------------------------------------------------------
To revalidate injection of a bean, we have to know that something in that bean is changed. If change is indirect, because of a change in a third file, we have to keep dependency of the bean's resource on that file. In the case of exact type name we easily can add dependency of 'exclude.p1.Bean2' on beans.xml, and I suggest that we do it.
But if one adds to beans.xml <weld:exclude name="exclude.p1.*"/>, then we have to scan the package and add dependency of all resources on beans.xml - that can be time consuming.
was (Author: scabanovich):
To revalidate injection of a bean, we have to know that something in that bean is changed. If change is indirect, because of a change in a third file, we have to keep dependency of the bean's resource on that file. In the case of exact type name we easily can add dependency of 'exclude.p1.Bean2' on beans.xml, and I suggest that we do it.
But if one adds to beans.xml <weld:exclude name="exclude.p1.*"/>, then we have to scan the package and add dependency of all resources to beans.xml - that can be time consuming.
> Beans are not automatically validated when beans.xml is changed
> ---------------------------------------------------------------
>
> Key: JBIDE-16947
> URL: https://issues.jboss.org/browse/JBIDE-16947
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdi
> Affects Versions: 4.2.0.Beta1
> Reporter: Rastislav Wagner
> Assignee: Alexey Kazakov
> Fix For: 4.2.x
>
>
> When beans.xml file is changed we always have to run validation manually to reflect newest changes. Shouldn't this be done automatically after beans.xml is changed and saved?
--
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
[JBoss JIRA] (JBIDE-16947) Beans are not automatically validated when beans.xml is changed
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16947?page=com.atlassian.jira.plugi... ]
Viacheslav Kabanovich commented on JBIDE-16947:
-----------------------------------------------
To revalidate injection of a bean, we have to know that something in that bean is changed. If change is indirect, because of a change in a third file, we have to keep dependency of the bean's resource on that file. In the case of exact type name we easily can add dependency of 'exclude.p1.Bean2' on beans.xml, and I suggest that we do it.
But if one adds to beans.xml <weld:exclude name="exclude.p1.*"/>, then we have to scan the package and add dependency of all resources to beans.xml - that can be time consuming.
> Beans are not automatically validated when beans.xml is changed
> ---------------------------------------------------------------
>
> Key: JBIDE-16947
> URL: https://issues.jboss.org/browse/JBIDE-16947
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdi
> Affects Versions: 4.2.0.Beta1
> Reporter: Rastislav Wagner
> Assignee: Alexey Kazakov
> Fix For: 4.2.x
>
>
> When beans.xml file is changed we always have to run validation manually to reflect newest changes. Shouldn't this be done automatically after beans.xml is changed and saved?
--
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
[JBoss JIRA] (TOOLSDOC-479) Update Usage Reporting topic with additional items recorded
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-479?page=com.atlassian.jira.plug... ]
Michelle Murray updated TOOLSDOC-479:
-------------------------------------
Original Estimate: 30 minutes
Remaining Estimate: 30 minutes
> Update Usage Reporting topic with additional items recorded
> -----------------------------------------------------------
>
> Key: TOOLSDOC-479
> URL: https://issues.jboss.org/browse/TOOLSDOC-479
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: Getting Started Guide, Installation Guide, User Guide
> Affects Versions: 4.2.0.Beta1
> Reporter: Michelle Murray
> Assignee: Michelle Murray
> Fix For: 4.2.0.Beta1
>
> Original Estimate: 30 minutes
> Remaining Estimate: 30 minutes
>
> Need to add to list of info tracked:
> * Installs from JBoss Central
> ** JBoss and 3rd Party plug-ins
> ** examples, specifically quickstarts
> ** whether have JBoss Central configured to show on startup
> * Servers created through new server wizard (not those created with runtime detection)
> ** whether wizard was completed to Finish or cancelled
> ** server type and version (e.g., JBoss 7.1)
> * JVM name
> * bit version of Eclipse
> * bit version of Java
--
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
[JBoss JIRA] (TOOLSDOC-479) Update Usage Reporting topic with additional items recorded
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-479?page=com.atlassian.jira.plug... ]
Michelle Murray updated TOOLSDOC-479:
-------------------------------------
Sprint: 2014/S5 (31-Mar > 13-Apr)
> Update Usage Reporting topic with additional items recorded
> -----------------------------------------------------------
>
> Key: TOOLSDOC-479
> URL: https://issues.jboss.org/browse/TOOLSDOC-479
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: Getting Started Guide, Installation Guide, User Guide
> Affects Versions: 4.2.0.Beta1
> Reporter: Michelle Murray
> Assignee: Michelle Murray
> Fix For: 4.2.0.Beta1
>
> Original Estimate: 30 minutes
> Remaining Estimate: 30 minutes
>
> Need to add to list of info tracked:
> * Installs from JBoss Central
> ** JBoss and 3rd Party plug-ins
> ** examples, specifically quickstarts
> ** whether have JBoss Central configured to show on startup
> * Servers created through new server wizard (not those created with runtime detection)
> ** whether wizard was completed to Finish or cancelled
> ** server type and version (e.g., JBoss 7.1)
> * JVM name
> * bit version of Eclipse
> * bit version of Java
--
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
[JBoss JIRA] (TOOLSDOC-479) Update Usage Reporting topic with additional items recorded
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-479?page=com.atlassian.jira.plug... ]
Michelle Murray updated TOOLSDOC-479:
-------------------------------------
Description:
Need to add to list of info tracked:
* Installs from JBoss Central
** JBoss and 3rd Party plug-ins
** examples, specifically quickstarts
** whether have JBoss Central configured to show on startup
* Servers created through new server wizard (not those created with runtime detection)
** whether wizard was completed to Finish or cancelled
** server type and version (e.g., JBoss 7.1)
* JVM name
* bit version of Eclipse
* bit version of Java
was:
Need to add to list of info tracked:
* JBoss and 3rd party installs from central
**
* Servers created through new server wizard (not those created with runtime detection)
** whether wizard was completed to Finish or cancelled
** server type and version (e.g., JBoss 7.1)
* JVM name
* bit version of Eclipse
* bit version of Java
> Update Usage Reporting topic with additional items recorded
> -----------------------------------------------------------
>
> Key: TOOLSDOC-479
> URL: https://issues.jboss.org/browse/TOOLSDOC-479
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: Getting Started Guide, Installation Guide, User Guide
> Affects Versions: 4.2.0.Beta1
> Reporter: Michelle Murray
> Assignee: Michelle Murray
> Fix For: 4.2.0.Beta1
>
>
> Need to add to list of info tracked:
> * Installs from JBoss Central
> ** JBoss and 3rd Party plug-ins
> ** examples, specifically quickstarts
> ** whether have JBoss Central configured to show on startup
> * Servers created through new server wizard (not those created with runtime detection)
> ** whether wizard was completed to Finish or cancelled
> ** server type and version (e.g., JBoss 7.1)
> * JVM name
> * bit version of Eclipse
> * bit version of Java
--
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
[JBoss JIRA] (TOOLSDOC-479) Update Usage Reporting topic with additional items recorded
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-479?page=com.atlassian.jira.plug... ]
Michelle Murray updated TOOLSDOC-479:
-------------------------------------
Description:
Need to add to list of info tracked:
* JBoss and 3rd party installs from central
**
* Servers created through new server wizard (not those created with runtime detection)
** whether wizard was completed to Finish or cancelled
** server type and version (e.g., JBoss 7.1)
* JVM name
* bit version of Eclipse
* bit version of Java
was:
Need to add to list of info tracked:
* JBoss and 3rd party installs from central
* Servers created
* JVM name
* bit version of Eclipse
* bit version of Java
> Update Usage Reporting topic with additional items recorded
> -----------------------------------------------------------
>
> Key: TOOLSDOC-479
> URL: https://issues.jboss.org/browse/TOOLSDOC-479
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: Getting Started Guide, Installation Guide, User Guide
> Affects Versions: 4.2.0.Beta1
> Reporter: Michelle Murray
> Assignee: Michelle Murray
> Fix For: 4.2.0.Beta1
>
>
> Need to add to list of info tracked:
> * JBoss and 3rd party installs from central
> **
> * Servers created through new server wizard (not those created with runtime detection)
> ** whether wizard was completed to Finish or cancelled
> ** server type and version (e.g., JBoss 7.1)
> * JVM name
> * bit version of Eclipse
> * bit version of Java
--
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
[JBoss JIRA] (TOOLSDOC-479) Update Usage Reporting topic with additional items recorded
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-479?page=com.atlassian.jira.plug... ]
Michelle Murray updated TOOLSDOC-479:
-------------------------------------
Description:
Need to add to list of info tracked:
* JBoss and 3rd party installs from central
* Servers created
* JVM name
* bit version of Eclipse
* bit version of Java
> Update Usage Reporting topic with additional items recorded
> -----------------------------------------------------------
>
> Key: TOOLSDOC-479
> URL: https://issues.jboss.org/browse/TOOLSDOC-479
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: Getting Started Guide, Installation Guide, User Guide
> Affects Versions: 4.2.0.Beta1
> Reporter: Michelle Murray
> Assignee: Michelle Murray
> Fix For: 4.2.0.Beta1
>
>
> Need to add to list of info tracked:
> * JBoss and 3rd party installs from central
> * Servers created
> * JVM name
> * bit version of Eclipse
> * bit version of Java
--
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