Deployable should be declarable without a context

[yagotlima]

I don't know if there is a reason for the "context" property being mandatory but my builds are working fine without it.

Since it prevents the deployment of artifacts other than war files I think it's better to make it optional.

[bmuschko]

Thanks for your pull request. Can you please also add a test case for this to DeployableIntegrationSpec?

[yagotlima]

Thanks for your pull request. Can you please also add a test case for this to DeployableIntegrationSpec?

Yes I can. I'll work on it.

[yagotlima]

So I was working on a "can deploy an ear file" test case when I realized it's gonna take longer than I thought initially.

I created a new class: DeployableEarIntegrationSpec to run this test case because it doesn't fit well inside DeployableIntegrationSpec

Turns out I can't extend AbstractIntegrationSpec because it runs tomcat and tomcat doesn't support ear files.

Before I proceed I'd like to know what is expected from this test case?

1. A "can deploy an ear file" on a new spec class that will need to install Wildfly or some other application server locally;

or

2. A "can deploy wars without context property" that will verify just that the parameter is indeed optional.

[bmuschko]

The use case we are changing here is "Can deploy a deployable (WAR or EAR or something else) without the need to specify a context". So it's really irrelevant what the deployable is. You can just go with a WAR as part of the test case. At the moment Gradle would complain about it either way if the context isn't provided.

[yagotlima]

Sorry for taking so long. Pushed a new test case just now.

[bmuschko]

Thanks for your work. It has been merged.