[JBoss JIRA] (JBIDE-23767) Jenkins build for OpenShift is failing with mirror problems
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23767?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-23767:
------------------------------------
Announcement, a few days after the fact. :)
http://lists.jboss.org/pipermail/jbosstools-dev/2017-January/011819.html
> Jenkins build for OpenShift is failing with mirror problems
> -----------------------------------------------------------
>
> Key: JBIDE-23767
> URL: https://issues.jboss.org/browse/JBIDE-23767
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.3.AM1
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Priority: Critical
> Labels: build
> Fix For: 4.4.3.AM2
>
>
> Starting with [#1782|https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JBossTools/view/JBossTools_Master/job/jbosstools-openshift_master/1782/] jenkins build for OpenShift started to fail with problems in the mirror tool (basic maven build competes successfully):
> {code}
> Results :
> Tests run: 15, Failures: 0, Errors: 0, Skipped: 0
> [INFO] All tests passed!
> [INFO]
> [INFO] --- tycho-p2-extras-plugin:0.26.0:compare-version-with-baselines (default) @ org.jboss.tools.openshift.cdk.server.test ---
> [INFO] Skipped
> [INFO] ------------------------------------------------------------------------
> [INFO] Reactor Summary:
> [INFO]
> [INFO] openshift.tests .................................... SUCCESS [ 1.115 s]
> [INFO] org.jboss.tools.openshift.egit.test ................ SUCCESS [ 20.698 s]
> [INFO] org.jboss.tools.openshift.express.test ............. SUCCESS [ 17.420 s]
> [INFO] org.jboss.tools.openshift.test ..................... SUCCESS [ 40.148 s]
> [INFO] org.jboss.tools.openshift.cdk.server.test .......... SUCCESS [ 17.296 s]
> [INFO] ------------------------------------------------------------------------
> [INFO] BUILD SUCCESS
> [INFO] ------------------------------------------------------------------------
> [INFO] Total time: 02:20 min
> [INFO] Finished at: 2017-01-18T05:49:08-05:00
> [INFO] Final Memory: 68M/657M
> [INFO] ------------------------------------------------------------------------
> Terminating xvnc.
> $ vncserver -kill :91
> Killing Xvnc process ID 589
> Checking console output
> /qa/hudson_master/hudson_home/hudson_workspace/jobs/jbosstools-openshift_master/builds/1788/log:
> [WARNING] Mirror tool: Problems resolving provisioning plan.: [Unable to satisfy dependency from v20170118-1044.JBoss Tools OpenShift Nightly Build Update Site 1.0.0._F_A8ccKm-FVF2YSFS8veUq9Grd2 to org.jboss.tools.openshift.js.feature.source.feature.group [1.0.0.v20161116-1518].; Unable to satisfy dependency from v20170118-1044.JBoss Tools OpenShift Nightly Build Update Site 1.0.0._F_A8ccKm-FVF2YSFS8veUq9Grd2 to org.jboss.tools.openshift.js.feature.feature.group [1.0.0.v20161116-1518].; Unable to satisfy dependency from v20170118-1044.JBoss Tools OpenShift Nightly Build Update Site 1.0.0._F_A8ccKm-FVF2YSFS8veUq9Grd2 to org.jboss.tools.openshift.test.feature.source.feature.group [3.3.1.v20161124-1528].; Unable to satisfy dependency from v20170118-1044.JBoss Tools OpenShift Nightly Build Update Site 1.0.0._F_A8ccKm-FVF2YSFS8veUq9Grd2 to org.jboss.tools.openshift.cdk.test.feature.feature.group [3.3.1.v20160928-2042].; Unable to satisfy dependency from v20170118-1044.JBoss Tools OpenShift Nightly Build Update Site 1.0.0._F_A8ccKm-FVF2YSFS8veUq9Grd2 to org.jboss.tools.openshift.feature.feature.group [3.3.1.v20161202-0851].; Unable to satisfy dependency from v20170118-1044.JBoss Tools OpenShift Nightly Build Update Site 1.0.0._F_A8ccKm-FVF2YSFS8veUq9Grd2 to org.jboss.tools.openshift.express.test.feature.feature.group [3.3.1.v20160919-1711].; Unable to satisfy dependency from v20170118-1044.JBoss Tools OpenShift Nightly Build Update Site 1.0.0._F_A8ccKm-FVF2YSFS8veUq9Grd2 to org.jboss.tools.openshift.egit.integration.feature.feature.group [3.3.1.v20160919-1711].; Unable to satisfy dependency from v20170118-1044.JBoss Tools OpenShift Nightly Build Update Site 1.0.0._F_A8ccKm-FVF2YSFS8veUq9Grd2 to org.jboss.tools.openshift.egit.integration.test.feature.feature.group [3.3.1.v20160919-1711].; Unable to satisfy dependency from v20170118-1044.JBoss Tools OpenShift Nightly Build Update Site 1.0.0._F_A8ccKm-FVF2YSFS8veUq9Grd2 to org.jboss.tools.openshift.feature.source.feature.group [3.3.1.v20161202-0851].; Unable to satisfy dependency from v20170118-1044.JBoss Tools OpenShift Nightly Build Update Site 1.0.0._F_A8ccKm-FVF2YSFS8veUq9Grd2 to org.jboss.tools.openshift.egit.integration.feature.source.feature.group [3.3.1.v20160919-1711].; Unable to satisfy dependency from v20170118-1044.JBoss Tools OpenShift Nightly Build Update Site 1.0.0._F_A8ccKm-FVF2YSFS8veUq9Grd2 to org.jboss.tools.openshift.test.feature.feature.group [3.3.1.v20161124-1528].; Unable to satisfy dependency from v20170118-1044.JBoss Tools OpenShift Nightly Build Update Site 1.0.0._F_A8ccKm-FVF2YSFS8veUq9Grd2 to org.jboss.tools.openshift.express.feature.source.feature.group [3.3.1.v20161117-0751].; Unable to satisfy dependency from v20170118-1044.JBoss Tools OpenShift Nightly Build Update Site 1.0.0._F_A8ccKm-FVF2YSFS8veUq9Grd2 to org.jboss.tools.openshift.cdk.feature.feature.group [3.3.1.v20161025-0131].; Unable to satisfy dependency from v20170118-1044.JBoss Tools OpenShift Nightly Build Update Site 1.0.0._F_A8ccKm-FVF2YSFS8veUq9Grd2 to org.jboss.tools.openshift.egit.integration.test.feature.source.feature.group [3.3.1.v20160919-1711].; Unable to satisfy dependency from v20170118-1044.JBoss Tools OpenShift Nightly Build Update Site 1.0.0._F_A8ccKm-FVF2YSFS8veUq9Grd2 to org.jboss.tools.openshift.cdk.test.feature.source.feature.group [3.3.1.v20160928-2042].; Unable to satisfy dependency from v20170118-1044.JBoss Tools OpenShift Nightly Build Update Site 1.0.0._F_A8ccKm-FVF2YSFS8veUq9Grd2 to org.jboss.tools.openshift.express.test.feature.source.feature.group [3.3.1.v20160919-1711].; Unable to satisfy dependency from v20170118-1044.JBoss Tools OpenShift Nightly Build Update Site 1.0.0._F_A8ccKm-FVF2YSFS8veUq9Grd2 to org.jboss.tools.openshift.express.feature.feature.group [3.3.1.v20161117-0751].; Unable to satisfy dependency from v20170118-1044.JBoss Tools OpenShift Nightly Build Update Site 1.0.0._F_A8ccKm-FVF2YSFS8veUq9Grd2 to org.jboss.tools.openshift.cdk.feature.source.feature.group [3.3.1.v20161025-0131].]
> Build step 'Jenkins Text Finder' changed build result to FAILURE
> Archiving artifacts
> Recording test results
> [description-setter] Description set:
> Sending e-mails to: jbosstools-builds(a)lists.jboss.org adietish(a)redhat.com jcantril(a)redhat.com fbricon(a)redhat.com slkabanovich(a)gmail.com
> Notifying upstream projects of job completion
> Finished: FAILURE
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (JBIDE-23757) Thread deadlock when starting Eclipse
by Cody Lerum (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23757?page=com.atlassian.jira.plugi... ]
Cody Lerum commented on JBIDE-23757:
------------------------------------
Ran into this as well and going to the nightly builds today resolved it.
> Thread deadlock when starting Eclipse
> -------------------------------------
>
> Key: JBIDE-23757
> URL: https://issues.jboss.org/browse/JBIDE-23757
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.4.2.Final
> Environment: MacOS Sierra, JDK 1.8.0_112
> Reporter: Jon Kranes
> Assignee: Rob Stryker
> Fix For: 4.4.3.AM2
>
>
> Steps to reproduce:
> * Install latest Eclipse (Neon 4.6.2) (also tested with Spring ToolSuite 3.8.3 with same result)
> * Install JBoss AS, Wildfly & EAP Server Tools from JBoss Tools 4.4.2 Final
> * Add Wildfly 10.x runtime to Eclipse (tested 10.0 and 10.1 with same results)
> * Add Wildfly 10.x server to Eclipse
> * Create a default Maven Web App project
> * Add the web app project to the Wildfly server
> * Exit Eclipse and restart
> Eclipse hangs on startup with a thread deadlock. Eclipse "Progress" window shows "Registering Listeners" which never completes and blocks other Eclipse startup tasks. At this point Eclipse cannot exit and must be force-quit.
> Thread dump output from jvisualvm shows a thread deadlock:
> Found one Java-level deadlock:
> =============================
> "Thread-8":
> waiting to lock monitor 0x000000011fe4e758 (object 0x0000000782b7aa00, a org.eclipse.wst.server.core.internal.Server),
> which is held by "Worker-0"
> "Worker-0":
> waiting to lock monitor 0x0000000101a566e8 (object 0x0000000782b7aa70, a org.jboss.ide.eclipse.as.core.server.UnitedServerListenerManager),
> which is held by "Thread-8"
> Java stack information for the threads listed above:
> ===================================================
> "Thread-8":
> at org.eclipse.wst.server.core.internal.Server.getServerNotificationManager(Server.java:1034)
> - waiting to lock <0x0000000782b7aa00> (a org.eclipse.wst.server.core.internal.Server)
> at org.eclipse.wst.server.core.internal.Server.removeServerListener(Server.java:697)
> at org.jboss.ide.eclipse.as.core.server.UnitedServerListenerManager.protectAddManagerAsListeners(UnitedServerListenerManager.java:152)
> - locked <0x0000000782b7aa70> (a org.jboss.ide.eclipse.as.core.server.UnitedServerListenerManager)
> at org.jboss.ide.eclipse.as.core.server.UnitedServerListenerManager.initializeManager(UnitedServerListenerManager.java:81)
> at org.jboss.ide.eclipse.as.core.server.UnitedServerListenerManager.access$1(UnitedServerListenerManager.java:73)
> at org.jboss.ide.eclipse.as.core.server.UnitedServerListenerManager$1.run(UnitedServerListenerManager.java:68)
> "Worker-0":
> at org.jboss.ide.eclipse.as.core.server.UnitedServerListenerManager.addListener(UnitedServerListenerManager.java:109)
> - waiting to lock <0x0000000782b7aa70> (a org.jboss.ide.eclipse.as.core.server.UnitedServerListenerManager)
> at org.jboss.ide.eclipse.as.core.JBossServerCorePlugin.start(JBossServerCorePlugin.java:74)
> at org.eclipse.osgi.internal.framework.BundleContextImpl$3.run(BundleContextImpl.java:774)
> at org.eclipse.osgi.internal.framework.BundleContextImpl$3.run(BundleContextImpl.java:1)
> at java.security.AccessController.doPrivileged(Native Method)
> at org.eclipse.osgi.internal.framework.BundleContextImpl.startActivator(BundleContextImpl.java:767)
> at org.eclipse.osgi.internal.framework.BundleContextImpl.start(BundleContextImpl.java:724)
> at org.eclipse.osgi.internal.framework.EquinoxBundle.startWorker0(EquinoxBundle.java:932)
> at org.eclipse.osgi.internal.framework.EquinoxBundle$EquinoxModule.startWorker(EquinoxBundle.java:309)
> at org.eclipse.osgi.container.Module.doStart(Module.java:581)
> at org.eclipse.osgi.container.Module.start(Module.java:449)
> at org.eclipse.osgi.framework.util.SecureAction.start(SecureAction.java:470)
> at org.eclipse.osgi.internal.hooks.EclipseLazyStarter.postFindLocalClass(EclipseLazyStarter.java:107)
> at org.eclipse.osgi.internal.loader.classpath.ClasspathManager.findLocalClass(ClasspathManager.java:529)
> at org.eclipse.osgi.internal.loader.ModuleClassLoader.findLocalClass(ModuleClassLoader.java:325)
> at org.eclipse.osgi.internal.loader.BundleLoader.findLocalClass(BundleLoader.java:345)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:423)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:372)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:364)
> at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:161)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> at org.eclipse.osgi.internal.framework.EquinoxBundle.loadClass(EquinoxBundle.java:564)
> at org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.createExecutableExtension(RegistryStrategyOSGI.java:174)
> at org.eclipse.core.internal.registry.ExtensionRegistry.createExecutableExtension(ExtensionRegistry.java:905)
> at org.eclipse.core.internal.registry.ConfigurationElement.createExecutableExtension(ConfigurationElement.java:243)
> at org.eclipse.core.internal.registry.ConfigurationElementHandle.createExecutableExtension(ConfigurationElementHandle.java:55)
> at org.eclipse.wst.server.core.internal.ServerType.createServerDelegate(ServerType.java:91)
> at org.eclipse.wst.server.core.internal.Server.getDelegate(Server.java:506)
> - locked <0x0000000782b7aa00> (a org.eclipse.wst.server.core.internal.Server)
> at org.eclipse.wst.server.core.internal.Server.getChildModules(Server.java:2634)
> at org.eclipse.wst.server.core.internal.Server.visitModule(Server.java:3058)
> at org.eclipse.wst.server.core.internal.Server.visit(Server.java:3039)
> at org.eclipse.wst.server.core.internal.Server.getAllModules(Server.java:1542)
> at org.eclipse.wst.server.ui.internal.cnf.ServersView2$3.run(ServersView2.java:189)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> Found 1 deadlock.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (JBIDE-23734) dedupe vpe unit test jobs / migrate vpe builds to CCI
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23734?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-23734:
------------------------------------
I agree: for all build and PR jobs, we should be running the {color:green}*QUICK RUNNING*{color} Unit and UI (type 1 and 2) tests.
Then once a week we can run the {color:red}*SLOW RUNNING*{color} ITests (type 3 and 4).
Thanks for moving the views!
So... I guess the next step is to dedupe the .prcheck jobs [1] vs. the -Pull-Request jobs [2] ?
[1] https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud...
[2] https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud...
We should decide if it makes sense to have 1 job per project (server), 1 job per functional grouping (as, archives, jmx, ...), or one MATRIX job per project, broken into functional groupings (eg., like the javaee-tests job [3]). Personally, I like the matrix approach because you can re-run just the failing parts, or run the whole suite for the whole project.
[3] https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud...
> dedupe vpe unit test jobs / migrate vpe builds to CCI
> -----------------------------------------------------
>
> Key: JBIDE-23734
> URL: https://issues.jboss.org/browse/JBIDE-23734
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, integration-tests
> Affects Versions: 4.4.3.AM1
> Reporter: Nick Boldt
> Assignee: Rastislav Wagner
> Fix For: 4.4.3.Final
>
>
> There are four VPE unit test jobs. We probably only need 2 of those.
> These both run on multiple OSes:
> https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud...
> https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS...
> These probably run the same unit tests, but against master or 4.4.x branches, and are called from the VPE build jobs [1], [2] on Boston MW Jenkins (because the tests were failing to run in Boston):
> https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud...
> https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud...
> [1] http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-vpe_master/
> [2] http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-vpe_4.4.neon/
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (JBTIS-1023) Features and plugins for Fuse tooling have various versions
by Lars Heinemann (JIRA)
[ https://issues.jboss.org/browse/JBTIS-1023?page=com.atlassian.jira.plugin... ]
Lars Heinemann commented on JBTIS-1023:
---------------------------------------
I already provided a PR to return to old naming style without the need to revert the parent pom version.
> Features and plugins for Fuse tooling have various versions
> -----------------------------------------------------------
>
> Key: JBTIS-1023
> URL: https://issues.jboss.org/browse/JBTIS-1023
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Components: build, distribution
> Affects Versions: 10.1.0.CR1
> Reporter: Andrej Podhradsky
> Assignee: Lars Heinemann
> Priority: Blocker
>
> |org.fusesource.ide.camel.editor.feature|9.1.0.CR1-v20170120-1811-B91|
> |org.fusesource.ide.core.feature|9.1.0.CR1-v20170120-1811-B91|
> |org.fusesource.ide.jmx.feature|9.1.0.CR1-v20170103-1319-B91|
> |org.fusesource.ide.server.extensions.feature|9.1.0.CR1-v20170105-1331-B91|
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (JBIDE-23811) ZipException in CDICoreBuilder when indexing some Maven artifacts
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23811?page=com.atlassian.jira.plugi... ]
Jeff MAURY commented on JBIDE-23811:
------------------------------------
I cannot reproduce with only a Maven project. How come the CDI builder will be invoked on a Maven project ? I enabled CDI on the project and then the CDI builder appears in the list of builders but even if I do a clean on the project then I can't get the error.
> ZipException in CDICoreBuilder when indexing some Maven artifacts
> -----------------------------------------------------------------
>
> Key: JBIDE-23811
> URL: https://issues.jboss.org/browse/JBIDE-23811
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdi
> Reporter: Aurélien Pupier
> Assignee: Jeff MAURY
> Fix For: 4.4.3.Final
>
>
> it would be nice to provide more information in log such as the classes in inspection by CDI Core Builder.
> Also if there are some issues with those jars, please report bugs to them.
> {noformat}
> !ENTRY org.jboss.tools.common.core 4 0 2017-01-17 11:17:20.815
> !MESSAGE invalid LOC header (bad signature)
> !STACK 0
> java.util.zip.ZipException: invalid LOC header (bad signature)
> at java.util.zip.ZipFile.read(Native Method)
> at java.util.zip.ZipFile.access$1400(ZipFile.java:60)
> at java.util.zip.ZipFile$ZipFileInputStream.read(ZipFile.java:717)
> at java.util.zip.ZipFile$ZipFileInflaterInputStream.fill(ZipFile.java:419)
> at java.util.zip.InflaterInputStream.read(InflaterInputStream.java:158)
> at java.io.BufferedInputStream.fill(BufferedInputStream.java:246)
> at java.io.BufferedInputStream.read1(BufferedInputStream.java:286)
> at java.io.BufferedInputStream.read(BufferedInputStream.java:345)
> at java.io.DataInputStream.readFully(DataInputStream.java:195)
> at java.io.DataInputStream.readFully(DataInputStream.java:169)
> at org.jboss.jandex.Indexer.verifyMagic(Indexer.java:433)
> at org.jboss.jandex.Indexer.index(Indexer.java:689)
> at org.jboss.tools.common.core.jandex.JandexUtil.createJarIndex(JandexUtil.java:56)
> at org.jboss.tools.common.core.jandex.JandexUtil.hasAnnotation(JandexUtil.java:104)
> at org.jboss.tools.cdi.internal.core.scanner.lib.BeanArchiveDetector.hasAnnotatedBeans(BeanArchiveDetector.java:276)
> at org.jboss.tools.cdi.internal.core.scanner.lib.BeanArchiveDetector.resolve(BeanArchiveDetector.java:203)
> at org.jboss.tools.cdi.internal.core.scanner.lib.ClassPathMonitor.detectBeanModule(ClassPathMonitor.java:150)
> at org.jboss.tools.cdi.internal.core.scanner.lib.ClassPathMonitor.process(ClassPathMonitor.java:106)
> at org.jboss.tools.cdi.core.CDICoreBuilder.build(CDICoreBuilder.java:215)
> at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:735)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:206)
> at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:246)
> at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:301)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:304)
> at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:360)
> at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:383)
> at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:144)
> at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:235)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> {noformat}
> {noformat}
> !ENTRY org.jboss.tools.common.model 4 0 2017-01-25 16:11:53.722
> !MESSAGE Exception occurs when reading C:\Users\Aurelien Pupier\.m2\repository\org\apache\aries\blueprint\org.apache.aries.blueprint.core\1.7.1\org.apache.aries.blueprint.core-1.7.1.jar
> !STACK 0
> java.util.zip.ZipException: invalid LOC header (bad signature)
> at java.util.zip.ZipFile.read(Native Method)
> at java.util.zip.ZipFile.access$1400(Unknown Source)
> at java.util.zip.ZipFile$ZipFileInputStream.read(Unknown Source)
> at java.util.zip.ZipFile$ZipFileInflaterInputStream.fill(Unknown Source)
> at java.util.zip.InflaterInputStream.read(Unknown Source)
> at java.io.BufferedInputStream.fill(Unknown Source)
> at java.io.BufferedInputStream.read1(Unknown Source)
> at java.io.BufferedInputStream.read(Unknown Source)
> at org.jboss.tools.common.model.filesystems.impl.JarAccess.getContent(JarAccess.java:235)
> at org.jboss.tools.common.model.filesystems.impl.JarAccess.isTextEntry(JarAccess.java:266)
> at org.jboss.tools.common.model.filesystems.impl.JarFolderImpl.createFileObject(JarFolderImpl.java:95)
> at org.jboss.tools.common.model.filesystems.impl.JarFolderImpl.loadChildren(JarFolderImpl.java:78)
> at org.jboss.tools.common.model.impl.RegularObjectImpl.getChildByPathPart(RegularObjectImpl.java:159)
> at org.jboss.tools.common.model.filesystems.impl.JarFolderImpl.getChildByPathPart(JarFolderImpl.java:152)
> at org.jboss.tools.common.model.impl.XModelObjectImpl.getChildByPath(XModelObjectImpl.java:347)
> at org.jboss.tools.common.model.impl.XModelObjectImpl.getChildByPath(XModelObjectImpl.java:352)
> at org.jboss.tools.cdi.internal.core.scanner.lib.ClassPathMonitor.readRuntimes(ClassPathMonitor.java:286)
> at org.jboss.tools.cdi.internal.core.scanner.lib.ClassPathMonitor.process(ClassPathMonitor.java:103)
> at org.jboss.tools.cdi.core.CDICoreBuilder.build(CDICoreBuilder.java:215)
> at org.jboss.tools.cdi.core.CDICoreBuilder.<init>(CDICoreBuilder.java:101)
> at org.jboss.tools.cdi.core.CDICoreNature.load(CDICoreNature.java:420)
> at org.jboss.tools.cdi.core.CDICoreNature.resolveStorage(CDICoreNature.java:393)
> at org.jboss.tools.cdi.core.CDICoreNature.resolve(CDICoreNature.java:406)
> at org.jboss.tools.cdi.core.CDICorePlugin.getCDI(CDICorePlugin.java:165)
> at org.jboss.tools.cdi.core.CDICorePlugin$RCL.resourceChanged(CDICorePlugin.java:104)
> at org.eclipse.core.internal.events.NotificationManager$1.run(NotificationManager.java:299)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.core.internal.events.NotificationManager.notify(NotificationManager.java:289)
> at org.eclipse.core.internal.events.NotificationManager.broadcastChanges(NotificationManager.java:152)
> at org.eclipse.core.internal.resources.Workspace.broadcastPostChange(Workspace.java:374)
> at org.eclipse.core.internal.resources.Workspace.endOperation(Workspace.java:1469)
> at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:46)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (JBTIS-1023) Features and plugins for Fuse tooling have various versions
by Paul Leacu (JIRA)
[ https://issues.jboss.org/browse/JBTIS-1023?page=com.atlassian.jira.plugin... ]
Paul Leacu commented on JBTIS-1023:
-----------------------------------
Agreed - so the Fuse guys will back off the parent pom and respin their packages for this release and we can tackle the larger issue for 10.1.1
> Features and plugins for Fuse tooling have various versions
> -----------------------------------------------------------
>
> Key: JBTIS-1023
> URL: https://issues.jboss.org/browse/JBTIS-1023
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Components: build, distribution
> Affects Versions: 10.1.0.CR1
> Reporter: Andrej Podhradsky
> Assignee: Lars Heinemann
> Priority: Blocker
>
> |org.fusesource.ide.camel.editor.feature|9.1.0.CR1-v20170120-1811-B91|
> |org.fusesource.ide.core.feature|9.1.0.CR1-v20170120-1811-B91|
> |org.fusesource.ide.jmx.feature|9.1.0.CR1-v20170103-1319-B91|
> |org.fusesource.ide.server.extensions.feature|9.1.0.CR1-v20170105-1331-B91|
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months