I don't believe I said there was a need for a separate profile.
It looks like the main issue is that ${wildfly.version} also points to the
arquillian container. So an entry like this:
dependency
groupIdorg.wildfly/groupId
hi john,
we added ci-jobs for wildfly8.x several months ago and for wildfly9 some
weeks ago.
there is no need for separated profiles - see e.g. [1], [2], [3] and [4].
regards,
gerhard
[1]
https://builds.apache.org/view/A-D/view/DeltaSpike/job/DeltaSpike_Wildfly_8.1/
[2]
@john:
you didn't mention the remote-profile in your initial mail.
what we maintain actively are the build-managed profiles, because we need
them for [1].
all remote profiles are for external tests and if something doesn't work
or is missing, we need to change it.
@marvin:
the same is true for
All,
Looking at http://deltaspike.apache.org/documentation/build.html it seems
we don't build and test against Wildfly 9, only 8. One key difference is
that now the arquillian container is separately managed.
Is this simply an over sight?
John
[mailto:johndam...@apache.org]
Sent: Sunday, August 16, 2015 10:07 PM
To: deltaspike dev@deltaspike.apache.org
Subject: Wildfly 9 Tests?
All,
Looking at http://deltaspike.apache.org/documentation/build.html it seems we
don't build and test against Wildfly 9, only 8. One key difference is that now
)?
_Marvin
-Original Message-
From: John D. Ament [mailto:johndam...@apache.org]
Sent: Sunday, August 16, 2015 10:07 PM
To: deltaspike dev@deltaspike.apache.org
Subject: Wildfly 9 Tests?
All,
Looking at http://deltaspike.apache.org/documentation/build.html it seems
we don't build
