<div dir="ltr"><div><div><div><div>plus:<br></div>all quickstarts should have common / same testing pattern!<br>End result must be that we can do mvn clean test/integration-test -P<some profile> and it would test the quickstart.<br>
</div>If we would run this in root folder it would test all quickstarts against target wildfly.<br><br></div>When we have this, we can test quickstarts on CI and have another set of tests to make sure we didn't break anything in nightly WildFly builds.<br>
<br>--<br></div>tomaz<br></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Mon, Feb 24, 2014 at 4:14 PM, Eduardo Martins <span dir="ltr"><<a href="mailto:emartins@redhat.com" target="_blank">emartins@redhat.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">There is now a fully working set of WildFly Quickstarts at <a href="https://github.com/wildfly/quickstart" target="_blank">https://github.com/wildfly/quickstart</a> , and a set of dev friendly Maven BOMs at <a href="https://github.com/wildfly/boms" target="_blank">https://github.com/wildfly/boms</a><br>
<br>
So what’s next? Here are some ideas:<br>
<br>
* integration at <a href="http://wildfly.org" target="_blank">wildfly.org</a><br>
<br>
* upgrade existent quickstarts to take advantage of Java EE 7 new features, for instance the default managed objects such as java:comp/DefaultDataSource<br>
<br>
* add new quickstarts wrt the new Java EE 7 technologies (Batch, EE Concurrency Utilities)<br>
<br>
Thoughts?<br>
<br>
—E<br>
_______________________________________________<br>
wildfly-dev mailing list<br>
<a href="mailto:wildfly-dev@lists.jboss.org">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><br></div>