<div dir="ltr">Hey Cody,<div><br></div><div>I know Aslak and Alex Soto work on a "proxy container" that will allow you to seamlessly switch between EAP/JBossAS/WildFly:</div><div><br></div><div><a href="https://github.com/lordofthejars/arquillian-container-proxy">https://github.com/lordofthejars/arquillian-container-proxy</a></div><div><br></div><div>That impl should auto-download configured container and run in managed mode.</div><div><br></div><div>Btw the name is not set in stone yet.. :-)</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, May 4, 2015 at 1:35 PM, Cody Lerum <span dir="ltr"><<a href="mailto:cody.lerum@gmail.com" target="_blank">cody.lerum@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><p dir="ltr">Is there a good example published somewhere for users who want to use a managed container within a CI like Travis? </p>
<p dir="ltr">This is becoming an increasingly pretty popular configuration, and the easier for the users to get started and update from release to release the better.</p><span class="HOEnZb"><font color="#888888">
<p dir="ltr">-C</p></font></span><div class="HOEnZb"><div class="h5">
<div class="gmail_quote">On May 4, 2015 3:28 AM, "Lukas Fryc" <<a href="mailto:lfryc@redhat.com" target="_blank">lfryc@redhat.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">An only embedded container's advantage over managed container is a simpler test debugging - no special setup required.<div><br></div><div>I'm fine with dropping it, just in case it wasn't intentional decision to remove embedded container, we can re-introduce it.<br><div><br></div><div>~ Lukas<br><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Apr 30, 2015 at 3:47 PM, Brian Stansberry <span dir="ltr"><<a href="mailto:brian.stansberry@redhat.com" target="_blank">brian.stansberry@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Lukas,<br>
<span><br>
On 4/29/15 9:58 AM, Lukas Fryc wrote:<br>
> Hey guys,<br>
><br>
> just wondering if wildfly-arquillian-container-embedded was discontinued<br>
> with split of 9.x:<br>
><br>
> <a href="https://github.com/wildfly/wildfly-arquillian/blob/master/pom.xml#L96" target="_blank">https://github.com/wildfly/wildfly-arquillian/blob/master/pom.xml#L96</a><br>
><br>
<br>
</span>It was, yes, as wildfly-arquillian shouldn't depend on WildFly Full (to<br>
avoid a circular dependency) and WildFly Core didn't have an embedding<br>
module.<br>
<span>><br>
> When working on a re-enablement, I found out that even though arq<br>
> adapter now depends on wildfly-core/embedded, particularly<br>
> on EmbeddedServerFactory, this class has its counterpart in<br>
> wildfly/embedded as well.<br>
><br>
<br>
</span>I added the wildfly-core/embedded module in order to support the Offline<br>
CLI.[1] At this point I consider it to be an internal module, not<br>
public API. I expect that will soften over time, but for WildFly Core<br>
1.0 / WildFly Full 9.0 at least, that's what it is.<br>
<br>
[1] <a href="http://wildfly.org/news/2015/03/13/Offline-CLI/" target="_blank">http://wildfly.org/news/2015/03/13/Offline-CLI/</a><br>
<span><br>
> Question is, should be embedded arquillian container still available for<br>
> 9.x?<br>
><br>
<br>
</span>Jason Greene would need to rule on that, but I know we were ok with<br>
dropping it before. Is there much use of it?<br>
<span><br>
> If yes, I can continue and provide a PR, just I will need a bit of<br>
> guidance with what EmbeddedServerFactory it should actually use (if that<br>
> matters).<br>
><br>
<br>
</span>What API would it need from wildfly-core/embedded? Is the<br>
StandaloneServer API there adequate?<br>
<span><br>
><br>
> Cheers,<br>
><br>
> ~ Lukas<br>
><br>
> --<br>
> Lukas Fryc<br>
> AeroGear Core Developer<br>
> Red Hat<br>
><br>
><br>
</span>> _______________________________________________<br>
> wildfly-dev mailing list<br>
> <a href="mailto:wildfly-dev@lists.jboss.org" target="_blank">wildfly-dev@lists.jboss.org</a><br>
> <a href="https://lists.jboss.org/mailman/listinfo/wildfly-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/wildfly-dev</a><br>
><br>
<span><font color="#888888"><br>
<br>
--<br>
Brian Stansberry<br>
Senior Principal Software Engineer<br>
JBoss by Red Hat<br>
_______________________________________________<br>
wildfly-dev mailing list<br>
<a href="mailto:wildfly-dev@lists.jboss.org" target="_blank">wildfly-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/wildfly-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/wildfly-dev</a><br>
</font></span></blockquote></div><br></div></div></div></div>
<br>_______________________________________________<br>
wildfly-dev mailing list<br>
<a href="mailto:wildfly-dev@lists.jboss.org" target="_blank">wildfly-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/wildfly-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/wildfly-dev</a><br></blockquote></div>
</div></div></blockquote></div><br></div>