I think it makes sense to test against kind of the latest EE6 and latest EE7
JBoss versions.
If AS7 is unmaintained then we should drop it. No need to support old
containers with known bugs which will never get any fixes anymore.
LieGrue,
strub
> Am 02.04.2017 um 21:01 schrieb John D. Ament :
>
Yes AS7 doesn't work on Java 8. EAP6 does though so you can use a weld
patch AFAIK.
What do you want someone to update the poms with?
On Apr 2, 2017 14:15, "Mark Struberg" wrote:
> Meant to write "require Java7"
>
> Lg,
> Strub
>
> > Am 02.04.2017 um 14:35 schrieb John D. Ament :
> >
> > Are y
Meant to write "require Java7"
Lg,
Strub
> Am 02.04.2017 um 14:35 schrieb John D. Ament :
>
> Are you running Java 8 as your JVM?
>
> John
>
> On Sun, Apr 2, 2017 at 8:24 AM Mark Struberg
> wrote:
>
>> hi folks!
>>
>> mvn clean install -Pjbossas-build-managed-7 | tee mvn-jbossas_7.log
>>
>
Yes, does JbossAS in that old version require java8?
Is there any EE6 version which is more recent?
Can some1 from JBoss plz update the poms?
Txs and LieGrue,
Strub
> Am 02.04.2017 um 14:35 schrieb John D. Ament :
>
> Are you running Java 8 as your JVM?
>
> John
>
> On Sun, Apr 2, 2017 at 8:2
Are you running Java 8 as your JVM?
John
On Sun, Apr 2, 2017 at 8:24 AM Mark Struberg
wrote:
> hi folks!
>
> mvn clean install -Pjbossas-build-managed-7 | tee mvn-jbossas_7.log
>
> This gets stuck whenever I run it. Used to work in the (maybe distant)
> past.
> Any idea?
>
> output is
>
> -
hi folks!
mvn clean install -Pjbossas-build-managed-7 | tee mvn-jbossas_7.log
This gets stuck whenever I run it. Used to work in the (maybe distant) past.
Any idea?
output is
---
T E S T S
