[JBoss JIRA] (JBDS-2044) .eclipseproduct file no longer refers to JBDS
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-2044?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-2044:
-----------------------------
Fix Version/s: LATER
(was: 10.1.0.AM2)
> .eclipseproduct file no longer refers to JBDS
> ---------------------------------------------
>
> Key: JBDS-2044
> URL: https://issues.jboss.org/browse/JBDS-2044
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: installer
> Affects Versions: 5.0.0.Beta1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Optional
> Labels: discuss
> Fix For: LATER
>
>
> Before, with the linux x64 installer (jbdevstudio-product-linux-gtk-x86_64-5.0.0.v201202271832M-H79-Beta1.jar) the .eclipseproduct file read:
> {code}
> name=JBoss Developer Studio
> id=com.jboss.jbds.all
> version=5.0.0.v201202271832M-H79-Beta1
> {code}
> Now, with the universal installer (jbdevstudio-product-universal-5.0.0.v201202271832M-H79-Beta1.jar), it reads:
> {code}
> name=Eclipse Platform
> id=org.eclipse.platform
> version=3.7.0
> {code}
> Latest code in equinox.runtime master branch is located http://git.eclipse.org/c/equinox/rt.equinox.framework.git/tree/bundles/or...
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (JBIDE-22611) target platform validation fails to detect duplicate IUs
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22611?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-22611:
-------------------------------
Fix Version/s: 4.4.1.AM3
(was: 4.4.1.AM2)
> 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.AM3
>
>
> 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, 8 months