I mean, if I can create a package ZIP, I should be...
# sdf
s
I mean, if I can create a package ZIP, I should be able to hand that ZIP to some other system in order to easily deploy it, yes? Otherwise, what's the point of a standalone
project:package
command?
a
Package command was created keeping in view marketplace for suiteapps specifically. This package commads respect the deploy xml of your project and only packages whats defined in deploy xml.
It also validates the project. So marketplace requires a zipped project to publish a suiteapp. And users can package and share the project also with team members if they like. Tools does not use that zipped file in any other way.
s
thanks Ali, so does
project:deploy
create its own temporary ZIP file behind the scenes in the same way
project:package
does? and to confirm,
project:deploy
does not and is not intended to use the output from
project:package
?
can I reliably use
project:package
then unzip it, then run
project:deploy
from the resulting extracted directory structure?
a
Yes deploy zips the structure behind the scenes. Yes project:deploy is not intended to use output of project:package But in java cli you can provide the zipped project as an argument of the command with -p. I think it will work. Yes you can unzip the project and deploy but keep in mind you will have to setup the account because package command doesn't zip your account info.
s
thanks Ali, that helps clarify things.