[JBoss JIRA] (JBDS-3213) Installer hangs at P2 director when command prompt is disabled
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3213?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBDS-3213:
----------------------------------
If you can't use the installer because your Windows install is locked down, and can't unlock the permissions, you can install Eclipse yourself (download the zip, unpack it), then install the devstudio features into that via its update site or via Eclipse Marketplace.
https://access.redhat.com/documentation/en-us/red_hat_developer_studio/12...
Or, you could try launching a Windows Powershell (Admin) console, then run this:
{code}java c:\path\to\where\you\downloaded\devstudio-installer.jar{code}
https://access.redhat.com/documentation/en-us/red_hat_developer_studio/12...
> Installer hangs at P2 director when command prompt is disabled
> --------------------------------------------------------------
>
> Key: JBDS-3213
> URL: https://issues.jboss.org/browse/JBDS-3213
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: installer
> Affects Versions: 8.0.0.GA
> Environment: Windows 7 Ultimate with group policy "Prevent access to the command prompt" enabled
> Reporter: Richard Hands
> Assignee: Denis Golovin
> Fix For: 9.x, 12.9.0.GA
>
>
> Trying to install JBDS 8.0.0.GA in a customer locked down environment, on a windows machine which has the group policy for locking out the cmd prompt enabled causes the installer to hang at the P2 Director stage. Running with -DTRACE=TRUE shows that it gets to running java -jar ...JBDS.....jar but is trying to use some mechanism which on windows invokes the command prompt, and we end up with, in the console, the message
> The command prompt has been disabled by your administrator.
> Press any key to continue . . .
> but this is hidden when not running in -DTRACE=TRUE mode, and even in trace mode, you can't hit a key as the installer has focus and not the console
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 6 months
[JBoss JIRA] (JBDS-4728) Jboss Developer Studio Hangs on Step 8 of 10
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4728?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBDS-4728:
----------------------------------
What would happen if you...
* launch a Windows Powershell (Admin) console, then run this:
* `java c:\path\to\where\you\downloaded\devstudio-installer.jar`
> Jboss Developer Studio Hangs on Step 8 of 10
> --------------------------------------------
>
> Key: JBDS-4728
> URL: https://issues.jboss.org/browse/JBDS-4728
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: installer
> Affects Versions: 12.0.0.GA
> Environment: Windows 7 (Enterprise) 64bit
> Reporter: Susmit Dey
> Assignee: Nick Boldt
> Fix For: 12.x
>
> Attachments: JBDS_Hung.jpg
>
>
> devstudio-12.0.0.GA-installer-standalone installer hangs on step 8 of 10
> installation progress stuck at 1/3
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 6 months
[JBoss JIRA] (JBDS-3213) Installer hangs at P2 director when command prompt is disabled
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3213?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-3213:
-----------------------------
Fix Version/s: 12.9.0.GA
> Installer hangs at P2 director when command prompt is disabled
> --------------------------------------------------------------
>
> Key: JBDS-3213
> URL: https://issues.jboss.org/browse/JBDS-3213
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: installer
> Affects Versions: 8.0.0.GA
> Environment: Windows 7 Ultimate with group policy "Prevent access to the command prompt" enabled
> Reporter: Richard Hands
> Assignee: Denis Golovin
> Fix For: 9.x, 12.9.0.GA
>
>
> Trying to install JBDS 8.0.0.GA in a customer locked down environment, on a windows machine which has the group policy for locking out the cmd prompt enabled causes the installer to hang at the P2 Director stage. Running with -DTRACE=TRUE shows that it gets to running java -jar ...JBDS.....jar but is trying to use some mechanism which on windows invokes the command prompt, and we end up with, in the console, the message
> The command prompt has been disabled by your administrator.
> Press any key to continue . . .
> but this is hidden when not running in -DTRACE=TRUE mode, and even in trace mode, you can't hit a key as the installer has focus and not the console
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 6 months
[JBoss JIRA] (JBIDE-26355) Fuse on openshift project does not work on CDK CDK v3.6.0-alpha.2-1
by Josef Kopriva (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26355?page=com.atlassian.jira.plugi... ]
Josef Kopriva updated JBIDE-26355:
----------------------------------
Description:
I have tried to reproduce JIRA https://issues.jboss.org/browse/JBIDE-25303 , but during deploy to OpenShift on CDK I get an error.
Full log of build:
{code:java}
[INFO] Scanning for projects...
[WARNING]
[WARNING] Some problems were encountered while building the effective model for org.mycompany:camel-ose-springboot-xml:jar:1.0.0-SNAPSHOT
[WARNING] 'build.plugins.plugin.(groupId:artifactId)' must be unique but found duplicate declaration of plugin org.springframework.boot:spring-boot-maven-plugin @ line 172, column 15
[WARNING]
[WARNING] It is highly recommended to fix these problems because they threaten the stability of your build.
[WARNING]
[WARNING] For this reason, future Maven versions might no longer support building such malformed projects.
[WARNING]
[INFO]
[INFO] ---------------< org.mycompany:camel-ose-springboot-xml >---------------
[INFO] Building Fabric8 :: Quickstarts :: Spring-Boot :: Camel XML 1.0.0-SNAPSHOT
[INFO] --------------------------------[ jar ]---------------------------------
[INFO]
[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ camel-ose-springboot-xml ---
[INFO] Deleting /home/jkopriva/fuse-on-openshift/target
[INFO]
[INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ camel-ose-springboot-xml ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 3 resources
[INFO]
[INFO] --- fabric8-maven-plugin:3.1.80.redhat-000019:resource (default) @ camel-ose-springboot-xml ---
[INFO] F8: Running in OpenShift mode
[INFO] F8: Using docker image name of namespace: myproject
[INFO] F8: spring-boot: Using fat jar packaging as the spring boot plugin is using `repackage` goal execution
[INFO] F8: Running generator spring-boot
[INFO] F8: spring-boot: Using Docker image fabric8/s2i-java as base / builder
[INFO] F8: Using resource templates from /home/jkopriva/fuse-on-openshift/src/main/fabric8
2018-09-10 14:36:03 INFO Version:30 - HV000001: Hibernate Validator 5.2.4.Final
[INFO] F8: fmp-service: Adding a default Service with ports [8080]
[INFO] F8: spring-boot-health-check: Adding readiness probe on port 8081, path='/health', with initial delay 10 seconds
[INFO] F8: spring-boot-health-check: Adding liveness probe on port 8081, path='/health', with initial delay 180 seconds
[WARNING] F8: fmp-git: No .git/config file could be found so cannot annotate kubernetes resources with git commit SHA and branch
[WARNING] F8: fmp-git: No .git/config file could be found so cannot annotate kubernetes resources with git commit SHA and branch
[WARNING] F8: fmp-git: No .git/config file could be found so cannot annotate kubernetes resources with git commit SHA and branch
[WARNING] F8: fmp-git: No .git/config file could be found so cannot annotate kubernetes resources with git commit SHA and branch
[WARNING] F8: fmp-git: No .git/config file could be found so cannot annotate kubernetes resources with git commit SHA and branch
[WARNING] F8: fmp-git: No .git/config file could be found so cannot annotate kubernetes resources with git commit SHA and branch
[INFO]
[INFO] --- maven-compiler-plugin:3.6.0:compile (default-compile) @ camel-ose-springboot-xml ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 2 source files to /home/jkopriva/fuse-on-openshift/target/classes
[INFO]
[INFO] --- maven-resources-plugin:2.6:testResources (default-testResources) @ camel-ose-springboot-xml ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory /home/jkopriva/fuse-on-openshift/src/test/resources
[INFO]
[INFO] --- maven-compiler-plugin:3.6.0:testCompile (default-testCompile) @ camel-ose-springboot-xml ---
[INFO] No sources to compile
[INFO]
[INFO] --- maven-surefire-plugin:2.12.4:test (default-test) @ camel-ose-springboot-xml ---
[INFO] No tests to run.
[INFO]
[INFO] --- maven-jar-plugin:2.4:jar (default-jar) @ camel-ose-springboot-xml ---
[INFO] Building jar: /home/jkopriva/fuse-on-openshift/target/camel-ose-springboot-xml-1.0.0-SNAPSHOT.jar
[INFO]
[INFO] --- spring-boot-maven-plugin:1.4.1.RELEASE:repackage (default) @ camel-ose-springboot-xml ---
[INFO]
[INFO] >>> fabric8-maven-plugin:3.1.80.redhat-000019:build (default) > initialize @ camel-ose-springboot-xml >>>
[INFO]
[INFO] <<< fabric8-maven-plugin:3.1.80.redhat-000019:build (default) < initialize @ camel-ose-springboot-xml <<<
[INFO]
[INFO]
[INFO] --- fabric8-maven-plugin:3.1.80.redhat-000019:build (default) @ camel-ose-springboot-xml ---
[INFO] F8: Using OpenShift build with strategy S2I
[INFO] F8: spring-boot: Using fat jar packaging as the spring boot plugin is using `repackage` goal execution
[INFO] F8: Running generator spring-boot
[INFO] F8: spring-boot: Using Docker image fabric8/s2i-java as base / builder
[INFO] Copying files to /home/jkopriva/fuse-on-openshift/target/docker/camel-ose-springboot-xml/latest/build/maven
[INFO] Building tar: /home/jkopriva/fuse-on-openshift/target/docker/camel-ose-springboot-xml/latest/tmp/docker-build.tar
[INFO] F8: [camel-ose-springboot-xml:latest] "spring-boot": Created docker source tar /home/jkopriva/fuse-on-openshift/target/docker/camel-ose-springboot-xml/latest/tmp/docker-build.tar
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 18.250 s
[INFO] Finished at: 2018-09-10T14:36:19+02:00
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal io.fabric8:fabric8-maven-plugin:3.1.80.redhat-000019:build (default) on project camel-ose-springboot-xml: Execution default of goal io.fabric8:fabric8-maven-plugin:3.1.80.redhat-000019:build failed: An error has occurred. timeout: Socket closed -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/PluginExecutionException
{code}
I have also tried this project with oc cluster up(version 3.9.0) and it went without errors.
was:
I have tried to reproduce JIRA https://issues.jboss.org/browse/JBIDE-25303 , but during deploy to OpenShift on CDK I get an error.
Full log of build:
{code:java}
https://issues.jboss.org/browse/JBIDE-25303
{code}
> Fuse on openshift project does not work on CDK CDK v3.6.0-alpha.2-1
> -------------------------------------------------------------------
>
> Key: JBIDE-26355
> URL: https://issues.jboss.org/browse/JBIDE-26355
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk, openshift
> Affects Versions: 4.9.0.AM3
> Environment: F28
> CDK v3.6.0-alpha.2-1
> Red Hat Developer Studio
> Version: 12.9.0.AM3
> Build id: AM3-v20180906-1322-B3331
> Build date: 20180906-1322
> Reporter: Josef Kopriva
>
> I have tried to reproduce JIRA https://issues.jboss.org/browse/JBIDE-25303 , but during deploy to OpenShift on CDK I get an error.
> Full log of build:
> {code:java}
> [INFO] Scanning for projects...
> [WARNING]
> [WARNING] Some problems were encountered while building the effective model for org.mycompany:camel-ose-springboot-xml:jar:1.0.0-SNAPSHOT
> [WARNING] 'build.plugins.plugin.(groupId:artifactId)' must be unique but found duplicate declaration of plugin org.springframework.boot:spring-boot-maven-plugin @ line 172, column 15
> [WARNING]
> [WARNING] It is highly recommended to fix these problems because they threaten the stability of your build.
> [WARNING]
> [WARNING] For this reason, future Maven versions might no longer support building such malformed projects.
> [WARNING]
> [INFO]
> [INFO] ---------------< org.mycompany:camel-ose-springboot-xml >---------------
> [INFO] Building Fabric8 :: Quickstarts :: Spring-Boot :: Camel XML 1.0.0-SNAPSHOT
> [INFO] --------------------------------[ jar ]---------------------------------
> [INFO]
> [INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ camel-ose-springboot-xml ---
> [INFO] Deleting /home/jkopriva/fuse-on-openshift/target
> [INFO]
> [INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ camel-ose-springboot-xml ---
> [INFO] Using 'UTF-8' encoding to copy filtered resources.
> [INFO] Copying 3 resources
> [INFO]
> [INFO] --- fabric8-maven-plugin:3.1.80.redhat-000019:resource (default) @ camel-ose-springboot-xml ---
> [INFO] F8: Running in OpenShift mode
> [INFO] F8: Using docker image name of namespace: myproject
> [INFO] F8: spring-boot: Using fat jar packaging as the spring boot plugin is using `repackage` goal execution
> [INFO] F8: Running generator spring-boot
> [INFO] F8: spring-boot: Using Docker image fabric8/s2i-java as base / builder
> [INFO] F8: Using resource templates from /home/jkopriva/fuse-on-openshift/src/main/fabric8
> 2018-09-10 14:36:03 INFO Version:30 - HV000001: Hibernate Validator 5.2.4.Final
> [INFO] F8: fmp-service: Adding a default Service with ports [8080]
> [INFO] F8: spring-boot-health-check: Adding readiness probe on port 8081, path='/health', with initial delay 10 seconds
> [INFO] F8: spring-boot-health-check: Adding liveness probe on port 8081, path='/health', with initial delay 180 seconds
> [WARNING] F8: fmp-git: No .git/config file could be found so cannot annotate kubernetes resources with git commit SHA and branch
> [WARNING] F8: fmp-git: No .git/config file could be found so cannot annotate kubernetes resources with git commit SHA and branch
> [WARNING] F8: fmp-git: No .git/config file could be found so cannot annotate kubernetes resources with git commit SHA and branch
> [WARNING] F8: fmp-git: No .git/config file could be found so cannot annotate kubernetes resources with git commit SHA and branch
> [WARNING] F8: fmp-git: No .git/config file could be found so cannot annotate kubernetes resources with git commit SHA and branch
> [WARNING] F8: fmp-git: No .git/config file could be found so cannot annotate kubernetes resources with git commit SHA and branch
> [INFO]
> [INFO] --- maven-compiler-plugin:3.6.0:compile (default-compile) @ camel-ose-springboot-xml ---
> [INFO] Changes detected - recompiling the module!
> [INFO] Compiling 2 source files to /home/jkopriva/fuse-on-openshift/target/classes
> [INFO]
> [INFO] --- maven-resources-plugin:2.6:testResources (default-testResources) @ camel-ose-springboot-xml ---
> [INFO] Using 'UTF-8' encoding to copy filtered resources.
> [INFO] skip non existing resourceDirectory /home/jkopriva/fuse-on-openshift/src/test/resources
> [INFO]
> [INFO] --- maven-compiler-plugin:3.6.0:testCompile (default-testCompile) @ camel-ose-springboot-xml ---
> [INFO] No sources to compile
> [INFO]
> [INFO] --- maven-surefire-plugin:2.12.4:test (default-test) @ camel-ose-springboot-xml ---
> [INFO] No tests to run.
> [INFO]
> [INFO] --- maven-jar-plugin:2.4:jar (default-jar) @ camel-ose-springboot-xml ---
> [INFO] Building jar: /home/jkopriva/fuse-on-openshift/target/camel-ose-springboot-xml-1.0.0-SNAPSHOT.jar
> [INFO]
> [INFO] --- spring-boot-maven-plugin:1.4.1.RELEASE:repackage (default) @ camel-ose-springboot-xml ---
> [INFO]
> [INFO] >>> fabric8-maven-plugin:3.1.80.redhat-000019:build (default) > initialize @ camel-ose-springboot-xml >>>
> [INFO]
> [INFO] <<< fabric8-maven-plugin:3.1.80.redhat-000019:build (default) < initialize @ camel-ose-springboot-xml <<<
> [INFO]
> [INFO]
> [INFO] --- fabric8-maven-plugin:3.1.80.redhat-000019:build (default) @ camel-ose-springboot-xml ---
> [INFO] F8: Using OpenShift build with strategy S2I
> [INFO] F8: spring-boot: Using fat jar packaging as the spring boot plugin is using `repackage` goal execution
> [INFO] F8: Running generator spring-boot
> [INFO] F8: spring-boot: Using Docker image fabric8/s2i-java as base / builder
> [INFO] Copying files to /home/jkopriva/fuse-on-openshift/target/docker/camel-ose-springboot-xml/latest/build/maven
> [INFO] Building tar: /home/jkopriva/fuse-on-openshift/target/docker/camel-ose-springboot-xml/latest/tmp/docker-build.tar
> [INFO] F8: [camel-ose-springboot-xml:latest] "spring-boot": Created docker source tar /home/jkopriva/fuse-on-openshift/target/docker/camel-ose-springboot-xml/latest/tmp/docker-build.tar
> [INFO] ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> [INFO] ------------------------------------------------------------------------
> [INFO] Total time: 18.250 s
> [INFO] Finished at: 2018-09-10T14:36:19+02:00
> [INFO] ------------------------------------------------------------------------
> [ERROR] Failed to execute goal io.fabric8:fabric8-maven-plugin:3.1.80.redhat-000019:build (default) on project camel-ose-springboot-xml: Execution default of goal io.fabric8:fabric8-maven-plugin:3.1.80.redhat-000019:build failed: An error has occurred. timeout: Socket closed -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please read the following articles:
> [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/PluginExecutionException
> {code}
> I have also tried this project with oc cluster up(version 3.9.0) and it went without errors.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 6 months