[JBoss JIRA] (JBIDE-22965) CDK tools should work behind proxy
by Dmitrii Bocharov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22965?page=com.atlassian.jira.plugi... ]
Dmitrii Bocharov commented on JBIDE-22965:
------------------------------------------
As i was asked on the last meeting, i'm providing here all the information about current status of the JIRA.
h3. Here is the step-by-step instructions of how i tested proxy for CDK. So if anything is not clear from the description of the current JIRA, come here.
I tested on Fedora 24, used libvirt box
1) As a sudo user do: _iptables-save > iptables-rules_
2) Run the script [^create_proxy-test_env.sh], which was created according to https://gist.github.com/LalatenduMohanty/5062050ac78721eda9676bbc15ecfd25
3) Do _service iptables restart_
4) According to [this description|https://github.com/projectatomic/adb-atomic-developer-bundle/...] set env vriables:
export PROXY="10.70.49.109:3128"
export PROXY_USER="ask me if you need it"
export PROXY_PASSWORD="sk me if you need it"
5) Then set _http_proxy_ and _https_proxy_ env vars - they have different meaning from the vars described in 4. See the quote from [~lalatendum] in the JIRA description
export http_proxy="10.70.49.109:3128"
export https_proxy="10.70.49.109:3128"
6) Do _service libvirtd restart_, as this is a know bug for Fedora/libvirt and it won't work without restarting libvirtd
7) Then i ran _vagrant up_, which was finished fine, even with registration and i could access OS via oc
8) I ran the server adapter for CDK, did registration, OS and docker connection were created and was able to create docker image and deploy it to OS.
9) Do _iptables-restore iptables-rules_ and _service iptables restart_ to restore all the network data that was before step 2.
[~lalatendum], [~rob.stryker], [~kumarpraveen], [~jeffmaury] is everything correct? Or did i configured and test anything wrong?
h3. The last status of email correspondence, which was "Sounds good" for many :)
{quote}
I discussed with [~mmalina], [~mlabuda], [~rhopp] and [~odockal] our plans on testing CDK. The first most important steps that are currently in progress and need to be finished are
1) create integration tests for CDK
2) solve problem with Nested virtualization in Central CI: https://engineering.redhat.com/rt/Ticket/Display.html?id=410151
After these problems will be solved, we'll think about dedicating machines for testing proxy. We have 2 machines in Brno that can be installed in our Mini Lab. In our opinion one will be for Windows and the other one for RHEL.
{quote}
As i can see, step 1 is done: https://github.com/jbosstools/jbosstools-integration-tests/tree/master/pl...
However last messages of the issue from step 2 are not so good. That's why we can't run even CDK integration tests without proxy on central CI. When we can, we'll need to do the same but on the machines with configured proxies.
[~akazakov], [~ldimaggio], [~budhrg], does it still sound good or do we need to plan/do anything else?
h3. The other bugs and testing proxy on other operating systems and VMs.
[~jeffmaury], [~adietish], [~lalatendum] are there any? How did you test proxy? And how did you configured the environment step-by-step?
I'm also adding [~hardy.ferentschik] and [~optak].
Please, everybody feel free to comment and add any information about testing CDK proxy here. And let all discussions be here, as it turned out that emails are easily forgotten and are hard to give the link to.
> CDK tools should work behind proxy
> ----------------------------------
>
> Key: JBIDE-22965
> URL: https://issues.jboss.org/browse/JBIDE-22965
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: cdk
> Reporter: Alexey Kazakov
> Assignee: Rob Stryker
> Priority: Critical
> Fix For: 4.4.2.AM2
>
> Attachments: create_proxy-test_env.sh
>
>
> Proxy support has been added in CDK vagrant box and in vagrant-registration plugin.
> We should make sure our CDK tooling supports it too.
> In order to run CDK behind proxy, we need to set environment variables: https://github.com/projectatomic/adb-atomic-developer-bundle/blob/master/...
> Eclipse Proxy Testing link: https://mojo.redhat.com/docs/DOC-989982
> + to create a proxy test environment: https://gist.github.com/LalatenduMohanty/5062050ac78721eda9676bbc15ecfd25
> Standard unix proxy environmet variable $http_proxy has different purpose then $PROXY that CDK uses. Comments from [~lalatendum]:
> {noformat}
> lalatenduM: we exepect customers workstation is configured to porixy server
> that means when you ping subscription-rhn-redhat-com.edge.prod.ext.phx2.redhat.com it should work
> lalatenduM: on a customer worksttaion
> lalatenduM: now teh challenge is to make openshift , docker and subscription manager in CDK VM aware of proxy server information
> lalatenduM: vagrant-registration uses subscription manager for registraton
> lalatenduM: whenyou use https://github.com/projectatomic/adb-atomic-developer-bundle/blob/master/... it will make openshift, docker and vagrant-registration aware of proxy server info
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (JBIDE-23289) ServerProfileModel.getController fails to find publish controller for wf10 [aeri]
by Automated Error Reporting Bot (JIRA)
Automated Error Reporting Bot created JBIDE-23289:
-----------------------------------------------------
Summary: ServerProfileModel.getController fails to find publish controller for wf10 [aeri]
Key: JBIDE-23289
URL: https://issues.jboss.org/browse/JBIDE-23289
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: server
Reporter: Automated Error Reporting Bot
I hesitated to make a bug report here. On the one hand, this is simply a log message, and the environment still has a chance to recover.
However, it does seem extremely strange that the publish subsystem is not being found for wf10. Our unit tests indicate it is found. The fact that this is still being replicated in astools 3.2.x is puzzling to me. But I simply cannot imagine what environment is causing this. Subsystem and profile mappings are done in the same plugin the subsystems are declared for the most part.
The following problem was reported via the automated error reporting:
Message: No subsystem found for servertype org.jboss.ide.eclipse.as.wildfly.100 and system type publish
{noformat}
com.ctrlflow.aer.NoStackTrace: This event was logged without a stack trace. A synthetic stack trace was hence inserted.
at org.jboss.ide.eclipse.as.wtp.core.server.behavior.ServerProfileModel.getController(ServerProfileModel.java:187)
at org.jboss.ide.eclipse.as.wtp.core.server.behavior.ProfileServerBehavior.getController(ProfileServerBehavior.java:59)
at org.jboss.ide.eclipse.as.wtp.core.server.behavior.CachedPublisherProfileBehavior.getPublishController(CachedPublisherProfileBehavior.java:35)
at org.jboss.ide.eclipse.as.wtp.core.server.behavior.ControllableServerBehavior.canPublish(ControllableServerBehavior.java:297)
at org.eclipse.wst.server.core.internal.Server.canPublish(Server.java:1218)
at org.eclipse.wst.server.core.internal.Server.shouldPublish(Server.java:1231)
at org.eclipse.wst.server.ui.internal.cnf.ServerDecorator.getServerStatusLabel(ServerDecorator.java:139)
at org.eclipse.wst.server.ui.internal.cnf.ServerDecorator.decorate(ServerDecorator.java:73)
at org.eclipse.ui.internal.decorators.LightweightDecoratorDefinition.decorate(LightweightDecoratorDefinition.java:273)
at org.eclipse.ui.internal.decorators.LightweightDecoratorManager$LightweightRunnable.run(LightweightDecoratorManager.java:83)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.ui.internal.decorators.LightweightDecoratorManager.decorate(LightweightDecoratorManager.java:367)
at org.eclipse.ui.internal.decorators.LightweightDecoratorManager.getDecorations(LightweightDecoratorManager.java:349)
at org.eclipse.ui.internal.decorators.DecorationScheduler$1.ensureResultCached(DecorationScheduler.java:372)
at org.eclipse.ui.internal.decorators.DecorationScheduler$1.run(DecorationScheduler.java:332)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
{noformat}
Bundles:
| org.eclipse.core.jobs | 3.7.0.v20150330-2103 | 3.8.0.v20160509-0411 |
| org.eclipse.core.runtime | 3.11.1.v20150903-1804 | 3.12.0.v20160606-1342 |
| org.eclipse.jface | 3.11.0.v20150602-1400 | 3.12.0.v20160518-1929 |
| org.eclipse.swt | 3.104.1.v20150825-0743 | 3.105.0.v20160603-0902 |
| org.eclipse.ui | 3.107.0.v20150507-1945 | 3.108.0.v20160518-1929 |
| org.eclipse.ui.navigator | 3.6.0.v20150422-0725 | 3.6.100.v20160518-1929 |
| org.eclipse.wst.server.core | 1.8.0.v201601132216 | 1.8.100.v201605201456 |
| org.eclipse.wst.server.ui | 1.5.202.v201602111638 | 1.5.304.v201605121430 |
| org.jboss.ide.eclipse.as.wtp.core | 3.1.0.Beta2-v20150723-0026-B29 | 3.2.1.v20160711-1757 |
Operating Systems:
| Linux | 3.10.0.28 | 4.6.7.fc24 |
| MacOSX | 10.10.5 | 10.12.0 |
| Windows | 5.1.0 | 10.0.0 |
The above information is a snapshot of the collected data. Visit [this page|https://redhat.ctrlflow.com/reviewers/#!/problems/56f024b6e4b08ccb7b...] for the latest data.
Thank you for your assistance.
Your friendly error-reports-inbox.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (JBIDE-23288) Users somehow have server configured for as6 shutdown behavior (jmx) and as7+ deployment scanner behavior (mgmt)
by Automated Error Reporting Bot (JIRA)
Automated Error Reporting Bot created JBIDE-23288:
-----------------------------------------------------
Summary: Users somehow have server configured for as6 shutdown behavior (jmx) and as7+ deployment scanner behavior (mgmt)
Key: JBIDE-23288
URL: https://issues.jboss.org/browse/JBIDE-23288
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: server
Reporter: Automated Error Reporting Bot
The following problem was reported via the automated error reporting:
Message: HIDDEN
{noformat}
org.jboss.ide.eclipse.as.management.core.JBoss7ManangerException: HIDDEN
at org.jboss.ide.eclipse.as.internal.management.wildfly9.Wildfly9Manager.execute(Wildfly9Manager.java:352)
at org.jboss.ide.eclipse.as.internal.management.wildfly9.Wildfly9ManagerService.execute(Wildfly9ManagerService.java:171)
at org.jboss.ide.eclipse.as.management.core.JBoss7ManagerServiceProxy.execute(JBoss7ManagerServiceProxy.java:87)
at org.jboss.ide.eclipse.as.core.server.internal.v7.AS7DeploymentScannerUtility$1.execute(AS7DeploymentScannerUtility.java:291)
at org.jboss.ide.eclipse.as.core.server.internal.v7.AS7DeploymentScannerUtility$1.execute(AS7DeploymentScannerUtility.java:1)
at org.jboss.ide.eclipse.as.management.core.JBoss7ManagerUtil.executeWithService(JBoss7ManagerUtil.java:136)
at org.jboss.ide.eclipse.as.core.server.internal.v7.AS7DeploymentScannerUtility.executeWithResult(AS7DeploymentScannerUtility.java:289)
at org.jboss.ide.eclipse.as.core.server.internal.v7.AS7DeploymentScannerUtility.getDeploymentScanners(AS7DeploymentScannerUtility.java:161)
at org.jboss.ide.eclipse.as.core.server.internal.v7.AS7DeploymentScannerUtility.getDeploymentScannersFromServer(AS7DeploymentScannerUtility.java:249)
at org.jboss.ide.eclipse.as.core.server.internal.v7.LocalJBoss7DeploymentScannerAdditions.loadScannersFromServer(LocalJBoss7DeploymentScannerAdditions.java:173)
at org.jboss.ide.eclipse.as.core.server.internal.v7.LocalJBoss7DeploymentScannerAdditions.loadScannersFromServerSafely(LocalJBoss7DeploymentScannerAdditions.java:135)
at org.jboss.ide.eclipse.as.core.server.internal.v7.LocalJBoss7DeploymentScannerAdditions.ensureScannersRemoved(LocalJBoss7DeploymentScannerAdditions.java:150)
at org.jboss.ide.eclipse.as.core.server.internal.AbstractDeploymentScannerAdditions.removeAddedDeploymentScanners(AbstractDeploymentScannerAdditions.java:83)
at org.jboss.tools.as.core.server.controllable.subsystems.internal.LocalLegacyShutdownController.removeScanners(LocalLegacyShutdownController.java:75)
at org.jboss.tools.as.core.server.controllable.subsystems.internal.LocalLegacyShutdownController.stop(LocalLegacyShutdownController.java:58)
at org.jboss.tools.as.core.server.controllable.subsystems.internal.LocalLegacyShutdownController.stop(LocalLegacyShutdownController.java:53)
at org.jboss.ide.eclipse.as.wtp.core.server.behavior.ControllableServerBehavior.stop(ControllableServerBehavior.java:252)
at org.eclipse.wst.server.core.internal.Server.stopImpl2(Server.java:3688)
at org.eclipse.wst.server.core.internal.Server.stopImpl(Server.java:3645)
at org.eclipse.wst.server.core.internal.Server$StopJob.run(Server.java:403)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
{noformat}
Bundles:
| org.eclipse.core.expressions | 3.5.0.v20150421-2214 | 3.5.100.v20160418-1621 |
| org.eclipse.core.jobs | 3.7.0.v20150330-2103 | 3.8.0.v20160509-0411 |
| org.eclipse.core.resources | 3.10.1.v20150725-1910 | 3.11.0.v20160503-1608 |
| org.eclipse.core.runtime | 3.11.1.v20150903-1804 | 3.12.0.v20160606-1342 |
| org.eclipse.e4.core.di | 1.5.0.v20150421-2214 | 1.5.0.v20150421-2214 |
| org.eclipse.jface | 3.11.1.v20160128-1644 | 3.12.0.v20160518-1929 |
| org.eclipse.jst.j2ee | 1.1.850.v201506041749 | 1.1.850.v201506041749 |
| org.eclipse.swt | 3.104.2.v20160212-1350 | 3.105.0.v20160603-0902 |
| org.eclipse.ui | 3.107.0.v20150507-1945 | 3.107.0.v20150507-1945 |
| org.eclipse.ui.forms | 3.6.200.v20150506-2029 | 3.6.200.v20150506-2029 |
| org.eclipse.ui.navigator | 3.6.0.v20150422-0725 | 3.6.100.v20160518-1929 |
| org.eclipse.wst.common.frameworks | 1.2.200.v201304241450 | 1.2.200.v201304241450 |
| org.eclipse.wst.server.core | 1.8.0.v201601132216 | 1.8.100.v201605201456 |
| org.eclipse.wst.server.ui | 1.5.202.v201602111638 | 1.5.304.v201605121430 |
| org.jboss.ide.eclipse.as.core | 3.1.0.Beta2-v20150723-0026-B29 | 3.3.1.Final-v20151021-0032-B49 |
| org.jboss.ide.eclipse.as.management.core | 3.1.0.Beta2-v20150723-0026-B29 | 3.3.1.Final-v20151021-0032-B49 |
| org.jboss.ide.eclipse.as.management.wildfly9 | 3.1.0.Beta2-v20150723-0026-B29 | 3.3.1.Final-v20151021-0032-B49 |
| org.jboss.ide.eclipse.as.ui | 3.1.0.Beta2-v20150723-0026-B29 | 3.1.1.Final-v20160409-0826-B118 |
| org.jboss.ide.eclipse.as.wtp.core | 3.1.0.Beta2-v20150723-0026-B29 | 3.3.1.Final-v20151021-0032-B49 |
| org.jboss.tools.jmx.ui | 1.7.1.Final-v20160409-0826-B118 | 1.8.0.Final-v20160614-2020-B9 |
Operating Systems:
| Linux | 2.6.32.3 | 4.7.4.fc24 |
| MacOSX | 10.11.4 | 10.11.6 |
| 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/570ce1e8e4b07391bf...] for the latest data.
Thank you for your assistance.
Your friendly error-reports-inbox.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (JBDS-4071) Validation for Traget Location path should have platform specific and shared checks
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-4071?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-4071:
--------------------------------
Summary: Validation for Traget Location path should have platform specific and shared checks (was: Validation for Traget Location path should depends on platform where it is running)
> Validation for Traget Location path should have platform specific and shared checks
> -----------------------------------------------------------------------------------
>
> Key: JBDS-4071
> URL: https://issues.jboss.org/browse/JBDS-4071
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Feature Request
> Components: platform-installer
> Affects Versions: 10.1.0.AM2
> Reporter: Denis Golovin
> Assignee: Denis Golovin
> Fix For: 10.2.0.AM2
>
>
> Current validation for target location is windows specific and does work right for other platforms. Set of validators used on this step should depend on platform installer is running.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (JBDS-4076) "RPM release" mismatch between src.rpm and x86_64.rpm
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4076?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBDS-4076:
----------------------------------
Looks like the timestamp is incrementing each time an rpm is created:
{code:title=10.2-0.20161004.1842, then 10.2-0.20161004.1843}
DEBUG util.py:502: Executing command: ['/bin/rpm', '-Uvh', '--nodeps', '/builddir/build/originals/devstudio-10.2-0.20161004.1842.el7.src.rpm'] with env {'LANG': 'en_US.UTF-8', 'TERM': 'vt100', 'SHELL': '/bin/bash', 'HOSTNAME': 'mock', 'PROMPT_COMMAND': 'printf "\\033]0;<mock-chroot>\\007"', 'HOME': '/builddir', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'PS1': '<mock-chroot> \\s-\\v\\$ '} and shell False
DEBUG util.py:421: Updating / installing...
DEBUG util.py:421: devstudio-10.2-0.20161004.1842.el7 ########################################
...
DEBUG util.py:502: Executing command: ['/bin/rpm', '-qpl', '/builddir/build/originals/devstudio-10.2-0.20161004.1842.el7.src.rpm'] with env {'LANG': 'en_US.UTF-8', 'TERM': 'vt100', 'SHELL': '/bin/bash', 'HOSTNAME': 'mock', 'PROMPT_COMMAND': 'printf "\\033]0;<mock-chroot>\\007"', 'HOME': '/builddir', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'PS1': '<mock-chroot> \\s-\\v\\$ '} and shell False
DEBUG util.py:421: build.sh
DEBUG util.py:421: devstudio.spec
DEBUG util.py:421: devstudio.tar.xz
DEBUG util.py:557: Child return code was: 0
DEBUG util.py:578: child environment: None
DEBUG package_manager.py:96: ['/usr/bin/yum-builddep', '--installroot', '/opt/data/mock_root/devstudio.rpm_master/root/', '/opt/data/mock_root/devstudio.rpm_master/root//builddir/build/SRPMS/rh-eclipse46-devstudio-10.2-0.20161004.1843.el7.src.rpm']
DEBUG util.py:578: child environment: None
DEBUG util.py:502: Executing command: ['/usr/bin/yum-builddep', '--installroot', '/opt/data/mock_root/devstudio.rpm_master/root/', '/opt/data/mock_root/devstudio.rpm_master/root//builddir/build/SRPMS/rh-eclipse46-devstudio-10.2-0.20161004.1843.el7.src.rpm', '--setopt=tsflags=nocontexts'] with env {'LANG': 'en_US.UTF-8', 'TERM': 'vt100', 'SHELL': '/bin/bash', 'LC_MESSAGES': 'C', 'HOSTNAME': 'mock', 'PROMPT_COMMAND': 'printf "\\033]0;<mock-chroot>\\007"', 'HOME': '/builddir', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'PS1': '<mock-chroot> \\s-\\v\\$ '} and shell False
DEBUG util.py:421: Getting requirements for rh-eclipse46-devstudio-10.2-0.20161004.1843.el7.src{code} -- http://wonka.mw.lab.eng.bos.redhat.com/jenkins/job/devstudio.rpm_master/w...
Then...
{code:title=10.2-0.20161004.1843, then 10.2-0.20161004.1844}
Wrote: /builddir/build/SRPMS/rh-eclipse46-devstudio-10.2-0.20161004.1843.el7.src.rpm
...
Executing(%install): /bin/sh -e /var/tmp/rpm-tmp.xYgqel
+ umask 022
+ cd /builddir/build/BUILD
+ '[' /builddir/build/BUILDROOT/rh-eclipse46-devstudio-10.2-0.20161004.1844.el7.x86_64 '!=' / ']'
+ rm -rf /builddir/build/BUILDROOT/rh-eclipse46-devstudio-10.2-0.20161004.1844.el7.x86_64
++ dirname /builddir/build/BUILDROOT/rh-eclipse46-devstudio-10.2-0.20161004.1844.el7.x86_64
+ mkdir -p /builddir/build/BUILDROOT
+ mkdir /builddir/build/BUILDROOT/rh-eclipse46-devstudio-10.2-0.20161004.1844.el7.x86_64
+ cd rh-eclipse46-devstudio-10.2
+ scl enable rh-maven33 rh-eclipse46 -
+ install -d -m755 /builddir/build/BUILDROOT/rh-eclipse46-devstudio-10.2-0.20161004.1844.el7.x86_64/opt/rh/rh-eclipse46/root/usr/share/eclipse/droplets/devstudio
++ pwd
+ eclipse -nosplash -consolelog -configuration /tmp/devstudio-rpm-eclipse-configuration -application org.eclipse.equinox.p2.repository.repo2runnable -createFragments -source /builddir/build/BUILD/rh-eclipse46-devstudio-10.2/p2-repo -destination /builddir/build/BUILDROOT/rh-eclipse46-devstudio-10.2-0.20161004.1844.el7.x86_64/opt/rh/rh-eclipse46/root/usr/share/eclipse/droplets/devstudio/eclipse
Eclipse: Cannot open display:
CompilerOracle: exclude org/eclipse/core/internal/dtree/DataTreeNode.forwardDeltaWith
CompilerOracle: exclude org/eclipse/jdt/internal/compiler/lookup/ParameterizedMethodBinding.<init>
CompilerOracle: exclude org/eclipse/cdt/internal/core/dom/parser/cpp/semantics/CPPTemplates.instantiateTemplate
CompilerOracle: exclude org/eclipse/cdt/internal/core/pdom/dom/cpp/PDOMCPPLinkage.addBinding
CompilerOracle: exclude org/python/pydev/editor/codecompletion/revisited/PythonPathHelper.isValidSourceFile
CompilerOracle: exclude org/eclipse/tycho/core/osgitools/EquinoxResolver.newState
Eclipse:
GTK+ Version Check
+ rm -fr /tmp/devstudio-rpm-eclipse-configuration
+ rm /builddir/build/BUILDROOT/rh-eclipse46-devstudio-10.2-0.20161004.1844.el7.x86_64/opt/rh/rh-eclipse46/root/usr/share/eclipse/droplets/devstudio/eclipse/artifacts.jar /builddir/build/BUILDROOT/rh-eclipse46-devstudio-10.2-0.20161004.1844.el7.x86_64/opt/rh/rh-eclipse46/root/usr/share/eclipse/droplets/devstudio/eclipse/content.jar
+ /usr/lib/rpm/find-debuginfo.sh --strict-build-id -m --run-dwz --dwz-low-mem-die-limit 10000000 --dwz-max-die-limit 110000000 /builddir/build/BUILD/rh-eclipse46-devstudio-10.2
/usr/lib/rpm/sepdebugcrcfix: Updated 0 CRC32s, 0 CRC32s did match.
{code} -- http://wonka.mw.lab.eng.bos.redhat.com/jenkins/job/devstudio.rpm_master/w...
> "RPM release" mismatch between src.rpm and x86_64.rpm
> -----------------------------------------------------
>
> Key: JBDS-4076
> URL: https://issues.jboss.org/browse/JBDS-4076
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: build, rpm
> Reporter: Václav Kadlčík
> Assignee: Nick Boldt
>
> This is an issue with upcoming rh-eclipse46-devstudio.rpm.
> Sometimes there's a mismatch in the "RPM release" between a built RPM and its src.rpm. For example https://devstudio.jboss.com/10.0/snapshots/builds/devstudio.rpm_master/20... contains:
> rh-eclipse46-devstudio-10.2-0.20161004.0056.el7.src.rpm
> rh-eclipse46-devstudio-10.2-0.20161004.0057.el7.x86_64.rpm
> The RPM release part is "0.20161004.0057.el7"; looks constructed using the date and time of building. The time bits are different between the two files.
> The SOURCERPM info in the RPM is broken as well:
> {{$ rpm -q --qf='%{SOURCERPM}\n' -p rh-eclipse46-devstudio-10.2-0.20161004.0057.el7.x86_64.rpm
> rh-eclipse46-devstudio-10.2-0.20161004.0057.el7.src.rpm
> }}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (JBIDE-18598) "Configure->Add JSF Capabilities ..." throws exception on OK/Apply button pressed for Dynamic Web Project
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18598?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-18598:
-------------------------------------
https://bugs.eclipse.org/bugs/show_bug.cgi?id=503733
> "Configure->Add JSF Capabilities ..." throws exception on OK/Apply button pressed for Dynamic Web Project
> ---------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-18598
> URL: https://issues.jboss.org/browse/JBIDE-18598
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsf, upstream
> Affects Versions: 4.2.0.CR2
> Reporter: Denis Golovin
> Assignee: Viacheslav Kabanovich
> Fix For: 4.3.x
>
>
> {code}java.util.ConcurrentModificationException
> at java.util.ArrayList$Itr.checkForComodification(ArrayList.java:859)
> at java.util.ArrayList$Itr.remove(ArrayList.java:845)
> at org.eclipse.jst.jee.model.internal.JEE5ModelProvider.addManagedResource(JEE5ModelProvider.java:142)
> at org.eclipse.jst.jee.model.internal.JEE5ModelProvider.getModelResource(JEE5ModelProvider.java:186)
> at org.eclipse.jst.jee.model.internal.Web25ModelProvider.getModelObject(Web25ModelProvider.java:44)
> at org.eclipse.jst.jee.model.internal.JEE5ModelProvider.getModelObject(JEE5ModelProvider.java:231)
> at org.eclipse.jst.jee.model.internal.common.AbstractMergedModelProvider.getLastModificationTimeOfDDFile(AbstractMergedModelProvider.java:235)
> at org.eclipse.jst.jee.model.internal.common.AbstractMergedModelProvider.hasToReloadModel(AbstractMergedModelProvider.java:229)
> at org.eclipse.jst.jee.model.internal.common.AbstractMergedModelProvider.getMergedModel(AbstractMergedModelProvider.java:218)
> at org.eclipse.jst.jee.model.internal.common.AbstractMergedModelProvider.getModelObject(AbstractMergedModelProvider.java:139)
> at org.eclipse.jst.jee.ui.internal.navigator.JEE5ContentProvider.getCachedContentProvider(JEE5ContentProvider.java:98)
> at org.eclipse.jst.jee.ui.internal.navigator.Web25ContentProvider.getChildren(Web25ContentProvider.java:35)
> at org.eclipse.ui.internal.navigator.extensions.SafeDelegateTreeContentProvider.getChildren(SafeDelegateTreeContentProvider.java:96)
> at org.eclipse.ui.internal.navigator.NavigatorContentServiceContentProvider$1.run(NavigatorContentServiceContentProvider.java:152)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.ui.internal.navigator.NavigatorContentServiceContentProvider.internalGetChildren(NavigatorContentServiceContentProvider.java:139)
> at org.eclipse.ui.internal.navigator.NavigatorContentServiceContentProvider.getChildren(NavigatorContentServiceContentProvider.java:119)
> at org.eclipse.jst.jee.ui.internal.navigator.JEE5ContentProvider$1.run(JEE5ContentProvider.java:142)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:136)
> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3806)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3444)
> at org.eclipse.jface.operation.ModalContext$ModalContextThread.block(ModalContext.java:175)
> at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:390)
> at org.eclipse.jface.dialogs.ProgressMonitorDialog.run(ProgressMonitorDialog.java:527)
> at org.eclipse.wst.common.project.facet.ui.internal.FacetsPropertyPage.performOk(FacetsPropertyPage.java:257)
> at org.eclipse.wst.common.project.facet.ui.internal.FacetsPropertyPage.performApply(FacetsPropertyPage.java:313)
> at org.eclipse.jface.preference.PreferencePage$2.widgetSelected(PreferencePage.java:284)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4486)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1388)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3831)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3441)
> at org.eclipse.jface.window.Window.runEventLoop(Window.java:832)
> at org.eclipse.jface.window.Window.open(Window.java:808)
> at org.jboss.tools.jsf.ui.internal.handlers.AddJSFNatureHandler.addJSFNature(AddJSFNatureHandler.java:137)
> at org.jboss.tools.jsf.ui.internal.handlers.AddJSFNatureHandler.execute(AddJSFNatureHandler.java:73)
> at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:294)
> at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:90)
> at sun.reflect.GeneratedMethodAccessor38.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:55)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:247)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:229)
> at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:132)
> at org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:149)
> at org.eclipse.core.commands.Command.executeWithChecks(Command.java:499)
> at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:508)
> at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:210)
> at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.executeItem(HandledContributionItem.java:825)
> at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.handleWidgetSelection(HandledContributionItem.java:701)
> at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.access$6(HandledContributionItem.java:685)
> at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem$4.handleEvent(HandledContributionItem.java:613)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4486)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1388)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3831)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3441)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1151)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1032)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:148)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:636)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:579)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:135)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:382)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:236)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:648)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:603)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1465)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1438){code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months