[JBoss JIRA] (JBIDE-24447) Look for minishift configuration in MINISHIFT_HOME
by Ondrej Dockal (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24447?page=com.atlassian.jira.plugi... ]
Ondrej Dockal commented on JBIDE-24447:
---------------------------------------
[~rob.stryker] [~mmalina] Yeah, I will take a look today and report back.
> Look for minishift configuration in MINISHIFT_HOME
> --------------------------------------------------
>
> Key: JBIDE-24447
> URL: https://issues.jboss.org/browse/JBIDE-24447
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: runtime-detection
> Affects Versions: 4.4.4.Final
> Reporter: Jan Richter
> Assignee: Rob Stryker
> Fix For: 4.5.x
>
> Attachments: cdk2_x_RD.png, cdk3_minishift_home.png
>
>
> One can use the MINISHIFT_HOME variable to save minishift configuration somewhere else than in ~/.minishift
> It would be nice if runtime detection looked there if the variable is configured.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (JBIDE-24447) Look for minishift configuration in MINISHIFT_HOME
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24447?page=com.atlassian.jira.plugi... ]
Martin Malina commented on JBIDE-24447:
---------------------------------------
And with JBIDE-24796 fixed and verified, I would think that this JIRA can be closed since it works as expected as far as I know.
[~odockal], can you confirm?
> Look for minishift configuration in MINISHIFT_HOME
> --------------------------------------------------
>
> Key: JBIDE-24447
> URL: https://issues.jboss.org/browse/JBIDE-24447
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: runtime-detection
> Affects Versions: 4.4.4.Final
> Reporter: Jan Richter
> Assignee: Rob Stryker
> Fix For: 4.5.x
>
> Attachments: cdk2_x_RD.png, cdk3_minishift_home.png
>
>
> One can use the MINISHIFT_HOME variable to save minishift configuration somewhere else than in ~/.minishift
> It would be nice if runtime detection looked there if the variable is configured.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (JBIDE-24447) Look for minishift configuration in MINISHIFT_HOME
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24447?page=com.atlassian.jira.plugi... ]
Martin Malina commented on JBIDE-24447:
---------------------------------------
{quote}
CDK 2 is automatically detected by checking the running eclipse's configuration location and going to the relative path Platform.getOS().equals(Platform.OS_MACOSX) ? "../../../" : "") + "../../../cdk/"; This is typically where the installer would install the older runtimes. It then scans that folder for stuff.
This sounds like it's working as expected?
{quote}
My understanding was that Ondrej didn't have cdk 2 set up at all so how come Eclipse used that location? But that would really be strange. It looks more likely that in fact cdk 2 path was set up somewhere. Ondrej will need to check again.
{quote}
This sounds like a legitimate bug.
{quote}
I created a JIRA for the inconsistent cdk 3 server adapter name: JBIDE-24875
> Look for minishift configuration in MINISHIFT_HOME
> --------------------------------------------------
>
> Key: JBIDE-24447
> URL: https://issues.jboss.org/browse/JBIDE-24447
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: runtime-detection
> Affects Versions: 4.4.4.Final
> Reporter: Jan Richter
> Assignee: Rob Stryker
> Fix For: 4.5.x
>
> Attachments: cdk2_x_RD.png, cdk3_minishift_home.png
>
>
> One can use the MINISHIFT_HOME variable to save minishift configuration somewhere else than in ~/.minishift
> It would be nice if runtime detection looked there if the variable is configured.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (JBIDE-24875) Name of cdk 3 adapter is different depending on using detection or adding manually
by Martin Malina (JIRA)
Martin Malina created JBIDE-24875:
-------------------------------------
Summary: Name of cdk 3 adapter is different depending on using detection or adding manually
Key: JBIDE-24875
URL: https://issues.jboss.org/browse/JBIDE-24875
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: cdk
Affects Versions: 4.5.0.Final
Reporter: Martin Malina
This is a followup of JBIDE-24447.
When cdk 3 is auto detected (typically when you start devstudio and ~/.minishift exists), the adapter will be created automatically with the name "Container Development Environment 3". On the other hand, if you choose to create the cdk 3 server adapter manually, the default name is "Container Development Environment". These should be consistent.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (JBIDE-24794) Hibernate Reverse Engineering doesn't work on 4.5.0.AM2
by Dmitrii Bocharov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24794?page=com.atlassian.jira.plugi... ]
Dmitrii Bocharov updated JBIDE-24794:
-------------------------------------
Workaround Description: Check the default schema that you set in hibernate.cfg.xml file. Should it be uppercase or lowercase? Check everything carefully there
Workaround: Workaround Exists
> Hibernate Reverse Engineering doesn't work on 4.5.0.AM2
> -------------------------------------------------------
>
> Key: JBIDE-24794
> URL: https://issues.jboss.org/browse/JBIDE-24794
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: hibernate
> Reporter: Dmitrii Bocharov
> Fix For: 4.5.x
>
> Attachments: 4.4.4.Final-works.webm, 4.5.0.AM2-doesnt-work.webm
>
>
> Reverse Engineering doesn't work at the moment, but it worked in 4.4.4.Final. See the attahced screencasts for details.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months