Remove the deployments module altogether?

[fabiobrz]

The deployments module seems to have no more rationale here:

• it was designed originally in the monolithic version in order to reuse application servers (EAP/WildFly) deployments.
• it was then kept in the internal version of the library in order to let both the demos submodule and integration tests depend on them.

Both the above are not requirements here in Intersmash, since there's a testsuite module which could contain the deployments sources.
BTW the testsuite filesystem structure could result in something more similar to the way currently implemented integration tests look like (e.g.: see existing WIldFly/Arquillian tests in the WIldFly testsuite).
A starting point could be what has been done here in Intersmash demos.

• Environment: testsuite
• Steps to reproduce: N/A

[dosubot]

Hi, @fabiobrz. I'm Dosu, and I'm helping the intersmash team manage their backlog. I'm marking this issue as stale.

Issue Summary:

• You suggested removing the deployments module as it no longer serves its purpose.
• Proposed moving deployment sources to the testsuite module for better alignment with integration tests.
• Referenced an example from Intersmash demos to support your proposal.
• No comments or further activity have occurred on this issue.

Next Steps:

• Please let us know if this issue is still relevant to the latest version of the intersmash repository by commenting here.
• If there is no further activity, the issue will be automatically closed in 30 days.

Thank you for your understanding and contribution!