[JBoss JIRA] (JBDS-2859) Include information on EAP version in installer
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-2859?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-2859:
--------------------------------
Attachment: summary-eap-version-fixed.png
> Include information on EAP version in installer
> -----------------------------------------------
>
> Key: JBDS-2859
> URL: https://issues.jboss.org/browse/JBDS-2859
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: installer
> Affects Versions: 7.1.0.CR1
> Reporter: Martin Malina
> Assignee: Denis Golovin
> Fix For: 8.0.0.CR1
>
> Attachments: step-6.png, summary-eap-version-fixed.png
>
>
> I find it hard for users to find out which version of EAP they are installing with JBDS. The installer has no mention of it. At least in the installer summary (Step 6 of 9) we could include this information.
> !step-6.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
12 years, 1 month
[JBoss JIRA] (JBIDE-16955) Daily usage event reporting job (sleeping) stays in Progress View
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16955?page=com.atlassian.jira.plugi... ]
Alexey Kazakov edited comment on JBIDE-16955 at 3/31/14 4:36 PM:
-----------------------------------------------------------------
Merged to master (JBIDE-16958) and waiting for beta1 approval.
was (Author: akazakov):
Merged to master and waiting for beta1 approval.
> Daily usage event reporting job (sleeping) stays in Progress View
> -----------------------------------------------------------------
>
> Key: JBIDE-16955
> URL: https://issues.jboss.org/browse/JBIDE-16955
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: usage
> Affects Versions: 4.2.0.Beta1
> Reporter: Fred Bricon
> Assignee: Alexey Kazakov
> Priority: Minor
> Labels: respin-b
> Fix For: 4.2.0.Beta1
>
>
> After restarting the workbench, "Daily usage event reporting job (sleeping)" stays in Progress View forever.
> !http://content.screencast.com/users/fbricon/folders/Jing/media/92f4cca0-5a94-45ac-b2c2-ce2d60c1aee3/daily-usage-reporting-job.png!
> I'm pretty sure it's gonna scare/annoy some 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
12 years, 1 month
[JBoss JIRA] (JBIDE-16955) Daily usage event reporting job (sleeping) stays in Progress View
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16955?page=com.atlassian.jira.plugi... ]
Alexey Kazakov commented on JBIDE-16955:
----------------------------------------
Merged to master and waiting for beta1 approval.
> Daily usage event reporting job (sleeping) stays in Progress View
> -----------------------------------------------------------------
>
> Key: JBIDE-16955
> URL: https://issues.jboss.org/browse/JBIDE-16955
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: usage
> Affects Versions: 4.2.0.Beta1
> Reporter: Fred Bricon
> Assignee: Alexey Kazakov
> Priority: Minor
> Labels: respin-b
> Fix For: 4.2.0.Beta1
>
>
> After restarting the workbench, "Daily usage event reporting job (sleeping)" stays in Progress View forever.
> !http://content.screencast.com/users/fbricon/folders/Jing/media/92f4cca0-5a94-45ac-b2c2-ce2d60c1aee3/daily-usage-reporting-job.png!
> I'm pretty sure it's gonna scare/annoy some 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
12 years, 1 month
[JBoss JIRA] (JBIDE-16958) Daily usage event reporting job (sleeping) stays in Progress View
by Alexey Kazakov (JIRA)
Alexey Kazakov created JBIDE-16958:
--------------------------------------
Summary: Daily usage event reporting job (sleeping) stays in Progress View
Key: JBIDE-16958
URL: https://issues.jboss.org/browse/JBIDE-16958
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: usage
Affects Versions: 4.2.0.Beta1
Reporter: Alexey Kazakov
Assignee: Alexey Kazakov
Priority: Minor
Fix For: 4.2.0.Beta1
After restarting the workbench, "Daily usage event reporting job (sleeping)" stays in Progress View forever.
!http://content.screencast.com/users/fbricon/folders/Jing/media/92f4cca0-5a94-45ac-b2c2-ce2d60c1aee3/daily-usage-reporting-job.png!
I'm pretty sure it's gonna scare/annoy some 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
12 years, 1 month
[JBoss JIRA] (JBIDE-16955) Daily usage event reporting job (sleeping) stays in Progress View
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16955?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen updated JBIDE-16955:
----------------------------------------
Fix Version/s: 4.2.0.Beta1
Labels: respin-b (was: )
if this is a trivial change lets get a PR ready to put in if a respin-b happens.
> Daily usage event reporting job (sleeping) stays in Progress View
> -----------------------------------------------------------------
>
> Key: JBIDE-16955
> URL: https://issues.jboss.org/browse/JBIDE-16955
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: usage
> Affects Versions: 4.2.0.Beta1
> Reporter: Fred Bricon
> Assignee: Alexey Kazakov
> Priority: Minor
> Labels: respin-b
> Fix For: 4.2.0.Beta1
>
>
> After restarting the workbench, "Daily usage event reporting job (sleeping)" stays in Progress View forever.
> !http://content.screencast.com/users/fbricon/folders/Jing/media/92f4cca0-5a94-45ac-b2c2-ce2d60c1aee3/daily-usage-reporting-job.png!
> I'm pretty sure it's gonna scare/annoy some 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
12 years, 1 month