Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [che-dev] Adding Arquillian Smart Testing to Che base distribution?

So each new release build for this plugin would need an accompanying PR to our report to update the artifacts? 


On Fri, Dec 1, 2017 at 03:43 Oleksandr Garagatyi <ogaragat@xxxxxxxxxx> wrote:
I think it is possible to add this plugin by adding corresponding dependencies into assemblies of Che (master for UI part, wsagent). In this case, we would be able to not maintain the plugin by Che team and have it in the assembly. 
This does not provide pluggability described by Stevan, but it might be better than adding it to our codebase. 

On Fri, Dec 1, 2017 at 5:30 AM, Gorkem Ercan <gorkem.ercan@xxxxxxxxx> wrote:

Unfortunately assembly is the only way to distribute this but I am not sure if it has to live on Che
repository. Wouldn’t it be possible for Che assembly to pull this from maven central?

Thanks,
Gorkem

On 30 Nov 2017, at 19:05, Stevan LeMeur wrote:

Hi all,

Maybe you already noticed it, we received a PR for adding Arquillian Smart Testing into Che: https://github.com/eclipse/che/pull/7636

The PR proposes to integrate Arquillian Smart Testing as experimental features into Che, so users will get the ability to enable/disable the capabilities provided by the plugin.

While this contribution is substantial, we don't really have a process for what's going or what's not going into our base distribution and I think it is a great opportunity to discuss it.

Arquillian Smart Testing, is a Red Hat influenced tech - while we appreciate the contribution, we, as a community, should integrate it into Che base distribution, only if we think it will bring value to Che.

Another aspect is once the plugin will be integrated into Che's base distribution, it will have to be maintained. It could be maintained with the help of the contributor, but we need to feel confortable enough with having the plugin into our codebase. 

In theory, a plugin like this should be delivered independently from Che base distribution. The plugin could have its own release cycles and be installed/uninstalled by the end-users through a plugin marketplace. While this is definitely our target and we are making progress on it, we are not yet there. And until we have a plugin marketplace, we don't have a great alternative for this kind of plugin: it either goes into the base distribution of Che or it will not be very easy for the Che community to benefit from it.

I'd like to open the discussion on how we determine whether we should or should not add a plugin into our base distribution and if we think Arquillian Smart Testing should go into Che's base distribution.

My proposal would be:
- we open a discussion on che-dev mailing list during a week or so, 
- once the period is over, we proceed by a community vote.

Thoughts?

Thanks!

Stévan.


_______________________________________________
che-dev mailing list
che-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/che-dev


_______________________________________________
che-dev mailing list
che-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/che-dev




--

OLEKSANDR GARAGATYI

SENIOR SOFTWARE ENGINEER

Red Hat 

_______________________________________________
che-dev mailing list
che-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/che-dev
--

Brad Micklea // Developer Tools // 416.707.0792 

Back to the top