On Oct 26, 2008, at 1:36 AM, Helmut Denk wrote:
this is interesting stuff and i am
quite sure that i will need something
like that too.
Phil Messenger wrote:
Deploy can be invoked on it's own, in which case it deploys a
snapshot
build to a snapshot repository.
some notes on 'terminology':
i think 'upload to artifact-repositories' is called 'publish' in
ivy-terms.
@see http://ant.apache.org/ivy/history/latest-milestone/use/
publish.html
(the use of the term 'publish' seems to be ambiguous in ivy,
as the term 'published artifacts' is also used for describing what
the publications-section of the module-descriptor is for)
in 'my-speek' i call 'publish-snapshot' what phil calles
'deploy a snapshot build to a snapshot repository'.
i use the term 'deploy' for triggering the deployment of
'published artifacts' to the runtime-system(s) (appserver).
in gradle the 'publish'-related tasks are called 'uploadLibs' and
'uploadDist' - if i understand it right. one can also find use of the
term 'install' in other build-systems.
it may be of value to establish some basic gradle-rules regarding
terminology ...
I agree that we should define our terminology here.
Maven:
install -> storing artifacts to local machine cache
deploy -> storing artifacts to remote repository
Ivy:
publish -> storing artifacts to wherever
Gradle:
upload -> storing artifacts to wherever
For me deploying has the meaning of putting it into an app server.
Should we stick with the current Gradle terminology or should we use
publish instead of upload for example?
- Hans
--
Hans Dockter
Gradle Project lead
http://www.gradle.org
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
