[JBoss JIRA] (JBTIS-990) JBTIS TP update - JBT 4.61.0/ 4.4.2
by Paul Leacu (JIRA)
[ https://issues.jboss.org/browse/JBTIS-990?page=com.atlassian.jira.plugin.... ]
Paul Leacu edited comment on JBTIS-990 at 12/2/16 4:23 PM:
-----------------------------------------------------------
An updated Neon target platform is now available - 4.4.1.CR1
https://repository.jboss.org/nexus/content/repositories/releases/org/jbos...
http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/4.4.1.CR1
This syncs with JBT 4.61.0/ 4.4.2 (Final).
Use the base classifier:
<classifier>base</classifier>
was (Author: pleacu):
An updated Neon target platform is now available - 4.4.1.Beta1-SNAPSHOT
https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo...
http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/4.4.1.Be...
This syncs with JBT 4.61.0/ 4.4.2 (AM3) - I'll respin when JBT releases .Final.
Use the base classifier:
<classifier>base</classifier>
> JBTIS TP update - JBT 4.61.0/ 4.4.2
> -----------------------------------
>
> Key: JBTIS-990
> URL: https://issues.jboss.org/browse/JBTIS-990
> Project: JBoss Tools Integration Stack
> Issue Type: Feature Request
> Reporter: Paul Leacu
> Assignee: Paul Leacu
>
> *Reason:* Update to 4.61.0/ 4.4.0 parent pom
> *Project page/sources:*
> *Version:* 4.61.0.Final-SNAPSHOT
> *License and owner:* EPL
> *Original p2 repo:* http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.6...
> *JBoss mirror:*
> *Include Sources:* Yes
> *Affected JBoss Tools components:* Devstudio IS
> *Include in JBDS:* Yes (DevstudioIS)
> *Type of dependency:* distribution
> *List of bundles added/removed:*
> {code}
> target-platform.p2diff:
> < org.jboss.tools.maven.jsf [1.3.1.20160831-1005]
> < org.jboss.tools.maven.jpa [1.3.1.20160831-1005]
> < org.eclipse.m2e.wtp.feature.feature.jar [1.3.1.20160831-1005]
> < org.eclipse.m2e.wtp.jsf.feature.feature.jar [1.3.1.20160831-1005]
> < org.eclipse.m2e.wtp.jaxrs.feature.feature.jar [1.3.1.20160831-1005]
> < org.eclipse.m2e.wtp.jpa.feature.feature.jar [1.3.1.20160831-1005]
> < org.maven.ide.eclipse.wtp [1.3.1.20160831-1005]
> < org.eclipse.m2e.wtp.jaxrs.feature.feature.group [1.3.1.20160831-1005]
> < org.eclipse.m2e.wtp.jaxrs [1.3.1.20160831-1005]
> < org.jboss.tools.maven.jaxrs [1.3.1.20160831-1005]
> < org.eclipse.m2e.wtp.jsf.feature.feature.group [1.3.1.20160831-1005]
> < org.eclipse.m2e.wtp.jpa.feature.feature.group [1.3.1.20160831-1005]
> < org.eclipse.m2e.wtp.overlay.ui [1.3.1.20160831-1005]
> < org.eclipse.m2e.wtp [1.3.1.20160831-1005]
> < org.eclipse.m2e.wtp.overlay [1.3.1.20160831-1005]
> < org.eclipse.m2e.wtp.jpa [1.3.1.20160831-1005]
> < org.eclipse.m2e.wtp.jsf [1.3.1.20160831-1005]
> < org.eclipse.m2e.wtp.feature.feature.group [1.3.1.20160831-1005]
> > org.eclipse.birt.report.data.oda.jdbc.ui [4.6.0.v201602022206]
> > org.eclipse.birt.data.oda.mongodb.ui [4.6.0.v201602022206]
> > org.eclipse.birt.core [4.6.0.v201602022206]
> > org.eclipse.birt.report.data.bidi.utils.ui [4.6.0.v201602022206]
> > org.eclipse.birt.report.data.oda.hive.ui [4.6.0.v201602022206]
> > org.eclipse.birt.report.data.oda.jdbc [4.6.0.v201602022206]
> > org.apache.poi [3.9.0.v201405241750]
> > org.eclipse.birt.report.data.oda.hive [4.6.0.v201602022206]
> > org.eclipse.birt.report.data.bidi.utils [4.6.0.v201602022206]
> > org.eclipse.core.runtime.compatibility [3.2.300.v20150423-0821]
> > org.eclipse.birt.data.oda.mongodb [4.6.0.v201602022206]
> > org.eclipse.orbit.mongodb [2.10.1.v20130422-1135]
> === Summary ===
> http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/4.4.0.Fi... contains 18 unique IUs
> file:/home/pleacu/git-clone/jbosstools-integration-stack/target-platform/target/target-platform.target.repo contains 12 unique IUs
> target-platform-ea.p2diff:
> < org.jboss.tools.maven.jsf [1.3.1.20160831-1005]
> < org.jboss.tools.maven.jpa [1.3.1.20160831-1005]
> < org.eclipse.m2e.wtp.feature.feature.jar [1.3.1.20160831-1005]
> < org.eclipse.m2e.wtp.jsf.feature.feature.jar [1.3.1.20160831-1005]
> < org.eclipse.m2e.wtp.jaxrs.feature.feature.jar [1.3.1.20160831-1005]
> < org.eclipse.m2e.wtp.jpa.feature.feature.jar [1.3.1.20160831-1005]
> < org.maven.ide.eclipse.wtp [1.3.1.20160831-1005]
> < org.eclipse.m2e.wtp.jaxrs.feature.feature.group [1.3.1.20160831-1005]
> < org.eclipse.m2e.wtp.jaxrs [1.3.1.20160831-1005]
> < org.jboss.tools.maven.jaxrs [1.3.1.20160831-1005]
> < org.eclipse.m2e.wtp.jsf.feature.feature.group [1.3.1.20160831-1005]
> < org.eclipse.m2e.wtp.jpa.feature.feature.group [1.3.1.20160831-1005]
> < org.eclipse.m2e.wtp.overlay.ui [1.3.1.20160831-1005]
> < org.eclipse.m2e.wtp [1.3.1.20160831-1005]
> < org.eclipse.m2e.wtp.overlay [1.3.1.20160831-1005]
> < org.eclipse.m2e.wtp.jpa [1.3.1.20160831-1005]
> < org.eclipse.m2e.wtp.jsf [1.3.1.20160831-1005]
> < org.eclipse.m2e.wtp.feature.feature.group [1.3.1.20160831-1005]
> === Summary ===
> http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/4.4.0.Fi... contains 18 unique IUs
> file:/home/pleacu/git-clone/jbosstools-integration-stack/target-platform/target/target-platform-ea.target.repo contains 0 unique IUs
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 7 months
[JBoss JIRA] (JBIDE-21857) Hot code replacement doesn't work on OpenShift
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21857?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-21857:
-------------------------------------
I would also like to add that what Marion shows in the video is expected. The very first structural change should definitely show the dialog. The problem is that future non-breaking changes should NOT show the dialog.
> Hot code replacement doesn't work on OpenShift
> ----------------------------------------------
>
> Key: JBIDE-21857
> URL: https://issues.jboss.org/browse/JBIDE-21857
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Reporter: Fred Bricon
> Assignee: Rob Stryker
> Fix For: 4.4.3.AM1, 4.5.0.AM1
>
> Attachments: HCRFailure.zip, code-out-of-sync.png, hot-code-replace-failed.png, jmx-connected-adapter-synchronized.png
>
>
> When enabling debug mode on an EAP server deployed on OpenShift, locally changing a class file will :
> - work sometimes when only the content of the method changed, but could fail in some other occasions with the Debugger saying the JDK is out of sync
> - will always fail if a method signature changed, the debugger saying JDK is out of sync
> Restarting the deployed module (with the .dodeploy flag) doesn't fixes the issue (as opposed to the same tweak ahen running on a local EAP server)
> This may be caused by running OpenJDK? Does it support the same level of debugging as Oracle JDK?
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 7 months
[JBoss JIRA] (JBIDE-21857) Hot code replacement doesn't work on OpenShift
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21857?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-21857:
-------------------------------------
Marian is right. It's not working as expected.
I spent the past 4 hours testing a few different additional ways to make this work, and nothing is working.
I've even tried disconnecting the remote debugger, doing a full publish, and then connecting the remote debugger again, an entirely new launch. Even this has failed.
[~tmader] - We may need some help on this issue. I know it is executing the gc's, but nothing seems to be working. I've tried adding delays, I've tried disconnecting and reconnecting, I've tried everything I can think of. I've tried removign all breakpoints, disconnecting,
I'm not really familiar with how to debug this more deeply or see what can be done. I'm shocked that the gc's aren't doing what we expected them to do.
> Hot code replacement doesn't work on OpenShift
> ----------------------------------------------
>
> Key: JBIDE-21857
> URL: https://issues.jboss.org/browse/JBIDE-21857
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Reporter: Fred Bricon
> Assignee: Rob Stryker
> Fix For: 4.4.3.AM1, 4.5.0.AM1
>
> Attachments: HCRFailure.zip, code-out-of-sync.png, hot-code-replace-failed.png, jmx-connected-adapter-synchronized.png
>
>
> When enabling debug mode on an EAP server deployed on OpenShift, locally changing a class file will :
> - work sometimes when only the content of the method changed, but could fail in some other occasions with the Debugger saying the JDK is out of sync
> - will always fail if a method signature changed, the debugger saying JDK is out of sync
> Restarting the deployed module (with the .dodeploy flag) doesn't fixes the issue (as opposed to the same tweak ahen running on a local EAP server)
> This may be caused by running OpenJDK? Does it support the same level of debugging as Oracle JDK?
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 7 months
[JBoss JIRA] (JBIDE-23149) Reverse engineering strategy cannot be set to custom class if generation target is Hibernate 5.x
by Koen Aers (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23149?page=com.atlassian.jira.plugi... ]
Koen Aers resolved JBIDE-23149.
-------------------------------
Resolution: Done
> Reverse engineering strategy cannot be set to custom class if generation target is Hibernate 5.x
> ------------------------------------------------------------------------------------------------
>
> Key: JBIDE-23149
> URL: https://issues.jboss.org/browse/JBIDE-23149
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: hibernate
> Affects Versions: 4.4.0.Final
> Reporter: Antal Varga
> Assignee: Koen Aers
> Fix For: 4.4.3.AM1
>
> Attachments: BaseReverseEngineeringStrategy.java, RMAReverseEngineeringStrategy.java
>
>
> The reason for that is the change in ServiceImpl.java in org.jboss.tools.hibernate.runtime.v_5_0*.jar or later.
> private Object newReverseEngineeringStrategy(String className, Object delegate) {...}
> tries to load class using the class loader of the delegate object at first which is *org.hibernate.cfg.reveng.OverrideRepository* and resides in *hibernate-tools-x.yy.jar*.
> The main problem is that while in case of the earlier Hibernate generation targets (e.g. 4.3) the reverse engineering strategy class loading was done by *org.hibernate.util.xpl.ReflectHelper* (and worked well), this option
> happens only as a fallback case now *BUT this only happens if the constructor has not been found* (only NoSuchMethodException is caught).
> Therefore a reverse engineering strategy can only be loaded if it is loaded by the classloader of the hibernate-tools-x.yy.jar or one of its parent loaders (OSGI can make the things more complicated).
> *I think the solution would be to catch ClassNotFoundException as well and try to load reverse engineering class using ReflectHelper in this case.*
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 7 months
[JBoss JIRA] (JBIDE-23149) Reverse engineering strategy cannot be set to custom class if generation target is Hibernate 5.x
by Koen Aers (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23149?page=com.atlassian.jira.plugi... ]
Koen Aers updated JBIDE-23149:
------------------------------
Fix Version/s: 4.4.3.AM1
(was: 4.5.0.AM1)
> Reverse engineering strategy cannot be set to custom class if generation target is Hibernate 5.x
> ------------------------------------------------------------------------------------------------
>
> Key: JBIDE-23149
> URL: https://issues.jboss.org/browse/JBIDE-23149
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: hibernate
> Affects Versions: 4.4.0.Final
> Reporter: Antal Varga
> Assignee: Koen Aers
> Fix For: 4.4.3.AM1
>
> Attachments: BaseReverseEngineeringStrategy.java, RMAReverseEngineeringStrategy.java
>
>
> The reason for that is the change in ServiceImpl.java in org.jboss.tools.hibernate.runtime.v_5_0*.jar or later.
> private Object newReverseEngineeringStrategy(String className, Object delegate) {...}
> tries to load class using the class loader of the delegate object at first which is *org.hibernate.cfg.reveng.OverrideRepository* and resides in *hibernate-tools-x.yy.jar*.
> The main problem is that while in case of the earlier Hibernate generation targets (e.g. 4.3) the reverse engineering strategy class loading was done by *org.hibernate.util.xpl.ReflectHelper* (and worked well), this option
> happens only as a fallback case now *BUT this only happens if the constructor has not been found* (only NoSuchMethodException is caught).
> Therefore a reverse engineering strategy can only be loaded if it is loaded by the classloader of the hibernate-tools-x.yy.jar or one of its parent loaders (OSGI can make the things more complicated).
> *I think the solution would be to catch ClassNotFoundException as well and try to load reverse engineering class using ReflectHelper in this case.*
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 7 months
[JBoss JIRA] (JBDS-4062) Error about space in User's Profile location (home) folder should be reported on confirmation page
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-4062?page=com.atlassian.jira.plugin.... ]
Denis Golovin commented on JBDS-4062:
-------------------------------------
I have no power there, but I did what I could and gave +1 to your PR.
> Error about space in User's Profile location (home) folder should be reported on confirmation page
> --------------------------------------------------------------------------------------------------
>
> Key: JBDS-4062
> URL: https://issues.jboss.org/browse/JBDS-4062
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: platform-installer
> Reporter: Denis Golovin
> Assignee: Denis Golovin
> Labels: ui
> Fix For: 10.3.0.AM1
>
>
> Considering every component from currently provided stack is optional for installation there is no reason to block installation process on Target Install Folder selection page in case user has space in his profile folder name (home folder). It should be reported on Confirmation page when vagrant is selected for install. It should not block installation for OpenJDK and DevStudio only.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 7 months
[JBoss JIRA] (JBDS-4062) Error about space in User's Profile location (home) folder should be reported on confirmation page
by Aurélien Pupier (JIRA)
[ https://issues.jboss.org/browse/JBDS-4062?page=com.atlassian.jira.plugin.... ]
Aurélien Pupier commented on JBDS-4062:
---------------------------------------
for information, I created a PR whcih should remove this limitation in Vagrant: https://github.com/mitchellh/vagrant/pull/7967 if you have more power than me to have it reviewed/tested/merged it might be simpler than to have a check in the devsuite installer
> Error about space in User's Profile location (home) folder should be reported on confirmation page
> --------------------------------------------------------------------------------------------------
>
> Key: JBDS-4062
> URL: https://issues.jboss.org/browse/JBDS-4062
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: platform-installer
> Reporter: Denis Golovin
> Assignee: Denis Golovin
> Labels: ui
> Fix For: 10.3.0.AM1
>
>
> Considering every component from currently provided stack is optional for installation there is no reason to block installation process on Target Install Folder selection page in case user has space in his profile folder name (home folder). It should be reported on Confirmation page when vagrant is selected for install. It should not block installation for OpenJDK and DevStudio only.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 7 months
[JBoss JIRA] (JBDS-4081) Installation fails with "Error: Command failed: vagrant box remove cdkv2 -f" when a previous installation went bad
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-4081?page=com.atlassian.jira.plugin.... ]
Denis Golovin commented on JBDS-4081:
-------------------------------------
[~aurelien.pupier] sorry for ignoring this, I probably didn't notice it because to many similar problems related to vagrant in jira.
I believe it is worth to mention this in release notes as known issue, I am not sure it would be possible to detect this exact error and provide guidance.
I'll add this to the list ow known issues to include into Release Notes.
> Installation fails with "Error: Command failed: vagrant box remove cdkv2 -f" when a previous installation went bad
> ------------------------------------------------------------------------------------------------------------------
>
> Key: JBDS-4081
> URL: https://issues.jboss.org/browse/JBDS-4081
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: platform-installer
> Affects Versions: 1.1.0.GA
> Reporter: Aurélien Pupier
> Assignee: Denis Golovin
> Fix For: 10.3.0.AM2
>
>
> {noformat}
> Tue, 04 Oct 2016 13:08:46 GMT-INFO: cdk - Execute command vagrant box remove cdkv2 -f
> Tue, 04 Oct 2016 13:08:46 GMT-INFO: cdk - Execute options {
> "env": {
> "ALLUSERSPROFILE": "C:\\ProgramData",
> "APPDATA": "C:\\Users\\Aurelien Pupier\\AppData\\Roaming",
> "CommonProgramFiles": "C:\\Program Files\\Common Files",
> "CommonProgramFiles(x86)": "C:\\Program Files (x86)\\Common Files",
> "CommonProgramW6432": "C:\\Program Files\\Common Files",
> "COMPUTERNAME": "DESKTOP-9NT300B",
> "ComSpec": "C:\\WINDOWS\\system32\\cmd.exe",
> "DOCKER_CERT_PATH": "C:\\certificate",
> "DOCKER_HOST": "tcp://10.1.2.2:2376",
> "DOCKER_MACHINE_NAME": "498b304",
> "DOCKER_TLS_VERIFY": "1",
> "DOCKER_TOOLBOX_INSTALL_PATH": "C:\\Program Files\\Docker Toolbox",
> "GIT_HOME": "C:\\Program Files\\Git",
> "GOOGLE_API_KEY": "AIzaSyAQfxPJiounkhOjODEO5ZieffeBv6yft2Q",
> "HOMEDRIVE": "C:",
> "HOMEPATH": "\\Users\\Aurelien Pupier",
> "JAVA_HOME": "C:\\Program Files\\Java\\jdk1.8.0_65",
> "LOCALAPPDATA": "C:\\Users\\Aurelien Pupier\\AppData\\Local",
> "LOGONSERVER": "\\\\DESKTOP-9NT300B",
> "MAVEN_HOME": "C:\\install\\apache-maven-3.3.9-bin\\apache-maven-3.3.9",
> "NUMBER_OF_PROCESSORS": "8",
> "OS": "Windows_NT",
> "Path": "C:\\ProgramData\\Oracle\\Java\\javapath;C:\\WINDOWS\\system32;C:\\WINDOWS;C:\\WINDOWS\\System32\\Wbem;C:\\WINDOWS\\System32\\WindowsPowerShell\\v1.0\\;C:\\Program Files (x86)\\Skype\\Phone\\;C:\\Program Files (x86)\\PuTTY\\;C:\\Program Files\\RedHat\\java-1.8.0-openjdk-1.8.0.102-1\\bin;C:\\HashiCorp\\Vagrant\\bin;c:\\install\\DevelopmentSuite\\cdk\\bin;c:\\install\\DevelopmentSuite\\cygwin\\bin;C:\\OpenShift;C:\\Program Files\\Docker Toolbox;C:\\install\\apache-maven-3.3.9-bin\\apache-maven-3.3.9\\bin;C:\\Program Files\\Git\\bin;C:\\Users\\Aurelien Pupier\\AppData\\Local\\Microsoft\\WindowsApps;C:\\HashiCorp\\Vagrant\\bin;bin;C:\\Program Files\\Oracle\\VirtualBox\\",
> "PATHEXT": ".COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC",
> "PROCESSOR_ARCHITECTURE": "AMD64",
> "PROCESSOR_IDENTIFIER": "Intel64 Family 6 Model 60 Stepping 3, GenuineIntel",
> "PROCESSOR_LEVEL": "6",
> "PROCESSOR_REVISION": "3c03",
> "ProgramData": "C:\\ProgramData",
> "ProgramFiles": "C:\\Program Files",
> "ProgramFiles(x86)": "C:\\Program Files (x86)",
> "ProgramW6432": "C:\\Program Files",
> "PSModulePath": "C:\\Program Files\\WindowsPowerShell\\Modules;C:\\WINDOWS\\system32\\WindowsPowerShell\\v1.0\\Modules",
> "PUBLIC": "C:\\Users\\Public",
> "SystemDrive": "C:",
> "SystemRoot": "C:\\WINDOWS",
> "TEMP": "C:\\Users\\AURELI~1\\AppData\\Local\\Temp",
> "TMP": "C:\\Users\\AURELI~1\\AppData\\Local\\Temp",
> "USERDOMAIN": "DESKTOP-9NT300B",
> "USERDOMAIN_ROAMINGPROFILE": "DESKTOP-9NT300B",
> "USERNAME": "Aurelien Pupier",
> "USERPROFILE": "C:\\Users\\Aurelien Pupier",
> "VAGRANT_DETECTED_OS": "cygwin",
> "VAGRANT_HOME": "C:\\install\\.vagrant_home",
> "VBOX_MSI_INSTALL_PATH": "C:\\Program Files\\Oracle\\VirtualBox\\",
> "windir": "C:\\WINDOWS",
> "__COMPAT_LAYER": "Installer"
> },
> "cwd": "c:\\install\\DevelopmentSuite-1.1.0\\cdk\\boxes"
> }
> Tue, 04 Oct 2016 13:08:48 GMT-ERROR: cdk - Error: Command failed: vagrant box remove cdkv2 -f
> [0;31mThe VirtualBox VM was created with a user that doesn't match the
> current user running Vagrant. VirtualBox requires that the same user
> be used to manage the VM that was created. Please re-run Vagrant with
> that user. This is not a Vagrant issue.
> The UID used to create the VM was: 0
> Your UID is: 1001
> {noformat}
> I tried to call the same command from cmd line and I have the same error.
> I tried to call the same command from cmd line as administrator and I have the same error.
> I found this on StackOverflow:http://stackoverflow.com/questions/31644222/vagrant-not-sta... but I have no .vagrant\machines\default\virtualbox\creator_uid files neither .vagrant folder, I have only .vagrant.d folder
> I'm on Windows 10
> I suppose that the previous version of the box was installed while I followed the steps to install CDK before the installer exists.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 7 months
[JBoss JIRA] (JBDS-4081) Installation fails with "Error: Command failed: vagrant box remove cdkv2 -f" when a previous installation went bad
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-4081?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-4081:
--------------------------------
Fix Version/s: 10.3.0.AM2
> Installation fails with "Error: Command failed: vagrant box remove cdkv2 -f" when a previous installation went bad
> ------------------------------------------------------------------------------------------------------------------
>
> Key: JBDS-4081
> URL: https://issues.jboss.org/browse/JBDS-4081
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: platform-installer
> Affects Versions: 1.1.0.GA
> Reporter: Aurélien Pupier
> Assignee: Denis Golovin
> Fix For: 10.3.0.AM2
>
>
> {noformat}
> Tue, 04 Oct 2016 13:08:46 GMT-INFO: cdk - Execute command vagrant box remove cdkv2 -f
> Tue, 04 Oct 2016 13:08:46 GMT-INFO: cdk - Execute options {
> "env": {
> "ALLUSERSPROFILE": "C:\\ProgramData",
> "APPDATA": "C:\\Users\\Aurelien Pupier\\AppData\\Roaming",
> "CommonProgramFiles": "C:\\Program Files\\Common Files",
> "CommonProgramFiles(x86)": "C:\\Program Files (x86)\\Common Files",
> "CommonProgramW6432": "C:\\Program Files\\Common Files",
> "COMPUTERNAME": "DESKTOP-9NT300B",
> "ComSpec": "C:\\WINDOWS\\system32\\cmd.exe",
> "DOCKER_CERT_PATH": "C:\\certificate",
> "DOCKER_HOST": "tcp://10.1.2.2:2376",
> "DOCKER_MACHINE_NAME": "498b304",
> "DOCKER_TLS_VERIFY": "1",
> "DOCKER_TOOLBOX_INSTALL_PATH": "C:\\Program Files\\Docker Toolbox",
> "GIT_HOME": "C:\\Program Files\\Git",
> "GOOGLE_API_KEY": "AIzaSyAQfxPJiounkhOjODEO5ZieffeBv6yft2Q",
> "HOMEDRIVE": "C:",
> "HOMEPATH": "\\Users\\Aurelien Pupier",
> "JAVA_HOME": "C:\\Program Files\\Java\\jdk1.8.0_65",
> "LOCALAPPDATA": "C:\\Users\\Aurelien Pupier\\AppData\\Local",
> "LOGONSERVER": "\\\\DESKTOP-9NT300B",
> "MAVEN_HOME": "C:\\install\\apache-maven-3.3.9-bin\\apache-maven-3.3.9",
> "NUMBER_OF_PROCESSORS": "8",
> "OS": "Windows_NT",
> "Path": "C:\\ProgramData\\Oracle\\Java\\javapath;C:\\WINDOWS\\system32;C:\\WINDOWS;C:\\WINDOWS\\System32\\Wbem;C:\\WINDOWS\\System32\\WindowsPowerShell\\v1.0\\;C:\\Program Files (x86)\\Skype\\Phone\\;C:\\Program Files (x86)\\PuTTY\\;C:\\Program Files\\RedHat\\java-1.8.0-openjdk-1.8.0.102-1\\bin;C:\\HashiCorp\\Vagrant\\bin;c:\\install\\DevelopmentSuite\\cdk\\bin;c:\\install\\DevelopmentSuite\\cygwin\\bin;C:\\OpenShift;C:\\Program Files\\Docker Toolbox;C:\\install\\apache-maven-3.3.9-bin\\apache-maven-3.3.9\\bin;C:\\Program Files\\Git\\bin;C:\\Users\\Aurelien Pupier\\AppData\\Local\\Microsoft\\WindowsApps;C:\\HashiCorp\\Vagrant\\bin;bin;C:\\Program Files\\Oracle\\VirtualBox\\",
> "PATHEXT": ".COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC",
> "PROCESSOR_ARCHITECTURE": "AMD64",
> "PROCESSOR_IDENTIFIER": "Intel64 Family 6 Model 60 Stepping 3, GenuineIntel",
> "PROCESSOR_LEVEL": "6",
> "PROCESSOR_REVISION": "3c03",
> "ProgramData": "C:\\ProgramData",
> "ProgramFiles": "C:\\Program Files",
> "ProgramFiles(x86)": "C:\\Program Files (x86)",
> "ProgramW6432": "C:\\Program Files",
> "PSModulePath": "C:\\Program Files\\WindowsPowerShell\\Modules;C:\\WINDOWS\\system32\\WindowsPowerShell\\v1.0\\Modules",
> "PUBLIC": "C:\\Users\\Public",
> "SystemDrive": "C:",
> "SystemRoot": "C:\\WINDOWS",
> "TEMP": "C:\\Users\\AURELI~1\\AppData\\Local\\Temp",
> "TMP": "C:\\Users\\AURELI~1\\AppData\\Local\\Temp",
> "USERDOMAIN": "DESKTOP-9NT300B",
> "USERDOMAIN_ROAMINGPROFILE": "DESKTOP-9NT300B",
> "USERNAME": "Aurelien Pupier",
> "USERPROFILE": "C:\\Users\\Aurelien Pupier",
> "VAGRANT_DETECTED_OS": "cygwin",
> "VAGRANT_HOME": "C:\\install\\.vagrant_home",
> "VBOX_MSI_INSTALL_PATH": "C:\\Program Files\\Oracle\\VirtualBox\\",
> "windir": "C:\\WINDOWS",
> "__COMPAT_LAYER": "Installer"
> },
> "cwd": "c:\\install\\DevelopmentSuite-1.1.0\\cdk\\boxes"
> }
> Tue, 04 Oct 2016 13:08:48 GMT-ERROR: cdk - Error: Command failed: vagrant box remove cdkv2 -f
> [0;31mThe VirtualBox VM was created with a user that doesn't match the
> current user running Vagrant. VirtualBox requires that the same user
> be used to manage the VM that was created. Please re-run Vagrant with
> that user. This is not a Vagrant issue.
> The UID used to create the VM was: 0
> Your UID is: 1001
> {noformat}
> I tried to call the same command from cmd line and I have the same error.
> I tried to call the same command from cmd line as administrator and I have the same error.
> I found this on StackOverflow:http://stackoverflow.com/questions/31644222/vagrant-not-sta... but I have no .vagrant\machines\default\virtualbox\creator_uid files neither .vagrant folder, I have only .vagrant.d folder
> I'm on Windows 10
> I suppose that the previous version of the box was installed while I followed the steps to install CDK before the installer exists.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 7 months