[10:09] <aslak> one example from the JavaOne demo: I had ran the example with jrebel earlier and it worked during preparation.
[10:10] <aslak> but not during the demo, because at demo time i had disabled the extension and ran a few other tests, then enabled it again. strange exceptions started to happen
[10:10] == mnovak [mnovak@nat/redhat/x-vnphfxzlziqohqfq] has joined #jbosstesting
[10:10] <aslak> the reason was that i hadn't cleaned up target, so the extension falsely found the old deployment metadata and assumed it was deployed
[10:11] <blabno> aslak: that's what i suspected
[10:11] == chm007 cmoulliar@ip-83-134-24-63.dsl.scarlet.be has joined #jbosstesting
[10:11] <blabno> aslak: devs need to remember to cleanup target
[10:12] <aslak> just wondering if there is some kind of check we can do to know if we're running within the same 'run' or not
[10:12] <aslak> basically knowing if what we assume is deployed is actually deployed.
[10:13] <aslak> pr spi now, we can't check if a deployment is deployed
[10:13] <aslak> but can we detect this in some other way
[10:15] <blabno> aslak: we could add servlet that would return deployments checksum
[10:15] <blabno> same as in metadata
[10:15] <aslak> hmm.. that's an option
[10:16] <aslak> we have the ProtocolMetadata stored, so we know the details of where that should be deployed
[10:16] <aslak> ip/port/context