i like both: 'install' and 'publish' ivy-users will probably prefer 'publish', as their semantics would be preserved.
i use the term 'publish' for over two years now and i cant remember situations where this was not appropriate. (lucky me has no maven-builds to maintain ;-) i associate the term 'upload' with filetransfer to a remote location. this expresses only a part of the semantics. perhaps changing from 'upload' is possible in context of an overall concept for the implementation of 'snapshot', 'release' and 'deploy'. but its a breaking change in any case ... hdockter wrote: > > For me deploying has the meaning of putting it into an app server. > yes 'deploy' should be reserved for this. mavens terminology is 'off target' here. >> putting it into an app server' if deploy-logic is established in the target-systems, which is a good idea IMO, then a trigger (remote-call) is sufficient. -> trigger osgi-core to 'resolve' osgi-bundles from artifact-repositories and 'install' (he he) them. grüsse h. denk -- View this message in context: http://www.nabble.com/%22forward%22-task-dependencies---more-plugin-fun-tp20147831p20172098.html Sent from the gradle-dev mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
