Currently the project uses a couple of different server types:
Remote - where you start up an external server
Managed - where you point to an externally installed server
Embedded - where a truly embedded server is used (true maven dependency on class path)
[Managed with embedded download] - feels like embedded, but a whole server distro is unpacked (often in every directory for each sample) and then treated as managed
[Embedded with embedded download] - technically embedded, but like [managed with embedded download] a whole server is unpacked (again, often for each sample).
The names of the profiles however don't accurately reflect those different types. I could rename the [Managed with embedded download] to something like "private-managed".
E.g.
wildfly-managed-arquillian
would become:
wildfly-privately-managed-arquillian
While at it, I wonder if the "-arquillian" suffix is really needed. Perhaps just wildly-privately-managed would be a better profile name?
arjantijms
commented
7 years ago
Hi,
Currently the project uses a couple of different server types:
The names of the profiles however don't accurately reflect those different types. I could rename the [Managed with embedded download] to something like "private-managed".
E.g.
wildfly-managed-arquillianwould become:
wildfly-privately-managed-arquillianWhile at it, I wonder if the "-arquillian" suffix is really needed. Perhaps just
wildly-privately-managedwould be a better profile name?Thoughts?