[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:
------------------------------------
Wasn't announced because I didn't think anyone had incorrectly formatted source plugins/features. Do you need me to send a note to jbosstools-dev@ ?
> 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-23767) Jenkins build for OpenShift is failing with mirror problems
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23767?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-23767:
------------------------------------------
merged to master.
jenkins is back to blue. Resolving.
> 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-23767) Jenkins build for OpenShift is failing with mirror problems
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23767?page=com.atlassian.jira.plugi... ]
Andre Dietisheim closed JBIDE-23767.
------------------------------------
Nothing for QE to verify. Closing.
> 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-20711) Changing deploy-name in component xml file will not take effect
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20711?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-20711:
-------------------------------------
I think I'll work on an upstream patch to make it so you don't have to refresh either. It's a needless action for the user.
> Changing deploy-name in component xml file will not take effect
> ---------------------------------------------------------------
>
> Key: JBIDE-20711
> URL: https://issues.jboss.org/browse/JBIDE-20711
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server, upstream
> Affects Versions: 4.3.0.CR1
> Reporter: Rob Stryker
> Assignee: Rob Stryker
> Fix For: 4.4.3.AM2
>
>
> Steps to replicate:
> 1) Create a dynamic web project TestProject
> 2) Create a server
> 3) Add/Remove action in servers view. You will see the module name is TestProject
> 4) Open the component.xml file in .settings folder and change deploy-name to some new value (RobsTest)
> 5) Add/Remove, note module name didn't change
> 6) Publish deployment, note its still deploying as TestProject
> 7) Close project, then re-open it
> 8) Add/Remove action, note the module now reads TestProject (RobsTest) (or similar)
> 9) Publish, note module is deployed as RobsTest.war
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (JBIDE-23766) ZipException in CDICoreBuilder when indexing some Camel artifacts
by Jane Murphey (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23766?page=com.atlassian.jira.plugi... ]
Jane Murphey edited comment on JBIDE-23766 at 1/19/17 12:05 PM:
----------------------------------------------------------------
Using JBDS 10.2.0.GA-v20161125-1418-B55 with Fuse Tooling 9.1.0.C1-v20170119-1320-B87 (staging repos enabled in Fuse Tooling Preferences and added to my settings.xml file), I was able to create a Fuse FIS project based on the SpringBoot on OpenShift template. (Downloading the repos took 23 mins!) Project had only warnings about Duplicating managed version 2.18.1.redhat-000007... in the pom file (can configure Maven Prefs to ignore).
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.)
Going to try to create an empty Blueprint project and run it.
was (Author: jmurphey):
Using JBDS 10.2.0.GA-v20161125-1418-B55 with Fuse Tooling 9.1.0.C1-v20170119-1320-B87 (staging repos enabled in Fuse Tooling Preferences and added to my settings.xml file), I was able to create a Fuse FIS project based on the SpringBoot on OpenShift template. (Downloading the repos took 23 mins!) Project had only warnings about Duplicating managed version 2.18.1.redhat-000007... in the pom file (can configure Maven Prefs to ignore).
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.)
> 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)
9 years, 2 months
[JBoss JIRA] (JBIDE-23766) ZipException in CDICoreBuilder when indexing some Camel artifacts
by Jane Murphey (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23766?page=com.atlassian.jira.plugi... ]
Jane Murphey edited comment on JBIDE-23766 at 1/19/17 12:04 PM:
----------------------------------------------------------------
Using JBDS 10.2.0.GA-v20161125-1418-B55 with Fuse Tooling 9.1.0.C1-v20170119-1320-B87 (staging repos enabled in Fuse Tooling Preferences and added to my settings.xml file), I was able to create a Fuse FIS project based on the SpringBoot on OpenShift template. (Downloading the repos took 23 mins!) Project had only warnings about Duplicating managed version 2.18.1.redhat-000007... in the pom file (can configure Maven Prefs to ignore).
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.)
was (Author: jmurphey):
Using JBDS 10.2.0.GA-v20161125-1418-B55 with Fuse Tooling 9.1.0.C1-v20170119-1320-B87 (staging repos enabled in Fuse Tooling Preferences and added to my settings.xml file), I was able to create a Fuse FIS project based on the SpringBoot on OpenShift template. (Downloading the repos took 23 mins!) Project had only warnings about Duplicating managed version 2.18.1.redhat-000007... in the pom file (can configure Maven Prefs to ignore).
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.
> 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)
9 years, 2 months
[JBoss JIRA] (JBIDE-23766) ZipException in CDICoreBuilder when indexing some Camel artifacts
by Jane Murphey (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23766?page=com.atlassian.jira.plugi... ]
Jane Murphey edited comment on JBIDE-23766 at 1/19/17 12:03 PM:
----------------------------------------------------------------
Using JBDS 10.2.0.GA-v20161125-1418-B55 with Fuse Tooling 9.1.0.C1-v20170119-1320-B87 (staging repos enabled in Fuse Tooling Preferences and added to my settings.xml file), I was able to create a Fuse FIS project based on the SpringBoot on OpenShift template. (Downloading the repos took 23 mins!) Project had only warnings about Duplicating managed version 2.18.1.redhat-000007... in the pom file (can configure Maven Prefs to ignore).
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.
was (Author: jmurphey):
Using JBDS 10.2.0.GA-v20161125-1418-B55 with Fuse Tooling 9.1.0.C1-v20170119-1320-B87 (staging repos enabled in Fuse Tooling Preferences and added to my settings.xml file), I was able to create a Fuse FIS project based on the SpringBoot on OpenShift template. Project had only warnings about Duplicating managed version 2.18.1.redhat-000007... in the pom file (can configure Maven Prefs to ignore).
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.
> 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)
9 years, 2 months
[JBoss JIRA] (JBIDE-23766) ZipException in CDICoreBuilder when indexing some Camel artifacts
by Jane Murphey (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23766?page=com.atlassian.jira.plugi... ]
Jane Murphey updated JBIDE-23766:
---------------------------------
Attachment: FT_FISprojectBldFail_011917.rtf
> 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)
9 years, 2 months
[JBoss JIRA] (JBIDE-23766) ZipException in CDICoreBuilder when indexing some Camel artifacts
by Jane Murphey (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23766?page=com.atlassian.jira.plugi... ]
Jane Murphey commented on JBIDE-23766:
--------------------------------------
Using JBDS 10.2.0.GA-v20161125-1418-B55 with Fuse Tooling 9.1.0.C1-v20170119-1320-B87 (staging repos enabled in Fuse Tooling Preferences and added to my settings.xml file), I was able to create a Fuse FIS project based on the SpringBoot on OpenShift template. Project had only warnings about Duplicating managed version 2.18.1.redhat-000007... in the pom file (can configure Maven Prefs to ignore).
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.
> 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_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)
9 years, 2 months