Looks like most folks are in fav. of Option 3)

-M

On Thu, Jul 25, 2013 at 5:03 PM, Daniel Bevenius <daniel.bevenius@gmail.com> wrote:

+1 for option 3

On 25 July 2013 16:53, Matthias Wessendorf <matzew@apache.org> wrote:

On Sun, Jul 14, 2013 at 4:23 AM, Douglas Campos <qmx@qmx.me> wrote:

On Fri, Jul 12, 2013 at 03:45:21PM +0200, Karel Piwko wrote:
> 3/ Skip integration tests by default. No "container" profile is activated by
> default, skipITs=true by default. Activate container profile in Travis and QE
> machines only.

+1, and kinda no-brainer - requiring an entire container to be available
during normal workflow is painful :P

+1 on option 3)

 

> Would need to activate a Maven profile for test development. Travis will
> still bug developers if something fails ;-)

And this was the biggest reason I was one of those who wanted this to
always live in a separate repo ;)

--
qmx

_______________________________________________
aerogear-dev mailing list
aerogear-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev

--
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf

_______________________________________________
aerogear-dev mailing list
aerogear-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev

_______________________________________________
aerogear-dev mailing list
aerogear-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev

--
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf