@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 "WAS" and/or "WAS Liberty". regards, gerhard [1] https://builds.apache.org/view/A-D/view/DeltaSpike/ 2015-08-17 13:36 GMT+02:00 John D. Ament <[email protected]>: > 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 < > [email protected]> > 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 <[email protected]>: > > > > > 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 > > > > > >
