[JBoss JIRA] (JBIDE-25152) Make the old Hibernate runtime plugins optional
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25152?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-25152:
-------------------------------
Fix Version/s: 4.5.x
(was: 4.5.1.Final)
> Make the old Hibernate runtime plugins optional
> -----------------------------------------------
>
> Key: JBIDE-25152
> URL: https://issues.jboss.org/browse/JBIDE-25152
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: hibernate
> Affects Versions: 4.5.1.AM2
> Reporter: Koen Aers
> Fix For: 4.5.x
>
>
> There are a fair number of Hibernate runtime plugins available for the current JBoss Tools. They are named ‘org.jboss.tools.hibernate.runtime.v_x_y’ and use the actual core Hibernate (and Hibernate tools) classes to implement the SPI defined in ‘org.jboss.tools.hibernate.runtime.spi’. But the number of these implementations keeps growing and so it is needed to get this under control. The aimed solution is to only provide the most recent implementation and make the other ones installable on request.
> To solve this issue all the places where the actual Hibernate version is hardcoded need to be identified and only the latest version can be used. This is especially true for the tests in 'org.hibernate.eclipse.console.test' which use version 3.5.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 5 months
[JBoss JIRA] (JBIDE-25152) Make the old Hibernate runtime plugins optional
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25152?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-25152:
------------------------------------
[checkUnresolvedIssues.py] Slip to fixversion = *4.5.x*
> Make the old Hibernate runtime plugins optional
> -----------------------------------------------
>
> Key: JBIDE-25152
> URL: https://issues.jboss.org/browse/JBIDE-25152
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: hibernate
> Affects Versions: 4.5.1.AM2
> Reporter: Koen Aers
> Fix For: 4.5.x
>
>
> There are a fair number of Hibernate runtime plugins available for the current JBoss Tools. They are named ‘org.jboss.tools.hibernate.runtime.v_x_y’ and use the actual core Hibernate (and Hibernate tools) classes to implement the SPI defined in ‘org.jboss.tools.hibernate.runtime.spi’. But the number of these implementations keeps growing and so it is needed to get this under control. The aimed solution is to only provide the most recent implementation and make the other ones installable on request.
> To solve this issue all the places where the actual Hibernate version is hardcoded need to be identified and only the latest version can be used. This is especially true for the tests in 'org.hibernate.eclipse.console.test' which use version 3.5.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 5 months
[JBoss JIRA] (JBIDE-25050) Prepare windows image with hyperv
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25050?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-25050:
-------------------------------
Fix Version/s: 4.5.x
(was: 4.5.1.Final)
> Prepare windows image with hyperv
> ---------------------------------
>
> Key: JBIDE-25050
> URL: https://issues.jboss.org/browse/JBIDE-25050
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: integration-tests, qa
> Affects Versions: 4.5.1.AM2
> Reporter: Ondrej Dockal
> Assignee: Ondrej Dockal
> Labels: jenkins
> Fix For: 4.5.x
>
> Attachments: error.log
>
>
> Prepare windows-based images with hyperv allowed and capable of running cdk in Central-ci and add new jenkins label.
> * Provision win10-x64-jbds (as some changes were made to jbds script)
> * Install manually HyperV in fresh windows image
> * Add new virtual switch
> * Set env. variable HYPERV_VIRTUAL_SWITCH
> * Add user into Hyper-V Administrators group
> * Test whether cdk can be run on the slave
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 5 months
[JBoss JIRA] (JBIDE-25050) Prepare windows image with hyperv
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25050?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-25050:
------------------------------------
[checkUnresolvedIssues.py] Slip to fixversion = *4.5.x*
> Prepare windows image with hyperv
> ---------------------------------
>
> Key: JBIDE-25050
> URL: https://issues.jboss.org/browse/JBIDE-25050
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: integration-tests, qa
> Affects Versions: 4.5.1.AM2
> Reporter: Ondrej Dockal
> Assignee: Ondrej Dockal
> Labels: jenkins
> Fix For: 4.5.x
>
> Attachments: error.log
>
>
> Prepare windows-based images with hyperv allowed and capable of running cdk in Central-ci and add new jenkins label.
> * Provision win10-x64-jbds (as some changes were made to jbds script)
> * Install manually HyperV in fresh windows image
> * Add new virtual switch
> * Set env. variable HYPERV_VIRTUAL_SWITCH
> * Add user into Hyper-V Administrators group
> * Test whether cdk can be run on the slave
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 5 months
[JBoss JIRA] (JBIDE-25314) CDK integration tests for propagation of values to launch configuration
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25314?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-25314:
------------------------------------
[checkUnresolvedIssues.py] Slip to fixversion = *4.5.2.AM1* and sprint = *devex #140 November 2017*
> CDK integration tests for propagation of values to launch configuration
> -----------------------------------------------------------------------
>
> Key: JBIDE-25314
> URL: https://issues.jboss.org/browse/JBIDE-25314
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: integration-tests
> Affects Versions: 4.5.1.Final
> Reporter: Ondrej Dockal
> Assignee: Ondrej Dockal
> Priority: Critical
> Labels: cdk
> Fix For: 4.5.2.AM1
>
>
> Check propagation of values of CDK server configuration into these launch config's part: Main Tab: Name, Location of minishift binary, Arguments (hypervisor and profile name), Environment Tab: Environment variables check (minishift home, minishift username and path). Also, this check can be done after CDK server adapter is created via wizard, and when CDK server editor is changed.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 5 months