[
https://issues.jboss.org/browse/WFLY-11121?page=com.atlassian.jira.plugin...
]
Alexey Loubyansky commented on WFLY-11121:
------------------------------------------
I've released Galleon and WFGP 2.0.1.Final that fixes this. The PRs integrating them
for Core and WF are
WFCORE-4155
https://github.com/wildfly/wildfly-core/pull/3545
WFLY-11126
https://github.com/wildfly/wildfly/pull/11719
The integration tests in Core CI fail due to the Galleon and WFGP version conflict between
WildFly Core and WildFly Full. There are two ways to proceed:
1) merge the corresponding PR for WildFly wildfly/wildfly#11719;
2) include WildFly provisioning plugin into Servlet feature-pack and not inherit it from
Core.
Either way it requires a change in WildFly Full build though.
CI - Master linux JDK 11 job - compilation fails - forked embedded
process has failed
--------------------------------------------------------------------------------------
Key: WFLY-11121
URL:
https://issues.jboss.org/browse/WFLY-11121
Project: WildFly
Issue Type: Bug
Reporter: Rostislav Svoboda
Assignee: Alexey Loubyansky
Priority: Blocker
Labels: Java11
Compilation of Master linux JDK 11 job fails - forked embedded process has failed.
https://ci.wildfly.org/viewType.html?buildTypeId=WF_MasterLinuxJdk11
{code}
[Step 2/3] [ERROR] Failed to execute goal
org.wildfly.galleon-plugins:wildfly-galleon-maven-plugin:
2.0.0.Final:generate-feature-specs (feature-spec-build) on project
wildfly-servlet-galleon-pack:
Feature spec generator failed: Forked embedded process has failed -> [Help 1]
{code}
My local machine runs are passing for me, using {{java version "11" 2018-09-25
(build 11+28)}}
This fail can be related to VMs setup on TeamCity, another option can be galleon related
issue.
CCing also [~aloubyansky]
We need to have valid Java 11 runs on upstream to guard proper functionality of WildFly.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)