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
Now that IBM finally got an EE7 server certified
(http://www.oracle.com/technetwork/java/javaee/overview/compatibility-jsp-136984.html
)... does it make sense to add them to the suite (particularly if we are going
to add Wildfly 9)?
_Marvin
-Original Message-
From: John D. Ament
Marvin,
It's definitely worth starting the conversations about.
Personally, I feel like the switch of impls between OWB and Weld may create
a lot of regression issues, but I've seen pretty quick turn around from the
devs on it (just not as quick of a release schedule).
John
On Sun, Aug 16,
