[JBoss JIRA] (JBDS-3642) Installer is too opaque - need a debug/verbose mode to track progress and debug failures
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3642?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-3642:
-----------------------------
Fix Version/s: 11.0.0.AM2
(was: 11.0.0.AM1)
Slip to AM2
> Installer is too opaque - need a debug/verbose mode to track progress and debug failures
> ----------------------------------------------------------------------------------------
>
> Key: JBDS-3642
> URL: https://issues.jboss.org/browse/JBDS-3642
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: platform-installer
> Affects Versions: 9.1.0.GA
> Reporter: Len DiMaggio
> Assignee: Denis Golovin
> Labels: ui
> Fix For: 11.0.0.AM2
>
>
> The install.log created by the installer does not contain a detailed listing of all actions performed by the installer. Setting the install browser into a debug mode ( "set PDKI_DEBUG=true" ) generated additional information, but it is still node a detailed dump of all actions. Can we add a debug/verbose/trace mode?
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
6 years, 11 months
[JBoss JIRA] (JBDS-2355) JEE web project example generates warnings
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-2355?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-2355:
-----------------------------
Fix Version/s: 11.0.0.AM2
(was: 11.0.0.AM1)
Slip to AM2
> JEE web project example generates warnings
> ------------------------------------------
>
> Key: JBDS-2355
> URL: https://issues.jboss.org/browse/JBDS-2355
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: central
> Affects Versions: 6.0.0.Alpha2
> Environment: Version: 6.0.0.Alpha2
> Build id: Alpha2-v20121004-2330-B40
> Build date: 20121004-2330
> Reporter: Len DiMaggio
> Assignee: Fred Bricon
> Labels: examplewarnings
> Fix For: 11.0.0.AM2
>
>
> The JEE web project example generates these warnings:
> The import java.util.logging.Logger is never used
> MemberController.java
> /jboss-javaee6-webapp/src/main/java/org/jboss/tools/examples/controller
> line 3
> No connection specified for project. No database-specific validation will be performed.
> jboss-javaee6-webapp
> Unnecessary @SuppressWarnings("unused") Resources.java
> /jboss-javaee6-webapp/src/main/java/org/jboss/tools/examples/util
> line 26
> The import javax.persistence.EntityManager is never used
> MemberController.java
> /jboss-javaee6-webapp/src/main/java/org/jboss/tools/examples/controller
> line 14
> The import javax.enterprise.event.Event is never used
> MemberController.java
> /jboss-javaee6-webapp/src/main/java/org/jboss/tools/examples/controller
> line 7
> The import javax.ejb.Stateful is never used
> MemberController.java
> /jboss-javaee6-webapp/src/main/java/org/jboss/tools/examples/controller
> line 6
> The import org.jboss.tools.examples.controller.MemberController is never used
> MemberRegistrationTest.java
> /jboss-javaee6-webapp/src/test/java/org/jboss/tools/examples/test
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
6 years, 11 months
[JBoss JIRA] (JBDS-3758) when something goes wrong, give user call to action / report of what went wrong
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3758?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-3758:
-----------------------------
Fix Version/s: 11.0.0.AM2
(was: 11.0.0.AM1)
Slip to AM2
> when something goes wrong, give user call to action / report of what went wrong
> -------------------------------------------------------------------------------
>
> Key: JBDS-3758
> URL: https://issues.jboss.org/browse/JBDS-3758
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Feature Request
> Components: platform-installer
> Affects Versions: 9.1.0.CR1
> Reporter: Nick Boldt
> Assignee: Denis Golovin
> Labels: ui
> Fix For: 11.0.0.AM2
>
> Attachments: jbds-install-ste-failed-progress-bar-keeps-moving.png
>
>
> I attempted to install from Setup-bundled-0.0.2-20160401-33.exe and while the installer was OK with my using my pre-installed JDK 8 in C:\Program Files\Java\jdk1.8.0_25 (or C:\Program Files\Java\jre1.8.0_25) it then ran into a problem using that JDK to install JBDS.
> I noticed the problem at about 12% on the progress bar but it was still moving along at 45% when I grabbed the screenshot (attached).
> If a failure occurs, perhaps *we could change the bar from blue to red and move it to 100%* ?
> Also, should there be a call to action for the user?
> Even something simple like "*go check in C:\DeveloperPlatform\install.log for what might have happened*" would be useful here.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
6 years, 11 months
[JBoss JIRA] (JBDS-4068) There should be UI to show additional info for detected JDK
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4068?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-4068:
-----------------------------
Fix Version/s: 11.0.0.AM2
(was: 11.0.0.AM1)
Slip to AM2
> There should be UI to show additional info for detected JDK
> -----------------------------------------------------------
>
> Key: JBDS-4068
> URL: https://issues.jboss.org/browse/JBDS-4068
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Enhancement
> Components: platform-installer
> Affects Versions: 10.2.0.AM3
> Reporter: Denis Golovin
> Assignee: Denis Golovin
> Labels: ui
> Fix For: 11.0.0.AM2
>
>
> When vagrant and virtualbox are provided each from the only vendor, the story is different for OpenJDK, because there are several vendors:
> - Oracle;
> - Red Hat;
> - Zulu;
> - IBM.
> Also on 64-bit system both 32-bit and 64-bit JDK could be installed.
> Current UI for OpenJDK component shows only version fro detected JDK. There should be UI to see additional info about selected JDK like vendor and arch.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
6 years, 11 months