On Jan 9, 2007, at 1:27 AM, Jim Marino wrote:
I know very little about Maven except to follow how it expects
projects to be structured and behave or it will inflict untold
amounts of pain (which is probably fair given its goal of trying to
standardize project build structures) :-) Here is how I picture
things will work:
+1 on the general description (snipped for brevity).
I'm perfectly cool. Thanks for your thoughts, I'm just trying to
understand what you're saying and how this modular build scheme is
going to work, and I'm still looking for answers to some of my
questions :)
- Are we going to update snapshot Jars over time? or use a
<uniqueVersion>true</uniqueVersion> repository config to publish
unique timestamped versions (which, if I understand correctly will
not update over time)? or do we only want to use releases of
pieces of Tuscany to build working assemblies?
By their nature SNAPSHOTS evolve over time. However, "working"
assemblies should generally never reference SNAPSHOT versions as
they change causing instability. Rather, working assemblies should
reference released versions of dependencies.
I would put less emphasis on "working" than on "released." We only
use released pieces to build released assemblies, following the
normal convention of not using SNAPSHOTs in any release.
- If we're going to use timestamped snapshots, does anybody know
how to reference a specific timestamp (I couldn't figure this out
from the Maven docs).
I don't think we need to reference specific timestamps. Either a
module references a released version or SNAPSHOT. If it references
the latter, it is responsible for tracking changes. If the module
developers require ongoing stability, they should not reference
SNAPSHOT.
I don't think you can from the build. You can install that version in
your repo as your SNAPSHOT and reference that - see the
install:install-file goal.
- How do people in the group want to associate a specific SVN
revision with a published snapshot? Jeremy, do you know the
recommended Maven way to do that?
We should never need to do this.
I don't want to. I don't know a way in Maven to do that. It is not
common practice.
--
Jeremy
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
