Uploaded image for project: 'Tools (JBoss Tools)'
  1. Tools (JBoss Tools)
  2. JBIDE-23766

Cannot launch Fuse project

    XMLWordPrintable

Details

    • Bug
    • Resolution: Cannot Reproduce
    • Major
    • 4.4.3.Final
    • 4.4.2.Final
    • cdi
    • None
    • Hide

      from Jane Murphey:

      "I downloaded JDBS 10.1.0 from the Customer Portal, added the Fuse Tools nightly update site, installed JBoss Fuse Development pack from JBoss Central, and restarted JDBS. When it restarted, I was notified there were updates available, which included JBDS 10.2.0 and the latest Fuse tooling from the nightly update site, so I updated everything on the list, and restarted JBDS again. I enabled the Fuse Tooling staging repos, added and started the CDK Development Environment, created a new project on OpenShift (OpenShift Explorer), and then created a new Fuse Integration Project using the SpringBoot on OpenShift template."
      then try to open a Camel file in Editor

      Show
      from Jane Murphey: "I downloaded JDBS 10.1.0 from the Customer Portal, added the Fuse Tools nightly update site, installed JBoss Fuse Development pack from JBoss Central, and restarted JDBS. When it restarted, I was notified there were updates available, which included JBDS 10.2.0 and the latest Fuse tooling from the nightly update site, so I updated everything on the list, and restarted JBDS again. I enabled the Fuse Tooling staging repos, added and started the CDK Development Environment, created a new project on OpenShift (OpenShift Explorer), and then created a new Fuse Integration Project using the SpringBoot on OpenShift template." then try to open a Camel file in Editor
    • Workaround Exists
    • Hide

      ensure to use a compatible SwitchYard Tooling version

      currently it is available using the latest SwitchYard Tooling available: http://download.jboss.org/jbosstools/neon/integration/updates/integration-stack/switchyard/2.3.0.CI/

      Show
      ensure to use a compatible SwitchYard Tooling version currently it is available using the latest SwitchYard Tooling available: http://download.jboss.org/jbosstools/neon/integration/updates/integration-stack/switchyard/2.3.0.CI/

    Description

      it would be nice to provide more information in log such as teh classes in inspection by CDI Core Builder

      !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)
      

      Attachments

        1. blankBlueprintPomError.png
          blankBlueprintPomError.png
          377 kB
        2. devstudio10.0ISinstalledFTplugins.png
          devstudio10.0ISinstalledFTplugins.png
          150 kB
        3. FT_blankBlueprintProj.log
          565 kB
        4. FT_FISprojectBldFail_011917.rtf
          48 kB
        5. FuseToolingInstalledSW.png
          FuseToolingInstalledSW.png
          557 kB
        6. newFuseFISProjectCreateLog.hang
          1.25 MB
        7. newFuseProjectCreateLog2.hang
          1.32 MB
        8. settings.xml
          20 kB

        Issue Links

          Activity

            People

              jmaury@redhat.com Jeff MAURY
              apupier@redhat.com Aurélien Pupier
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: