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>
<groupId>org.wildfly</groupId>
<artifactId>wildfly-arquillian-container-remote</artifactId>
<version>${wildfly.version}</version>
<scope>test</scope>
</dependency>
Doesn't actually exist in maven central. There may be just some small
tweaks needed.
John
On Mon, Aug 17, 2015 at 7:16 AM Gerhard Petracek <gerhard.petra...@gmail.com>
wrote:
> 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]
>
> https://builds.apache.org/view/A-D/view/DeltaSpike/job/DeltaSpike_Wildfly_8.2/
> [3]
>
> https://builds.apache.org/view/A-D/view/DeltaSpike/job/DeltaSpike_Wildfly_9.0/
> [4] https://issues.apache.org/jira/browse/DELTASPIKE-945
>
>
>
> 2015-08-17 4:06 GMT+02:00 John D. Ament <johndam...@apache.org>:
>
> > 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
> >
>
