[JBoss JIRA] (JBIDE-13123) openshift-java-client: increase timeouts when running integration tests on CI
by Andre Dietisheim (JIRA)
Andre Dietisheim created JBIDE-13123:
----------------------------------------
Summary: openshift-java-client: increase timeouts when running integration tests on CI
Key: JBIDE-13123
URL: https://issues.jboss.org/browse/JBIDE-13123
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: openshift
Affects Versions: 4.0.0.CR1
Reporter: Andre Dietisheim
Assignee: Andre Dietisheim
Fix For: 4.1.x
The integration tests for the openshift-java-client, that are run on the jenkins instance, fail on a regular basis due to timeouts when communicating with the OpenShift platform. Having tests failing because of timeouts produces false positives and we should fix this.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months
[JBoss JIRA] (JBIDE-13042) fix bootstrap profiles so they use ../jbosstools-<component> convention instead of ../<component>
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-13042:
----------------------------------
Summary: fix bootstrap profiles so they use ../jbosstools-<component> convention instead of ../<component>
Key: JBIDE-13042
URL: https://issues.jboss.org/browse/JBIDE-13042
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng
Affects Versions: 4.0.0.Beta2
Reporter: Nick Boldt
Assignee: Max Rydahl Andersen
Fix For: 4.0.0.CR1
With the changes in JBIDE-12993, my assumed paths when checking out projects are no longer correct, and therefore the bootstrap profiles in the root poms are no longer working.
Since I don't have global write perms, this either requires that someone with God access fix them all across the board, or I submit 19 PRs.
Here's a sample of the changes needed, which will also need to be folded into JBIDE-12993 so that the recursion step (reading the root pom to decide if any child projects are needed) works w/ the new on-disk structure:
{code}
diff --git a/pom.xml b/pom.xml
index 45cfe11..c5b946b 100644
--- a/pom.xml
+++ b/pom.xml
@@ -23,7 +23,7 @@
<profile>
<id>bootstrap</id>
<modules>
- <module>../portlet</module>
+ <module>../jbosstools-portlet</module>
</modules>
</profile>
</profiles>
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months
[JBoss JIRA] (JBIDE-13110) Put CI jobs for target-platform into a dedicated view
by Mickael Istria (JIRA)
Mickael Istria created JBIDE-13110:
--------------------------------------
Summary: Put CI jobs for target-platform into a dedicated view
Key: JBIDE-13110
URL: https://issues.jboss.org/browse/JBIDE-13110
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: Build/Releng, target-platform
Reporter: Mickael Istria
Assignee: Nick Boldt
As we now agree that TP are not following JBT versionning and that they are built independently of JBT releases, it would make sense to replace jbosstools-*-target-platforms jobs by jobs whose name is not related to a JBT version or branch, and to put them into their own view.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months
[JBoss JIRA] (JBIDE-12061) Cannot install the ESB tools and ESB detector with Juno
by Len DiMaggio (JIRA)
Len DiMaggio created JBIDE-12061:
------------------------------------
Summary: Cannot install the ESB tools and ESB detector with Juno
Key: JBIDE-12061
URL: https://issues.jboss.org/browse/JBIDE-12061
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: SOA Tooling
Affects Versions: 3.3.0.CR1
Environment: http://www.qa.jboss.com/binaries/RHDS/updates/development/5.0.0.Beta2.soa...
http://download.jboss.org/jbosstools/updates/JBossTools-3.3.0.CR1.core/
Eclipse Juno:
Version: 4.2.0
Build id: I20120524-2100
Reporter: Len DiMaggio
Assignee: Nick Boldt
Priority: Critical
Fix For: 3.4.x
Cannot complete the install because of a conflicting dependency.
Software being installed: JBoss Runtime ESB Detector 1.3.0.v20120522-1702-H4-Beta2-SOA (org.jboss.tools.runtime.esb.detector.feature.feature.group 1.3.0.v20120522-1702-H4-Beta2-SOA)
Software currently installed: Eclipse SDK 4.2.0.I20120524-2100 (org.eclipse.sdk.ide 4.2.0.I20120524-2100)
Only one of the following can be installed at once:
Core Runtime 3.8.0.v20120521-2346 (org.eclipse.core.runtime 3.8.0.v20120521-2346)
Core Runtime 3.8.0.v20120511-1333 (org.eclipse.core.runtime 3.8.0.v20120511-1333)
Core Runtime 3.7.0.v20110110 (org.eclipse.core.runtime 3.7.0.v20110110)
Cannot satisfy dependency:
From: Eclipse e4 Rich Client Platform 1.1.0.v20120521-2329-8yFTIGF3GGduEYaFQA2M2RMm (org.eclipse.e4.rcp.feature.group 1.1.0.v20120521-2329-8yFTIGF3GGduEYaFQA2M2RMm)
To: org.eclipse.core.runtime [3.8.0.v20120521-2346]
Cannot satisfy dependency:
From: Eclipse Platform 4.2.0.v20120508-1726-9JF7AHV8FyMteja0CggfF3FfqHnxgnrWaBmfoD (org.eclipse.platform.feature.group 4.2.0.v20120508-1726-9JF7AHV8FyMteja0CggfF3FfqHnxgnrWaBmfoD)
To: org.eclipse.rcp.feature.group [4.2.0.v20120403-2031-7IAPA7BrHQicRoOdPwOavbGRB3N3]
Cannot satisfy dependency:
From: Eclipse RCP 4.2.0.v20120403-2031-7IAPA7BrHQicRoOdPwOavbGRB3N3 (org.eclipse.rcp.feature.group 4.2.0.v20120403-2031-7IAPA7BrHQicRoOdPwOavbGRB3N3)
To: org.eclipse.e4.rcp.feature.group [1.1.0.v20120521-2329-8yFTIGF3GGduEYaFQA2M2RMm]
Cannot satisfy dependency:
From: Eclipse Project SDK 4.2.0.v20120522-2109-7T7mDFDPz-3FdpcTdH3vf9z-X_aZ4Bz-tcBJLHHhcWJnb (org.eclipse.sdk.feature.group 4.2.0.v20120522-2109-7T7mDFDPz-3FdpcTdH3vf9z-X_aZ4Bz-tcBJLHHhcWJnb)
To: org.eclipse.platform.feature.group [4.2.0.v20120508-1726-9JF7AHV8FyMteja0CggfF3FfqHnxgnrWaBmfoD]
Cannot satisfy dependency:
From: Eclipse SDK 4.2.0.I20120524-2100 (org.eclipse.sdk.ide 4.2.0.I20120524-2100)
To: org.eclipse.sdk.feature.group [4.2.0.v20120522-2109-7T7mDFDPz-3FdpcTdH3vf9z-X_aZ4Bz-tcBJLHHhcWJnb]
Cannot satisfy dependency:
From: JBoss Runtime ESB Detector 1.3.0.v20120522-1702-H4-Beta2-SOA (org.jboss.tools.runtime.esb.detector 1.3.0.v20120522-1702-H4-Beta2-SOA)
To: bundle org.eclipse.core.runtime [3.7.0,3.8.0)
Cannot satisfy dependency:
From: JBoss Runtime ESB Detector 1.3.0.v20120522-1702-H4-Beta2-SOA (org.jboss.tools.runtime.esb.detector.feature.feature.group 1.3.0.v20120522-1702-H4-Beta2-SOA)
To: org.jboss.tools.runtime.esb.detector [1.3.0.v20120522-1702-H4-Beta2-SOA]
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months
[JBoss JIRA] (JBDS-2374) Cannot install JBoss SwitchYard tools into JBDS 6.0.beta1
by Len DiMaggio (JIRA)
Len DiMaggio created JBDS-2374:
----------------------------------
Summary: Cannot install JBoss SwitchYard tools into JBDS 6.0.beta1
Key: JBDS-2374
URL: https://issues.jboss.org/browse/JBDS-2374
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Feature Request
Components: SOA Tooling / Platform
Affects Versions: 6.0.0.Beta1
Environment: Version: 6.0.0.Beta1
Build id: Beta1-v20121024-2033-B58
Build date: 20121024-2033
Reporter: Len DiMaggio
Assignee: Douglas Palmer
Fix For: 6.0.0.Beta2
It's possible to successfully install SwitchYard eclipse tools into Eclipse Juno, if these update sites are defined to resolve dependencies:
JBT - http://download.jboss.org/jbosstools/updates/development/juno/
m2e - http://download.jboss.org/jbosstools/updates/m2eclipse-wtp/
SY - jar:file:/jboss/local/downloads/switchyard-site-assembly-0.6.0.Beta2.zip!/
EMF - http://download.eclipse.org/modeling/emf/updates/releases/
GEF - http://download.eclipse.org/tools/gef/updates/releases/
But - trying to install SwitchYard eclipse tools into JBDS 6.0.beta1 fails with this dependency error:
Cannot complete the install because one or more required items could not be found.
Software being installed: SwitchYard Tools 0.6.0.v20121031-1758-H213-Beta2 (org.switchyard.tools.feature.feature.group 0.6.0.v20121031-1758-H213-Beta2)
Missing requirement: SwitchYard Tools 0.6.0.v20121031-1758-H213-Beta2 (org.switchyard.tools.feature.feature.group 0.6.0.v20121031-1758-H213-Beta2) requires 'org.maven.ide.eclipse.wtp.feature.feature.group 0.14.0' but it could not be found
Adding this update site:
http://download.jboss.org/jbosstools/updates/m2eclipse-wtp/
Results in this error:
Cannot complete the install because of a conflicting dependency.
Software being installed: SwitchYard Tools 0.6.0.v20121031-1758-H213-Beta2 (org.switchyard.tools.feature.feature.group 0.6.0.v20121031-1758-H213-Beta2)
Software currently installed: JBoss Developer Studio (Branded Product) 6.0.0.Beta1-v20121024-2033-B58 (com.jboss.jbds.all 6.0.0.Beta1-v20121024-2033-B58)
Only one of the following can be installed at once:
Maven Integration for Eclipse WTP 0.15.3.20120830-0850 (org.maven.ide.eclipse.wtp 0.15.3.20120830-0850)
This version of m2e-wtp cannot be installed on top of the already installed m2eclipse-wtp. Uninstall the previous version of m2eclipse-wtp and try the install again. 0.16.0.20120914-0945 (org.maven.ide.eclipse.wtp 0.16.0.20120914-0945)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months
[JBoss JIRA] (JBIDE-13072) Manage SSH Keys Dialog - OK button
by Burr Sutter (JIRA)
Burr Sutter created JBIDE-13072:
-----------------------------------
Summary: Manage SSH Keys Dialog - OK button
Key: JBIDE-13072
URL: https://issues.jboss.org/browse/JBIDE-13072
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: openshift
Reporter: Burr Sutter
Assignee: Andre Dietisheim
The Manage SSH Keys dialog has a "off center" OK button and no Cancel button. This looks awkward - my guess is that Cancel is not needed because the user can not make a change in this UI but that suggests OK is also not needed - OK typically means "commit my changes" and Cancel "undo my changes". It could this dialog needs a Close button that is in the proper position on the dialog.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months