On Jan 6, 2007, at 11:41 AM, Jean-Sebastien Delfino wrote:
I'm trying to understand the new modularized build scheme, and have
a few questions:
I'm not quite sure what you mean by published dependencies?
releases? snapshots?
Anything that a module depends on that is not built by the current
build run. It could be from Tuscany, it could be from another
project; it could be released (preferable) or it could be a snapshot.
Basically, if it's not built by the current run then it needs to have
been published somewhere for the build to work.
What are the criteria for deciding to re-publish a Tuscany jar?
For a release, we need to release it :-)
For a snapshot, any committer can publish one at any time and should
if there is function in there that other modules depend on. For
example, adding a new annotation to spec would be a good reason to
republish the spec snapshot.
Is the online repository going to keep multiple levels of published
dependencies?
It does. Releases generally live forever, snapshots get removed
periodically when they are deemed obsolete. Published snapshots have
a timestamp in the version so it is possible to refer to an older one
if something in the latest causes problems; referring to an obsolete
snapshot is generally problematic as at some point it will go away.
HTH
--
Jeremy
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
