[JBoss JIRA] (JBDS-4176) Useless-provides detected by RPMlint
by Lukáš Valach (JIRA)
[ https://issues.jboss.org/browse/JBDS-4176?page=com.atlassian.jira.plugin.... ]
Lukáš Valach commented on JBDS-4176:
------------------------------------
??Can we run this rpmlint check as part of the rpm build, using that exclusion list???
I think so. It is quite easy to run rpmlint. You can see how I do that in [this jenkins job|https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Dev...]. Maybe we can add new build step to job which builds our RPM. The only requirement is to have rpmlint installed on slave which builds devstudio RPM.
??What's in rpmlint.conf???
There is only exclusion list which you can see in description of this ticket. This file are created during build and contains only value stored in build parameter $FILTER_CONFIG.
{code}
echo "$FILTER_CONFIG" > ./rpmlint.conf
{code}
> Useless-provides detected by RPMlint
> ------------------------------------
>
> Key: JBDS-4176
> URL: https://issues.jboss.org/browse/JBDS-4176
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: rpm
> Affects Versions: 10.2.0.AM3
> Environment: RHEL7
> Reporter: Lukáš Valach
> Assignee: Nick Boldt
> Priority: Optional
> Fix For: 10.x
>
> Attachments: opt-rh-list.2.txt, opt-rh-list.2.txt.sh, opt-rh-list.txt, opt-rh-list.txt.sh
>
>
> The rpmlint detects some problems in rpm package:
> {code}
> rpmlint -f ./rpmlint.conf ./rh-eclipse46-devstudio-10.2-0.20161111.1151.el7.x86_64.rpm
> rh-eclipse46-devstudio.x86_64: E: useless-provides rh-eclipse46-osgi(com.google.guava)
> rh-eclipse46-devstudio.x86_64: E: useless-provides rh-eclipse46-osgi(com.google.inject)
> rh-eclipse46-devstudio.x86_64: E: useless-provides rh-eclipse46-osgi(javax.wsdl)
> rh-eclipse46-devstudio.x86_64: E: useless-provides rh-eclipse46-osgi(org.apache.commons.collections)
> rh-eclipse46-devstudio.x86_64: E: useless-provides rh-eclipse46-osgi(org.apache.commons.io)
> rh-eclipse46-devstudio.x86_64: E: useless-provides rh-eclipse46-osgi(org.apache.commons.lang3)
> rh-eclipse46-devstudio.x86_64: E: useless-provides rh-eclipse46-osgi(org.apache.commons.logging)
> rh-eclipse46-devstudio.x86_64: E: useless-provides rh-eclipse46-osgi(org.eclipse.aether.api)
> rh-eclipse46-devstudio.x86_64: E: useless-provides rh-eclipse46-osgi(org.eclipse.aether.connector.basic)
> rh-eclipse46-devstudio.x86_64: E: useless-provides rh-eclipse46-osgi(org.eclipse.aether.impl)
> rh-eclipse46-devstudio.x86_64: E: useless-provides rh-eclipse46-osgi(org.eclipse.aether.spi)
> rh-eclipse46-devstudio.x86_64: E: useless-provides rh-eclipse46-osgi(org.eclipse.aether.util)
> rh-eclipse46-devstudio.x86_64: E: useless-provides rh-eclipse46-osgi(com.fasterxml.classmate)
> rh-eclipse46-devstudio.x86_64: E: useless-provides rh-eclipse46-osgi(org.jboss.logging.jboss-logging)
> rh-eclipse46-devstudio.x86_64: E: useless-provides rh-eclipse46-osgi(org.yaml.snakeyaml)
> rh-eclipse46-devstudio.x86_64: E: useless-provides rh-eclipse46-osgi(slf4j.api)
> rh-eclipse46-devstudio.x86_64: E: useless-provides rh-eclipse46-osgi(org.objectweb.asm)
> 1 packages and 0 specfiles checked; 17 errors, 0 warnings.
> {code}
> There are only important problems in the list above, another errors/warnings were suppressed according to discussion with [~vkadlcik].
> There is configuration of rpmlint filter:
> {code}
> addFilter("W: ") # Warnings can be suppressed
> addFilter("E: dir-or-file-in-opt") # False positive
> addFilter("E: devel-dependency") # False positive
> addFilter("E: explicit-lib-dependency") # May be improved but is not important for now
> addFilter("E: non-executable-script") # 99% of these errors are false positive comming from upstream, there is a very small chance to get relevant error
> addFilter("E: wrong-script-interpreter") # The same as above
> addFilter("E: zero-length") # The same as above
> {code}
> [~vkadlcik] please correct me if I'm wrong.
> RPMlint test has been automated, you can find it in [jenkins|https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view...]
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBDS-4175) NPE/broken functionality/cannot start after install from Red Hat Central into rh-eclipse46-devstudio
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4175?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-4175:
-----------------------------
Summary: NPE/broken functionality/cannot start after install from Red Hat Central into rh-eclipse46-devstudio (was: RPM version: NPE after install from Red Hat Central)
> NPE/broken functionality/cannot start after install from Red Hat Central into rh-eclipse46-devstudio
> ----------------------------------------------------------------------------------------------------
>
> Key: JBDS-4175
> URL: https://issues.jboss.org/browse/JBDS-4175
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: central-update, rpm
> Environment: RHEL 7.2 with RHSCL repositories available:
> * RHSCL 2.3 RC (http://download-node-02.eng.bos.redhat.com/rel-eng/RHSCL-2.3-RHEL-7-RC-1....)
> * update for RHBZ#1392095 (http://nest.test.redhat.com/mnt/qa/scratch/vkadlcik/eclipse/repos/rhscl23...)
> Reporter: Václav Kadlčík
> Assignee: Nick Boldt
> Priority: Critical
> Fix For: 10.2.0.GA
>
> Attachments: JBDS-4175_logs_first_half.tar.gz, rh-eclipse46-devstudio10.2.log.20161115-0953.txt, spring-ide-fail-aop.png, spring-ide-fail-list.png, spring-ide-fail-npe.png, spring-ide-fail-project-explorer-broken-package-explorer-OK.png, spring-ide-fail.png, spring-ide-view-fail.png, sw_to_install.txt, workspace.log, wst.xsd.core_diff.png
>
>
> I installed rh-eclipse46-devstudio-10.2-0.20161111.0219.el7.x86_64.rpm and followed Nick's scenario [1]. In Red Hat Central, I clicked "Select All" (it found 36 items), then "Install/Update", did all the confirmations, including a restart. After the restart, Eclipse died on java.lang.NullPointerException. I'm attaching the workspace log (aside from the NPE, it's full of "Could not resolve module").
> I reproduced the problem several times on two different machines. The update for RHBZ#1392095 (rh-eclipse46-eclipse-4.6.1-2.4.el7) isn't necessary, it just makes the reproduction much faster.
> Not sure how related it is, but rh-eclipse46 disallows updating packages installed from RPM [2]. But in the list of software to be installed/updated, I saw, among others, EGit and Mylyn, which are definitely included in rh-eclipse46-base. In any case, I'm attaching the list, too.
> [1] https://bugzilla.redhat.com/show_bug.cgi?id=1392095#c6
> [2] https://bugzilla.redhat.com/show_bug.cgi?id=1173024
> (copied from comment below to make it sticky)
> Results of installing first half of the items in Central:
> ||Item||Result||Description or Errors||
> |Android_Development_Tools|(/)||
> |JBoss_Hybrid_Mobile_Tools|(/)||
> |AngularJS_for_Web_Tools|(x)|IllegalStateException: BundleContext, NullPointerException|
> |JBoss_Arquillian_Tools|(/)||
> |JBoss_Forge_Tools|(/)||
> |JBoss_OpenShift_2_Tools|(x)|BundleException|
> |JBoss_OpenShift_3_Tools|(x)|BundleException|
> |JBoss_Portlet_Tools|(x)|BundleException, NullPointerException, eclipse didn't start|
> |JBoss_Seam_Tools|(x)|BundleException, NullPointerException, eclipse didn't start|
> |JBoss_Tools_LiveReload|(x)|BundleException|
> |JST_Server|(x)|BundleException|
> |Spring_IDE|(x)|BundleException, NullPointerException, eclipse didn't start|
> |Atlassian_Connector|(x)|BundleException, loader constraint violation|
> |Eclipse_EGit_Mylyn_Support|(x)|BundleException|
> |Subclipse_SVNKit|(/)|First attempt failed due to SocketTimeoutException but second passed|
> |Subclipse_SVNKit_Mylyn_Support|(x)|BundleException|
> |Eclipse_Checkstyle|(x)|NullPointerException|
> All logs [^JBDS-4175_logs_first_half.tar.gz].
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBTIS-986) Fix failing Flat file test
by Matus Makovy (JIRA)
Matus Makovy created JBTIS-986:
----------------------------------
Summary: Fix failing Flat file test
Key: JBTIS-986
URL: https://issues.jboss.org/browse/JBTIS-986
Project: JBoss Tools Integration Stack
Issue Type: Bug
Components: QE, teiid
Affects Versions: 4.4.0.Final, 4.3.3.Final
Reporter: Matus Makovy
Assignee: Matus Makovy
Fix For: 4.4.0.Final, 4.3.3.Final
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBIDE-23050) Exception in Tools.findFirstValidVMInstall
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23050?page=com.atlassian.jira.plugi... ]
Martin Malina closed JBIDE-23050.
---------------------------------
I never saw this, but that's probably because I don't watch the eclipse log - this was not in the error log view according to Rob.
And he saw the error and saw it fixed. So I'll take his word for it this time.
> Exception in Tools.findFirstValidVMInstall
> ------------------------------------------
>
> Key: JBIDE-23050
> URL: https://issues.jboss.org/browse/JBIDE-23050
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: common
> Affects Versions: 4.4.0.Alpha1
> Reporter: Automated Error Reporting Bot
> Assignee: Rob Stryker
> Fix For: 4.4.2.AM1
>
>
> The following problem was reported via the automated error reporting:
> Message: <no message>
> {noformat}
> java.lang.Exception: null
> at org.jboss.tools.common.jdt.debug.tools.internal.Tools.findFirstValidVMInstall(Tools.java:267)
> at org.jboss.tools.common.jdt.debug.tools.internal.Tools.findSecondaryVMInstall(Tools.java:424)
> at org.jboss.tools.common.jdt.debug.tools.internal.Tools.findHomeDirectoryToAddToClasspath(Tools.java:409)
> at org.jboss.tools.common.jdt.debug.tools.internal.Tools.getToolsJar(Tools.java:125)
> at org.jboss.tools.common.jdt.debug.tools.internal.Tools.getToolsLoader(Tools.java:100)
> at org.jboss.tools.common.jdt.debug.tools.internal.Tools.reset(Tools.java:93)
> at org.jboss.tools.common.jdt.debug.tools.internal.Tools.<init>(Tools.java:80)
> at org.jboss.tools.common.jdt.debug.tools.internal.Tools.getInstance(Tools.java:71)
> at org.jboss.tools.common.jdt.debug.RemoteDebugActivator.propertyChange(RemoteDebugActivator.java:248)
> at org.eclipse.core.runtime.Preferences$1.run(Preferences.java:510)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.core.runtime.Preferences.firePropertyChangeEvent(Preferences.java:513)
> at org.eclipse.core.internal.preferences.legacy.PreferenceForwarder.preferenceChange(PreferenceForwarder.java:116)
> at org.eclipse.core.internal.preferences.EclipsePreferences$2.run(EclipsePreferences.java:848)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.core.internal.preferences.EclipsePreferences.firePreferenceEvent(EclipsePreferences.java:851)
> at org.eclipse.core.internal.preferences.EclipsePreferences.put(EclipsePreferences.java:863)
> at org.eclipse.jdt.launching.JavaRuntime.initializeVMs(JavaRuntime.java:2769)
> at org.eclipse.jdt.launching.JavaRuntime.getVMInstallTypes(JavaRuntime.java:539)
> at org.jboss.tools.common.jdt.debug.tools.internal.Tools.getAllVMInstalls(Tools.java:183)
> at org.jboss.tools.common.jdt.debug.tools.internal.Tools.getAllCompatibleInstalls(Tools.java:214)
> at org.jboss.tools.common.jdt.debug.tools.internal.Tools.findFirstValidVMInstall(Tools.java:257)
> at org.jboss.tools.common.jdt.debug.tools.internal.Tools.findSecondaryVMInstall(Tools.java:424)
> at org.jboss.tools.common.jdt.debug.tools.internal.Tools.findHomeDirectoryToAddToClasspath(Tools.java:409)
> at org.jboss.tools.common.jdt.debug.tools.internal.Tools.getToolsJar(Tools.java:125)
> at org.jboss.tools.common.jdt.debug.tools.internal.Tools.getToolsLoader(Tools.java:100)
> at org.jboss.tools.common.jdt.debug.tools.internal.Tools.reset(Tools.java:93)
> at org.jboss.tools.common.jdt.debug.tools.internal.Tools.<init>(Tools.java:80)
> at org.jboss.tools.common.jdt.debug.tools.internal.Tools.getInstance(Tools.java:71)
> at org.jboss.tools.common.jdt.debug.tools.ToolsCore.getActiveProcessIds(ToolsCore.java:179)
> at org.jboss.tools.jmx.jvmmonitor.internal.tools.JvmAttachHandler.updatesActiveJvms(JvmAttachHandler.java:100)
> at org.jboss.tools.jmx.jvmmonitor.internal.tools.JvmAttachHandler$1.run(JvmAttachHandler.java:78)
> at java.util.TimerThread.mainLoop(null:-1)
> at java.util.TimerThread.run(null:-1)
> {noformat}
> Bundles:
> | org.eclipse.core.jobs | 3.7.0.v20150330-2103 | 3.8.0.v20160509-0411 |
> | org.eclipse.core.resources | 3.11.0.v20160503-1608 | 3.11.0.v20160503-1608 |
> | org.eclipse.core.runtime | 3.11.0.v20150405-1723 | 3.12.0.v20160606-1342 |
> | org.eclipse.debug.ui | 3.11.101.v20160203-1230 | 3.11.101.v20160203-1230 |
> | org.eclipse.jdt.core | 3.12.0.v20160516-2131 | 3.12.0.v20160516-2131 |
> | org.eclipse.jdt.debug.ui | 3.7.101.v20160203-1236 | 3.7.200.v20160423-1519 |
> | org.eclipse.jdt.launching | 3.8.0.v20150527-0946 | 3.8.100.v20160505-0636 |
> | org.eclipse.jdt.ui | 3.12.0.v20160525-1829 | 3.12.0.v20160525-1829 |
> | org.eclipse.jface | 3.11.0.v20150602-1400 | 3.12.0.v20160518-1929 |
> | org.eclipse.m2e.core | 1.7.0.20160603-1933 | 1.7.0.20160603-1933 |
> | org.eclipse.m2e.core.ui | 1.7.0.20160603-1933 | 1.7.0.20160603-1933 |
> | org.eclipse.m2e.jdt | 1.7.0.20160603-1933 | 1.7.0.20160603-1933 |
> | org.eclipse.pde.core | 3.11.0.v20160510-1223 | 3.11.0.v20160510-1223 |
> | org.eclipse.pde.ui | 3.9.0.v20160525-1830 | 3.9.0.v20160525-1830 |
> | org.eclipse.swt | 3.104.0.v20150528-0211 | 3.105.0.v20160603-0902 |
> | org.eclipse.ui | 3.107.0.v20150507-1945 | 3.108.0.v20160518-1929 |
> | org.jboss.tools.common.jdt.debug | 3.7.0.CR1-v20150915-2036-B30 | 3.8.0.Final-v20160610-1533-B7 |
> | org.jboss.tools.common.jdt.debug.ui | 3.7.0.CR1-v20150915-2036-B30 | 3.8.0.Final-v20160610-1533-B7 |
> | org.jboss.tools.jmx.jvmmonitor.tools | 1.7.1.Final-v20160409-0826-B118 | 1.8.0.Final-v20160614-2020-B9 |
> Operating Systems:
> | Linux | 2.6.32.22 | 4.6.4.fc24 |
> | MacOSX | 10.11.5 | 10.11.5 |
> | Windows | 6.1.0 | 10.0.0 |
> The above information is a snapshot of the collected data. Visit [this page|https://redhat.ctrlflow.com/reviewers/#!/problems/57001066e4b08ccb7b...] for the latest data.
> Thank you for your assistance.
> Your friendly error-reports-inbox.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBTIS-984) Update info about Early Access components in RH Central
by Paul Leacu (JIRA)
[ https://issues.jboss.org/browse/JBTIS-984?page=com.atlassian.jira.plugin.... ]
Paul Leacu resolved JBTIS-984.
------------------------------
Fix Version/s: 10.0.0.GA
Resolution: Done
Corrected in devstudio IS discovery.
https://github.com/jbosstools/jbosstools-integration-stack/commit/ac0f98b...
> Update info about Early Access components in RH Central
> -------------------------------------------------------
>
> Key: JBTIS-984
> URL: https://issues.jboss.org/browse/JBTIS-984
> Project: JBoss Tools Integration Stack
> Issue Type: Task
> Components: distribution
> Affects Versions: 10.0.0.CR1
> Environment: Devstudio IS 10.0.0.CR4
> Reporter: Andrej Podhradsky
> Assignee: Paul Leacu
> Fix For: 10.0.0.GA
>
> Attachments: devstudio-is-10.0.0.CR4-central.png
>
>
> Devstudio 10.1.0.GA with the following VM args
> -Djboss.discovery.directory.url=https://devstudio.redhat.com/10.0/staging/updates/integration-stack/discovery/10.0.0.CR4/earlyaccess/devstudio-directory.xml
> -Djboss.discovery.site.integration-stack.url=https://devstudio.redhat.com/10.0/staging/updates/integration-stack/discovery/10.0.0.CR4/
> -Djboss.discovery.earlyaccess.site.integration-stack.url=https://devstudio.redhat.com/10.0/staging/updates/integration-stack/discovery/10.0.0.CR4/earlyaccess/
> says that the Fuse tooling in on Early Access and is available in 9.x (EDIT: now I noticed that there is "Also available in 9.x" - do we need this?)
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBTIS-984) Update info about Early Access components in RH Central
by Paul Leacu (JIRA)
[ https://issues.jboss.org/browse/JBTIS-984?page=com.atlassian.jira.plugin.... ]
Paul Leacu reassigned JBTIS-984:
--------------------------------
Assignee: Paul Leacu
> Update info about Early Access components in RH Central
> -------------------------------------------------------
>
> Key: JBTIS-984
> URL: https://issues.jboss.org/browse/JBTIS-984
> Project: JBoss Tools Integration Stack
> Issue Type: Task
> Components: distribution
> Affects Versions: 10.0.0.CR1
> Environment: Devstudio IS 10.0.0.CR4
> Reporter: Andrej Podhradsky
> Assignee: Paul Leacu
> Attachments: devstudio-is-10.0.0.CR4-central.png
>
>
> Devstudio 10.1.0.GA with the following VM args
> -Djboss.discovery.directory.url=https://devstudio.redhat.com/10.0/staging/updates/integration-stack/discovery/10.0.0.CR4/earlyaccess/devstudio-directory.xml
> -Djboss.discovery.site.integration-stack.url=https://devstudio.redhat.com/10.0/staging/updates/integration-stack/discovery/10.0.0.CR4/
> -Djboss.discovery.earlyaccess.site.integration-stack.url=https://devstudio.redhat.com/10.0/staging/updates/integration-stack/discovery/10.0.0.CR4/earlyaccess/
> says that the Fuse tooling in on Early Access and is available in 9.x (EDIT: now I noticed that there is "Also available in 9.x" - do we need this?)
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBDS-4175) RPM version: NPE after install from Red Hat Central
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4175?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-4175:
-----------------------------
Description:
I installed rh-eclipse46-devstudio-10.2-0.20161111.0219.el7.x86_64.rpm and followed Nick's scenario [1]. In Red Hat Central, I clicked "Select All" (it found 36 items), then "Install/Update", did all the confirmations, including a restart. After the restart, Eclipse died on java.lang.NullPointerException. I'm attaching the workspace log (aside from the NPE, it's full of "Could not resolve module").
I reproduced the problem several times on two different machines. The update for RHBZ#1392095 (rh-eclipse46-eclipse-4.6.1-2.4.el7) isn't necessary, it just makes the reproduction much faster.
Not sure how related it is, but rh-eclipse46 disallows updating packages installed from RPM [2]. But in the list of software to be installed/updated, I saw, among others, EGit and Mylyn, which are definitely included in rh-eclipse46-base. In any case, I'm attaching the list, too.
[1] https://bugzilla.redhat.com/show_bug.cgi?id=1392095#c6
[2] https://bugzilla.redhat.com/show_bug.cgi?id=1173024
(copied from comment below to make it sticky)
Results of installing first half of the items in Central:
||Item||Result||Description or Errors||
|Android_Development_Tools|(/)||
|JBoss_Hybrid_Mobile_Tools|(/)||
|AngularJS_for_Web_Tools|(x)|IllegalStateException: BundleContext, NullPointerException|
|JBoss_Arquillian_Tools|(/)||
|JBoss_Forge_Tools|(/)||
|JBoss_OpenShift_2_Tools|(x)|BundleException|
|JBoss_OpenShift_3_Tools|(x)|BundleException|
|JBoss_Portlet_Tools|(x)|BundleException, NullPointerException, eclipse didn't start|
|JBoss_Seam_Tools|(x)|BundleException, NullPointerException, eclipse didn't start|
|JBoss_Tools_LiveReload|(x)|BundleException|
|JST_Server|(x)|BundleException|
|Spring_IDE|(x)|BundleException, NullPointerException, eclipse didn't start|
|Atlassian_Connector|(x)|BundleException, loader constraint violation|
|Eclipse_EGit_Mylyn_Support|(x)|BundleException|
|Subclipse_SVNKit|(/)|First attempt failed due to SocketTimeoutException but second passed|
|Subclipse_SVNKit_Mylyn_Support|(x)|BundleException|
|Eclipse_Checkstyle|(x)|NullPointerException|
All logs [^JBDS-4175_logs_first_half.tar.gz].
was:
I installed rh-eclipse46-devstudio-10.2-0.20161111.0219.el7.x86_64.rpm and followed Nick's scenario [1]. In Red Hat Central, I clicked "Select All" (it found 36 items), then "Install/Update", did all the confirmations, including a restart. After the restart, Eclipse died on java.lang.NullPointerException. I'm attaching the workspace log (aside from the NPE, it's full of "Could not resolve module").
I reproduced the problem several times on two different machines. The update for RHBZ#1392095 (rh-eclipse46-eclipse-4.6.1-2.4.el7) isn't necessary, it just makes the reproduction much faster.
Not sure how related it is, but rh-eclipse46 disallows updating packages installed from RPM [2]. But in the list of software to be installed/updated, I saw, among others, EGit and Mylyn, which are definitely included in rh-eclipse46-base. In any case, I'm attaching the list, too.
[1] https://bugzilla.redhat.com/show_bug.cgi?id=1392095#c6
[2] https://bugzilla.redhat.com/show_bug.cgi?id=1173024
> RPM version: NPE after install from Red Hat Central
> ---------------------------------------------------
>
> Key: JBDS-4175
> URL: https://issues.jboss.org/browse/JBDS-4175
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: central-update, rpm
> Environment: RHEL 7.2 with RHSCL repositories available:
> * RHSCL 2.3 RC (http://download-node-02.eng.bos.redhat.com/rel-eng/RHSCL-2.3-RHEL-7-RC-1....)
> * update for RHBZ#1392095 (http://nest.test.redhat.com/mnt/qa/scratch/vkadlcik/eclipse/repos/rhscl23...)
> Reporter: Václav Kadlčík
> Assignee: Nick Boldt
> Priority: Critical
> Fix For: 10.2.0.GA
>
> Attachments: JBDS-4175_logs_first_half.tar.gz, rh-eclipse46-devstudio10.2.log.20161115-0953.txt, spring-ide-fail-aop.png, spring-ide-fail-list.png, spring-ide-fail-npe.png, spring-ide-fail-project-explorer-broken-package-explorer-OK.png, spring-ide-fail.png, spring-ide-view-fail.png, sw_to_install.txt, workspace.log, wst.xsd.core_diff.png
>
>
> I installed rh-eclipse46-devstudio-10.2-0.20161111.0219.el7.x86_64.rpm and followed Nick's scenario [1]. In Red Hat Central, I clicked "Select All" (it found 36 items), then "Install/Update", did all the confirmations, including a restart. After the restart, Eclipse died on java.lang.NullPointerException. I'm attaching the workspace log (aside from the NPE, it's full of "Could not resolve module").
> I reproduced the problem several times on two different machines. The update for RHBZ#1392095 (rh-eclipse46-eclipse-4.6.1-2.4.el7) isn't necessary, it just makes the reproduction much faster.
> Not sure how related it is, but rh-eclipse46 disallows updating packages installed from RPM [2]. But in the list of software to be installed/updated, I saw, among others, EGit and Mylyn, which are definitely included in rh-eclipse46-base. In any case, I'm attaching the list, too.
> [1] https://bugzilla.redhat.com/show_bug.cgi?id=1392095#c6
> [2] https://bugzilla.redhat.com/show_bug.cgi?id=1173024
> (copied from comment below to make it sticky)
> Results of installing first half of the items in Central:
> ||Item||Result||Description or Errors||
> |Android_Development_Tools|(/)||
> |JBoss_Hybrid_Mobile_Tools|(/)||
> |AngularJS_for_Web_Tools|(x)|IllegalStateException: BundleContext, NullPointerException|
> |JBoss_Arquillian_Tools|(/)||
> |JBoss_Forge_Tools|(/)||
> |JBoss_OpenShift_2_Tools|(x)|BundleException|
> |JBoss_OpenShift_3_Tools|(x)|BundleException|
> |JBoss_Portlet_Tools|(x)|BundleException, NullPointerException, eclipse didn't start|
> |JBoss_Seam_Tools|(x)|BundleException, NullPointerException, eclipse didn't start|
> |JBoss_Tools_LiveReload|(x)|BundleException|
> |JST_Server|(x)|BundleException|
> |Spring_IDE|(x)|BundleException, NullPointerException, eclipse didn't start|
> |Atlassian_Connector|(x)|BundleException, loader constraint violation|
> |Eclipse_EGit_Mylyn_Support|(x)|BundleException|
> |Subclipse_SVNKit|(/)|First attempt failed due to SocketTimeoutException but second passed|
> |Subclipse_SVNKit_Mylyn_Support|(x)|BundleException|
> |Eclipse_Checkstyle|(x)|NullPointerException|
> All logs [^JBDS-4175_logs_first_half.tar.gz].
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBDS-4175) RPM version: NPE after install from Red Hat Central
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4175?page=com.atlassian.jira.plugin.... ]
Nick Boldt edited comment on JBDS-4175 at 11/15/16 10:41 AM:
-------------------------------------------------------------
I've also caused a set of Use constraint violations to occur... something in one of the three installs above (Openshift v3, Seam, or SpringIDE) installed
/home/nboldt/.eclipse/org.eclipse.platform_283378046_linux_gtk_x86_64/plugins/javax.servlet_3.1.0.v201410161800.jar
which conflicts with
/opt/rh/rh-eclipse46/root/usr/lib64/eclipse/plugins/javax.servlet-api_3.1.0.jar
{code}
./eclipse -vmargs -Dosgi.resolver.usesMode=strict
...
org.osgi.service.resolver.ResolutionException: Uses constraint violation. Unable to resolve resource org.eclipse.jgit.pgm
[osgi.identity; osgi.identity="org.eclipse.jgit.pgm"; type="osgi.bundle"; version:Version="4.5.0.201609210915-r"] because it is exposed to package 'javax.servlet' from resources javax.servlet [osgi.identity; osgi.identity="javax.servlet"; type="osgi.bundle"; version:Version="3.1.0.v201410161800"] and javax.servlet-api [osgi.identity; osgi.identity="javax.servlet-api"; type="osgi.bundle"; version:Version="3.1.0"] via two dependency chains.
org.osgi.service.resolver.ResolutionException: Uses constraint violation. Unable to resolve resource org.jboss.tools.browsersim.ui
[osgi.identity; osgi.identity="org.jboss.tools.browsersim.ui"; type="osgi.bundle"; version:Version="3.8.2.v20161114-2256"; singleton:="true"] because it is exposed to package 'javax.servlet' from resources javax.servlet [osgi.identity; osgi.identity="javax.servlet"; type="osgi.bundle"; version:Version="3.1.0.v201410161800"] and javax.servlet-api [osgi.identity; osgi.identity="javax.servlet-api"; type="osgi.bundle"; version:Version="3.1.0"] via two dependency chains.
org.osgi.service.resolver.ResolutionException: Uses constraint violation. Unable to resolve resource org.jboss.tools.livereload.core
[osgi.identity; osgi.identity="org.jboss.tools.livereload.core"; type="osgi.bundle"; version:Version="1.4.2.v20161103-0923"; singleton:="true"] because it is exposed to package 'javax.servlet' from resources javax.servlet [osgi.identity; osgi.identity="javax.servlet"; type="osgi.bundle"; version:Version="3.1.0.v201410161800"] and javax.servlet-api [osgi.identity; osgi.identity="javax.servlet-api"; type="osgi.bundle"; version:Version="3.1.0"] via two dependency chains.{code}
was (Author: nickboldt):
I've also caused a set of Use constraint violations to occur... something in one of the three installs above (Openshift v3, Seam, or SpringIDE) installed
/home/nboldt/.eclipse/org.eclipse.platform_283378046_linux_gtk_x86_64/plugins/javax.servlet_3.1.0.v201410161800.jar
which conflicts with
/opt/rh/rh-eclipse46/root/usr/lib64/eclipse/plugins/javax.servlet-api_3.1.0.jar
{code}
./eclipse -vmargs -Dosgi.resolver.usesMode=strict
...
org.osgi.service.resolver.ResolutionException: Uses constraint violation. Unable to resolve resource org.eclipse.jgit.pgm [osgi.identity; osgi.identity="org.eclipse.jgit.pgm"; type="osgi.bundle"; version:Version="4.5.0.201609210915-r"] because it is exposed to package 'javax.servlet' from resources javax.servlet [osgi.identity; osgi.identity="javax.servlet"; type="osgi.bundle"; version:Version="3.1.0.v201410161800"] and javax.servlet-api [osgi.identity; osgi.identity="javax.servlet-api"; type="osgi.bundle"; version:Version="3.1.0"] via two dependency chains.
org.osgi.service.resolver.ResolutionException: Uses constraint violation. Unable to resolve resource org.jboss.tools.browsersim.ui [osgi.identity; osgi.identity="org.jboss.tools.browsersim.ui"; type="osgi.bundle"; version:Version="3.8.2.v20161114-2256"; singleton:="true"] because it is exposed to package 'javax.servlet' from resources javax.servlet [osgi.identity; osgi.identity="javax.servlet"; type="osgi.bundle"; version:Version="3.1.0.v201410161800"] and javax.servlet-api [osgi.identity; osgi.identity="javax.servlet-api"; type="osgi.bundle"; version:Version="3.1.0"] via two dependency chains.
org.osgi.service.resolver.ResolutionException: Uses constraint violation. Unable to resolve resource org.jboss.tools.livereload.core [osgi.identity; osgi.identity="org.jboss.tools.livereload.core"; type="osgi.bundle"; version:Version="1.4.2.v20161103-0923"; singleton:="true"] because it is exposed to package 'javax.servlet' from resources javax.servlet [osgi.identity; osgi.identity="javax.servlet"; type="osgi.bundle"; version:Version="3.1.0.v201410161800"] and javax.servlet-api [osgi.identity; osgi.identity="javax.servlet-api"; type="osgi.bundle"; version:Version="3.1.0"] via two dependency chains.{code}
> RPM version: NPE after install from Red Hat Central
> ---------------------------------------------------
>
> Key: JBDS-4175
> URL: https://issues.jboss.org/browse/JBDS-4175
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: central-update, rpm
> Environment: RHEL 7.2 with RHSCL repositories available:
> * RHSCL 2.3 RC (http://download-node-02.eng.bos.redhat.com/rel-eng/RHSCL-2.3-RHEL-7-RC-1....)
> * update for RHBZ#1392095 (http://nest.test.redhat.com/mnt/qa/scratch/vkadlcik/eclipse/repos/rhscl23...)
> Reporter: Václav Kadlčík
> Assignee: Nick Boldt
> Priority: Critical
> Fix For: 10.2.0.GA
>
> Attachments: JBDS-4175_logs_first_half.tar.gz, rh-eclipse46-devstudio10.2.log.20161115-0953.txt, spring-ide-fail-aop.png, spring-ide-fail-list.png, spring-ide-fail-npe.png, spring-ide-fail-project-explorer-broken-package-explorer-OK.png, spring-ide-fail.png, spring-ide-view-fail.png, sw_to_install.txt, workspace.log, wst.xsd.core_diff.png
>
>
> I installed rh-eclipse46-devstudio-10.2-0.20161111.0219.el7.x86_64.rpm and followed Nick's scenario [1]. In Red Hat Central, I clicked "Select All" (it found 36 items), then "Install/Update", did all the confirmations, including a restart. After the restart, Eclipse died on java.lang.NullPointerException. I'm attaching the workspace log (aside from the NPE, it's full of "Could not resolve module").
> I reproduced the problem several times on two different machines. The update for RHBZ#1392095 (rh-eclipse46-eclipse-4.6.1-2.4.el7) isn't necessary, it just makes the reproduction much faster.
> Not sure how related it is, but rh-eclipse46 disallows updating packages installed from RPM [2]. But in the list of software to be installed/updated, I saw, among others, EGit and Mylyn, which are definitely included in rh-eclipse46-base. In any case, I'm attaching the list, too.
> [1] https://bugzilla.redhat.com/show_bug.cgi?id=1392095#c6
> [2] https://bugzilla.redhat.com/show_bug.cgi?id=1173024
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBDS-4175) RPM version: NPE after install from Red Hat Central
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4175?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBDS-4175:
----------------------------------
I've also caused a set of Use constraint violations to occur... something in one of the three installs above (Openshift v3, Seam, or SpringIDE) installed
/home/nboldt/.eclipse/org.eclipse.platform_283378046_linux_gtk_x86_64/plugins/javax.servlet_3.1.0.v201410161800.jar
which conflicts with
/opt/rh/rh-eclipse46/root/usr/lib64/eclipse/plugins/javax.servlet-api_3.1.0.jar
{code}
./eclipse -vmargs -Dosgi.resolver.usesMode=strict
...
org.osgi.service.resolver.ResolutionException: Uses constraint violation. Unable to resolve resource org.eclipse.jgit.pgm [osgi.identity; osgi.identity="org.eclipse.jgit.pgm"; type="osgi.bundle"; version:Version="4.5.0.201609210915-r"] because it is exposed to package 'javax.servlet' from resources javax.servlet [osgi.identity; osgi.identity="javax.servlet"; type="osgi.bundle"; version:Version="3.1.0.v201410161800"] and javax.servlet-api [osgi.identity; osgi.identity="javax.servlet-api"; type="osgi.bundle"; version:Version="3.1.0"] via two dependency chains.
org.osgi.service.resolver.ResolutionException: Uses constraint violation. Unable to resolve resource org.jboss.tools.browsersim.ui [osgi.identity; osgi.identity="org.jboss.tools.browsersim.ui"; type="osgi.bundle"; version:Version="3.8.2.v20161114-2256"; singleton:="true"] because it is exposed to package 'javax.servlet' from resources javax.servlet [osgi.identity; osgi.identity="javax.servlet"; type="osgi.bundle"; version:Version="3.1.0.v201410161800"] and javax.servlet-api [osgi.identity; osgi.identity="javax.servlet-api"; type="osgi.bundle"; version:Version="3.1.0"] via two dependency chains.
org.osgi.service.resolver.ResolutionException: Uses constraint violation. Unable to resolve resource org.jboss.tools.livereload.core [osgi.identity; osgi.identity="org.jboss.tools.livereload.core"; type="osgi.bundle"; version:Version="1.4.2.v20161103-0923"; singleton:="true"] because it is exposed to package 'javax.servlet' from resources javax.servlet [osgi.identity; osgi.identity="javax.servlet"; type="osgi.bundle"; version:Version="3.1.0.v201410161800"] and javax.servlet-api [osgi.identity; osgi.identity="javax.servlet-api"; type="osgi.bundle"; version:Version="3.1.0"] via two dependency chains.{code}
> RPM version: NPE after install from Red Hat Central
> ---------------------------------------------------
>
> Key: JBDS-4175
> URL: https://issues.jboss.org/browse/JBDS-4175
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: central-update, rpm
> Environment: RHEL 7.2 with RHSCL repositories available:
> * RHSCL 2.3 RC (http://download-node-02.eng.bos.redhat.com/rel-eng/RHSCL-2.3-RHEL-7-RC-1....)
> * update for RHBZ#1392095 (http://nest.test.redhat.com/mnt/qa/scratch/vkadlcik/eclipse/repos/rhscl23...)
> Reporter: Václav Kadlčík
> Assignee: Nick Boldt
> Priority: Critical
> Fix For: 10.2.0.GA
>
> Attachments: JBDS-4175_logs_first_half.tar.gz, rh-eclipse46-devstudio10.2.log.20161115-0953.txt, spring-ide-fail-aop.png, spring-ide-fail-list.png, spring-ide-fail-npe.png, spring-ide-fail-project-explorer-broken-package-explorer-OK.png, spring-ide-fail.png, spring-ide-view-fail.png, sw_to_install.txt, workspace.log, wst.xsd.core_diff.png
>
>
> I installed rh-eclipse46-devstudio-10.2-0.20161111.0219.el7.x86_64.rpm and followed Nick's scenario [1]. In Red Hat Central, I clicked "Select All" (it found 36 items), then "Install/Update", did all the confirmations, including a restart. After the restart, Eclipse died on java.lang.NullPointerException. I'm attaching the workspace log (aside from the NPE, it's full of "Could not resolve module").
> I reproduced the problem several times on two different machines. The update for RHBZ#1392095 (rh-eclipse46-eclipse-4.6.1-2.4.el7) isn't necessary, it just makes the reproduction much faster.
> Not sure how related it is, but rh-eclipse46 disallows updating packages installed from RPM [2]. But in the list of software to be installed/updated, I saw, among others, EGit and Mylyn, which are definitely included in rh-eclipse46-base. In any case, I'm attaching the list, too.
> [1] https://bugzilla.redhat.com/show_bug.cgi?id=1392095#c6
> [2] https://bugzilla.redhat.com/show_bug.cgi?id=1173024
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months