[jboss-as7-dev] Deployment -- why marker files?
David M. Lloyd
david.lloyd at redhat.com
Tue Apr 12 12:17:35 EDT 2011
On 04/12/2011 11:14 AM, Jim Tyrrell wrote:
> Okay so great minds think alike i think, but looking at these two/three
> things:
>
> 1. touch $AS/standalone/deployments/example.war.skipdeploy
> 2. cp -r target/example.war/foo.html $AS/standalone/deployments/example.war
>
> You are copying to a different directory, that is hard to GROK.
GROK isn't an acronym :)
> 1. touch $AS/standalone/deployments/example.war.skipdeploy
> 2. cp -r target/example.war/ $AS/standalone/deployments
> 3. rm $AS/standalone/deployments/example.war.skipdeploy
>
> It is a little odd to copy the new things skipped NOT into the
> example.war.skipdeploy directory?
That's not what's happening here at all, read it again.
> 1. rm $AS/standalone/deployments/example.war.deployed
> 2. wait for $AS/standalone/deployments/example.war.undeployed file to appear
> 3. cp -r target/example.war/ $AS/standalone/deployments
> 4. touch $AS/standalone/deployments/example.war.dodeploy
>
> Above your touching a file you did not explicitly create above, again
> kinda odd.
"touch" creates a file if it doesn't exist, it's a pretty standard idiom.
> I get what you are doing I think, and I like the directory renaming as I
> came up with it independently, but the seemingly magic/gaps from one
> step the next is troublesome in getting what I am able/should do?
You can't assume that every filesystem supports directory renaming.
In any case this bikeshed has been painted numerous times... must we
cover it again here?
--
- DML
More information about the jboss-as7-dev
mailing list