[JBoss JIRA] (JBDS-3786) CDK fails on 'vagrant plugin install'
by Jan Richter (JIRA)
[ https://issues.jboss.org/browse/JBDS-3786?page=com.atlassian.jira.plugin.... ]
Jan Richter updated JBDS-3786:
------------------------------
Description:
Using bundled installer B90. Everything goes well up to the point when CDK gets into the post-Vagrant setup and fail on vagrant plugin installation. This is the error from install.log:
{noformat}
Mon, 11 Apr 2016 08:08:14 GMT-INFO: cdk - postVagrantSetup called
Mon, 11 Apr 2016 08:08:14 GMT-INFO: cdk - Execute command vagrant plugin install c:\DeveloperPlatform\cdk\plugins\vagrant-registration-1.2.1.gem
Mon, 11 Apr 2016 08:08:14 GMT-INFO: cdk - Execute options {
"env": {
"path": "c:\\DeveloperPlatform\\vagrant;C:\\DeveloperPlatform\\virtualbox\\;"
}
}
Mon, 11 Apr 2016 08:08:14 GMT-ERROR: cdk - Error: Command failed: vagrant plugin install c:\DeveloperPlatform\cdk\plugins\vagrant-registration-1.2.1.gem
'vagrant' is not recognized as an internal or external command,
operable program or batch file.
Mon, 11 Apr 2016 08:08:14 GMT-ERROR: cdk - 'vagrant' is not recognized as an internal or external command,
operable program or batch file.
Mon, 11 Apr 2016 08:08:14 GMT-ERROR: cdk failed to install: Error: Command failed: vagrant plugin install c:\DeveloperPlatform\cdk\plugins\vagrant-registration-1.2.1.gem
'vagrant' is not recognized as an internal or external command,
operable program or batch file.
{noformat}
was:
Everything goes well up to the point when CDK gets into the post-Vagrant setup and fail on vagrant plugin installation. This is the error from install.log:
{noformat}
Mon, 11 Apr 2016 08:08:14 GMT-INFO: cdk - postVagrantSetup called
Mon, 11 Apr 2016 08:08:14 GMT-INFO: cdk - Execute command vagrant plugin install c:\DeveloperPlatform\cdk\plugins\vagrant-registration-1.2.1.gem
Mon, 11 Apr 2016 08:08:14 GMT-INFO: cdk - Execute options {
"env": {
"path": "c:\\DeveloperPlatform\\vagrant;C:\\DeveloperPlatform\\virtualbox\\;"
}
}
Mon, 11 Apr 2016 08:08:14 GMT-ERROR: cdk - Error: Command failed: vagrant plugin install c:\DeveloperPlatform\cdk\plugins\vagrant-registration-1.2.1.gem
'vagrant' is not recognized as an internal or external command,
operable program or batch file.
Mon, 11 Apr 2016 08:08:14 GMT-ERROR: cdk - 'vagrant' is not recognized as an internal or external command,
operable program or batch file.
Mon, 11 Apr 2016 08:08:14 GMT-ERROR: cdk failed to install: Error: Command failed: vagrant plugin install c:\DeveloperPlatform\cdk\plugins\vagrant-registration-1.2.1.gem
'vagrant' is not recognized as an internal or external command,
operable program or batch file.
{noformat}
> CDK fails on 'vagrant plugin install'
> -------------------------------------
>
> Key: JBDS-3786
> URL: https://issues.jboss.org/browse/JBDS-3786
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: installer
> Affects Versions: 9.1.0.CR1
> Reporter: Jan Richter
> Assignee: Denis Golovin
> Priority: Blocker
> Labels: havoc
>
> Using bundled installer B90. Everything goes well up to the point when CDK gets into the post-Vagrant setup and fail on vagrant plugin installation. This is the error from install.log:
> {noformat}
> Mon, 11 Apr 2016 08:08:14 GMT-INFO: cdk - postVagrantSetup called
> Mon, 11 Apr 2016 08:08:14 GMT-INFO: cdk - Execute command vagrant plugin install c:\DeveloperPlatform\cdk\plugins\vagrant-registration-1.2.1.gem
> Mon, 11 Apr 2016 08:08:14 GMT-INFO: cdk - Execute options {
> "env": {
> "path": "c:\\DeveloperPlatform\\vagrant;C:\\DeveloperPlatform\\virtualbox\\;"
> }
> }
> Mon, 11 Apr 2016 08:08:14 GMT-ERROR: cdk - Error: Command failed: vagrant plugin install c:\DeveloperPlatform\cdk\plugins\vagrant-registration-1.2.1.gem
> 'vagrant' is not recognized as an internal or external command,
> operable program or batch file.
> Mon, 11 Apr 2016 08:08:14 GMT-ERROR: cdk - 'vagrant' is not recognized as an internal or external command,
> operable program or batch file.
> Mon, 11 Apr 2016 08:08:14 GMT-ERROR: cdk failed to install: Error: Command failed: vagrant plugin install c:\DeveloperPlatform\cdk\plugins\vagrant-registration-1.2.1.gem
> 'vagrant' is not recognized as an internal or external command,
> operable program or batch file.
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBDS-3786) CDK fails on 'vagrant plugin install'
by Jan Richter (JIRA)
[ https://issues.jboss.org/browse/JBDS-3786?page=com.atlassian.jira.plugin.... ]
Jan Richter updated JBDS-3786:
------------------------------
Description:
Using bundled installer B90. Everything goes well up to the point when CDK gets into the post-Vagrant setup and fails on vagrant plugin installation. This is the error from install.log:
{noformat}
Mon, 11 Apr 2016 08:08:14 GMT-INFO: cdk - postVagrantSetup called
Mon, 11 Apr 2016 08:08:14 GMT-INFO: cdk - Execute command vagrant plugin install c:\DeveloperPlatform\cdk\plugins\vagrant-registration-1.2.1.gem
Mon, 11 Apr 2016 08:08:14 GMT-INFO: cdk - Execute options {
"env": {
"path": "c:\\DeveloperPlatform\\vagrant;C:\\DeveloperPlatform\\virtualbox\\;"
}
}
Mon, 11 Apr 2016 08:08:14 GMT-ERROR: cdk - Error: Command failed: vagrant plugin install c:\DeveloperPlatform\cdk\plugins\vagrant-registration-1.2.1.gem
'vagrant' is not recognized as an internal or external command,
operable program or batch file.
Mon, 11 Apr 2016 08:08:14 GMT-ERROR: cdk - 'vagrant' is not recognized as an internal or external command,
operable program or batch file.
Mon, 11 Apr 2016 08:08:14 GMT-ERROR: cdk failed to install: Error: Command failed: vagrant plugin install c:\DeveloperPlatform\cdk\plugins\vagrant-registration-1.2.1.gem
'vagrant' is not recognized as an internal or external command,
operable program or batch file.
{noformat}
was:
Using bundled installer B90. Everything goes well up to the point when CDK gets into the post-Vagrant setup and fail on vagrant plugin installation. This is the error from install.log:
{noformat}
Mon, 11 Apr 2016 08:08:14 GMT-INFO: cdk - postVagrantSetup called
Mon, 11 Apr 2016 08:08:14 GMT-INFO: cdk - Execute command vagrant plugin install c:\DeveloperPlatform\cdk\plugins\vagrant-registration-1.2.1.gem
Mon, 11 Apr 2016 08:08:14 GMT-INFO: cdk - Execute options {
"env": {
"path": "c:\\DeveloperPlatform\\vagrant;C:\\DeveloperPlatform\\virtualbox\\;"
}
}
Mon, 11 Apr 2016 08:08:14 GMT-ERROR: cdk - Error: Command failed: vagrant plugin install c:\DeveloperPlatform\cdk\plugins\vagrant-registration-1.2.1.gem
'vagrant' is not recognized as an internal or external command,
operable program or batch file.
Mon, 11 Apr 2016 08:08:14 GMT-ERROR: cdk - 'vagrant' is not recognized as an internal or external command,
operable program or batch file.
Mon, 11 Apr 2016 08:08:14 GMT-ERROR: cdk failed to install: Error: Command failed: vagrant plugin install c:\DeveloperPlatform\cdk\plugins\vagrant-registration-1.2.1.gem
'vagrant' is not recognized as an internal or external command,
operable program or batch file.
{noformat}
> CDK fails on 'vagrant plugin install'
> -------------------------------------
>
> Key: JBDS-3786
> URL: https://issues.jboss.org/browse/JBDS-3786
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: installer
> Affects Versions: 9.1.0.CR1
> Reporter: Jan Richter
> Assignee: Denis Golovin
> Priority: Blocker
> Labels: havoc
>
> Using bundled installer B90. Everything goes well up to the point when CDK gets into the post-Vagrant setup and fails on vagrant plugin installation. This is the error from install.log:
> {noformat}
> Mon, 11 Apr 2016 08:08:14 GMT-INFO: cdk - postVagrantSetup called
> Mon, 11 Apr 2016 08:08:14 GMT-INFO: cdk - Execute command vagrant plugin install c:\DeveloperPlatform\cdk\plugins\vagrant-registration-1.2.1.gem
> Mon, 11 Apr 2016 08:08:14 GMT-INFO: cdk - Execute options {
> "env": {
> "path": "c:\\DeveloperPlatform\\vagrant;C:\\DeveloperPlatform\\virtualbox\\;"
> }
> }
> Mon, 11 Apr 2016 08:08:14 GMT-ERROR: cdk - Error: Command failed: vagrant plugin install c:\DeveloperPlatform\cdk\plugins\vagrant-registration-1.2.1.gem
> 'vagrant' is not recognized as an internal or external command,
> operable program or batch file.
> Mon, 11 Apr 2016 08:08:14 GMT-ERROR: cdk - 'vagrant' is not recognized as an internal or external command,
> operable program or batch file.
> Mon, 11 Apr 2016 08:08:14 GMT-ERROR: cdk failed to install: Error: Command failed: vagrant plugin install c:\DeveloperPlatform\cdk\plugins\vagrant-registration-1.2.1.gem
> 'vagrant' is not recognized as an internal or external command,
> operable program or batch file.
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBDS-3786) CDK fails on 'vagrant plugin install'
by Jan Richter (JIRA)
Jan Richter created JBDS-3786:
---------------------------------
Summary: CDK fails on 'vagrant plugin install'
Key: JBDS-3786
URL: https://issues.jboss.org/browse/JBDS-3786
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Components: installer
Affects Versions: 9.1.0.CR1
Reporter: Jan Richter
Assignee: Denis Golovin
Priority: Blocker
Everything goes well up to the point when CDK gets into the post-Vagrant setup and fail on vagrant plugin installation. This is the error from install.log:
{noformat}
Mon, 11 Apr 2016 08:08:14 GMT-INFO: cdk - postVagrantSetup called
Mon, 11 Apr 2016 08:08:14 GMT-INFO: cdk - Execute command vagrant plugin install c:\DeveloperPlatform\cdk\plugins\vagrant-registration-1.2.1.gem
Mon, 11 Apr 2016 08:08:14 GMT-INFO: cdk - Execute options {
"env": {
"path": "c:\\DeveloperPlatform\\vagrant;C:\\DeveloperPlatform\\virtualbox\\;"
}
}
Mon, 11 Apr 2016 08:08:14 GMT-ERROR: cdk - Error: Command failed: vagrant plugin install c:\DeveloperPlatform\cdk\plugins\vagrant-registration-1.2.1.gem
'vagrant' is not recognized as an internal or external command,
operable program or batch file.
Mon, 11 Apr 2016 08:08:14 GMT-ERROR: cdk - 'vagrant' is not recognized as an internal or external command,
operable program or batch file.
Mon, 11 Apr 2016 08:08:14 GMT-ERROR: cdk failed to install: Error: Command failed: vagrant plugin install c:\DeveloperPlatform\cdk\plugins\vagrant-registration-1.2.1.gem
'vagrant' is not recognized as an internal or external command,
operable program or batch file.
{noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-22105) Update AERI Server to 2.0
by Marcel Bruch (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22105?page=com.atlassian.jira.plugi... ]
Marcel Bruch updated JBIDE-22105:
---------------------------------
Fix Version/s: 4.3.1.Final
(was: 4.3.x)
> Update AERI Server to 2.0
> -------------------------
>
> Key: JBIDE-22105
> URL: https://issues.jboss.org/browse/JBIDE-22105
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: aeri
> Reporter: Marcel Bruch
> Assignee: Marcel Bruch
> Priority: Minor
> Fix For: 4.3.1.Final
>
>
> I'd like to roll out an update of the aeri server.
> Notable changes on for Eclipse clients:
> This update changes the sever responses send back to clients on submission of a problem report. The response format is compatible with the Eclipse AERI integration 1.100+
> No breaking changes.
> Most notable changes on the server's web-site:
> * The UI changed from AngularJS to Vaadin
> * Improved JIRA integration.
> * Improved customization of email digests and bug creation templates
> * Fine-grained control over server-responses
> * Auto-Actions for automated problem state transitions on problem state changes (e.g., _number-of-reporters > 100 && status=open --> Set Severity to major._ or _If new error reports arrived in with bundle.version > 1.2.3 --> set status=reopen.
> Details will be announced separately.
> In this bug I'm looking for a process *how* to perform an server-update for JBoss Tools.
> I'd like to know who needs to be involved in case of major/minor updates? Is some testing / approval from QE required before an update can go live?
> My proposed way of doing a major update:
> * Copy the current database.
> * Set up a sandbox instance running on the copied database
> * Create a JIRA issue for the planned update.
> * After approval by QE switch testing instance to production
> FWIW, I don't plan to announce minor bugfixes and minor improvements (e.g., to duplicate detection) as long as they do have user-observable impact or lead to significant changes in the UI and workflows.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBTIS-655) Add tests for launchers
by Tomáš Sedmík (JIRA)
Tomáš Sedmík created JBTIS-655:
----------------------------------
Summary: Add tests for launchers
Key: JBTIS-655
URL: https://issues.jboss.org/browse/JBTIS-655
Project: JBoss Tools Integration Stack
Issue Type: Task
Components: Fuse IDE, QE
Affects Versions: 4.3.0.CR1
Reporter: Tomáš Sedmík
Assignee: Tomáš Sedmík
Fix For: 4.3.0.Final
SSIA (see related issue)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years