[JBoss JIRA] (JBIDE-22611) target platform validation fails to detect duplicate IUs
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22611?page=com.atlassian.jira.plugi... ]
Mickael Istria commented on JBIDE-22611:
----------------------------------------
Please split Jiras then. Working on distinct issues in the same Jira usually slows down progress on both of them.
> target platform validation fails to detect duplicate IUs
> --------------------------------------------------------
>
> Key: JBIDE-22611
> URL: https://issues.jboss.org/browse/JBIDE-22611
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: target-platform
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Critical
> Fix For: 4.4.1.S116
>
>
> Recently, I added the Jenkins Text Finder to the target platform matrix job so that when bad things happen in the log, the build is shown in yellow instead of having the bad things ignored behind a blue ball. For example:
> {code}
> [p2.dir] !MESSAGE Cannot complete the install because of a conflicting dependency.
> [p2.dir] !MESSAGE Maven Project Model Edit Bundle 1.7.0.20160603-1933 (org.eclipse.m2e.model.edit 1.7.0.20160603-1933)
> [p2.dir] !MESSAGE Maven Project Model Edit Bundle 1.7.0.20160531-2022 (org.eclipse.m2e.model.edit 1.7.0.20160531-2022)
> BUILD FAILED
> {code}
> But this is not the same error that Paul Leacu recently reported:
> {code}
> > [ERROR] Resolution failed:
> > [ERROR] Software being installed: org.eclipse.egit.ui.smartimport 4.4.0.201606011500-rc2
> > [ERROR] Software being installed: org.eclipse.egit.ui.smartimport 4.4.0.201606070830-r
> > [ERROR] Only one of the following can be installed at once: [org.eclipse.egit.ui.smartimport 4.4.0.201606070830-r, org.eclipse.egit.ui.smartimport 4.4.0.201606011500-rc2]{code}
> So either we have multiple instances of multiple versions of the same IU, or he's doing a different installation than the TP verification step is.
> Either way, we need to make these problems more visible so they're caught sooner.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (JBIDE-22611) target platform validation fails to detect duplicate IUs
by Paul Leacu (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22611?page=com.atlassian.jira.plugi... ]
Paul Leacu commented on JBIDE-22611:
------------------------------------
I'd like to split out the immediate concern of getting a new jbosstools-multiple TP from the TP auto-validation. The IS is currently blocked from going to 4.0.0.Alpha1 until I can build with a corrected 4.60.x JBT TP. SwitchYard can't build its TP (neither can Fuse but that's used for development). Since it's a trivial fix - can I get that first?
> target platform validation fails to detect duplicate IUs
> --------------------------------------------------------
>
> Key: JBIDE-22611
> URL: https://issues.jboss.org/browse/JBIDE-22611
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: target-platform
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Critical
> Fix For: 4.4.1.S116
>
>
> Recently, I added the Jenkins Text Finder to the target platform matrix job so that when bad things happen in the log, the build is shown in yellow instead of having the bad things ignored behind a blue ball. For example:
> {code}
> [p2.dir] !MESSAGE Cannot complete the install because of a conflicting dependency.
> [p2.dir] !MESSAGE Maven Project Model Edit Bundle 1.7.0.20160603-1933 (org.eclipse.m2e.model.edit 1.7.0.20160603-1933)
> [p2.dir] !MESSAGE Maven Project Model Edit Bundle 1.7.0.20160531-2022 (org.eclipse.m2e.model.edit 1.7.0.20160531-2022)
> BUILD FAILED
> {code}
> But this is not the same error that Paul Leacu recently reported:
> {code}
> > [ERROR] Resolution failed:
> > [ERROR] Software being installed: org.eclipse.egit.ui.smartimport 4.4.0.201606011500-rc2
> > [ERROR] Software being installed: org.eclipse.egit.ui.smartimport 4.4.0.201606070830-r
> > [ERROR] Only one of the following can be installed at once: [org.eclipse.egit.ui.smartimport 4.4.0.201606070830-r, org.eclipse.egit.ui.smartimport 4.4.0.201606011500-rc2]{code}
> So either we have multiple instances of multiple versions of the same IU, or he's doing a different installation than the TP verification step is.
> Either way, we need to make these problems more visible so they're caught sooner.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (JBIDE-22632) Spurious message due to incorrect I18N
by Jeff MAURY (JIRA)
Jeff MAURY created JBIDE-22632:
----------------------------------
Summary: Spurious message due to incorrect I18N
Key: JBIDE-22632
URL: https://issues.jboss.org/browse/JBIDE-22632
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.4.0.Final
Reporter: Jeff MAURY
Priority: Minor
Fix For: 4.4.1.S117
When JBossTools Openshift is starting, a spurious message is written in the Eclipse log:{{
Warning: NLS missing message: ProjectDeletionDialogTitle in: org.jboss.tools.openshift.internal.ui.OpenShiftUIMessages}}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (JBIDE-22627) Docker image tag is ignored in Deploy Image to OpenShift wizard
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22627?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-22627:
-------------------------------------
Fix Version/s: 4.4.1.S117
> Docker image tag is ignored in Deploy Image to OpenShift wizard
> ---------------------------------------------------------------
>
> Key: JBIDE-22627
> URL: https://issues.jboss.org/browse/JBIDE-22627
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.0.Final
> Reporter: Marián Labuda
> Labels: docker, openshift_v3
> Fix For: 4.4.1.S117
>
>
> When deploying a docker image from docker explorer by selecting context menu item Deploy to OpenShift..., image name in opened Deploy Image to OpenShift wizard does not contain tag of the image. This requires manual addition of image tag, otherwise latest tag is presumed by default, what does not have to be desired at some scenarios.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months