[JBoss JIRA] (JBIDE-24133) org.jboss.tools.central.reddeer 2.1.3.v20170130-1737 requires 'bundle org.jboss.tools.runtime.reddeer [3.2.3, 3.3.0)' but it could not be found
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24133?page=com.atlassian.jira.plugi... ]
Jeff MAURY commented on JBIDE-24133:
------------------------------------
[~mmalina] merged
> org.jboss.tools.central.reddeer 2.1.3.v20170130-1737 requires 'bundle org.jboss.tools.runtime.reddeer [3.2.3,3.3.0)' but it could not be found
> ----------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-24133
> URL: https://issues.jboss.org/browse/JBIDE-24133
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Affects Versions: 4.4.4.AM2
> Reporter: Nick Boldt
> Assignee: Jeff MAURY
> Priority: Blocker
> Fix For: 4.4.4.AM2
>
>
> Problem running the composite install job [1] - can't find org.jboss.tools.runtime.reddeer [3.2.3,3.3.0).
> {code}
> [p2.dir] Installation failed.
> [p2.dir] !SESSION 2017-03-24 21:14:43.235 -----------------------------------------------
> [p2.dir] eclipse.buildId=4.7.0.I20170126-1030
> --
> [p2.dir] !MESSAGE Cannot complete the install because one or more required items could not be found.
> [p2.dir] !SUBENTRY 1 org.eclipse.equinox.p2.director 4 0 2017-03-24 21:15:23.659
> [p2.dir] !MESSAGE Software being installed: JBoss Tools - Tests - JBoss Central Developer Resources 2.1.3.v20170130-1737 (org.jboss.tools.central.test.feature.source.feature.group 2.1.3.v20170130-1737)
> [p2.dir] !SUBENTRY 1 org.eclipse.equinox.p2.director 4 0 2017-03-24 21:15:23.659
> [p2.dir] !MESSAGE Missing requirement: Central Reddeer 2.1.3.v20170130-1737 (org.jboss.tools.central.reddeer 2.1.3.v20170130-1737) requires 'bundle org.jboss.tools.runtime.reddeer [3.2.3,3.3.0)' but it could not be found
> [p2.dir] !SUBENTRY 1 org.eclipse.equinox.p2.director 4 1 2017-03-24 21:15:23.659
> [p2.dir] !MESSAGE Cannot satisfy dependency:
> [p2.dir] !SUBENTRY 2 org.eclipse.equinox.p2.director 4 0 2017-03-24 21:15:23.659
> [p2.dir] !MESSAGE From: JBoss Tools - Tests - JBoss Central 2.1.3.v20170130-1737 (org.jboss.tools.central.test.feature.feature.group 2.1.3.v20170130-1737)
> --
> [p2.dir] !MESSAGE Cannot satisfy dependency:
> [p2.dir] !SUBENTRY 2 org.eclipse.equinox.p2.director 4 0 2017-03-24 21:15:23.659
> [p2.dir] !MESSAGE From: JBoss Tools - Tests - JBoss Central Developer Resources 2.1.3.v20170130-1737 (org.jboss.tools.central.test.feature.source.feature.group 2.1.3.v20170130-1737)
> --
> [p2.dir] Cannot complete the install because one or more required items could not be found.
> [p2.dir] Software being installed: JBoss Tools - Tests - JBoss Central Developer Resources 2.1.3.v20170130-1737 (org.jboss.tools.central.test.feature.source.feature.group 2.1.3.v20170130-1737)
> [p2.dir] Missing requirement: Central Reddeer 2.1.3.v20170130-1737 (org.jboss.tools.central.reddeer 2.1.3.v20170130-1737) requires 'bundle org.jboss.tools.runtime.reddeer [3.2.3,3.3.0)' but it could not be found
> [p2.dir] Cannot satisfy dependency:
> [p2.dir] From: JBoss Tools - Tests - JBoss Central 2.1.3.v20170130-1737 (org.jboss.tools.central.test.feature.feature.group 2.1.3.v20170130-1737)
> [p2.dir] To: org.jboss.tools.central.reddeer [2.1.3.v20170130-1737]
> [p2.dir] Cannot satisfy dependency:
> [p2.dir] From: JBoss Tools - Tests - JBoss Central Developer Resources 2.1.3.v20170130-1737 (org.jboss.tools.central.test.feature.source.feature.group 2.1.3.v20170130-1737)
> [p2.dir] To: org.jboss.tools.central.test.feature.feature.group [2.1.3.v20170130-1737]
> [p2.dir] Application failed, log file location: /mnt/hudson_workspace/workspace/jbosstools-composite-install_master/eclipse/configuration/1490390083328.log
> !SESSION 2017-03-24 21:14:40.982 -----------------------------------------------{code}
> -- [1] https://jenkins.hosts.mwqe.eng.bos.redhat.com/hudson/job/jbosstools-compo...
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (JBIDE-23905) Wrong layout in cdk3 server editor
by Ondrej Dockal (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23905?page=com.atlassian.jira.plugi... ]
Ondrej Dockal edited comment on JBIDE-23905 at 3/28/17 4:36 AM:
----------------------------------------------------------------
I checked the 10.4.0.AM2-v20170328-0337-B324 build on windows and the layout is just fine! Thanks!
was (Author: odockal):
I checked the 10.4.0.AM2-v20170328-0337-B324 build on windows and it is the layout just fine! Thanks!
> Wrong layout in cdk3 server editor
> ----------------------------------
>
> Key: JBIDE-23905
> URL: https://issues.jboss.org/browse/JBIDE-23905
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk
> Affects Versions: 4.4.3.Final
> Reporter: Jeff MAURY
> Assignee: Rob Stryker
> Labels: cdk, server_adapter, server_adapter_editor
> Fix For: 4.4.4.AM2, 4.5.0.AM1
>
> Attachments: screenshot-1.png, screenshot-2.png
>
>
> The cdk v3 server editor shows a wrong layout (at least on Windows)
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (JBIDE-23905) Wrong layout in cdk3 server editor
by Ondrej Dockal (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23905?page=com.atlassian.jira.plugi... ]
Ondrej Dockal commented on JBIDE-23905:
---------------------------------------
I checked the 10.4.0.AM2-v20170328-0337-B324 build on windows and it is the layout just fine! Thanks!
> Wrong layout in cdk3 server editor
> ----------------------------------
>
> Key: JBIDE-23905
> URL: https://issues.jboss.org/browse/JBIDE-23905
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk
> Affects Versions: 4.4.3.Final
> Reporter: Jeff MAURY
> Assignee: Rob Stryker
> Labels: cdk, server_adapter, server_adapter_editor
> Fix For: 4.4.4.AM2, 4.5.0.AM1
>
> Attachments: screenshot-1.png, screenshot-2.png
>
>
> The cdk v3 server editor shows a wrong layout (at least on Windows)
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (JBIDE-23825) Improve eap compatibility test execution
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23825?page=com.atlassian.jira.plugi... ]
Martin Malina closed JBIDE-23825.
---------------------------------
Closing.
> Improve eap compatibility test execution
> ----------------------------------------
>
> Key: JBIDE-23825
> URL: https://issues.jboss.org/browse/JBIDE-23825
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: integration-tests, server
> Affects Versions: 4.4.3.AM2
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.4.4.AM1
>
>
> This is a followup of JBIDE-23756 - with that, we are once again able to execute compatibility tests for eap. But there are a few things missing:
> For now I will make it work with what we have, but there are several things that need to be fixed:
> 1. Even if you only run the eap7x-compatibility profile, all of the runtimes (jboss as 4, as 5, as 7, wildfly...) will be downloaded anyway, because this is set up in as/itests/pom.xml - we need to come up with a way to only do this if the compatibility profile is not active. Maybe we need to switch to profile activation by property, e.g. eap7x-compatibility - the profile in as/itests/org.jboss.tools.as.ui.bot.itests/pom.xml would be activated by this, whereas all the other runtime downloads in as/itests/pom.xml would be in a profile that is deactivated using this property.
> 2. https://github.com/jbosstools/jbosstools-server/blob/master/as/itests/org...
> The eap7x-compatibility profile has jboss-eap-7.0 server directory hardcoded. You can still override the whole property with something else for eap 7.1, but it would be nice to improve this.
> For reference, this is a job where Radim demonstrated the new way to execute tests:
> https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/All/job...
> And these are the two jobs EAP QE uses for the compatibilty testing:
> https://eap-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/eap-70x-jbds-c...
> https://eap-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/EAP7/view/EAP...
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (JBIDE-24048) Import application: would like to get a workspace project that's using the context-dir and branch used in OpenShift
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24048?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-24048:
-------------------------------------
Fix Version/s: 4.5.0.AM1
> Import application: would like to get a workspace project that's using the context-dir and branch used in OpenShift
> -------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-24048
> URL: https://issues.jboss.org/browse/JBIDE-24048
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.4.4.AM1
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Labels: import_wizard, openshift_v3
> Fix For: 4.4.4.AM2, 4.5.0.AM1
>
> Attachments: CONTEXT_DIR.png, SOURCE_REPOSITORY_REF.png, jboss-eap-quickstarts.png, jboss-kitchensink.png
>
>
> We're missing the ability to provide a context dir within a git repo when importing an application from OpenShift. The application wizard allows the user to set a context dir, which is used when importing right after the successfull creation. The (standalone) import is lacking this.
> steps to reproduce:
> # EXEC: launch openshift application wizard and pick "eap64-basic-s2i"
> # ASSERT: in the next page make sure there is "kitchensink" set to the CONTEXT_DIR template parameter
> !CONTEXT_DIR.png!
> # ASSERT: in the parameters, make sure that the SOURCE_REPOSITORY_REF is set to "6.4.x"
> !SOURCE_REPOSITORY_REF.png!
> # EXEC: finish the wizard and once the resources are created, simply confirm the import dialog that pops up
> # ASSERT: you get a "jboss-kitchensink" in your workspace. The import actually cloned the whole repo "jboss-eap-quickstarts" and imported the project within the "kitchensink" (the CONTEXT_DIR) folder as a workspace project
> !jboss-kitchensink.png!
> # EXEC: switch the branch in the git repo that already exists (ex. switch to master)
> # EXEC: in OpenShift Explorer: kill your workspace project, select the "eap-app" service and choose "Import Application" in the context-menu.
> # EXEC: in the upcoming import wizard, check "reuse existing repository" and then hit "Finish"
> Result:
> You get a project "jboss-eap-quickstart".
> !jboss-eap-quickstarts.png!
> There was no way to provide a context dir. To get the kitchensink project you need to remove the jboss-eap-quickstart" project, checkout the correct branch and reimport "kitchensink" (kitchensink only exists in the 6.4.x branch, not in the 7.x branches) manually as an existing maven project.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years