separate deploy modules from rest extensions and transforms

[peetkes]

Is it an idea to add extra commands for deployment of the src folder (only the website and libraries if any), deployment of rest extensions and deployment of custom transforms?
So when you do deploy modules it will deploy everything
deploy rest will deploy only the rest extensions, with an extra option to just deploy a single extension if you specify the name of the extension and deploy transform will deploy only the transforms , with an extra option to just deploy a single transform when you specify the name of the transform.

[dmcassel]

Sounds like a reasonable idea to me. I'd say:

# deploy everything:
ml {env} deploy modules

# deploy just the src folder
ml {env} deploy src

# deploy properties, extensions, and transforms
ml {env} deploy rest

# deploy just extensions
ml {env} deploy ext

# deploy just one extension (--filename provides path relative to ml.rest-ext.dir)
ml {env} deploy ext --filename=foo.xqy

# deploy just transforms
ml {env} deploy transforms

# deploy just one transform
ml {env} deploy transform --filename=foo.xqy

Does that cover what you're looking for?

[peetkes]

Even better than I just did in my fork;-)

[peetkes]

Think I accidentally closed it

[dmcassel]

I'd be happy to get a pull request with the commands outlined above. :) Please make it on the dev branch if you pursue this (dev is where it will go, so that would let me get it integrated sooner).

[peetkes]

I am working on it now. You'll get the pull request as soon as I'm ready

[paxtonhare]

I already added ml deploy rest a while ago.

[grtjn]

Yes, but this goes further, upto the level of single extensions and transforms you want to get deployed..

[grtjn]

Fixed in dev (and master?)