4:40 a.m.
[
https://issues.jboss.org/browse/JBIDE-23766?page=com.atlassian.jira.plugi...
]
Aurélien Pupier commented on JBIDE-23766:
-----------------------------------------
I was able to create a Fuse FIS project based on the SpringBoot on OpenShift template.
(Downloading the repos took 23 mins!)
{quote}
Project had only warnings about Duplicating managed version 2.18.1.redhat-000007... in the
pom file (can configure Maven Prefs to ignore).
{quote}
yes, known limitation. This feature need to be implemented to get rid of it:
[FUSETOOLS-2242]
{quote}
However, when I tried to run the project as a local camel context the build failed citing
"A required class was missing while executing
io.fabric8:fabric8-maven-plugin:3.1.80.redhat-000006:resource:
io/fabric8/kubernetes/api/model/KubernetesList" as the cause. See attached file
FT_FISprojectBldFail_011917.rtf. (I copied the Console output. Couldn't find the
generated .log file.)
{quote}
this looks alike some corrupted jars in .m2 or an issue during compilation of project in
Eclipse.
Please, try:
# Project --> Clean
# relaunch
# if still not working:
## close Eclipse
## clean your .m2 folder
## open eclipse
## relaunch as local camel context (and be patient as it seems that it takes a long time
on your machine)
{quote}
Going to try to create an empty Blueprint project and run it.
Was able to create a Fuse empty Blueprint project after some time, but could not run it as
local camel context. Will attach error and console logs.
{quote}
Blueprint project with camel version 2.18.1 is not "supported". With current
version it is not even working due to [OSFUSE-482]. The next productized version that will
be integrated will fix the issue.
For now, I can only recommend to use a previous Camel version.
{quote}Hitting the ZipException: invalid LOC header (bad signature)
org.jboss.tools.common.model... error. Will provide more information shortly.
{quote}
yes it is the error explaining why I open a ticket in JBDS. I initially thought that it
was impacting Fuse Tooling but as I was able to have it working on my side, this is not
the case (apart from having a more complex log file to investigate on our specific Fuse
Tooling issues)
{quote}
Had lots of trouble adding and configuring nodes (route editor very flakey, switching
location of choice and otherwise nodes back and forth inside the route container) to build
the route.
{quote}
We will need more precise details. Please open a different issue in Fuse Tooling Jira.
ZipException in CDICoreBuilder when indexing some Camel artifacts
-----------------------------------------------------------------
Key: JBIDE-23766
URL: https://issues.jboss.org/browse/JBIDE-23766
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: cdi
Affects Versions: 4.4.2.Final
Reporter: Aurélien Pupier
Assignee: Jeff MAURY
Fix For: 4.4.3.AM2
Attachments: FT_FISprojectBldFail_011917.rtf, FT_blankBlueprintProj.log,
FuseToolingInstalledSW.png, blankBlueprintPomError.png, settings.xml
it would be nice to provide more information in log such as teh classes in inspection by
CDI Core Builder
{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}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)