[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.AM2
(was: 4.4.1.AM1)
> 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.AM2
>
>
> 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-22703) NoStackTrace below DiscoveryViewer$18.run
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22703?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-22703:
-------------------------------
Project: Tools (JBoss Tools) (was: Red Hat JBoss Developer Studio (devstudio))
Key: JBIDE-22703 (was: JBDS-3603)
Workflow: GIT Pull Request workflow (was: CDW v1)
Status: Open (was: New)
Docs QE Status: (was: NEW)
Component/s: central-update
(was: central-update)
Affects Version/s: 4.4.1.AM1
(was: 9.1.0.CR1)
Fix Version/s: 4.4.x
(was: 10.x)
> NoStackTrace below DiscoveryViewer$18.run
> -----------------------------------------
>
> Key: JBIDE-22703
> URL: https://issues.jboss.org/browse/JBIDE-22703
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central-update
> Affects Versions: 4.4.1.AM1
> Reporter: Automated Error Reporting Bot
> Assignee: Nick Boldt
> Fix For: 4.4.x
>
>
> The following incident was reported via the automated error reporting:
> The user(s) left the following comments:
> --- manderse(a)redhat.com wrote: ---
> test message - why is this happening.
>
> code: 0
> plugin: org.eclipse.mylyn.discovery.core_3.17.0.v20150625-2042
> message: Unknown category 'org.jboss.tools.discovery.certification.earlyaccess' referenced by connector 'org.jboss.tools.esb.feature' declared in org.jboss.tools.central.discovery.integration_stack.earlyaccess_4.3.0.Alpha2a_v20151006_1928_B438.jar_806886544943382023.jar
> fingerprint: dd8fd5fff4740f5c681ba9438f20d2d5
> exception class: org.eclipse.epp.logging.aeri.core.util.NoStackTrace
> exception message: This event was logged without a stack trace. A synthetic stack trace was hence inserted.
> number of children: 0
>
> org.eclipse.epp.logging.aeri.core.util.NoStackTrace: This event was logged without a stack trace. A synthetic stack trace was hence inserted.
> at org.eclipse.mylyn.commons.core.StatusHandler.log(StatusHandler.java:47)
> at org.eclipse.mylyn.internal.discovery.core.model.ConnectorDiscovery.connectCertificationsToDescriptors(ConnectorDiscovery.java:235)
> at org.eclipse.mylyn.internal.discovery.core.model.ConnectorDiscovery.performDiscovery(ConnectorDiscovery.java:128)
> at org.jboss.tools.central.editors.xpl.DiscoveryViewer$18.run(DiscoveryViewer.java:1189)
> at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:119)
>
>
> General Information:
> reported-by: manderse(a)redhat.com
> anonymous-id: 751eebb9-1908-48d7-882a-d109eb3ae47e
> eclipse-build-id: 4.5.0.I20150603-2000
> eclipse-product: org.eclipse.platform.ide
> operating system: MacOSX 10.11.2 (x86_64) - cocoa
> jre-version: 1.8.0_20-b26
> The following plug-ins were present on the execution stack (*):
> 1. org.eclipse.jface_3.11.0.v20150602-1400
> 2. org.eclipse.mylyn.commons.core_3.17.0.v20150625-2042
> 3. org.eclipse.mylyn.discovery.core_3.17.0.v20150625-2042
> 4. org.jboss.tools.central_2.0.0.Final-v20151001-1531-B45
> Please note that:
> * Messages, stacktraces, and nested status objects may be shortened.
> * Bug fields like status, resolution, and whiteboard are sent
> back to reporters.
> * The list of present bundles and their respective versions was
> calculated by package naming heuristics. This may or may not reflect reality.
> Other Resources:
> * Report: https://dev.eclipse.org/recommenders/committers/confess/#/problems/56b7dc...
> * Manual: https://dev.eclipse.org/recommenders/community/confess/#/guide
> Thank you for your assistance.
> Your friendly error-reports-inbox.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (JBIDE-22703) Unknown category 'org.jboss.tools.discovery.certification.earlyaccess' referenced by connector 'org.jboss.tools.esb.feature' ( NoStackTrace below DiscoveryViewer$18.run )
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22703?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-22703:
-------------------------------
Summary: Unknown category 'org.jboss.tools.discovery.certification.earlyaccess' referenced by connector 'org.jboss.tools.esb.feature' ( NoStackTrace below DiscoveryViewer$18.run ) (was: NoStackTrace below DiscoveryViewer$18.run)
> Unknown category 'org.jboss.tools.discovery.certification.earlyaccess' referenced by connector 'org.jboss.tools.esb.feature' ( NoStackTrace below DiscoveryViewer$18.run )
> ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-22703
> URL: https://issues.jboss.org/browse/JBIDE-22703
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central-update
> Affects Versions: 4.4.1.AM1
> Reporter: Automated Error Reporting Bot
> Assignee: Nick Boldt
> Fix For: 4.4.x
>
>
> The following incident was reported via the automated error reporting:
> The user(s) left the following comments:
> --- manderse(a)redhat.com wrote: ---
> test message - why is this happening.
>
> code: 0
> plugin: org.eclipse.mylyn.discovery.core_3.17.0.v20150625-2042
> message: Unknown category 'org.jboss.tools.discovery.certification.earlyaccess' referenced by connector 'org.jboss.tools.esb.feature' declared in org.jboss.tools.central.discovery.integration_stack.earlyaccess_4.3.0.Alpha2a_v20151006_1928_B438.jar_806886544943382023.jar
> fingerprint: dd8fd5fff4740f5c681ba9438f20d2d5
> exception class: org.eclipse.epp.logging.aeri.core.util.NoStackTrace
> exception message: This event was logged without a stack trace. A synthetic stack trace was hence inserted.
> number of children: 0
>
> org.eclipse.epp.logging.aeri.core.util.NoStackTrace: This event was logged without a stack trace. A synthetic stack trace was hence inserted.
> at org.eclipse.mylyn.commons.core.StatusHandler.log(StatusHandler.java:47)
> at org.eclipse.mylyn.internal.discovery.core.model.ConnectorDiscovery.connectCertificationsToDescriptors(ConnectorDiscovery.java:235)
> at org.eclipse.mylyn.internal.discovery.core.model.ConnectorDiscovery.performDiscovery(ConnectorDiscovery.java:128)
> at org.jboss.tools.central.editors.xpl.DiscoveryViewer$18.run(DiscoveryViewer.java:1189)
> at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:119)
>
>
> General Information:
> reported-by: manderse(a)redhat.com
> anonymous-id: 751eebb9-1908-48d7-882a-d109eb3ae47e
> eclipse-build-id: 4.5.0.I20150603-2000
> eclipse-product: org.eclipse.platform.ide
> operating system: MacOSX 10.11.2 (x86_64) - cocoa
> jre-version: 1.8.0_20-b26
> The following plug-ins were present on the execution stack (*):
> 1. org.eclipse.jface_3.11.0.v20150602-1400
> 2. org.eclipse.mylyn.commons.core_3.17.0.v20150625-2042
> 3. org.eclipse.mylyn.discovery.core_3.17.0.v20150625-2042
> 4. org.jboss.tools.central_2.0.0.Final-v20151001-1531-B45
> Please note that:
> * Messages, stacktraces, and nested status objects may be shortened.
> * Bug fields like status, resolution, and whiteboard are sent
> back to reporters.
> * The list of present bundles and their respective versions was
> calculated by package naming heuristics. This may or may not reflect reality.
> Other Resources:
> * Report: https://dev.eclipse.org/recommenders/committers/confess/#/problems/56b7dc...
> * Manual: https://dev.eclipse.org/recommenders/community/confess/#/guide
> Thank you for your assistance.
> Your friendly error-reports-inbox.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (JBDS-3603) NoStackTrace below DiscoveryViewer$18.run
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3603?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-3603:
-----------------------------
Fix Version/s: 10.x
> NoStackTrace below DiscoveryViewer$18.run
> -----------------------------------------
>
> Key: JBDS-3603
> URL: https://issues.jboss.org/browse/JBDS-3603
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: central-update
> Affects Versions: 9.1.0.CR1
> Reporter: Automated Error Reporting Bot
> Assignee: Nick Boldt
> Fix For: 10.x
>
>
> The following incident was reported via the automated error reporting:
> The user(s) left the following comments:
> --- manderse(a)redhat.com wrote: ---
> test message - why is this happening.
>
> code: 0
> plugin: org.eclipse.mylyn.discovery.core_3.17.0.v20150625-2042
> message: Unknown category 'org.jboss.tools.discovery.certification.earlyaccess' referenced by connector 'org.jboss.tools.esb.feature' declared in org.jboss.tools.central.discovery.integration_stack.earlyaccess_4.3.0.Alpha2a_v20151006_1928_B438.jar_806886544943382023.jar
> fingerprint: dd8fd5fff4740f5c681ba9438f20d2d5
> exception class: org.eclipse.epp.logging.aeri.core.util.NoStackTrace
> exception message: This event was logged without a stack trace. A synthetic stack trace was hence inserted.
> number of children: 0
>
> org.eclipse.epp.logging.aeri.core.util.NoStackTrace: This event was logged without a stack trace. A synthetic stack trace was hence inserted.
> at org.eclipse.mylyn.commons.core.StatusHandler.log(StatusHandler.java:47)
> at org.eclipse.mylyn.internal.discovery.core.model.ConnectorDiscovery.connectCertificationsToDescriptors(ConnectorDiscovery.java:235)
> at org.eclipse.mylyn.internal.discovery.core.model.ConnectorDiscovery.performDiscovery(ConnectorDiscovery.java:128)
> at org.jboss.tools.central.editors.xpl.DiscoveryViewer$18.run(DiscoveryViewer.java:1189)
> at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:119)
>
>
> General Information:
> reported-by: manderse(a)redhat.com
> anonymous-id: 751eebb9-1908-48d7-882a-d109eb3ae47e
> eclipse-build-id: 4.5.0.I20150603-2000
> eclipse-product: org.eclipse.platform.ide
> operating system: MacOSX 10.11.2 (x86_64) - cocoa
> jre-version: 1.8.0_20-b26
> The following plug-ins were present on the execution stack (*):
> 1. org.eclipse.jface_3.11.0.v20150602-1400
> 2. org.eclipse.mylyn.commons.core_3.17.0.v20150625-2042
> 3. org.eclipse.mylyn.discovery.core_3.17.0.v20150625-2042
> 4. org.jboss.tools.central_2.0.0.Final-v20151001-1531-B45
> Please note that:
> * Messages, stacktraces, and nested status objects may be shortened.
> * Bug fields like status, resolution, and whiteboard are sent
> back to reporters.
> * The list of present bundles and their respective versions was
> calculated by package naming heuristics. This may or may not reflect reality.
> Other Resources:
> * Report: https://dev.eclipse.org/recommenders/committers/confess/#/problems/56b7dc...
> * Manual: https://dev.eclipse.org/recommenders/community/confess/#/guide
> Thank you for your assistance.
> Your friendly error-reports-inbox.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (JBIDE-21364) [CDK] Change how fetching environment vars via adbinfo works
by Navid Shaikh (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21364?page=com.atlassian.jira.plugi... ]
Navid Shaikh edited comment on JBIDE-21364 at 7/8/16 9:11 AM:
--------------------------------------------------------------
> Also worth noting: we cannot switch to script-readable because the previous release which we must still support did not have a functional --script-readable / --machine-readable.
For clarity, can you please enlist the version(s) of the plugin to be supported for a year ?
> So we're kinda stuck this way for at least a year.
:(
was (Author: navidshaikh):
> Also worth noting: we cannot switch to script-readable because the previous release which we must still support did not have a functional --script-readable / --machine-readable.
For clarity, can you please enlist the version(s) of the plugin to be supported for a year ?
> So we're kinda stuck this way for at least a year.
:-(
> [CDK] Change how fetching environment vars via adbinfo works
> ------------------------------------------------------------
>
> Key: JBIDE-21364
> URL: https://issues.jboss.org/browse/JBIDE-21364
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: cdk
> Affects Versions: 4.3.1.Beta1
> Reporter: Rob Stryker
> Assignee: Rob Stryker
> Fix For: 4.5.0.AM1
>
>
> Current behavior runs adbinfo directly via runtime.exec(etc).
> Investigate upstream solutions as shown here: https://github.com/eclipse/linuxtools/blob/master/containers/org.eclipse....
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (JBTIS-802) JBTIS 4.4.0.Alpha1/ DevstudioIS 10.0.0.Alpha1
by Paul Leacu (JIRA)
Paul Leacu created JBTIS-802:
--------------------------------
Summary: JBTIS 4.4.0.Alpha1/ DevstudioIS 10.0.0.Alpha1
Key: JBTIS-802
URL: https://issues.jboss.org/browse/JBTIS-802
Project: JBoss Tools Integration Stack
Issue Type: Feature Request
Components: distribution
Reporter: Paul Leacu
Assignee: Paul Leacu
Fix For: 4.4.0.Alpha1, 10.0.0.Alpha1
Component and metadata updates required for a Neon Alpha1 IS release.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (JBIDE-22673) Need better duplicate IU detection when validating target platforms
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22673?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-22673:
------------------------------------
[~mickael_istria] Can you submit a PR for how this would be implemented in jbosstools-target-platforms and jbosstools-discovery? I tried to use <tychoVersion>0.26.0-SNAPSHOT</tychoVersion> and <tychoExtrasVersion>0.26.0-SNAPSHOT</tychoExtrasVersion> but could not resolve them. When you say "is now published" do you mean "at some time in the near future" ?
> Need better duplicate IU detection when validating target platforms
> -------------------------------------------------------------------
>
> Key: JBIDE-22673
> URL: https://issues.jboss.org/browse/JBIDE-22673
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: build, target-platform, upstream
> Affects Versions: 4.4.0.Final
> Reporter: Nick Boldt
> Assignee: Mickael Istria
> Fix For: 4.4.1.AM2
>
>
> As discussed in JBIDE-22633, we have no way of knowing when the target platform SHOULD contain duplicate IUs, and when it should not.
> {quote}Problem is there's no way to identify easily which dupes are OK and which are not. I suppose I could crack open all the jars and see which are singletons...?
> Or add a whitelist?{quote}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months