[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
11 years, 7 months
[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
11 years, 7 months
[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
11 years, 7 months
[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
11 years, 7 months
[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
11 years, 7 months
[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
11 years, 7 months
[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
11 years, 7 months
[JBoss JIRA] (JBIDE-16800) Add usage tracking for server creation
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16800?page=com.atlassian.jira.plugi... ]
Michelle Murray closed JBIDE-16800.
-----------------------------------
> Add usage tracking for server creation
> --------------------------------------
>
> Key: JBIDE-16800
> URL: https://issues.jboss.org/browse/JBIDE-16800
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: server, usage
> Reporter: Alexey Kazakov
> Assignee: Max Rydahl Andersen
> Labels: new_and_noteworthy
> Fix For: 4.2.0.Beta1
>
> Attachments: action.png, category.png, label.png, preferences.png
>
>
> Usage tracks "Perform Finish" (value=1) and "Perform Cancel" (value=0) events for New JBoss Servers.
> This event type in Preferences:
> !preferences.png!
> A few examples in google analytics:
> !category.png!
> !action.png!
> !label.png!
--
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, 7 months
[JBoss JIRA] (JBIDE-16800) Add usage tracking for server creation
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16800?page=com.atlassian.jira.plugi... ]
Michelle Murray resolved JBIDE-16800.
-------------------------------------
Resolution: Done
> Add usage tracking for server creation
> --------------------------------------
>
> Key: JBIDE-16800
> URL: https://issues.jboss.org/browse/JBIDE-16800
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: server, usage
> Reporter: Alexey Kazakov
> Assignee: Max Rydahl Andersen
> Labels: new_and_noteworthy
> Fix For: 4.2.0.Beta1
>
> Attachments: action.png, category.png, label.png, preferences.png
>
>
> Usage tracks "Perform Finish" (value=1) and "Perform Cancel" (value=0) events for New JBoss Servers.
> This event type in Preferences:
> !preferences.png!
> A few examples in google analytics:
> !category.png!
> !action.png!
> !label.png!
--
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, 7 months