<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">I found that the problem is with the
last commit where Stuart set copy-module-artifacts=false in
core-build/server-build.xml.<br>
<br>
Not sure why that caused me a problem. I'll look closer tomorrow.<br>
<br>
On 8/18/2014 3:11 PM, Eduardo Martins wrote:<br>
</div>
<blockquote
cite="mid:05AC44A4-9568-468C-A8F9-9A78C60833CB@redhat.com"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=ISO-8859-1">
Perhaps a clean local build of WFLY Core will help?
<div><br>
</div>
<div>—E</div>
<div><br>
<div>
<div>On 18 Aug 2014, at 19:33, Brian Stansberry <<a
moz-do-not-send="true"
href="mailto:brian.stansberry@redhat.com">brian.stansberry@redhat.com</a>>
wrote:</div>
<br class="Apple-interchange-newline">
<blockquote type="cite">
<div style="font-size: 12px; font-style: normal;
font-variant: normal; font-weight: normal; letter-spacing:
normal; line-height: normal; orphans: auto; text-align:
start; text-indent: 0px; text-transform: none;
white-space: normal; widows: auto; word-spacing: 0px;
-webkit-text-stroke-width: 0px;">On 8/18/14, 12:44 PM,
Stan Silvert wrote:<br>
<blockquote type="cite">No joy.<br>
<br>
</blockquote>
<br>
Sorry, I don't know what your issue is then. :(<br>
<br>
<blockquote type="cite">Does that build use the core
snapshot?<br>
<br>
</blockquote>
<br>
Yes. It uses the most recent result of [1] if the code
that produced<span class="Apple-converted-space"> </span><br>
that result matches wildfly-core/master's HEAD, and if it
doesn't match<span class="Apple-converted-space"> </span><br>
it runs that job first.<br>
<br>
[1]<span class="Apple-converted-space"> </span><br>
<a moz-do-not-send="true"
href="http://brontes.lab.eng.brq.redhat.com/viewType.html?buildTypeId=WildFlyCore_MasterLinux">http://brontes.lab.eng.brq.redhat.com/viewType.html?buildTypeId=WildFlyCore_MasterLinux</a><br>
<br>
<blockquote type="cite">On 8/18/2014 1:39 PM, Brian
Stansberry wrote:<br>
<blockquote type="cite">Perhaps do a full clean and
install?<br>
<br>
The CI test with the latest WildFly core master is
working fine -- I<br>
kicked it off when I got your last email and it's
through the build and<br>
into the testsuite:<br>
<br>
<a moz-do-not-send="true"
href="http://brontes.lab.eng.brq.redhat.com/viewLog.html?buildTypeId=WF_WildFlyCoreIntegration&buildId=20129">http://brontes.lab.eng.brq.redhat.com/viewLog.html?buildTypeId=WF_WildFlyCoreIntegration&buildId=20129</a><br>
<br>
On 8/18/14, 12:24 PM, Stan Silvert wrote:<br>
<blockquote type="cite">When I do that it gets worse:<br>
<br>
[ERROR] Failed to execute goal<br>
org.wildfly.core:wildfly-build-plugin:1.0.0.Alpha5-SNAPSHOT:build<br>
(create-server) on project wildfly-web-build:
Execution create-server of<br>
goal
org.wildfly.core:wildfly-build-plugin:1.0.0.Alpha5-SNAPSHOT:build<br>
failed: java.lang.RuntimeException: Could not
extract resources from<br>
artifact org.slf4j:slf4j-api:1<br>
.7.7.jbossorg-1 contents<br>
{org.jboss.spec.javax.security.auth.message:jboss-jaspi-api_1.1_spec:1.0.0.Final=org.jboss.spec.javax.security.auth.message:jboss-jaspi-api_1.1_s<br>
pec:jar:1.0.0.Final:compile,<br>
org.wildfly:wildfly-security=org.wildfly:wildfly-security:jar:9.0.0.Alpha1-SNAPSHOT:compile,<br>
org.wildfly.security:wildfly-security-manager=or<br>
g.wildfly.security:wildfly-security-manager:jar:1.0.0.Final:compile,<br>
org.jboss.aesh:aesh=org.jboss.aesh:aesh:jar:0.33.12:compile,<br>
org.wildfly.core:wildfly-domain-http-int<br>
erface:1.0.0.Alpha5-SNAPSHOT=org.wildfly.core:wildfly-domain-http-interface:jar:1.0.0.Alpha5-SNAPSHOT:compile,<br>
io.undertow:undertow-core:1.1.0.Beta6=io.undertow:undertow-<br>
core:jar:1.1.0.Beta6:compile,<br>
org.jboss.sasl:jboss-sasl:1.0.4.Final=org.jboss.sasl:jboss-sasl:jar:1.0.4.Final:compile,<br>
org.wildfly:wildfly-security:9.0.0.Alpha1-SNAPSHOT=<br>
org.wildfly:wildfly-security:jar:9.0.0.Alpha1-SNAPSHOT:compile,<br>
org.picketbox:picketbox=org.picketbox:picketbox:jar:4.0.21.Beta3:compile,
org.fusesource.jansi:jansi=org.f<br>
usesource.jansi:jansi:jar:1.9:compile,<br>
org.jboss.spec.javax.servlet.jstl:jboss-jstl-api_1.2_spec:1.1.2.Beta1=org.jboss.spec.javax.servlet.jstl:jboss-jstl-api_1.2_spec:jar<br>
:1.1.2.Beta1:compile,<br>
org.jboss.logmanager:log4j-jboss-logmanager=org.jboss.logmanager:log4j-jboss-logmanager:jar:1.1.0.Final:compile,<br>
org.picketbox:picketbox-infinispan:<br>
4.0.21.Beta3=org.picketbox:picketbox-infinispan:jar:4.0.21.Beta3:compile,
org.wildfly.core:wildfly-io=org.wildfly.core:wildfly-io:jar:1.0.0.Alpha5-SNAPSHOT:compile,<br>
org.j<br>
<br>
On 8/18/2014 1:18 PM, Brian Stansberry wrote:<br>
<blockquote type="cite">When you build master,
include -Dskip-enforce in your args to maven.<br>
That turns off the problematic transitive
dependency enforcement, which<br>
is more trouble than it is worth when dealing with
snapshots.<br>
<br>
When we bring the next release of core in, the
master pom will be<br>
updated to include the
org.wildfly.core:wildfly-launcher dependency.<br>
<br>
On 8/18/14, 12:09 PM, Stan Silvert wrote:<br>
<blockquote type="cite">Build the latest WildFly
Core master.<br>
<br>
In WildFly Full master, change the root pom to
use latest core:<br>
<version.org.wildfly.core>1.0.0.Alpha5-SNAPSHOT</version.org.wildfly.core><br>
<br>
When you build full, you will get:<br>
[WARNING] Rule 0:<br>
org.apache.maven.plugins.enforcer.BanTransitiveDependencies
failed with<br>
message:<br>
org.wildfly:wildfly-web-build:pom:9.0.0.Alpha1-SNAPSHOT<br>
org.wildfly.core:wildfly-core-build:zip:1.0.0.Alpha5-SNAPSHOT:compile<br>
has transitive dependencies:<br>
org.wildfly.core:wildfly-launcher:jar:1.0.0.Alpha5-SNAPSHOT:compile<br>
<br>
If you exclude the wildfly-launcher dependency,
the build gets even uglier.<br>
<br>
Should these two builds stay in sync somehow?
For some features, we<br>
need to be able to make changes to both builds
at the same time and see<br>
them work together.<br>
<br>
Stan<br>
<br>
<br>
<br>
_______________________________________________<br>
wildfly-dev mailing list<br>
<a class="moz-txt-link-abbreviated" href="mailto:wildfly-dev@lists.jboss.org">wildfly-dev@lists.jboss.org</a><br>
<a class="moz-txt-link-freetext" href="https://lists.jboss.org/mailman/listinfo/wildfly-dev">https://lists.jboss.org/mailman/listinfo/wildfly-dev</a><br>
<br>
</blockquote>
</blockquote>
_______________________________________________<br>
wildfly-dev mailing list<br>
<a class="moz-txt-link-abbreviated" href="mailto:wildfly-dev@lists.jboss.org">wildfly-dev@lists.jboss.org</a><br>
<a class="moz-txt-link-freetext" href="https://lists.jboss.org/mailman/listinfo/wildfly-dev">https://lists.jboss.org/mailman/listinfo/wildfly-dev</a><br>
<br>
</blockquote>
<br>
</blockquote>
<br>
_______________________________________________<br>
wildfly-dev mailing list<br>
<a moz-do-not-send="true"
href="mailto:wildfly-dev@lists.jboss.org">wildfly-dev@lists.jboss.org</a><br>
<a class="moz-txt-link-freetext" href="https://lists.jboss.org/mailman/listinfo/wildfly-dev">https://lists.jboss.org/mailman/listinfo/wildfly-dev</a><br>
<br>
</blockquote>
<br>
<br>
--<span class="Apple-converted-space"> </span><br>
Brian Stansberry<br>
Senior Principal Software Engineer<br>
JBoss by Red Hat<br>
_______________________________________________<br>
wildfly-dev mailing list<br>
<a moz-do-not-send="true"
href="mailto:wildfly-dev@lists.jboss.org">wildfly-dev@lists.jboss.org</a><br>
<a moz-do-not-send="true"
href="https://lists.jboss.org/mailman/listinfo/wildfly-dev">https://lists.jboss.org/mailman/listinfo/wildfly-dev</a></div>
</blockquote>
</div>
<br>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
wildfly-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:wildfly-dev@lists.jboss.org">wildfly-dev@lists.jboss.org</a>
<a class="moz-txt-link-freetext" href="https://lists.jboss.org/mailman/listinfo/wildfly-dev">https://lists.jboss.org/mailman/listinfo/wildfly-dev</a></pre>
</blockquote>
<br>
</body>
</html>