[JBoss JIRA] (JBIDE-23766) ZipException in CDICoreBuilder prevents build of Fuse project
by Jane Murphey (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23766?page=com.atlassian.jira.plugi... ]
Jane Murphey commented on JBIDE-23766:
--------------------------------------
Haven't tried, but I will and let you know.
> ZipException in CDICoreBuilder prevents build of Fuse project
> -------------------------------------------------------------
>
> Key: JBIDE-23766
> URL: https://issues.jboss.org/browse/JBIDE-23766
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdi
> Reporter: Aurélien Pupier
> Priority: Blocker
> Attachments: FuseToolingInstalledSW.png
>
>
> {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)
9 years, 2 months
[JBoss JIRA] (JBIDE-23766) ZipException in CDICoreBuilder prevents build of Fuse project
by Aurélien Pupier (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23766?page=com.atlassian.jira.plugi... ]
Aurélien Pupier commented on JBIDE-23766:
-----------------------------------------
[~jmurphey] Are you reproducing with other project type? (if you create a simple blank blueprint project for instance)
does the error occur everytime?
> ZipException in CDICoreBuilder prevents build of Fuse project
> -------------------------------------------------------------
>
> Key: JBIDE-23766
> URL: https://issues.jboss.org/browse/JBIDE-23766
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdi
> Reporter: Aurélien Pupier
> Priority: Blocker
> Attachments: FuseToolingInstalledSW.png
>
>
> {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)
9 years, 2 months
[JBoss JIRA] (JBIDE-21969) Show in Browser: route chooser should allow to user to choose route permanently
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21969?page=com.atlassian.jira.plugi... ]
Andre Dietisheim reassigned JBIDE-21969:
----------------------------------------
Assignee: (was: Viacheslav Kabanovich)
> Show in Browser: route chooser should allow to user to choose route permanently
> -------------------------------------------------------------------------------
>
> Key: JBIDE-21969
> URL: https://issues.jboss.org/browse/JBIDE-21969
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Andre Dietisheim
> Labels: openshift_v3, server_adapter
> Fix For: 4.4.3.AM2
>
> Attachments: route-chooser.png
>
>
> steps to reproduce:
> # ASSERT: have an apps with service and route running on OpenShift. Have it imported to your workspace
> # ASSERT: you need at least a 2nd route in the same project (ex. by having a 2nd app in the same project)
> # EXEC: launch New OpenShift 3 Server Adapter wizard
> # ASSERT: make sure that you have *Prompt for route when multiple routes available to show in browser* checked (no route permanently selected)
> # EXEC: create the adapter by picking service, local project etc.
> # EXEC: in the context menu of your new server adapter: pick Show In > Web Browser
> # ASSERT: Route chooser shows up (since there are several routes available)
> Result:
> There's no way to permanently choose a route. The route chooser will always show up (as long as I have several routes in the same project)
> !route-chooser.png!
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (JBIDE-23733) Merge .smoke and .nightly integration jobs into a single job and run them weekly
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23733?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-23733:
------------------------------------
Why not just manually trigger the weekly job, but pointed at the /staging/ bits instead of the /snapshots/ bits?
Hell, I could trigger it automatically as part of me copying the bits from /snapshots/ to /staging/, if you give me the list of jobs to run against the new staging sites. Then you'd have the FULL suite of ITests run, instead of a subset, automatically after each staged build. That might make it possible to sign off on Monday instead of Tuesday, further speeding up our release process and making us even more Agile.
> Merge .smoke and .nightly integration jobs into a single job and run them weekly
> --------------------------------------------------------------------------------
>
> Key: JBIDE-23733
> URL: https://issues.jboss.org/browse/JBIDE-23733
> 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
>
>
> Purpose:
> a) easier maintenance of jobs / tests
> b) run fewer nightly jobs so that we don't block slaves from being available for other builds / tests
> c) more frequent full integration runs (rather than once per sprint, once per week)
> Tests to merge are in this view:
> https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud...
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (JBIDE-21969) Show in Browser: route chooser should allow to user to choose route permanently
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21969?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-21969:
-------------------------------------
Fix Version/s: 4.4.3.AM2
(was: 4.4.x)
> Show in Browser: route chooser should allow to user to choose route permanently
> -------------------------------------------------------------------------------
>
> Key: JBIDE-21969
> URL: https://issues.jboss.org/browse/JBIDE-21969
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Andre Dietisheim
> Assignee: Viacheslav Kabanovich
> Labels: openshift_v3, server_adapter
> Fix For: 4.4.3.AM2
>
> Attachments: route-chooser.png
>
>
> steps to reproduce:
> # ASSERT: have an apps with service and route running on OpenShift. Have it imported to your workspace
> # ASSERT: you need at least a 2nd route in the same project (ex. by having a 2nd app in the same project)
> # EXEC: launch New OpenShift 3 Server Adapter wizard
> # ASSERT: make sure that you have *Prompt for route when multiple routes available to show in browser* checked (no route permanently selected)
> # EXEC: create the adapter by picking service, local project etc.
> # EXEC: in the context menu of your new server adapter: pick Show In > Web Browser
> # ASSERT: Route chooser shows up (since there are several routes available)
> Result:
> There's no way to permanently choose a route. The route chooser will always show up (as long as I have several routes in the same project)
> !route-chooser.png!
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (JBIDE-21935) Import application wizard: "Reuse" flow in clone wizard is ambiguous
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21935?page=com.atlassian.jira.plugi... ]
Rob Stryker updated JBIDE-21935:
--------------------------------
Fix Version/s: 4.5.0.AM1
(was: 4.4.x)
> Import application wizard: "Reuse" flow in clone wizard is ambiguous
> --------------------------------------------------------------------
>
> Key: JBIDE-21935
> URL: https://issues.jboss.org/browse/JBIDE-21935
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Max Rydahl Andersen
> Assignee: Rob Stryker
> Labels: import_wizard, openshift_v3
> Fix For: 4.5.0.AM1
>
>
> continuation of JBIDE-14828:
> with the intended behavior explained then lets make that visible to the user:
> a) don't hide/show controls in a wizard, enable/disable them.
> b) The "Reuse" is ambiguous, i.e. I read it as the clone will happen into this folder, not that it will do exactly the opposite of what the wizard says (not clone). I suggest something like "Do not clone - reuse existing folder".
> c) if not already there, add a check that what is inside the folder is actually a clone of what we are trying to clone.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (JBIDE-21869) Encoding issue in when streaming Build Logs to the console
by Dmitrii Bocharov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21869?page=com.atlassian.jira.plugi... ]
Dmitrii Bocharov updated JBIDE-21869:
-------------------------------------
Fix Version/s: 4.5.0.AM1
(was: 4.4.3.AM2)
> Encoding issue in when streaming Build Logs to the console
> ----------------------------------------------------------
>
> Key: JBIDE-21869
> URL: https://issues.jboss.org/browse/JBIDE-21869
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Fred Bricon
> Assignee: Andre Dietisheim
> Priority: Minor
> Fix For: 4.5.0.AM1
>
> Attachments: screenshot-1.png, screenshot-2.png
>
>
> Create a new nodejs app, when a build is running, in the OpenShift Explorer, right click on the build and select the Build Log... menu.
> It'll start to spew weird characters eventually :
> {noformat}
> I0315 10:38:28.749220 1 docker.go:286] Image "registry.access.redhat.com/openshift3/nodejs-010-rhel7:latest" not available locally, pulling ...
> I0315 10:39:16.195418 1 source.go:197] Downloading "https://github.com/openshift/nodejs-ex.git" ...
> I0315 10:39:19.670243 1 install.go:236] Using "assemble" installed from "image:///usr/libexec/s2i/assemble"
> I0315 10:39:19.670318 1 install.go:236] Using "run" installed from "image:///usr/libexec/s2i/run"
> I0315 10:39:19.670356 1 install.go:236] Using "save-artifacts" installed from "image:///usr/libexec/s2i/save-artifacts"
> ---> Installing application source
> ---> Building your Node application from source
> E0315 10:39:21.193046 1 util.go:91] npm info it worked if it ends with ok
> E0315 10:39:21.193216 1 util.go:91] npm info using npm(a)2.14.13
> E0315 10:39:21.193229 1 util.go:91] npm info using node(a)v0.10.40
> ...
> E0315 10:39:27.511826 1 util.go:91] npm info prepublish nodejs-ex(a)0.0.1
> ejs(a)2.4.1 node_modules/ejs
> express(a)4.13.4 node_modules/express
> ��������� escape-html(a)1.0.3
> ��������� array-flatten(a)1.1.1
> ��������� utils-merge(a)1.0.0
> ��������� cookie-signature(a)1.0.6
> ��������� merge-descriptors(a)1.0.1
> ��������� fresh(a)0.3.0
> ��������� methods(a)1.1.2
> ��������� range-parser(a)1.0.3
> ��������� vary(a)1.0.1
> ��������� path-to-regexp(a)0.1.7
> ��������� cookie(a)0.1.5
> ��������� parseurl(a)1.3.1
> ��������� content-type(a)1.0.1
> ��������� etag(a)1.7.0
> ��������� content-disposition(a)0.5.1
> ��������� serve-static(a)1.10.2
> ��������� depd(a)1.1.0
> ��������� qs(a)4.0.0
> ��������� finalhandler(a)0.4.1 (unpipe(a)1.0.0)
> ��������� on-finished(a)2.3.0 (ee-first(a)1.1.1)
> ��������� debug(a)2.2.0 (ms(a)0.7.1)
> ��������� proxy-addr(a)1.0.10 (forwarded(a)0.1.0, ipaddr.js(a)1.0.5)
> ��������� send(a)0.13.1 (destroy(a)1.0.4, statuses(a)1.2.1, ms(a)0.7.1, mime(a)1.3.4, http-errors(a)1.3.1)
> ��������� type-is(a)1.6.12 (media-typer(a)0.3.0, mime-types(a)2.1.10)
> ��������� accepts(a)1.2.13 (negotiator(a)0.5.3, mime-types(a)2.1.10)
> mongodb(a)2.1.8 node_modules/mongodb
> ��������� es6-promise(a)3.0.2
> ��������� mongodb-core(a)1.3.5 (bson(a)0.4.22, require_optional(a)1.0.0)
> ��������� readable-stream(a)1.0.31 (inherits(a)2.0.1, isarray(a)0.0.1, string_decoder(a)0.10.31, core-util-is(a)1.0.2)
> E0315 10:39:27.684535 1 util.go:91] npm info ok
> I0315 10:39:42.202321 1 sti.go:245] Using provided push secret for pushing 172.30.183.94:5000/node/nodejs-mongodb-example:latest image
> I0315 10:39:42.202361 1 sti.go:249] Pushing 172.30.183.94:5000/node/nodejs-mongodb-example:latest image ...
> {noformat}
> I'm running on OSX
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (JBIDE-21869) Encoding issue in when streaming Build Logs to the console
by Dmitrii Bocharov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21869?page=com.atlassian.jira.plugi... ]
Dmitrii Bocharov updated JBIDE-21869:
-------------------------------------
Fix Version/s: 4.4.3.AM2
(was: 4.4.x)
> Encoding issue in when streaming Build Logs to the console
> ----------------------------------------------------------
>
> Key: JBIDE-21869
> URL: https://issues.jboss.org/browse/JBIDE-21869
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Fred Bricon
> Assignee: Jeff Cantrill
> Priority: Minor
> Fix For: 4.4.3.AM2
>
> Attachments: screenshot-1.png, screenshot-2.png
>
>
> Create a new nodejs app, when a build is running, in the OpenShift Explorer, right click on the build and select the Build Log... menu.
> It'll start to spew weird characters eventually :
> {noformat}
> I0315 10:38:28.749220 1 docker.go:286] Image "registry.access.redhat.com/openshift3/nodejs-010-rhel7:latest" not available locally, pulling ...
> I0315 10:39:16.195418 1 source.go:197] Downloading "https://github.com/openshift/nodejs-ex.git" ...
> I0315 10:39:19.670243 1 install.go:236] Using "assemble" installed from "image:///usr/libexec/s2i/assemble"
> I0315 10:39:19.670318 1 install.go:236] Using "run" installed from "image:///usr/libexec/s2i/run"
> I0315 10:39:19.670356 1 install.go:236] Using "save-artifacts" installed from "image:///usr/libexec/s2i/save-artifacts"
> ---> Installing application source
> ---> Building your Node application from source
> E0315 10:39:21.193046 1 util.go:91] npm info it worked if it ends with ok
> E0315 10:39:21.193216 1 util.go:91] npm info using npm(a)2.14.13
> E0315 10:39:21.193229 1 util.go:91] npm info using node(a)v0.10.40
> ...
> E0315 10:39:27.511826 1 util.go:91] npm info prepublish nodejs-ex(a)0.0.1
> ejs(a)2.4.1 node_modules/ejs
> express(a)4.13.4 node_modules/express
> ��������� escape-html(a)1.0.3
> ��������� array-flatten(a)1.1.1
> ��������� utils-merge(a)1.0.0
> ��������� cookie-signature(a)1.0.6
> ��������� merge-descriptors(a)1.0.1
> ��������� fresh(a)0.3.0
> ��������� methods(a)1.1.2
> ��������� range-parser(a)1.0.3
> ��������� vary(a)1.0.1
> ��������� path-to-regexp(a)0.1.7
> ��������� cookie(a)0.1.5
> ��������� parseurl(a)1.3.1
> ��������� content-type(a)1.0.1
> ��������� etag(a)1.7.0
> ��������� content-disposition(a)0.5.1
> ��������� serve-static(a)1.10.2
> ��������� depd(a)1.1.0
> ��������� qs(a)4.0.0
> ��������� finalhandler(a)0.4.1 (unpipe(a)1.0.0)
> ��������� on-finished(a)2.3.0 (ee-first(a)1.1.1)
> ��������� debug(a)2.2.0 (ms(a)0.7.1)
> ��������� proxy-addr(a)1.0.10 (forwarded(a)0.1.0, ipaddr.js(a)1.0.5)
> ��������� send(a)0.13.1 (destroy(a)1.0.4, statuses(a)1.2.1, ms(a)0.7.1, mime(a)1.3.4, http-errors(a)1.3.1)
> ��������� type-is(a)1.6.12 (media-typer(a)0.3.0, mime-types(a)2.1.10)
> ��������� accepts(a)1.2.13 (negotiator(a)0.5.3, mime-types(a)2.1.10)
> mongodb(a)2.1.8 node_modules/mongodb
> ��������� es6-promise(a)3.0.2
> ��������� mongodb-core(a)1.3.5 (bson(a)0.4.22, require_optional(a)1.0.0)
> ��������� readable-stream(a)1.0.31 (inherits(a)2.0.1, isarray(a)0.0.1, string_decoder(a)0.10.31, core-util-is(a)1.0.2)
> E0315 10:39:27.684535 1 util.go:91] npm info ok
> I0315 10:39:42.202321 1 sti.go:245] Using provided push secret for pushing 172.30.183.94:5000/node/nodejs-mongodb-example:latest image
> I0315 10:39:42.202361 1 sti.go:249] Pushing 172.30.183.94:5000/node/nodejs-mongodb-example:latest image ...
> {noformat}
> I'm running on OSX
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months