Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jakartaee-tck-dev] Is Arquillian still alive?

I'm sorry, but I don't see any benefit in using Arquillian even more if we have to now get it in Jakarta and maintain it.

This is not really what's difficult in TCK architecture.
And in essence it does not change anything.

There is currently an interface vendors have to implement to start the server and do the deployment. When it's done, no other work is needed.
Moving away from this interface to use Arquillian's interface isn't going to make TCK simpler.

Splitting TCK to make them easier to use like CDI, BVal for instance is a good thing.
It's also a way to move forward with profiles because we'll be able to compose the TCK more easily



On Sat, Oct 9, 2021 at 4:59 PM Reza Rahman <reza_rahman@xxxxxxxxx> wrote:
I have a related but somewhat separate query.

What about getting the Arquillian project donated to EE4J? Who do we ask at Red Hat about this? I would be happy to lead such a project since it would not technically be a specification with IP flow concerns I am pretty sure there is enough people in the community that would sign up to be committers. In my view, this is the best way of making the project more active and more aligned to Jakarta EE/MicroProfile than it has been after the original project leadership left.

Could someone from Red Hat kindly comment?

Reza Rahman
Jakarta EE Ambassador, Author, Blogger, Speaker

Please note views expressed here are my own as an individual community member and do not reflect the views of my employer.
 

From: jakartaee-tck-dev <jakartaee-tck-dev-bounces@xxxxxxxxxxx> on behalf of Olivier Lamy <olamy@xxxxxxxxxxx>
Sent: Tuesday, October 5, 2021 3:54 AM
To: jakartaee-tck developer discussions
Subject: [jakartaee-tck-dev] Is Arquillian still alive?
 
Hi,
We discussed using arquillian which sounds like a good idea.
I started looking at Jetty support but I have a bit of concern on the project.
last commit 31/03/2017 [1]
and tomcat support is not better [2]

I guess we have some contacts here @ redhat to ask if
maintenance/upgrade is scheduled?
As Jetty committer I'm happy to do the job on jetty support.

Toughts?

cheers
--
Olivier
[1] https://github.com/arquillian/arquillian-container-jetty
[2] https://github.com/arquillian/arquillian-container-tomcat
_______________________________________________
jakartaee-tck-dev mailing list
jakartaee-tck-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakartaee-tck-dev
_______________________________________________
jakartaee-tck-dev mailing list
jakartaee-tck-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakartaee-tck-dev

Back to the top