[JBoss JIRA] (TOOLSDOC-718) Getting Started / Readme for new CDK users
by Misha Ali (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-718?page=com.atlassian.jira.plug... ]
Misha Ali commented on TOOLSDOC-718:
------------------------------------
[~fbricon] - I sent a following up question to others forgetting that you responded to this for me, so maybe you're the one to ask:
Is the server adapter the only real use case we want to talk about for CDK? Basically: does it do anything else we want to document?
> Getting Started / Readme for new CDK users
> -------------------------------------------
>
> Key: TOOLSDOC-718
> URL: https://issues.jboss.org/browse/TOOLSDOC-718
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Feature Request
> Components: General documentation issues
> Affects Versions: 9.1 CR1
> Reporter: Nick Boldt
> Assignee: Misha Ali
> Labels: Havoc
> Fix For: 9.1 CR1
>
>
> See JBDS-3738.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-22139) 20% of openshift tests are not run
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22139?page=com.atlassian.jira.plugi... ]
Fred Bricon reassigned JBIDE-22139:
-----------------------------------
Assignee: Fred Bricon
> 20% of openshift tests are not run
> ----------------------------------
>
> Key: JBIDE-22139
> URL: https://issues.jboss.org/browse/JBIDE-22139
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Fred Bricon
> Assignee: Fred Bricon
> Fix For: 4.4.0.Alpha1
>
>
> I realized Openshift builds only run ~ 337 tests via tycho, but we have about 411 tests to run.
> This is caused by that stupid tycho-surefire setting that only runs testsuites. Guess what? Some of those test classes are not added to any test suite.
> As a developer I just write my test class and expect the build to pick it up automatically
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-22139) 20% of openshift tests are not run
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22139?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-22139:
--------------------------------
Fix Version/s: 4.4.0.Alpha1
> 20% of openshift tests are not run
> ----------------------------------
>
> Key: JBIDE-22139
> URL: https://issues.jboss.org/browse/JBIDE-22139
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Fred Bricon
> Assignee: Fred Bricon
> Fix For: 4.4.0.Alpha1
>
>
> I realized Openshift builds only run ~ 337 tests via tycho, but we have about 411 tests to run.
> This is caused by that stupid tycho-surefire setting that only runs testsuites. Guess what? Some of those test classes are not added to any test suite.
> As a developer I just write my test class and expect the build to pick it up automatically
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-22139) 20% of openshift tests are not run
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22139?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-22139:
--------------------------------
Issue Type: Task (was: Bug)
> 20% of openshift tests are not run
> ----------------------------------
>
> Key: JBIDE-22139
> URL: https://issues.jboss.org/browse/JBIDE-22139
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Fred Bricon
> Assignee: Fred Bricon
> Fix For: 4.4.0.Alpha1
>
>
> I realized Openshift builds only run ~ 337 tests via tycho, but we have about 411 tests to run.
> This is caused by that stupid tycho-surefire setting that only runs testsuites. Guess what? Some of those test classes are not added to any test suite.
> As a developer I just write my test class and expect the build to pick it up automatically
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-22139) 20% of openshift tests are not run
by Fred Bricon (JIRA)
Fred Bricon created JBIDE-22139:
-----------------------------------
Summary: 20% of openshift tests are not run
Key: JBIDE-22139
URL: https://issues.jboss.org/browse/JBIDE-22139
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.3.1.CR1
Reporter: Fred Bricon
I realized Openshift builds only run ~ 337 tests via tycho, but we have about 411 tests to run.
This is caused by that stupid tycho-surefire setting that only runs testsuites. Guess what? Some of those test classes are not added to any test suite.
As a developer I just write my test class and expect the build to pick it up automatically
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBDS-3774) Failed due to 2 attempts at installing CDK's vagrant box
by CDW Engine (JIRA)
[ https://issues.jboss.org/browse/JBDS-3774?page=com.atlassian.jira.plugin.... ]
CDW Engine updated JBDS-3774:
-----------------------------
> Failed due to 2 attempts at installing CDK's vagrant box
> --------------------------------------------------------
>
> Key: JBDS-3774
> URL: https://issues.jboss.org/browse/JBDS-3774
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: installer
> Affects Versions: 9.1.0.CR1
> Environment: Windows 10 Pro
> Reporter: Burr Sutter
> Assignee: Denis Golovin
> Labels: havoc
> Fix For: 9.1.0.GA
>
> Attachments: install.log, vagrant.log, vbox.log
>
>
> Wed, 06 Apr 2016 01:01:51 GMT-ERROR: cdk - Error: Command failed:
> C:\WINDOWS\system32\cmd.exe /s /c "vagrant box remove cdkv2 -f"
> 'vagrant' is not recognized as an internal or external command,
> operable program or batch file.
> ...
> Wed, 06 Apr 2016 01:02:15 GMT-ERROR: cdk - Error: Command failed:
> C:\WINDOWS\system32\cmd.exe /s /c "vagrant box add --name cdkv2
> c:\DeveloperPlatform\cdk\boxes\rhel-vagrant-virtualbox.box"
> The box you're attempting to add already exists. Remove it before
> adding it again or add it with the `--force` flag.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBDS-3774) Failed due to 2 attempts at installing CDK's vagrant box
by CDW Engine (JIRA)
[ https://issues.jboss.org/browse/JBDS-3774?page=com.atlassian.jira.plugin.... ]
CDW Engine reassigned JBDS-3774:
--------------------------------
> Failed due to 2 attempts at installing CDK's vagrant box
> --------------------------------------------------------
>
> Key: JBDS-3774
> URL: https://issues.jboss.org/browse/JBDS-3774
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: installer
> Affects Versions: 9.1.0.CR1
> Environment: Windows 10 Pro
> Reporter: Burr Sutter
> Assignee: Denis Golovin
> Labels: havoc
> Fix For: 9.1.0.GA
>
> Attachments: install.log, vagrant.log, vbox.log
>
>
> Wed, 06 Apr 2016 01:01:51 GMT-ERROR: cdk - Error: Command failed:
> C:\WINDOWS\system32\cmd.exe /s /c "vagrant box remove cdkv2 -f"
> 'vagrant' is not recognized as an internal or external command,
> operable program or batch file.
> ...
> Wed, 06 Apr 2016 01:02:15 GMT-ERROR: cdk - Error: Command failed:
> C:\WINDOWS\system32\cmd.exe /s /c "vagrant box add --name cdkv2
> c:\DeveloperPlatform\cdk\boxes\rhel-vagrant-virtualbox.box"
> The box you're attempting to add already exists. Remove it before
> adding it again or add it with the `--force` flag.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBDS-3774) Failed due to 2 attempts at installing CDK's vagrant box
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3774?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-3774:
--------------------------------
Status: New (was: New)
Target Release: 9.1.0.GA
> Failed due to 2 attempts at installing CDK's vagrant box
> --------------------------------------------------------
>
> Key: JBDS-3774
> URL: https://issues.jboss.org/browse/JBDS-3774
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: installer
> Affects Versions: 9.1.0.CR1
> Environment: Windows 10 Pro
> Reporter: Burr Sutter
> Assignee: Denis Golovin
> Labels: havoc
> Fix For: 9.1.0.GA
>
> Attachments: install.log, vagrant.log, vbox.log
>
>
> Wed, 06 Apr 2016 01:01:51 GMT-ERROR: cdk - Error: Command failed:
> C:\WINDOWS\system32\cmd.exe /s /c "vagrant box remove cdkv2 -f"
> 'vagrant' is not recognized as an internal or external command,
> operable program or batch file.
> ...
> Wed, 06 Apr 2016 01:02:15 GMT-ERROR: cdk - Error: Command failed:
> C:\WINDOWS\system32\cmd.exe /s /c "vagrant box add --name cdkv2
> c:\DeveloperPlatform\cdk\boxes\rhel-vagrant-virtualbox.box"
> The box you're attempting to add already exists. Remove it before
> adding it again or add it with the `--force` flag.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBDS-3766) Installer - Seeing an intermittent issue where vagrant fails to start - is a system restart needed as indicated in the vagrant log?
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3766?page=com.atlassian.jira.plugin.... ]
Denis Golovin commented on JBDS-3766:
-------------------------------------
Len, IMO problem is in VirtualBox, not vagrant. Looks like you have virtual machine left from previous CDK installation and vagrant fails to modify that..
> Installer - Seeing an intermittent issue where vagrant fails to start - is a system restart needed as indicated in the vagrant log?
> -----------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBDS-3766
> URL: https://issues.jboss.org/browse/JBDS-3766
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: installer
> Affects Versions: 9.1.0.CR1
> Environment: Installer: Setup-bundled-0.0.2-20160401-33
> Reporter: Len DiMaggio
> Assignee: Denis Golovin
> Priority: Critical
> Labels: havoc
> Fix For: 9.1.0.GA
>
> Attachments: install.log, Is_Restart_Needed.png, vagrant.log, vbox.log
>
>
> See attached log files.
> After some install attempts, Vagrant fails to start. The vagrant install log reports the following:
> {code}
> MSI (s) (DC:C4) [11:00:34:591]: Product: Vagrant -- Installation completed successfully.
> MSI (s) (DC:C4) [11:00:34:591]: Windows Installer installed the product. Product Name: Vagrant. Product Version: 1.7.4. Product Language: 1033. Manufacturer: HashiCorp. Installation success or error status: 0.
> MSI (s) (DC:C4) [11:00:34:591]: Windows Installer requires a system restart. Product Name: Vagrant. Product Version: 1.7.4. Product Language: 1033. Manufacturer: HashiCorp. Type of System Restart: 2. Reason for Restart: 2.
> MSI (s) (DC:C4) [11:00:34:591]: Product: Vagrant. Restart required. The installation or update for the product required a restart for all changes to take effect. The restart was deferred to a later time.
> {code}
> Is a system restart needed to ensure that the vagrant installation is successful on Windows?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-22138) Openshift 3 plugin "Server Adapter" doesn't respect openshift maven profile
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22138?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-22138:
--------------------------------
Description:
This is a follow up on JBIDE-22128.
The maven profile is never read to determine the actual archive name. That will require more coupling to m2e, in order to load the pom.xml model using the openshift profile, if it exists, in order to determine the archive name. This will be a long running operation and will require more significant changes
was:the maven profile is never read to determine the actual archive name. That will require more coupling to m2e, in order to load the pom.xml model using the openshift profile, if it exists, in order to determine the archive name. This will be a long running operation and will require more significant changes
> Openshift 3 plugin "Server Adapter" doesn't respect openshift maven profile
> ---------------------------------------------------------------------------
>
> Key: JBIDE-22138
> URL: https://issues.jboss.org/browse/JBIDE-22138
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Environment: JBoss Developer Studio (Core Features) 9.1.0.GA-v20160403-1700-B477
> Openshift plugin 3.1.0.Final-v20160401-2357-B263
> Reporter: Rafael Benevides
> Assignee: Fred Bricon
> Fix For: 4.4.x
>
>
> This is a follow up on JBIDE-22128.
> The maven profile is never read to determine the actual archive name. That will require more coupling to m2e, in order to load the pom.xml model using the openshift profile, if it exists, in order to determine the archive name. This will be a long running operation and will require more significant changes
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years